Matrix management

src: matrixmanagementinstitute.com

Strictly speaking, matrix management, which was "introduced in the 1970s in the context of competition" is the practice of managing individuals with more than one reporting line (in a matrix organization structure), but it is also commonly used to describe managing cross functional, cross business group and other forms of working that cross the traditional vertical business units - often silos - of function and geography.

Video Matrix management

What is it?

It is a type of organizational structure in which people with similar skills are pooled for work assignments, resulting in more than one manager (sometimes referred to as solid line and dotted line reports, in reference to traditional business organization charts).

For example, all engineers may be in one engineering department and report to an engineering manager, but these same engineers may be assigned to different projects and report to a different engineering manager or a project manager while working on that project. Therefore, each engineer may have to work under several managers to get his or her job done.

The matrix for project management

A lot of the early literature on the matrix comes from the field of cross functional project management where matrices are described as strong, medium or weak depending on the level of power of the project manager.

While some form of matrix management has become fairly common in certain industries, particularly among companies that have multiple business units and international operations, upon closer inspection, different organizations implement a matrix structure in different ways to support their needs.

Some organizations fall somewhere between the fully functional and the pure matrix. These organizations are defined in A Guide to the Project Management Body of Knowledge as 'composite'. For example, even a fundamentally functional organization may create a special project team to handle a critical project.

Maps Matrix management

Management advantages and disadvantages

Key advantages that organizations seek when introducing a matrix include:

• To break business information silos - to increase cooperation and communication across the traditional silos and unlock resources and talent that are currently inaccessible to the rest of the organization.
• To deliver work across the business more effectively - to serve global customers, manage supply chains that extend outside the organization, and run integrated business regions, functions and processes.
• To be able to respond more flexibly - to reflect the importance of both the global and the local, the business and the function in the structure, and to respond quickly to changes in markets and priorities.
• To develop broader people capabilities - a matrix helps develop individuals with broader perspectives and skills who can deliver value across the business and manage in a more complex and interconnected environment.

Key disadvantages of matrix organizations include:

• Mid-level management having multiple supervisors can be confusing, in that competing agendas and emphases can pull employees in different directions, which can lower productivity.
• Mid-level management can become frustrated with what appears to be a lack of clarity with priorities.
• Mid-level management can become over-burdened with the diffusion of priorities.
• Supervisory management can find it more difficult to achieve results within their area of expertise with subordinate staff being pulled in different directions.

Advantages and disadvantages in a project management situation

The advantages of a matrix for project management can include:

• Individuals can be chosen according to the needs of the project.
• The use of a project team that is dynamic and able to view problems in a different way as specialists have been brought together in a new environment.
• Project managers are directly responsible for completing the project within a specific deadline and budget.

The disadvantages for project management can include:

• A conflict of loyalty between line managers and project managers over the allocation of resources.
• Projects can be difficult to monitor if teams have a lot of independence.
• Costs can be increased if more managers (i.e. project managers) are created through the use of project teams.
• Organizational efficiencies are very difficult to identify because benchmarking headcount against revenue (or output) is not possible due to the scattered nature of the supporting functions

In popular culture

• An example of matrix-style management can be seen when Peter Gibbons messes up his TPS reports in the movie Office Space.

src: i.ytimg.com

Matrix Management in Practice

Examples of using Matrix Management:

• Digital Equipment Corporation founder Ken Olsen spawned and popularized Matrix Management.
• ABB Group, formed from a 1988 merger and followed by "an ambitious acquisition program." Guiding this was a corporate structure whereby "local operations were organized within the framework of a two-dimensional matrix."

As for why the term is not publicly and formally affiliated with large numbers of corporations, a 2007 book about how "matrix management made a big splash in the 1970s" said that, "for the most part... companies using matrix structures tend to keep quiet about it."

src: 1.bp.blogspot.com

Current Thinking on Matrix Management

In 1990 Christopher A. Bartlett and Sumantra Ghoshal writing on matrix management in the Harvard Business Review, quoted a line manager saying "The challenge is not so much to build a matrix structure as it is to create a matrix in the minds of our managers". Despite this, most academic work has focused on structure, where most practitioners seem to struggle with the skills and behaviours needed to make matrix management a success. Most of the disadvantages are about the way people work together, not the structure.

In "Designing Matrix Organizations That Actually Work" Jay R. Galbraith says "Organization structures do not fail, but management fails at implementing them successfully." He argues that strategy, structure, processes, rewards and people all need to be aligned in a successful matrix implementation.

