Most leaders did not choose to work in a matrix organisation. They arrived there gradually, through a series of structural changes that seemed logical at the time. Reporting lines were shared. Functional teams were given cross-business responsibilities. Projects required cooperation across multiple departments. Decision-making moved away from individual leaders and towards collective governance.

At some point, the organisation stopped feeling like a hierarchy and started feeling like something considerably more complex.

Welcome to the defining structural challenge of modern organisational life.

Matrix organisations are now the dominant model for large and mid-sized enterprises across the world. McKinsey research suggests that most large organisations operate with some form of matrix structure, and that the trend towards greater organisational complexity is accelerating rather than slowing. Deloitte’s Global Human Capital Trends research has consistently found that organisations are moving away from traditional hierarchies towards more networked, team-based, and cross-functional models of working.

Yet despite how widespread matrix structures have become, many of the leaders working within them remain unclear about what a matrix organisation actually is, why their organisation adopted one, and what it means for how they need to lead.

This article addresses those questions. It provides the context and background for a series of articles exploring how leaders can succeed in matrix environments. Understanding the origins and logic of the matrix is essential preparation for understanding the leadership challenges it creates.

What is a matrix organisation?

A matrix organisation is a structure in which employees and leaders have more than one reporting relationship. Rather than reporting to a single manager within a single function, individuals typically report to both a functional leader (responsible for their professional discipline, such as Finance, Technology, or Marketing) and a business or project leader (responsible for a specific product, geography, customer, or initiative).

This dual reporting structure is the defining characteristic of the matrix. It creates a grid-like pattern of relationships rather than the simple vertical lines of a traditional hierarchy. In practice, matrix structures vary considerably in their form and complexity.

Some organisations operate a relatively simple functional matrix, in which functional leaders retain primary authority and project or business leaders play a coordinating role. Others operate a balanced matrix, in which authority is more genuinely shared between functional and business dimensions. Others adopt a strong project matrix, in which project leaders hold primary accountability and functional managers play a supporting role.

Beyond these classical forms, many contemporary organisations operate structures that are considerably more complex. Leaders may have responsibilities that span multiple geographies, business units, functions, and customer segments simultaneously. Galbraith (2009), whose work on organisational design remains foundational to understanding matrix structures, describes these more complex forms as multi-dimensional matrices, in which several different organisational dimensions intersect within a single structure.

What all of these forms share is the replacement of simple, single-point accountability with shared, distributed responsibility. This is both the defining feature of the matrix and the source of its most significant leadership challenges.

Why did organisations adopt the matrix?

The matrix did not emerge by accident. It was a deliberate organisational response to a set of pressures that traditional hierarchies were struggling to manage effectively.

To understand why organisations adopted matrix structures, it is necessary to understand what those hierarchies were designed to do, and where they began to fail.

Traditional hierarchical organisations were built for stability and efficiency. Clear reporting lines established unambiguous authority. Functional departments developed deep specialisation. Decision-making flowed through vertical chains of command. These structures were well-suited to environments where tasks were relatively predictable, competition was relatively stable, and coordination demands were relatively modest.

From the mid-twentieth century onwards, those conditions began to change.

The pressure of complexity

As organisations grew in size and scope, the demands they faced became increasingly complex. Products required input from multiple technical disciplines. Customers expected solutions that combined expertise from several functional areas. Geographical expansion created the need for local responsiveness alongside global consistency. Regulatory environments became more demanding and varied.

Hierarchical structures, with their emphasis on vertical coordination and functional specialisation, were poorly equipped to manage this growing complexity. As Lawrence and Lorsch (1967) demonstrated in their foundational research on organisational design, the increasing differentiation of functions created an equally urgent need for integration across those functions. Traditional hierarchies struggled to provide that integration without creating bureaucratic overhead that slowed decision-making and frustrated both leaders and customers.

The matrix offered a solution. By creating explicit horizontal relationships alongside vertical reporting lines, it attempted to build integration into the structure of the organisation itself rather than relying on coordination mechanisms that sat above or outside the day-to-day work.

The pressure of globalisation

The acceleration of globalisation from the 1980s onwards created a further set of structural challenges that traditional hierarchies found difficult to address.

Organisations expanding into international markets faced a fundamental tension: how to achieve the efficiencies of global scale while remaining responsive to local market conditions, customer needs, and regulatory requirements. A purely centralised structure optimised for global efficiency at the expense of local relevance. A purely decentralised structure optimised for local responsiveness at the expense of global coordination and cost efficiency.

