Spans and Layers: Getting Organisation Shape Right

No company decides to become slow. It happens one reasonable decision at a time: a strong performer gets two reports as a retention gesture; a stretched leader inserts a deputy; a new function arrives with a head, a lead, and an associate before it has work for one. Each decision defensible; the sum, an organisation where a customer's problem passes through six approvals and a frontline insight dies three layers below the people who could act on it.

Spans and layers — how many people each manager leads, and how many levels sit between CEO and front line — are the geometry of speed. Reviewing them is the cheapest organisational tune-up there is.

Why layers are so expensive

Each management layer adds:

• Latency. Decisions and information cross every level, losing time and fidelity at each hop. The game of telephone is structural, not anecdotal.
• Cost. Layers are populated by your most expensive people, plus the meetings they generate.
• Diluted accountability. When five levels touch every outcome, no level owns it.
• Talent frustration. Capable people two layers from real decisions feel it — and your engagement verbatims will say so.

A scale-up under 500 people rarely needs more than four or five layers, founder to front line. Most that look have six or seven, discovered rather than designed.

Why spans fail in both directions

• Too narrow (1–3 reports): the manager either micromanages or is a layer pretending to be a job. Narrow spans usually mark title-inflation debt or unfinished delegation.
• Too wide (12+ for judgement-heavy work): one-on-ones vanish, feedback dies, and development stops. Wide spans work for homogeneous, process-driven work with strong systems; they break where coaching is the manager's core output.

There is no universal right number — span capacity depends on work similarity, team maturity, process strength, and geography. The design question is always "what does this manager's work require?", not "what is the benchmark?"

Run the diagnostic

A spans-and-layers review is straightforward:

• Map the real structure from HRMS data — every reporting line, every level. (The chart in the deck always flatters; use the data.)
• Compute spans per manager and layer counts per path from CEO to front line.
• Flag anomalies: spans under four, spans over twelve in complex work, paths with more layers than peers, "manager of one" chains.
• For each flag, ask the honest question: what does this layer or role decide that the levels adjacent to it cannot?

The last question is where the value lives. Layers that exist to "coordinate" or "review" — without owning distinct decisions — are candidates for removal.

Fix it without breaking people

Delayering done crudely is a layoff with a consultant's vocabulary. Done well:

• Redesign the structure first, then cast people into it — some narrow-span managers return to expert individual-contributor roles, which must be made genuinely respectable in pay and status.
• Widen spans only while investing in the managers absorbing them: delegation skills, operating rhythms, prioritisation. This is precisely where manager development and structure work must travel together — wider spans with unsupported managers just converts a structure problem into a burnout problem.
• Sequence transparently. People can accept structural logic; they cannot accept stealth demotions.

Keep the shape from regressing

Layers grow back. Prevent it with standing rules: minimum spans for creating a new manager role, a named approver for any new layer, and a yearly shape review alongside budget planning. If your organisation feels slower than its size justifies, a spans-and-layers diagnostic takes two to three weeks — contact us to scope one, or see how it fits within a broader fractional HR engagement.