Organisation, performance
Organisation, performance
Matrix organisations: why good intentions create friction
Matrix organisations: why good intentions create friction
Decision delays, resource conflicts and too many meetings can undermine a matrix organisation. Mapping how work actually flows helps identify what needs to change.
Decision delays, resource conflicts and too many meetings can undermine a matrix organisation. Mapping how work actually flows helps identify what needs to change.
You designed your organisation to be agile. A matrix was meant to break down silos, connect expertise and speed up projects. That was the strategic promise. What do you see today? Execution may be getting caught in lengthy approval processes, unclear responsibilities and decisions that keep coming back to you.
You designed your organisation to be agile. A matrix was meant to break down silos, connect expertise and speed up projects. That was the strategic promise. What do you see today? Execution may be getting caught in lengthy approval processes, unclear responsibilities and decisions that keep coming back to you.
You designed your organisation to be agile. A matrix was meant to break down silos, connect expertise and speed up projects. That was the strategic promise. What do you see today? Execution may be getting caught in lengthy approval processes, unclear responsibilities and decisions that keep coming back to you.
On paper, the equation was compelling: expertise + collaboration across functions = agility.
In practice, hidden operational friction can consume time and capacity. An organisation designed for agility can become difficult to navigate.
When the matrix stops working: early signs
At Spentia, we group operational friction into five broad categories. Three are particularly visible when a matrix organisation struggles:
Conflicting instructions: friction in decision-making. An employee reports to both a functional manager and a project lead. Without alignment, they may be unable to act. Decisions escalate too far or spend too long waiting for approval.
Resource conflicts: organisational friction. A matrix is meant to share expertise. Key specialists can instead become bottlenecks, pulled into several projects without clear priorities.
Delays and meeting overload: friction in information flow. Coordination produces more and more status meetings. Teams can end up spending more time reporting progress than making it.
The problem is the gap between the formal structure and the way work actually flows: how decisions are made, resources allocated and responsibilities exercised.
Listen to teams to map the organisation as it works
Before drawing another organisation chart, understand the structure that already operates in practice.
From a static picture to a view of how work moves
Formal reviews often document the organisation chart, IT architecture and process map. To address the problems in a matrix, leaders also need to see how decisions move through the business. That means asking employees how they make decisions in practice and why they do it that way.
Find the working organisation behind the formal chart
The organisation chart tells us who holds each role. An operational map helps show who influences decisions and keeps work moving. By listening to employees through our conversational AI agent, we can reveal two less visible features:
Informal routes: the shortcuts and alternative channels teams create to get around obstacles and keep work moving.
Informal decision-makers: people who have become critical decision points through expertise or necessity, without a formal management title.
When the matrix stops working: early signs
At Spentia, we group operational friction into five broad categories. Three are particularly visible when a matrix organisation struggles:
Conflicting instructions: friction in decision-making. An employee reports to both a functional manager and a project lead. Without alignment, they may be unable to act. Decisions escalate too far or spend too long waiting for approval.
Resource conflicts: organisational friction. A matrix is meant to share expertise. Key specialists can instead become bottlenecks, pulled into several projects without clear priorities.
Delays and meeting overload: friction in information flow. Coordination produces more and more status meetings. Teams can end up spending more time reporting progress than making it.
The problem is the gap between the formal structure and the way work actually flows: how decisions are made, resources allocated and responsibilities exercised.
Listen to teams to map the organisation as it works
Before drawing another organisation chart, understand the structure that already operates in practice.
From a static picture to a view of how work moves
Formal reviews often document the organisation chart, IT architecture and process map. To address the problems in a matrix, leaders also need to see how decisions move through the business. That means asking employees how they make decisions in practice and why they do it that way.
Find the working organisation behind the formal chart
The organisation chart tells us who holds each role. An operational map helps show who influences decisions and keeps work moving. By listening to employees through our conversational AI agent, we can reveal two less visible features:
Informal routes: the shortcuts and alternative channels teams create to get around obstacles and keep work moving.
Informal decision-makers: people who have become critical decision points through expertise or necessity, without a formal management title.
To address the problems in a matrix organisation, leaders need to see how decisions, information and resources actually move through the business.
To address the problems in a matrix organisation, leaders need to see how decisions, information and resources actually move through the business.
Article
Article
To address the problems in a matrix organisation, leaders need to see how decisions, information and resources actually move through the business.
Article
Include IT in the organisational map
As AI agents become part of workflows, information systems need to be considered part of the organisation itself. We distinguish two roles that are often treated as one:
Tools that carry information, such as messaging systems. When they fail, they disrupt the flow of information.
Systems that make or enforce decisions, such as a workflow that automatically blocks an order. Employee accounts can reveal automated processes with no clear owner or effective human oversight. These processes can create hidden rigidity, leaving people to compensate for it.
Mapping these flows helps align the formal organisation with the way people and technology work together. It also makes the cost of long-tolerated problems visible, so leaders can address them.
Include IT in the organisational map
As AI agents become part of workflows, information systems need to be considered part of the organisation itself. We distinguish two roles that are often treated as one:
Tools that carry information, such as messaging systems. When they fail, they disrupt the flow of information.
Systems that make or enforce decisions, such as a workflow that automatically blocks an order. Employee accounts can reveal automated processes with no clear owner or effective human oversight. These processes can create hidden rigidity, leaving people to compensate for it.
Mapping these flows helps align the formal organisation with the way people and technology work together. It also makes the cost of long-tolerated problems visible, so leaders can address them.
