Introduction to Matrix Management

A leader is responsible to empower his people and get the best out of them. Yet an organisational structure can either help or hamper performance. Worst, it can make or break success.

Looking at the fast-changing world of the global economy, whatsoever slows up and obstructs decision-making is a challenge. Hierarchical management is rather unattractive and functional silos are unlikable. Instead, employees desire to create teams equipped with flexibility, cooperation and coordination.

Recognising that companies have both vertical and horizontal chains of command, the matrix model is created. The concept of this principle lies in the ability to manage the collaboration of people across various functions and achieve strategic objectives through key projects.

Consider this scenario:

Ian is a sales executive of a company. His role is to sell a new product under the supervision of a product manager. The manager is expert about the product and she is accountable to coordinate the people across the organisation, making sure the product is achieved.

Moreover, Ian also reports to the sales manager who oversees his overall performance, monitors his pay and benefits and guides his personal development.

Complicated it may seem but this set-up is common to companies that seek to maximise the effect of expert product managers, without compromising the function of the staffing overhead in control of the organisation. This is a successful approach to management known as Matrix Management.

Matrix Management Defined

Matrix management is a type of organisational management wherein employees of similar skills are shared for work assignments. Simply stated, it is a structure in which the workforce reports to multiple managers of different roles.

For example, a team of engineers work under the supervision of their department head, which is the engineering manager. However, the same people from the engineering department may be assigned to other projects where they report to the project manager. Thus, while working on a designated project, each engineer has to work under various managers to accomplish the job.

Historical Background

Although some critics say that matrix management was first adopted in the Second World War, its origins can be traced more reliably to the US space programme of the 1960’s when President Kennedy has drawn his vision of putting a man on the moon. In order to accomplish the objective, NASA revolutionised its approach on the project leading to the consequent birth of ?matrix organisation?. This strategic method facilitated the energy, creativity and decision-making to triumph the grand vision.

In the 1970’s, matrix organisation received huge attention as the only new form of organisation in the twentieth century. In fact it was applied by Digital Equipment, Xerox, and Citibank. Despite its initial success, the enthusiasm of corporations with regards to matrix organisation declined in the 1980’s, largely because it was complex.

Furthermore, the drive for motivating people to work creatively and flexibly has only strengthened. And by the 1990’s, the evolution of matrix management geared towards creation and empowerment of virtual teams that focused on customer service and speedy delivery.

Although all forms of matrix has loopholes and flaws, research says that until today, matrix management is still the leading approach used by companies to achieve organisational goals.

Check our similar posts

Transformation to a process based organisation

Today’s global marketplace rewards nimble organisations that learn and reinvent themselves faster than their competition. Employees at all levels of these organisations see themselves as members of teams responsible for specific business processes, with performance measures tied to the success of the enterprise. As team members, they are “owners” of the process (or processes) to which they are assigned. They are responsible for both the day to day functioning of their process(s), and also for continuously seeking sustainable process improvements.

Transforming a traditionally designed “top down control” enterprise to a process-based organisation built around empowered teams actively engaged in business process re-engineering (BPR) has proven more difficult than many corporate leaders have expected. Poorly planned transformation efforts have resulted in both serious impacts to the bottom line, and even more serious damage to the organisation’s fabric of trust and confidence in leadership.

Tomislav Hernaus, in a publication titled “Generic Process Transformation Model: Transition to Process-based Organisation” has presented an overview of existing approaches to organisational transformation. From the sources reviewed, Heraus has synthesised a set of steps that collectively represent a framework for planning a successful organisational change effort. Key elements identified by Hernaus include:

Strategic Analysis:

The essential first step in any transformation effort must be development of a clear and practical vision of a future organisation that will be able to profitably compete under anticipated market conditions. That vision must be expected to flex and adjust as understanding of future market conditions change, but it must always be stated in terms that all organisational members can understand.

Identifying Core Business Processes:

With the strategic vision for the organisation in mind, the next step is to define the core business processes necessary for the future organisation to function. These processes may exist across the legacy organisation’s organisational structures.

Designing around Core Processes:

The next step is development of a schematic representation of the “end state” company, organised around the Core Business Processes defined in the previous step.

Transitional Organisational Forms/ Developing Support Systems:

