# Spans and Layers: How Many Management Levels a Company Needs

Author: Marin Niehues, Niehues Consulting · Published: 2024-10-10 · Updated: 2026-11-16 · Organizational Design
Source: https://www.niehuesconsulting.com/blog/spans-and-layers-management-levels/

A company needs as many management levels as headcount and span of control yield arithmetically, so with 1,000 employees and a span of ten, three layers below the top. Every additional layer must prove a decision function of its own. Spans and layers describes this relationship through two measures: the number of direct reports per manager and the number of levels between executive leadership and operational work.

This article explains the connection, sets out the factors that shape span of control and shows an approach for deriving the right structure from data. It includes a savings calculation for removing layers.

**Every layer must make a decision that would not be made better above or below it. A layer without this function lengthens the path without return.**

## How are span of control and layers related?

Span of control and the number of layers are linked by headcount: for a given workforce, a larger average span leads to fewer layers. Span of control states how many employees report directly to a manager. The number of layers states how many levels lie between top leadership and operational work.

A worked example shows the order of magnitude. A company of 1,000 employees has, at an average span of ten, three layers below the top on paper, including the operational layer. At a span of five there are five. The two additional layers mean additional management posts and additional alignment meetings, and every further station lengthens the path of information and decisions. Span therefore determines the length of decision paths and is one of the strongest levers of delivery capability.

**Layers below the top on paper, including the operational layer**
Headcount | Span 5 | Span 8 | Span 10
100 employees | 3 | 3 | 2
1,000 employees | 5 | 4 | 3
10,000 employees | 6 | 5 | 4
50,000 employees | 7 | 6 | 5

The table follows a simple rule: the number of layers equals the logarithm of headcount to the base of the span, rounded up. It assumes even spans across all areas. In real organizations spans vary considerably, and that variation shows which areas deserve closer examination. If a unit's actual number of layers exceeds the table value by more than one, that is a clear signal for an analysis.

*Interactive tool: management layers calculator, derives the number of management layers and managers from headcount and average span of control. Available at https://www.niehuesconsulting.com/blog/spans-and-layers-management-levels/*

## Five factors determine the right span

The right span differs by area, because the nature of the work differs. The organization theorist V. A. Graicunas showed as early as 1933 why span has limits: the number of possible relationships a manager coordinates grows far faster than the number of direct reports, reaching 18 on paper with three direct reports and 100 with five. Five factors have proved useful as a test grid.

1. Nature of the work: standardized, recurring activities allow wide spans because the need for alignment per person is low. Complex tasks with frequent exceptions call for closer management.
2. Team maturity: experienced specialists with clear objectives need less direction than a newly formed team.
3. Clarity of roles and decision rights: where responsibilities are unambiguous, the number of queries to the manager falls.
4. The manager's own specialist tasks: every share of specialist work ties up time that management needs.
5. Distribution of the team: spatial and temporal distribution raises the effort per person.

## How do you recognize too many management layers?

You recognize too many management layers when decisions escalate more than once and return changed, while many managers have only two or three direct reports. Further signs are information that reaches the front line late or filtered, and the same work being reviewed at several levels. Managers with very small spans fill the rest of their time with operational work or with reporting to the next level.

An analysis makes this pattern measurable. Reporting lines from the HR system provide the distribution of spans per area and the number of layers per unit. Together with the decision time of selected processes and the share of managers with very small spans, the result is a picture that makes areas comparable. Where the picture stands out, a substantive review of the layer's function follows. It establishes whether a layer makes decisions, condenses information or merely passes it on, and provides the basis for deciding whether to keep, merge or remove it.

## What is delayering, and what are the disadvantages of flat hierarchies?

Delayering is the deliberate removal of management layers, with the remaining managers taking on larger spans. The aim is shorter decision paths and lower structural cost. A panel study of large US companies documents the trend: the number of managers reporting directly to the chief executive rose on average from 4.4 to 8.2 between 1986 and 1998. Flat hierarchies have four disadvantages that a target design accounts for from the outset.

First, the load on managers rises, and without clear roles the quality of feedback and development falls. Second, career steps disappear, so the company needs specialist career paths as a second route for development. Third, without defined decision rights, informal hierarchies form that are harder to steer than formal ones. Fourth, coordination shifts from the manager to the teams, which costs time as long as interfaces are unregulated.

**Flat and deep structures compared**
Criterion | Flat structure | Deep structure | With Niehues Consulting
Decision path | short, few stations | long, several approvals | Decision rights defined and measurable for each layer
Management effort per person | high, requires clear roles | low, close supervision | Span corridor per area derived from nature of work and maturity
Structural cost | low | higher due to management posts | Cost and delivery impact in one business case
Risk | overload of management | delay and loss of information | Rollout with enablement of managers