In "Making the Matrix Work: How Matrix Managers Engage People and Cut through Complexity", Kevan Hall identifies a number of specific matrix management challenges in an environment where accountability without control, and influence without authority, become the normal way of working:

• Context - matrix managers need to make sure that people understand the reasoning behind matrix working and change their behaviours accordingly
• Cooperation - a matrix is intended to improve cooperation across the silos, but it can easily lead to an increase in bureaucracy, more meetings and slower decisions where too many people are involved.
• Control - In a matrix managers are often dependent on strangers where they don't have direct control. There are many factors that can undermine trust such as cross cultural differences and communicating through technology and when trust is undermined managers often increase control. Centralization can make the matrix slow and expensive to run with high levels of escalation. Matrix managers need to directly build trust in distributed and diverse teams and to empower people, even though they may rarely get face-to-face.
• Community - the formal structure becomes less important to getting things done in a matrix so managers need to focus on the "soft structure" of networks, communities, teams and groups that need to be set up and maintained to get things done.

Paula K. Martin, in her books The Matrix Management 2.0 Body of Knowledge and Matrix Management Reinvented - The New Game in Town, introduced the concept of Matrix Management 2.0, an organizational operating System that focuses on running a matrix organization from two dimensions - the horizontal and the vertical.

MM 2.0 is defined in Matrix Management Reinvented - The New Game in Town as "A management operating system specifically designed to make a matrix organization function effectively and efficiently." This new system updates other organizational operating systems such as Vertical Management 1.0 which is a one-dimensional, authority based system invented in the 1950s, and the Matrix Management (1.0) system that is focused on creating a specific matrix structure and authority based relationships with dual-reporting or dotted-line relationships on an Org Chart.

Matrix Management 2.0 is based on a new set of assumptions that change how we look at the organization as a system and matrix leadership.

MM 2.0 Organizational Assumptions, as defined in Matrix Management Reinvented - The New Game in Town:

• An organization is a system; therefore, the parts (areas and people) are interdependent
• The whole is equal to the product of the interaction of the parts
• Optimization of an organization is best accomplished using cooperation
• Team performance is what is important

MM 2.0 Leadership Assumptions, as defined in Matrix Management Reinvented - The New Game in Town:

• Leaders do not need authority in order to lead and be accountable

The MM 2.0 system is broken up into five SPARC Keys that cover the different aspects organizations address when they apply matrix management - Structure, Productivity, Accountability, Relationship Management and Collaborative Leadership. With MM 2.0, each Key follows the premises and principles based upon the new assumptions.

SPARC Keys, as defined in Matrix Management Reinvented - The New Game in Town:

• S Key - Horizontal & vertical structure
• P Key - Productivity of the team & organization
• A Key - Proactive and commitment-focused accountability system
• R Key - Management of non-authority horizontal relationships
• C Key - Collaborative leadership without authority

src: i.ytimg.com

Visual representation

Representing matrix organizations visually has challenged managers ever since the matrix management structure was invented. Most organizations use dotted lines to represent secondary relationships between people, and charting software such as Visio and OrgPlus supports this approach. Until recently, enterprise resource planning (ERP) and human resource management systems (HRMS) software did not support matrix reporting. Late releases of SAP software support matrix reporting, and Oracle eBusiness Suite can also be customized to store matrix information.

src: www.mandsconsulting.com

Clarification

Matrix management should not be confused with "tight matrix". Tight matrix, or co-location, refers to locating offices for a project team in the same room, regardless of management structure.

src: www.asiansalesguru.com

See also

• Organization development
• Colocation Project management

src: i.ytimg.com

References

src: opentextbc.ca

Further reading

• R. J. Shepherd (2007). "Mentoring Soft Boundaries for Management", MIDAS MDF 2007; 2:79-89
• Jay R. Galbraith Designing Matrix Organizations That Actually Work: How IBM, Procter & Gamble and Others Design for Success. (Jossey-Bass Business & Management) ISBN 0470316314 | ISBN 978-0470316313
• "Organization structure as a determinant of organizational performance, uncovering essential facets of organic and mechanistic structure", by Mansoor, Masala, Barbuda, Capusneanu and Lodhi. American Journal of Scientific Research 2012.
• Harvard Business Review: The Importance of Organization

Source of the article : Wikipedia