In his transformation model, Hernaus recognises that information management systems designed for the legacy organisation may not be able to meet the needs of the process management teams in the new organisation. Interim management structures (that can function with currently available IT system outputs) may be required to allow IT professionals time to redesign the organisation’s information management system to be flexible enough to meet changing team needs.

Creating Awareness, Understanding, and Acceptance of the Process-based Organisation:

Starting immediately after the completion of the Strategic Analysis process described above, management must devote sufficient resources to assure that all organisation members, especially key managers, have a full understanding of how a process-based organisation functions. In addition, data based process management skills need to be provided to future process team members. It is not enough to schedule communication and training activities, and check them off the list as they are completed. It is critical that management set behavioural criteria for communication and training efforts that allow objective evaluation of the results of these efforts. Management must commit to continuing essential communication and training efforts until success criteria are achieved. During this effort, it may be determined that some members of the organisation are unlikely to ever accept the new roles they will be required to assume in a process-based organization. Replacement of these individuals should be seen as both an organisational necessity and a kindness to the employees affected.

Implementation of Process Teams:

After the completion of required training AND the completion of required IT system changes, process teams can be formally rolled out in a planned sequence. Providing new teams with part time support by qualified facilitators during the firsts weeks after start-up can pay valuable long term dividends.

Team Skill Development and Continuous Process Improvement:

Providing resources for on-going skill development and for providing timely and meaningful recognition of process team successes are two keys for success in a process-based organisation. Qualified individuals with responsibility for providing training and recognition must be clearly identified and provided with sufficient budgetary resources.

The Hernaus model for transformation to a process based organisation is both well thought out and clear. His paper provides an ample resource of references for further study.

Contact Us

(+353)(0)1-443-3807 – IRL
(+44)(0)20-7193-9751 – UK

What is work force management?

For organisations to ensure they provide the right service. In order to do they need to assign the right employees with the right skills to the right job at the right time to meet demand.

Workforce Management Background

Workforce management (WFM) is a strategy used by companies to increase their efficiency and performance. It entails all activities aimed at maintaining a steady output, such as human resource management, forecasting, field service management, budgeting, scheduling, performance and training management, analytics, recruitment and data collection.

Workforce management utilizes a unique set of performance enhancing tools and software to bolster corporate management, workers, and other categories of managers and supervisors in the manufacturing team, distribution, transportation, and retail operators. This is sometimes called HRM systems, or part of ERP systems, or workforce asset management.

Unlike the conventional outlay that only needed staff scheduling to improve time management, workforce management is now all-inclusive and demand-oriented to optimize staff scheduling. Apart from focusing on demand-orientation and optimization, workforce management also incorporates:

Estimating the workload and resource utilisation
Job scheduling
Management of working times and accounts
Monitoring the process of workforce management

Each task should be clearly defined and performed efficiently based on set engineering standards and methods of optimizing each task as much as possible. Out of this framework and demand based forecasts, workers are scheduled and given tasks, performance measured, give feedback, and incentives computed and paid.

Workforce management is an entire scheme aimed at building the capacity of workers, increase productivity and client relations, and where possible reduce labour costs.

What is Mobile Workforce Management (MWM)

Mobile workforce management (MWM) is a software-based service used to oversee employees outside of the institution?s premises; MWM sometimes refers to the field teams. Mobile workforce management encompasses all activities done to monitor and schedule the field workforce.

The entire process includes procurement, management and using mobile devices, applications and computer software. Related support services like tracking, logging, dispatch, productivity management, and other types of communication are also to make it efficient.

Companies do not have the same needs and MWM firms need to fine-tune their software and devices to sufficiently bridge this gap. Some providers are suited only to a specific type of company because of specialization, like managing the electric grid. This experience makes the MWM company suited to provide applications that are relevant to the company for them to continue operating smoothly and efficiently.

With the increase in mobile devices, applications, secured wireless networks and virtual desktop, there comes a stream of opportunities for small and medium-sized businesses (SMB) and other ventures. Nevertheless, a mobile workforce needs better controls, security and support, as well as a functioning mobile workforce management strategy.

MMS (managed mobility services) is often used interchangeably with MWM, but they should not be confused. MWM is related to software and applications used by mobile and computer devices to manage on-field work while MMS focuses on enterprises, and is like a way of keeping in touch with the company, other employees, and linking the mobile while at work to servers and the database.