Bartlett and Ghoshal (1989), in their influential work on the transnational organisation, argued that neither a purely global nor a purely local model was sufficient for competing in complex international markets. Organisations needed to develop what they described as a transnational capability: the ability to achieve global integration, local responsiveness, and worldwide learning simultaneously. The matrix structure, in various forms, became the primary vehicle through which organisations attempted to develop this capability.

The pressure of speed and innovation

More recently, a further set of pressures has driven continued adoption and evolution of matrix structures.

In environments characterised by rapid technological change, shortening product cycles, and intensifying competition, the ability to innovate quickly has become a critical source of competitive advantage. Innovation rarely emerges from a single function working in isolation. It typically requires the integration of diverse perspectives, capabilities, and knowledge from across the organisation.

McKinsey research into agile organisations has highlighted how leading companies have moved towards more flexible, team-based structures that can rapidly assemble and deploy cross-functional capability in response to emerging opportunities and challenges. Deloitte’s research on the future of work has similarly identified the shift towards networked, project-based models of organisation as one of the most significant structural trends of the past decade.

The matrix, in its various contemporary forms, provides the structural foundation for this kind of cross-functional collaboration. It creates the connections between functions, disciplines, and business units that enable organisations to bring together diverse expertise quickly and effectively.

What does a matrix structure mean in practice?

Understanding the logic of the matrix is one thing. Understanding what it feels like to work within one is quite another.

For most leaders, the experience of working in a matrix is characterised by a particular set of recurring challenges that have no simple equivalent in a traditional hierarchy.

Accountability without authority is perhaps the most common. Leaders are held responsible for outcomes that depend on people, teams, and resources they do not control. A project leader may be accountable for delivering a major initiative while having no formal authority over the functional teams whose cooperation is essential to its success.

Competing priorities create a further layer of complexity. In a matrix, individuals often receive direction from multiple leaders with different objectives, different timescales, and different definitions of success. Navigating these competing demands requires continuous negotiation and judgement rather than simple compliance with a single set of instructions.

Decision-making becomes slower and more complicated. When accountability is shared, decisions require broader consultation and alignment. Governance mechanisms such as steering committees, decision rights frameworks, and escalation procedures become necessary but can also create bureaucratic friction that frustrates leaders and slows progress.

Conflict becomes endemic rather than exceptional. When functions, business units, and geographies pursue their own objectives within a shared structure, tension is inevitable. The matrix does not eliminate conflict; it reorganises it, distributing it throughout the structure rather than concentrating it at the top.

HBR research into matrix organisations has consistently found that these structural tensions are not the result of poor leadership or organisational dysfunction. They are the predictable consequences of a structure that deliberately creates shared accountability, distributed authority, and cross-functional interdependence. The tensions are features, not bugs, of the matrix design.

The challenge, therefore, is not to eliminate the tensions that matrix structures create. It is to develop the leadership capabilities needed to navigate them effectively.

The leadership gap

This is where the most significant problem becomes apparent.

Most leaders working in matrix organisations were developed in a different kind of environment. They built their careers in structures where authority was relatively clear, reporting relationships were relatively simple, and progress depended primarily on technical expertise and the ability to direct the work of people who reported to them.

The skills that enabled success in those environments, expertise, decisiveness, efficient execution, and clear direction-setting, remain valuable in a matrix. But they are no longer sufficient.

Matrix leadership requires something additional. It requires the ability to create progress without relying on authority. It requires the ability to build influence across functions and boundaries. It requires the ability to mobilise people who have a choice about whether and how they contribute. It requires the ability to navigate competing priorities and ambiguous governance without becoming paralysed or resorting to escalation.

Research consistently suggests that organisations are not adequately preparing leaders for this shift. Deloitte has identified the development of leaders who can work effectively across boundaries as one of the most urgent capability gaps in global organisations. HBR has highlighted the persistent failure of leadership development programmes to equip leaders with the influence, network-building, and collaborative skills that matrix environments demand.

The consequence is a significant and costly mismatch. Organisations adopt matrix structures because they need greater cross-functional integration, faster innovation, and more flexible deployment of capability. They then discover that their leaders lack the skills to make those structures work effectively. The result is frustration, conflict, slow decision-making, and underperformance, not because the matrix is the wrong structure, but because the leadership capability required to operate within it has not been developed.

This is the problem this series of articles is designed to address.

A different kind of leadership

Succeeding in a matrix organisation requires a fundamental shift in how leaders think about their role.

