How To Count Layers
A layer is a management level with distinct decision authority. Counting sounds simple but gets complicated when the org has player-coaches, team leads who "aren't really managers," and "Head of" titles that may or may not carry management responsibility.
Counting rules
- Count from the CEO to the front-line IC. The CEO is layer 1. A VP reporting to the CEO is layer 2. A Director reporting to the VP is layer 3. And so on.
- Only count a layer if it carries real management authority. If a "team lead" manages daily work, runs 1:1s, and makes hiring/firing recommendations, they're a management layer. If a "team lead" is a senior IC with a title and no direct reports, they're not.
- Count the deepest path. Different branches of the org may have different depth. Engineering might have 5 layers while Finance has 3. The organization's depth is the maximum.
- Don't count dotted lines as layers. A dotted-line to a project lead doesn't add a layer unless the project lead has management authority over the person.
Quick benchmark: most organizations with 50-200 people should have 3-4 layers. Most with 200-500 should have 4-5. If you have significantly more, investigate. Each extra layer costs about 10-15% in management overhead and slows decision speed.
The Core Tradeoff
Layers and spans are directly linked. For a given organization size, removing a layer means widening spans, and adding a layer means narrowing spans. You cannot change one without affecting the other. See Span of Control for the math.
| Fewer layers (flatter) | More layers (deeper) |
|---|---|
| Decisions are faster because fewer people filter information between the front line and leadership. | Managers have narrower spans and can provide closer coaching, tighter quality control, and more hands-on support. |
| Less management overhead: fewer manager salaries, fewer manager meetings, fewer 1:1 chains. | More career steps between IC and senior leadership, which can improve retention for people who want management progression. |
| Information reaches leadership with fewer hops, reducing distortion. | More capacity to handle complexity: each manager handles a smaller piece, reducing cognitive load at each level. |
| Managers have wider spans, which may mean less time for each report and less detailed oversight. | Each layer adds a communication hop. By the time a message from the front line reaches the C-suite (and vice versa), key nuance may be lost. |
The Title Inflation Problem
Some organizations have many layers not because the work requires it, but because titles proliferated. IC > Senior > Staff > Principal > Lead > Manager > Senior Manager > Director > Senior Director > VP > SVP. That's 11 "levels" but only 3-4 of them carry meaningful differences in decision authority.
Title inflation creates the illusion of organizational depth. The chart looks deep, but most of the layers are title tiers, not real management levels. This matters because:
- People expect the responsibilities of the title. A "Director" expects to direct something. If the Director has no reports and no distinct decision authority from the Senior Manager below them, the title creates mismatched expectations.
- External benchmarking breaks. When everyone is a VP, salary benchmarks, hiring expectations, and partner-facing introductions lose meaning.
- Real management layers get lost. When the chart has 7 "levels" but only 4 actual management layers, it's hard to reason about decision speed, information flow, and spans.
Fix: distinguish between career levels and management layers. You can have a Staff Engineer at career level 6 who is not a management layer. The career ladder and the org chart are two different structures; conflating them creates false depth.
Layer Compression: When And How
Layer compression (sometimes called "delayering") means removing a management level. It's one of the most impactful structural changes you can make, and one of the most disruptive if done poorly.
When to consider it
- A management layer exists but doesn't make distinct decisions. The Director approves everything the Manager recommends without adding judgment. The layer is a pass-through.
- Information travels too many hops. Front-line signals (customer feedback, operational problems) take days to reach the people who can act on them because they pass through 5 management levels.
- Managers at one layer have only 1-2 direct reports. This often happens when a "Head of" is created for a team of 3 people. The layer adds cost and slows decisions without providing meaningful management value.
- The company has more layers than peers of similar size and complexity. A 150-person company with 6 layers is unusual and worth examining.
How to do it without creating chaos
- Identify which layer to remove. It's usually the layer where managers have the fewest reports and the least distinct decision authority.
- Check span impact. When you remove a layer, the reports roll up one level. Will the remaining manager's span be sustainable? Use the span review worksheet.
- Move decision authority explicitly. If the removed layer was making real decisions (even if they were just rubber-stamping), those decisions need to be explicitly assigned to either the layer above or the layer below.
- Handle the people. The managers whose layer is removed need a clear path: become an IC at a senior level, move to a different management role, or leave with dignity. Do not pretend this isn't a significant career change.
Worked Example: 150 People, 6 Layers To 4
A 150-person company has 6 layers in its Engineering org: CTO > VP Engineering > 2 Engineering Directors > 6 Engineering Managers > 10 Team Leads > ~80 Engineers.
The symptoms: product decisions take weeks to flow from the CTO to the teams and back. The Engineering Directors mostly relay information between the VP and the Managers without adding distinct decisions. Team Leads function as senior engineers, not managers: they don't do 1:1s, they don't make staffing decisions, and they don't own team outcomes.
Layer 1 (CTO): Sets technical strategy. Necessary.
Layer 2 (VP Engineering): Manages Engineering Directors, owns hiring and org-level planning. Necessary unless the CTO can manage Directors directly (possible if there are only 2).
Layer 3 (Directors): Each manages 3 Engineering Managers. They attend planning meetings and relay information. They don't make architecture decisions (CTO does that) and they don't do performance reviews (Managers do that). This layer is a pass-through.
Layer 4 (Managers): Each manages a team of 8-12 engineers. They run 1:1s, own hiring, and make daily prioritization decisions. Necessary.
Layer 5 (Team Leads): Senior engineers with a title. They don't manage people. Not a real management layer.
Layer 6 (Engineers): Do the work.
Remove the Director layer. Engineering Managers report directly to the VP Engineering (or the CTO, if the VP role is also eliminated). The VP's span goes from 2 to 6. That's within range for a manager-of-managers role.
Reclassify Team Leads. They're senior engineers, not managers. Remove them from the management chart. Their title can stay for career ladder purposes, but they're not a layer in the org structure.
Result: 4 layers: CTO > VP Engineering > 6 Engineering Managers > Engineers. Decision speed improves because there are 2 fewer hops. The VP has a wider span but is managing experienced managers who need direction-setting, not daily oversight.
What happens to the Directors: one becomes a Staff Engineer (strong technical contributor who prefers IC work). One becomes the VP Engineering (was the stronger manager of the two, gets promoted into the role). This is handled in 1:1s before any announcement.
Sources And Further Reading
- Henry Mintzberg, Structure in Fives: Designing Effective Organizations.
- Jay R. Galbraith, Designing Organizations.
- Elliott Jaques, Requisite Organization.
- Matthew Skelton and Manuel Pais, Team Topologies.
Continue Reading
When layers and spans are balanced, the next step is planning structural changes deliberately.
Next guideReorg Planning Guide
A calmer way to move from current structure to future-state scenario, with timeline, communication plan, and 90-day follow-up.