Benefits of Mobile Workforce Management

MWM allows the utilization of technology to drive productivity. Here are the top five advantages of MWM..

Customer focused. The customer is the backbone of any business. The team needs to keep in touch with up-to-date information about every interaction. In the end, better client relation makes sure that the customer is always happy.
Information has the power to build or destroy. A cloud-based system is easier to manage and can help with collection of data which is used to make business decisions. This can help cut costs, increase the workforce support, and identify areas where polishing needs to be done.
Improved efficiency. Mobile workforce management is majorly used in taskforce allocation. If the company adopts a cloud-based work force management system, allocation is done automatically saving a lot of time.
Increased revenue. Each business seeks to maximize the profit. With cloud-based mobile workforce management some operations like task management, data analysis, customer communication, reporting, and performance monitoring can be automated. This reduces the costs incurred for multiple applications and saves time.
Ease of communication. Communication is vital. Constant communication with customers drives sales rates and everyone loves that. Quick communication will help customers solve their problems faster and get instant feedback.

Additional WFM benefits

Other WFM benefits are:

Operations are made efficient as all complex processes are automated.
Employers learn more about worker engagement, productivity and attendance, allowing them to modify training, coaching and processes aimed at streamlining performance.
Automation and easy manipulation of data to improve HR, productivity and slash administrative costs.
It increases employee productivity by reducing absenteeism and late arrivals.
Boosts the morale of employees by encouraging transparency and facilitating manager-employee communication.
WFM analyzes market and schedule requirements to pick the right employee with the best set of skills for a certain task.

Companies which embrace workforce management and mobile workforce management have a higher operational efficiency. They have lower operational costs and limit manual work as much as possible

A Small External Enterprise Development Team is Cheaper than Your Own

Time is money in the application development business. We have to get to market sooner so someone else does not gazump us, and pip us at the post. We increase the likelihood of this with every delay. Moreover, the longer your in-house team takes to get you through the swamp, the higher the project cost to you.

Of course, in theory this should not be the case. Why bring in a team from outside, and pay more to support their corporate structure? Even going for a contract micro team ought not to make financial sense, because we have to fund their mark-up and their profit taking. Our common sense tells us that this is crazy. But, hold that thought for a minute. What would you say if a small external enterprise development team was actually cheaper? To achieve that, they would have to work faster too.

The costs of an Enterprise Internal Development Team

Even if you were able to keep your own team fully occupied ? which is unlikely in the long term ? having your own digital talent pool works out expensive when you factor in the total cost. Your difficulties begin with the hiring process, especially if you do not fully understand the project topic, and have to subcontract the hiring task.

If you decide to attempt this yourself, your learning curve could push out the project completion date. Whichever way you decide to go, you are up for paying advertising, orientation training, technical upskilling, travel expenses, and salaries all of which are going to rob your time. Moreover, a wrong recruitment decision would cost three times the new employee?s annual salary, and there is no sign of that changing.

But that is not all, not all by far. If want your in-house team to keep their work files in the office, then you are going to have to buy them laptops, plus extra screens so they can keep track of what they are doing. Those laptops are going to need desks, and those employees, chairs to sit in. Plus, you are going to need expensive workspace with good security for your team?s base.

If we really wanted to lay it on, we would add software / cloud costs, telephony, internet access, and ongoing technical training to the growing pile. We did a quick scan on PayScale. The median salary of a computer programmer in Ireland is ?38,000 per year and that is just the beginning. If you need a program manager for your computer software, their salary will be almost double that at ?65,000 annually.

Advantages of R&D outsourcing

The case for a small externally sourced enterprise development team revolves around the opportunity cost ? or loss to put in bluntly ? of hiring your own specialist staff for projects. If you own a smaller business with up to 100 people, you are going to have to find work for idle digital fingers, after you roll out your in-house enterprise project. If you do not, you head down the road towards owning a dysfunctional team lacking a core, shared objective to drive them forward.

Compared to this potential extravagance, hiring a small external enterprise development team on an as-needed basis makes far more sense. Using a good service provider as a ?convenience store? drives enterprise development costs down through the floor, relative to having your own permanent team. Moreover, the major savings that arise are in your hands and free to deploy as opportunities arise. A successful business is quick and nimble, with cash flow on tap for R & D.