## How much does removing management layers save?

The savings from removing management layers can be calculated in advance, and they are larger the smaller today's spans are. The number of management posts is roughly the headcount divided by the span minus one. With 1,000 employees and a span of five, that is around 250 management posts, and at a span of ten around 110.

**Calculating the savings**
- Step 1: determine today's management posts from the reporting lines, or roughly as headcount divided by (span minus one).
- Step 2: calculate the management posts in the target design using the new span corridor per area.
- Step 3: multiply the difference by the share of working time these posts currently spend on management.
- Step 4: value the result at fully loaded cost per post and deduct the one-off cost of the change, for instance for enablement and transitions.

The third step prevents the most common overestimate. Many managers with small spans mostly do specialist work, which continues after the change. Only the management share of the posts is therefore a reliable basis. The second return lies in shorter decision paths and belongs in the business case as a metric, measured as decision time before and after the change.

## An approach in four steps

A sound decision on spans and layers follows four steps, which delivery management uses to steer structural change.

1. Baseline: reporting lines and spans, layers and the management share of roles, plus the duration of typical decisions.
2. Function of each layer: each layer receives a list of the decisions that rest with it alone. Any layer without such a list comes under review.
3. Target design: a span corridor per area, justified by the five factors.
4. Implementation: adjusted roles and new decision paths, along with enablement of managers for larger teams, steered through metrics such as lead time and decision time.

**Test questions for each management layer**
- Which decisions are made at this layer, and by whom otherwise not?
- Which information is condensed or translated here, and what happens if the layer is removed?
- How many reports does the manager have, and what share of their time does management take?

Removing layers changes tasks and career paths and shifts weight onto the remaining managers.

## Niehues Consulting as a partner for structure and delivery capability

[Niehues Consulting](/) is a Düsseldorf consultancy for AI management and organization design from the delivery perspective. Founder Marin Niehues builds organizations that deliver and has led projects from VC-funded scale-ups to DAX 40 groups in 20+ countries on six continents, with the DACH region as his home base.

The approach follows the Niehues Delivery Model with its three phases. In the understand phase, the data basis is built from reporting lines and decision paths. In the build phase, the team designs roles and decision paths that make the target design concrete and tests them against real processes in the area before they take effect. In the implement phase, Niehues Consulting steers implementation as delivery manager, project manager or product owner until the organization delivers reliably. Three of the model's review questions matter most for spans and layers: Who decides, who delivers, who uses? Which roles, decision paths and interfaces does operation require? What is the baseline, and how do we measure success? How structure and delivery belong together is described in the article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/).

The entry point is a free initial consultation of 30 minutes, arranged via the [contact page](/#kontakt).

**Recommendation for the executive team**
Map the reporting lines of your company, compare the number of layers per unit with the arithmetic value and assign each layer its decisions. Set a span corridor for each area and calculate the savings using the actual management share of the posts.

**Sources**
- Graicunas, V. A.: Relationship in Organization, Bulletin of the International Management Institute, journal article, 1933
- Woodward, Joan: Industrial Organization. Theory and Practice, book, 1965
- Rajan, Raghuram G.; Wulf, Julie: The Flattening Firm. Evidence from Panel Data on the Changing Nature of Corporate Hierarchies, Review of Economics and Statistics, journal article, 2006

## Frequently asked questions

### How many management layers are ideal?

The ideal number of layers is the one that headcount and span of control yield arithmetically: at a span of eight to ten, that is three to four layers below the top for 1,000 employees and five to six for 50,000. Every additional layer must prove a decision function of its own.

### What does span of control mean?

Span of control is the number of employees reporting directly to a manager. Together with the number of layers, it shapes how quickly decisions and information move through the organization.

### What is delayering?

Delayering is the deliberate removal of management layers, with the remaining managers taking on larger spans. It shortens decision paths and lowers structural cost when roles and decision rights have been clarified beforehand.

### When does it pay to remove management layers?

Removal pays off when decisions pass through several levels without any level making its own contribution, and when spans lie well below the corridor that the nature of the work allows. The analysis of reporting lines and decision time provides the evidence.

### What are the disadvantages of a flat hierarchy?

Flat hierarchies increase the load on managers, reduce career steps and encourage informal hierarchies where decision rights are missing. These disadvantages can be contained with clear roles, specialist career paths and regulated interfaces.

### How much can delayering save?

The saving is the difference in management posts before and after the change, multiplied by their management share and the fully loaded cost per post. With 1,000 employees, the arithmetic number of management posts falls from around 250 at a span of five to around 110 at a span of ten. The one-off cost of the change is deducted.

### How does the management role change with larger spans?

The manager gives up control over individual steps and gains time for objectives, feedback and development. This requires clear roles and reliable metrics as well as enablement for leading larger teams.
