Skip to content
Playbook
AdvancedManagerHRFounder

Module 2 — Org Design — Span, Layers, Levelling

Span-of-control trade-offs, the cost of layers, levelling discipline, and how to redesign an org without breaking the people in it.

12 min read
On this page
60-Second Summary
  • Module 2 of the Advanced Manager-of-Managers program. Theme: Design an org chart you can defend.
  • Future-state org design with rationale — the real artefact you produce.
  • 4-hour monthly intensive + biweekly coached practice on real work.
  • Reviewed by CHRO, VP/Director, sitting CEO, and OB faculty lenses.

Most directors inherit an org and never redesign it on purpose. The shape of your org silently determines what's possible — how fast decisions get made, who has growth room, where the bottleneck managers are, which functions are over- or under-invested. This module makes org design a deliberate practice, not an accident of historical hiring.

What the evidence says

  • Gallup and Galbraith on span-of-control: optimal span varies by function (engineering 5–8, sales 8–12, ops 10–15) — uniform spans are an anti-pattern.
  • Bain on org layers: each additional layer adds ~10–15% to decision latency. Most orgs have 1–2 too many.
  • Lawler & Worley on levelling: inconsistent levelling is the largest single source of internal pay-equity issues.

Pre-read (90 minutes)

  • Galbraith — Designing Organizations, ch. on structure — 40 min.
  • Stanier — The Coaching Habit + org-shape implications — 20 min.
  • Your company's current org chart, levelling guide, and most recent comp distribution — 30 min.

Monthly intensive (4 hours)

Cohort flow with a senior practitioner coach
  1. 1
    Current-state diagnostic (60 min)
    Each leader brings their org chart. Cohort and coach diagnose: where are the spans wrong, the layers extra, the levels inconsistent, the single points of failure?
  2. 2
    Span and layers (45 min)
    Coach walks through the trade-offs. Why narrow spans create over-management; why wide spans create under-coaching; the layer math.
  3. 3
    Levelling discipline (45 min)
    Walk through your levelling rubric. Audit: are people at the right level? Where is title inflation? Where is under-levelling creating attrition risk?
  4. 4
    Redesign workshop (60 min)
    Each leader proposes a 12-month org evolution. Cohort and coach stress-test.
  5. 5
    Wrap (30 min)
    One redesign decision each leader will socialise this month.

The artefact you produce

Future-state org design with rationale

A target org chart for 12 months out with: span rationale per manager, layer count rationale, levelling audit, identified single points of failure, and the sequence of moves to get there. Reviewed with your manager and HRBP.

Tools at this layer

LayerExamples (2026)Use
Org modellingChartHop, OrgVitals, Agentnoon, PingboardModel scenarios; calculate spans and costs
LevellingProgression.fyi, internal levelling rubric, Lattice GrowAudit and enforce consistency
Workforce planningVisier, Anaplan, internal headcount modelTie the design to budget and growth plans
Copy-paste AI prompt

Here's my current org chart [structure, roles, levels, tenure]. Help me: (1) identify span-of-control outliers and recommend changes, (2) detect possible levelling inconsistencies, (3) propose a 12-month evolution that closes single points of failure and creates growth room for at least 2 high-potential ICs.

Between-session homework

  • Span audit completed; outliers documented with rationale.
  • Levelling audit completed; 2–3 corrections proposed.
  • Future-state org chart submitted to coach.
  • First redesign move socialised with your manager.

Success signal

By end of this module, you can defend the shape of your org — every span, every layer, every level — with a written rationale. You have a 12-month evolution plan that ties to strategy and budget, not just to who you happened to hire.

Reviewer notes

CHRO (20+ yrs)

The directors who can talk org design with me are the ones I push for VP roles. The ones who treat their org as fixed are the ones I worry about.

VP / Director (15+ yrs, 3+ scaled orgs)

Redesign your org once a year, on purpose. Not because anything's broken — because by next year, the org you have today will be wrong for the work you'll be doing.

Sitting CEO

I want my directors to bring me org proposals before I notice the problem. That's how I know they're thinking at the right layer.

OB / HR Professor (25+ yrs)

Galbraith's Star Model remains the cleanest framework: strategy → structure → processes → rewards → people. The common failure is changing strategy without changing the other four. Org design is how you keep them aligned.

Written by Pawan Joshi.Sources cited inline.
First published 23 Jun 2026See site changelog →