Matrix, functional, divisional:
choosing a structure.
The four common organisational structures are functional, divisional, matrix and flat. Each optimises for something different and pays for it elsewhere: functional buys depth at the cost of coordination, divisional buys focus at the cost of duplication, matrix buys both at the cost of clarity, and flat buys speed at the cost of scale.
The four compared
| Structure | Optimises for | Pays in | Suits |
|---|---|---|---|
| Functional | Depth of expertise, efficiency | Slow cross-functional work | Single product or market, stable environment |
| Divisional | Focus on a product, market or region | Duplicated functions | Several distinct businesses under one roof |
| Matrix | Both depth and focus at once | Ambiguity over who decides | Complex projects needing scarce specialists |
| Flat | Speed and autonomy | Breaks down with scale | Small organisations, early-stage companies |
Functional
People grouped by discipline: engineering together, finance together, sales together. The default shape for most organisations under a few hundred people, and the one they tend to return to.
It concentrates expertise, so specialists learn from each other and standards rise. It uses people efficiently, because one team serves the whole company. Its weakness appears whenever work has to cross a boundary: a product launch that needs engineering, marketing and legal in sequence will move at the speed of the slowest handover, and nobody below the chief executive owns the whole of it.
- Works when the company sells one thing into one market and the environment is stable.
- Strains when products multiply, or when speed across functions matters more than depth within them.
Divisional
People grouped around a product, market, customer segment or region, with each division carrying most of the functions it needs.
It puts accountability in one place. A division head owns a result and has the people to deliver it, which shortens decisions and makes performance legible. The price is duplication: several finance teams, several marketing teams, and specialists spread thinly enough that none of them has a peer group.
- Works when the businesses are genuinely distinct, with different customers, economics or regulation.
- Strains when divisions begin competing for the same customer, or when the duplicated cost grows faster than the focus is worth.
Matrix
People report along two axes at once, typically to a functional manager for craft and development, and to a product or regional leader for the work itself.
It is an attempt to have both depth and focus, and it can genuinely deliver both. It is also the structure that breaks down most often, for a single reason: the two axes are given equal authority and left to negotiate. Where that happens, every contested decision travels upward to the one person both report to.
- Name which axis wins by default on each type of decision, in writing.
- Give one axis the performance review, so an employee has one answer to the question of who they work for.
- Expect it to require active management for as long as it exists. A matrix left alone decays into a functional structure with confusing titles.
The honest position on matrix structures is that they work where the organisation is prepared to invest continuously in making them work. Most are adopted for the benefits and abandoned when the maintenance cost becomes apparent, which is a decision better taken at the start.
Flat
Few management layers, sometimes none at all, with decisions pushed down to the people doing the work.
Fast, cheap in overhead, and attractive to capable people who want autonomy. It holds well up to roughly fifty people, beyond which the informal coordination that replaced management begins to strain. What usually appears next is an unofficial hierarchy based on tenure and proximity to the founder, which carries all the costs of structure and none of the clarity.
- Works when the organisation is small, the people are senior, and the work is self-directing.
- Strains when headcount passes the point where everyone knows what everyone else is doing, usually somewhere between forty and eighty people.
Most real organisations are hybrids
Pure structures are rarer in practice than in textbooks. What most companies operate is a deliberate mixture, and naming the mixture honestly is more useful than claiming one of the four labels.
- Functional core, divisional front end. Shared engineering and finance, with customer-facing teams organised by segment. Common in software and professional services.
- Divisional with shared services. Autonomous businesses drawing on central legal, finance and technology. It recovers some of the duplicated cost while leaving accountability with the division.
- Matrix in one place only. A matrix applied to a single programme or a scarce capability, with the rest of the company left functional. Considerably easier to operate than a whole-organisation matrix.
- Flat within layers. Broad spans and few levels at the top, with conventional management where volume and consistency matter.
The value of naming the hybrid is that it makes the trade explicit. A company describing itself as flat while operating four management layers has a communication problem sitting on top of a structural one.
Signals that a structure has stopped fitting
Structures age. A shape that suited a business at sixty people frequently obstructs it at two hundred, and the symptoms arrive well before anyone proposes a redesign.
- Routine decisions reaching the chief executive. Authority sits above the information, so the people who know have to ask the people who may decide.
- Coordination roles multiplying. Programme managers and business partners appearing to bridge gaps between groups is an organisation paying to compensate for its own shape.
- The same customer served by three teams. Usually divisional boundaries drawn around internal history rather than around how the market buys.
- Capable people leaving laterally. Where strong performers move to competitors at the same level, scope rather than pay is the common cause, and scope is a structural question.
One caution against acting too quickly. Each redesign costs two or three quarters of reduced output while people learn the new pattern. Organisations that restructure every year pay that cost continuously and collect the benefit rarely, which is its own kind of structural problem.
Choosing between them
Structure follows from three questions about the business rather than from preference.
- How different are the businesses? Genuinely distinct customers, economics or regulation argue for divisional. One product into one market argues for functional.
- Where does speed matter most? Speed within a discipline favours functional. Speed to a customer outcome favours divisional or matrix.
- How scarce are the specialists? Where a capability is scarce enough that it has to be shared across several businesses, matrix becomes the honest answer rather than the ambitious one.
One further consideration outranks all three: which structure the leadership team can actually operate. A theoretically superior design run by people who dislike it performs worse than a simpler one they believe in.
Worth settling at the same time is how the structure will be explained. Every shape creates losers, and people read a reorganisation for what it says about their own standing long before they read it for what it does to the business. A design announced with a clear account of the problem it solves survives contact with that reading. One announced as a chart invites everyone to supply their own explanation, and the explanations people invent are reliably worse than the truth.
Frequently asked questions
Functional, divisional, matrix and flat are the four in common use. Most real organisations are hybrids: a functional core with divisional front-ends, or a matrix confined to one part of the business. Pure forms are rarer than the textbooks suggest.
One where people report along two axes at once, usually a function and a product or region. It aims to combine functional depth with product focus. It succeeds where the organisation states which axis wins on which decisions, and struggles where both are given equal authority.
Because the two reporting lines are given equal weight and left to resolve conflicts themselves. Every contested decision then escalates to the one person both report to, which is the bottleneck the matrix was supposed to remove. Naming a default winner per decision type fixes most of it.
Functional groups people by discipline; divisional groups them around a product, market or region. Functional buys depth and efficiency at the cost of slow cross-functional work. Divisional buys accountability and focus at the cost of duplicated functions.
Commonly between forty and eighty people. The limit arrives when informal coordination gives way, because people lose track of what everyone else is doing. What replaces it is usually an unofficial hierarchy, which is worse than an explicit one.
The one that matches how distinct the businesses are and where speed matters most. A fourth consideration outranks the theory: whether the leadership team can operate it. A better design run reluctantly performs worse than a simpler one run with conviction.
Rarely, and in response to a strategic change rather than on a cycle. Each redesign costs two or three quarters of reduced output while people learn the new pattern. Organisations that restructure annually pay that cost continuously and collect the benefit rarely.
