A matrix structure gives people two reporting lines — typically a functional manager who owns their craft and career, and a project or product lead who owns their work.
It solves a real problem. It creates a set of quieter ones, and organisations adopt it without pricing those, because the problem it solves is visible and the ones it creates are not.
For a practical reference on handling multiple clients, Monitask provides learn more.
What it genuinely solves
Specialists spread across products. A designer, an analyst or a lawyer who works on several things needs a functional home for standards and development, and a work home for priorities. Without a matrix, they end up with neither or with one that is a fiction.
Craft standards across an organisation. If every product team hires and manages its own specialists, practice diverges and nobody notices until it is expensive.
Scarce capability allocation. Three people with a rare skill serving eight teams need someone deciding where they go. A functional manager can do that; eight product leads competing cannot.
Career paths for specialists who would otherwise be one-of-one in a product team with nobody to develop them.
These are real, and small organisations that grow into specialisation hit them all at once. See team size.
What it reliably costs
Two managers means twice the coordination. For the individual, twice the meetings, twice the priorities, and twice the possibility that the two disagree.
The person absorbs the conflict. When functional standards and delivery deadlines pull against each other, the disagreement lands on the person least able to resolve it. They are then made responsible for a negotiation between two people senior to them.
Decision rights become genuinely ambiguous, and this is the central failure. Who decides priority? Who decides technical approach? Who decides whether the work is good enough to ship? A matrix without answers to these is a permanent argument. See decision rights.
Performance assessment is diluted. Two managers, each with partial visibility, produces reviews that are either an average of two incomplete pictures or dominated by whichever manager writes more.
Meeting load multiplies. Two sets of team meetings, two sets of one-to-ones, two planning cycles.
Slower decisions, because two people have to agree where one used to decide.
The rules that make one work
A matrix that works is not a matrix with better people. It is a matrix where a small number of things were decided explicitly and written down.
Say which line is primary. Most functioning matrices are not balanced — one line is dominant and the other is consulted. Pretending they are equal produces deadlock. Decide, and say so.
Split the decision rights, explicitly:
- Priority and sequencing — usually the delivery line
- Technical approach and quality standards — usually the functional line
- Allocation, who works on what — usually the functional line
- Whether it ships — must be one of them, named
- Hiring and firing — usually the functional line
- Day-to-day direction — usually the delivery line
The specific allocation matters less than that it exists in writing.
Name the escalation path. When the two disagree, who resolves it, and how fast. Without this, disagreements resolve by attrition, which means the more persistent manager wins regardless of the merits.
One performance conversation, with input from both. Not two reviews. One owner of the assessment, with structured input.
Limit the number of lines to two. Three-way matrices exist and do not function.
Cap how many things one person is matrixed into. Someone serving five teams has five sets of meetings and no time to do the work.
When not to use one
When the work is not genuinely shared. If a specialist works predominantly on one product, put them in that team. A matrix for the sake of consistency is pure overhead.
When the organisation is too small. Below a certain size, the coordination cost exceeds the standards benefit. Two designers do not need a design function with a manager.
When decision rights cannot be agreed. If the two managers will not agree who decides what, the matrix will not fix that — it will formalise it and hand it to their reports.
When it is being used to avoid a reorganisation. A matrix laid over a structure that no longer fits is a way of not making a decision. See reorganisations.
The diagnostic
Ask someone in the matrix three questions:
Who decides what you work on this week? Who decides whether your work is good enough? If those two disagree, what happens?
If the answers are confident and consistent across several people, the matrix is working. If they hesitate, or if you get different answers from different people, the structure is not the problem — the undefined decision rights are, and they will not be fixed by moving anyone.
For broader public guidance and background, consult the OECD.