Two numbers explain most of the cost
Structural cost is explained essentially by two variables: the number of layers between the CEO and the frontline employee, and the average number of direct reports per manager. When the span of control is narrow, layers appear to accommodate all the managers; when there are many layers, information filters and decisions slow down. Both effects are paid for in payroll and in speed.
The right span isn't universal
There's no single right number. A standardized operations area can sustain wide spans; a team of specialized projects cannot. The practical rule is to differentiate by the nature of the work and then eliminate exceptions that have no justification.
- Repetitive, supervisable work: wide spans
- Expert, project-based work: narrow spans, but fewer layers
- Managers with only one direct report: a sign of an unnecessary layer
- Layers created to solve a compensation problem, not a management one
The one-off cost against the recurring saving
Every reorganization has a transition cost: severance, learning curve, temporary loss of productivity. The economic case must show both sides and the point at which the recurring saving offsets it. Without that calculation, the discussion becomes political.
Key takeaways
- Measure layers and spans before proposing any org chart.
- Differentiate the target span by the nature of the work, not by hierarchical level.
- Approve the redesign with transition cost and recurring saving on the table.
NS frameworks and reference sources
- Proprietary NS framework · S2S·NS — methodological notes from the Organizational Design practice
- NS project base: anonymized cases by sector and geography
- Open market evidence and academic literature, recalibrated with client data
- Bain & Company — Spans and Layers benchmarks
- McKinsey — Organizational Health Index
- Deloitte — Global Human Capital Trends
This article develops proprietary NS Business Strategy frameworks, drawing on our project base and on public industry literature and studies cited above. Figures are reference ranges; each project is measured against the client's actual data.