In a hierarchy, leadership is primarily a function of position. Authority flows from the organisation chart. Progress depends on the effective exercise of that authority within a defined area of responsibility.

In a matrix, leadership is primarily a function of contribution. Progress depends less on the authority you possess and more on your ability to create direction, alignment, and commitment across boundaries that your formal role does not cross.

This shift is more significant than it might initially appear. It means that many of the instinctive responses that leaders bring to matrix challenges, seeking more authority, demanding clearer governance, escalating conflict upwards, are not simply ineffective. They can actively make the situation worse by undermining the collaborative relationships and distributed ownership that matrix structures require.

The most effective leaders in matrix organisations have learned to approach these challenges differently. Rather than asking how they can acquire more authority, they ask how they can create more commitment. Rather than managing through formal reporting lines, they lead through relationships, credibility, and shared purpose. Rather than optimising their own function or department, they take responsibility for the health of the wider system.

These are learnable capabilities. They are not simply personality traits or natural talents, although certain personal qualities can support their development. They are skills and practices that can be developed through deliberate attention and consistent application.

In the next article in this series, we explore a framework for developing exactly these capabilities: Influence, Networks, Convening, and Stewardship. Together, these four capabilities provide a practical foundation for leading effectively in a matrix organisation, not by acquiring more authority, but by becoming the kind of leader that others choose to follow.

Wrapping up

Matrix organisations have become the dominant structural model for complex, global, and fast-moving enterprises. They emerged in response to genuine and significant pressures: the need for cross-functional integration, global scale alongside local responsiveness, and the ability to innovate and adapt quickly in competitive environments.

These structures create real and predictable challenges for leaders. Accountability without authority. Competing priorities. Complex governance. Endemic conflict. These are not signs of organisational dysfunction. They are the inevitable consequences of structures built on shared accountability and distributed decision-making.

The critical issue is that most leaders have not been adequately prepared for these challenges. The skills and instincts developed in hierarchical environments, while still valuable, are insufficient in a matrix. A different set of capabilities is required.

Understanding what the matrix is, why it exists, and what it demands of leaders is the essential starting point. It creates the context within which the more practical questions of matrix leadership become meaningful.

How do you build influence without authority? How do you develop networks that span organisational boundaries? How do you bring people together around a shared commitment when they have no obligation to prioritise your agenda? How do you act as a steward of the wider organisation rather than simply a representative of your own function? These are the questions this series is designed to answer,

Three questions for reflection

How would you describe the matrix structure in your own organisation? Where does shared accountability create the most tension?

Which of the leadership challenges described in this article, accountability without authority, competing priorities, complex governance, or endemic conflict, has the greatest impact on your effectiveness?

In your current role, to what extent do you rely on formal authority to create progress? What would change if that authority were reduced or removed?

Sources

Bartlett, C.A. and Ghoshal, S. (1989) Managing across borders: The transnational solution. Boston, MA: Harvard Business School Press.

Deloitte (2016) Global human capital trends 2016: The new organisation — different by design. London: Deloitte University Press. Available at: https://www2.deloitte.com/content/dam/Deloitte/global/Documents/HumanCapital/gx-dup-global-human-capital-trends-2016.pdf

Deloitte (2023) Global human capital trends 2023: New fundamentals for a boundaryless world. London: Deloitte Insights. Available at: https://www.deloitte.com/us/en/insights/topics/talent/human-capital-trends/2023.html (Accessed: 5 June 2026).

Galbraith, J.R. (2009) Designing matrix organisations that actually work: How IBM, Procter & Gamble, and others design for success. San Francisco: Jossey-Bass.

Kesler, G. and Kates, A. (2011) Leading organization design: How to make organization design decisions to drive the results you want. San Francisco: John Wiley & Sons.

Lawrence, P.R. and Lorsch, J.W. (1967) Organisation and environment: Managing differentiation and integration. Boston, MA: Harvard Business School Press.

McKinsey & Company (2018) The five trademarks of agile organisations. McKinsey Quarterly. Available at: https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/the-five-trademarks-of-agile-organizations

McKinsey & Company (2021) Organizing for the future: Nine keys to becoming a future-ready company. McKinsey Quarterly. Available at: https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/organizing-for-the-future-nine-keys-to-becoming-a-future-ready-company

Worley, C.G. and Lawler, E.E. (2006) ‘Designing organisations that are built to change’, MIT Sloan Management Review, 48(1), pp. 19–23. Available at: https://sloanreview.mit.edu/article/designing-organizations-that-are-built-to-change/