Span and Layers Analysis

Span and layers analysis is a review of how an organization's management structure is built. It counts each manager's direct reports (span) and the number of management levels between the top executive and frontline staff (layers), then uses both figures to spot where structure may be slowing decisions or adding cost.

Why does span and layers analysis matter for enterprise HR?

Span and layers analysis matters because an org chart that grew role by role, without a plan, often ends up with inconsistent management structures that nobody has actually measured. Leaders typically run the analysis when decisions feel slow, management costs look high relative to headcount, or a reorganization or acquisition has combined teams built on different structures.

The analysis is a diagnostic, not a cost-cutting formula. Gallup's 2025 workplace data found that the average span of control had risen to 12.1 direct reports, up from 10.9 in 2024.

The right number for any one team depends on the complexity of the work and how much coaching the team needs, not a single industry benchmark. Broader organizational-design research from groups such as McKinsey and the World Economic Forum consistently links inconsistent management layering, not headcount alone, to slower decision-making in large organizations, which is why the analysis looks at structure rather than just cost.

Across the teams we work with, the trigger for running this analysis is rarely a single bad number. It is usually a pattern: a reorg that never got cleaned up, a few departments that grew faster than their management layer, or a sense that approvals take longer than they should without anyone being able to say exactly why. Across the teams we have seen run this analysis, naming the real question up front is what keeps the project from turning into an open-ended audit nobody finishes.

What are the core metrics in a span and layers analysis?

A span and layers analysis is built from five core metrics, each describing a different part of the management structure.

Looking at the average alone can hide real problems. An average span of seven can sit on top of some managers with one direct report and others with twenty, so the distribution matters as much as the mean.

How do you run a span and layers analysis?

Running a span and layers analysis starts with a clear question, not a spreadsheet. The method below works for most mid-market and enterprise organizations.

1. Define the question: Decide what you are trying to learn, such as whether decisions are slow, whether management cost is too high, or whether a merger left duplicate layers.
2. Pull the data: Export role, manager and grade fields from the HRIS, and separate true people managers from senior individual contributors who do not manage anyone.
3. Clean the data first: Incorrect manager fields and inflated titles are common and will distort every metric downstream, so fix these before calculating anything.
4. Calculate spans and layers: Work out each metric above for every manager, then chart the results by function and level. A heat map makes outliers easy to spot.
5. Interview the outliers: Talk to managers at the extremes, both very wide and very narrow spans, to learn why their teams are structured the way they are before changing anything.

Pro tip: Review the span distribution, not just the average. A single outlier manager can make a healthy-looking average hide a real coaching or workload problem.

How does span and layers analysis compare to span of control?

Span and layers analysis and span of control overlap but answer different questions: span of control looks at one manager's direct reports, while span and layers analysis looks at spans and management levels together, across the whole organization.

For the concept of spans and layers itself, including how they trade off against each other, see spans and layers. For the direct-reports metric on its own, see span of control.

What are best practices for span and layers analysis?

• Run it on a schedule, not just in a crisis: Annual reviews, plus a check after any reorganization or acquisition, catch drift before it compounds.
• Pilot changes in one area first: Test a change to spans or layers in a single function before rolling it out everywhere.
• Match spans to work complexity: Routine, well-documented work can support a wider span than complex or coaching-heavy work.
• Watch remote and hybrid teams separately: Distributed teams often need narrower spans than co-located ones to get the same level of support.
• Pair structure change with how work gets done: Removing a layer without changing how decisions are made usually shifts workload rather than improving speed.

Getting spans and layers right only pays off if the people in those roles can actually do the job the new structure expects of them. A manager who is asked to take on a wider span after a delayering exercise needs real delegation and coaching skill, not just a bigger team on paper.

Key takeaway: Skills-based hiring and assessment, such as evaluating a candidate's management or technical ability before a promotion or a new hire, helps confirm that a manager can handle a wider span or a flatter structure before the org chart changes around them. talent benchmarking

Frequently asked questions