Recent from talks
Nothing was collected or created yet.
Matrix management
View on Wikipedia
Matrix management is an organizational structure in which some individuals report to more than one supervisor or leader—relationships described as solid line or dotted line reporting, also understood in context of vertical, horizontal & diagonal communication in organisation for keeping the best output of product or services. More broadly, it may also describe the management of cross-functional, cross-business groups and other work models that do not maintain strict vertical business units or silos grouped by function and geography.
Matrix management, developed in U.S. aerospace in the 1950s, achieved wider adoption in the 1970s.[1]
Overview
[edit]There are different types of matrix management, including strong, weak, and balanced,[2] and there are hybrids between functional grouping and divisional or product structuring. [3]
For example, by having staff in an engineering group who have marketing skills and who report to both the engineering and the marketing hierarchy, an engineering-oriented company produced "many ground-breaking computer systems."[4] This is an example of cross-functional matrix management, and is not the same as when, in the 1980s, a department acquired PCs and hired programmers.[5][6]
Often senior employees, these employees are part of a product-oriented project manager's team but also report to another boss in a functional department. A senior employee who may have worked previously for an advertising agency, designing ads for computers, may now be part of a marketing department at a computer company, but be working with an engineering group. This is often called cross-functional matrix management.[citation needed]
Companies that have multiple business units and international operations, upon closer inspection may apply matrix structures in different ways.[7]
Even function-based organizations may apply this arrangement for limited projects.[8]
In practice
[edit]Examples of using matrix management:
- Digital Equipment Corporation founder Ken Olsen spawned and popularized Matrix Management.[9][10][11]
- ABB, 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."[12]
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."[1]
Scaling back
[edit]Two decades after pioneering in matrix management, Digital Equipment Corporation backed out, citing it as a source of "sapped energy and efficiency from product-development efforts."[13]
Regarding earlier years, when it worked, The New York Times praised "consensus building that may have once helped Digital become the nation's second-largest computer maker" (after IBM). The same article noted the cutting of 20,000 jobs, and that what worked with the PC market didn't work as well with larger systems, such as DEC Alpha.
This does not take away from what, a week earlier, the same author wrote: "It fostered internal competition and resulted in many ground-breaking computer systems like the PDP and VAX lines."[4]
Matrix management 2.0
[edit]In 2004, despite matrix management having become disfavored,[13] Nokia made an attempt at using a form of it, later described as "matrix management 2.0".[14][15] The focus is intended to be "leading without authority" so that "no one functional leader is in charge."
Academic overview
[edit]
- Christopher A. Bartlett and Sumantra Ghoshal, writing on matrix management in Harvard Business Review,[16] 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".
- "Designing Matrix Organizations That Actually Work" Jay R. Galbraith[17] 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.
- Making the Matrix Work: How Matrix Managers Engage People and Cut through Complexity, Kevan Hall[18] identifies a number of specific matrix management challenges in an environment where accountability without control, and influence without authority, become the norm:
- Context – ensure that people understand the reasoning behind the matrix
- Cooperation – improve cooperation across the silos, but avoid bureaucracy and having too many people involved
- Control – avoid centralization, build trust, empower people
- Community – focus on the "soft structure" of networks, communities, teams and groups
See also
[edit]References
[edit]- ^ a b Marvin R. Gottlieb (2007). The Matrix Organization Reloaded: Adventures in Team and Project Management. ISBN 978-0275991333.
- ^ "Types of Matrix Organizational Structure".
- ^ "What are the 4 Types of Organizational Structures?".
- ^ a b Glenn Rifkin (July 15, 1994). "COMPANY NEWS: Big Charge To Be Taken By Digital". The New York Times.
- ^ "CIO". CIO. April 1991. p. 66.
.. the explosion of stand-alone PCs in the '80s .. ensuing rise of departmental computing
- ^ John Markoff (November 15, 2005). "Microsoft Enters the High-Performance Computing Fray". The New York Times.
- ^ Neff, Kristin M.; White, Ralph D. "REDEFINING PROJECT MANAGEMENT IN A MATRIX ENVIRONMENT" (PDF).
- ^ Seet, Daniel. "Power: The Functional Manager’s Meat and Project Manager’s Poison?", PM Hut, February 6, 2009. Retrieved on March 2, 2010.
- ^ "early use of matrix management"Edgar H. Schein (2010). DEC Is Dead, Long Live DEC: The Lasting Legacy of Digital Equipment Corporation. ReadHowYouWant.com. ISBN 978-1458777676.
- ^ gives MM components without using the term itself.Win Hindle, DEC senior VP (2008). "Ken's Leadership".
- ^ Glenn Rifkin (1988). The Ultimate Entrepreneur: The Story of Ken Olsen and Digital Equipment Corporation. Contemporary Books. ISBN 0809245590.
- ^ Kettinger, William J.; Marchand, Donald A. (February 2002). "Leveraging Information Locally and Globally: The Right Mix of Flexibility and Standardization" (PDF).
- ^ a b Glenn Rifkin (July 20, 1994). "BUSINESS TECHNOLOGY: Digital Shows Doctrine the Door". The New York Times.
- ^ "The Demise of Nokia—A Cautionary Tale of Restructuring Gone Wrong".
- ^ Martin, Paula K. (June 2013). 9780988334205: Matrix Management 2.0(TM) Body of Knowledge. International Matrix Management Institute. ISBN 978-0988334205.
- ^ Barlett CA; Ghoshal S (1990). "Matrix management: not a structure, a frame of mind". Harvard Business Review. 68 (4): 138–145.
- ^ Galbraith, J.R. (1971). "Matrix Organization Designs: How to combine functional and project forms". In: Business Horizons, February 1971, 29-40.
- ^ Kevan Hall. Making the Matrix Work: How Matrix Managers Engage People and Cut Through Complexity. ISBN 1904838421. | ISBN 978-1904838425
External links
[edit]- Understanding Matrix Management, John Wiley, CBS MoneyWatch
- Matrix Management Reinvented – The New Game in Town, Paula K. Martin, 2015, International Matrix Management Institute, ISBN 0988334216
- "Successful Organizational Structure", Tara Duggan, Houston Chronicle
Matrix management
View on GrokipediaFundamentals
Definition
Matrix management is an organizational structure characterized by employees having dual or multiple reporting lines, typically integrating functional hierarchies—such as departments focused on expertise like engineering or marketing—with project- or product-based teams to promote both specialization and adaptability.[1] This approach creates overlapping chains of command, allowing resources to be allocated dynamically across initiatives while maintaining departmental accountability.[2] Central to matrix management are horizontal and vertical reporting relationships, where vertical lines enforce functional oversight and horizontal lines facilitate project coordination. Authority is shared between functional managers, who prioritize technical proficiency and long-term development, and project managers, who focus on timely delivery and cross-team integration, often requiring negotiation to resolve conflicts. Resource allocation occurs through collaborative agreements, enabling employees to contribute to multiple teams without rigid silos.[1][2] In contrast to traditional hierarchical structures, which rely on a single chain of command for clear but potentially rigid decision-making, matrix management introduces dual accountability to enhance responsiveness and multidisciplinary collaboration. Unlike flat structures, which minimize layers of management to encourage broad autonomy and direct communication with minimal formal reporting, the matrix preserves functional depth while adding project-oriented dimensions for balanced oversight.[3][2] A basic representation of matrix management appears as a grid diagram, with functional managers listed along one axis (e.g., vertically for departments like finance, HR, and operations) and project or product managers along the other (e.g., horizontally for initiatives like product launches or client projects), positioning employees at the intersections to denote their simultaneous reporting obligations.[3]Historical Development
Matrix management originated in the post-World War II era, driven by increasing complexity in R&D-intensive sectors such as aerospace and defense, where traditional hierarchical structures struggled to coordinate large-scale, innovative projects requiring specialized expertise across functions.[4] The need for integrated systems engineering emerged from challenges like the integration issues in the B-47 bomber program in the early 1950s, prompting the U.S. Air Force to establish joint project offices and formalize matrix-like approaches by the mid-1950s.[4] In the 1960s, matrix management took shape in the U.S. space program, particularly NASA's Apollo initiative, which demanded flexible resource allocation and dual reporting lines to integrate functional specialists with project goals amid unprecedented technical demands.[5] By 1967, contractors like North American Aviation implemented systematic matrix structures for Apollo, peaking with over 390,000 industry personnel coordinated through functional and program matrices to achieve the moon landing.[5] This period marked a shift from purely functional organizations to hybrid forms, as outlined in evolutionary models progressing through project, product/matrix, and full matrix stages to handle growing environmental uncertainty.[6] The 1970s saw widespread adoption in multinational corporations facing global pressures, with companies like Philips implementing matrix structures to balance product divisions and geographic operations.[7] Philips, for instance, introduced dual reporting for managers in the 1970s to manage diverse electronics lines across regions, though it encountered coordination inefficiencies.[7] Management consultants Stanley M. Davis and Paul R. Lawrence popularized the concept through their 1977 book Matrix, analyzing its forms and applications in decentralized firms, and a 1978 Harvard Business Review article highlighting its challenges and benefits.[8][7] By the 1980s, amid accelerating globalization, matrix management expanded beyond aerospace to industries like information technology, consulting, and manufacturing, enabling firms to navigate multiple dimensions such as products, regions, and functions simultaneously.[7] This diffusion addressed the bureaucratic limitations of earlier divisional models, fostering responsiveness in dynamic markets, though it often amplified decision-making delays.[7]Key Characteristics
Structure and Reporting Lines
Matrix management structures vary in the distribution of authority between functional and project (or product) managers, typically categorized as weak, balanced, or strong matrices. In a weak matrix, functional managers hold primary authority, with project managers serving in a coordinative role that has limited decision-making power and often part-time involvement. Employees report primarily to their functional manager for day-to-day supervision, while project-related coordination occurs through informal or dotted-line interactions.[1] A balanced matrix aims for equal authority between functional and project managers, though this equilibrium is challenging to maintain in practice; here, project managers may lead dedicated teams but still rely on functional input for resource commitments. Reporting lines involve shared oversight, with employees navigating dual influences without a clear dominant hierarchy.[1] In a strong matrix, project managers wield greater authority, often with dedicated project offices that include specialized roles like systems engineering; functional managers focus on technical expertise and long-term development, while project delivery drives priorities. Employees report more directly to project managers for task execution, with functional lines emphasizing skill enhancement.[1]| Type | Authority Balance | Reporting Lines | Key Features |
|---|---|---|---|
| Weak Matrix | Functional-dominant | Primary to functional; dotted to project | Project coordinator role; minimal project office |
| Balanced Matrix | Equal (theoretical) | Dual solid lines to both | Negotiated resource use; shared decision-making |
| Strong Matrix | Project-dominant | Primary to project; solid to functional | Dedicated project teams; enhanced project control |