spans-and-layers

name	spans-and-layers
description	Use when auditing or designing manager spans and organizational layers — covers diagnostics, healthy ranges, and reorg patterns.

Spans and Layers

Why It Matters

Spans (number of direct reports) and layers (depth from CEO to most-junior employee) are two of the most measurable structural variables. They surface bottlenecks, decision speed problems, and over- or under-management that other diagnostics miss.

Span of Control Heuristics

Manager type	Healthy span
First-line manager of ICs	6–12
Manager of managers	5–9
Senior leaders / Directors	5–8
VPs	5–8
CEO	7–10
Founder	Audit if > 9

Wider spans demand:

• More autonomous teams
• Better goal-setting and OKRs
• Stronger managers
• Less hands-on supervision

Narrower spans mean:

• More management overhead per IC
• Higher manager headcount
• Risk of micromanagement

Span Patterns to Watch

• Founder hoarding directs: founders typically over-collect; comfort with high-context, low-trust delegation. Audit any span > 10 reporting to founder.
• VP of Engineering with 18 directs: typically a missing director layer
• Manager with 2–3 directs: under-utilized; team probably should consolidate
• Executive with 4 directs but 10 dotted-line: matrix structure that needs explicit norms

Layers Heuristics

Headcount	Layers
< 100	3–5
100–500	4–6
500–2000	5–7
2000+	7–9

More layers correlate with:

• Slower decisions
• More political work
• More "translation" overhead between top and bottom
• More misalignment between strategy and execution

The "Extra Layer" Pattern

Senior leader inserts a director / VP between themselves and existing managers — often because they don't trust the existing managers.

Costs:

• The layer rarely comes out
• Existing managers feel demoted
• Decisions slow
• Layer adds little real value

Better: address the trust issue (replace, coach, or restructure) rather than papering over with structure.

Layers vs. Reporting Distance

Two common questions:

• "How many layers are between CEO and the most junior employee?" (layer count)
• "How many people does information go through?" (reporting distance)

These usually match but not always. Document both.

Span and Layer Audit

Every quarter:

• Map current org chart (HRIS data)
• Count spans for every manager
• Count layers from CEO to deepest IC
• Compare to peer-stage benchmarks
• Flag anomalies (very wide / narrow spans; deep layers)

Reorg Patterns

When span/layer audit reveals problems:

Span Compression

Reduce a span by:

• Promoting someone to manage a sub-team
• Creating a new manager role
• Splitting the function

Layer Removal

Remove a layer by:

• Promoting team leads to direct reports of senior leader
• Eliminating director role and absorbing scope upward
• Restructuring teams to eliminate the level

Layer Addition

Add a layer when:

• Span has expanded beyond healthy range
• Senior leader is the bottleneck on tactical decisions
• Mentorship and development of mid-level leaders is suffering

Common Failures

• Span too wide (>15) without compensating autonomy
• Span too narrow (<3) without specialized rationale
• Layer added to manage a single person
• Layer added without removing one
• Founder maintains 18 directs and complains about "fires everywhere"
• Director title without director-scope work
• Manager-of-one (single direct, no other team relevance)

Communication During Reorgs

• All-hands message before individual conversations leak
• Manager talking points
• Individual employee letters where reporting changes
• FAQ
• Comp / title implications addressed clearly
• 30/60/90 day check-ins post-reorg

Cross-References

• org-design-principles skill
• org-designer agent
• workforce-planning skill
• change-management skill

Key References

• Industry practitioner work; CEO 7–10 directs is common-knowledge convention rather than research
• Holacracy / Sociocracy variants for reference (specialized)
• Lencioni, P. (2012). The Advantage.