Delayering

Choosing where delayering will improve the organisation

Delayering is useful when management steps duplicate decisions, obscure accountability or slow work. It should begin with evidence about how work moves through the organisation. Counting reporting lines alone cannot show whether a manager contributes technical judgement, coordinates complex delivery or provides essential supervision.

Identify the work behind each layer

Map the responsibilities of adjacent management levels and follow a small number of important decisions from request to approval. Repeated review of the same issue can reveal unclear decision rights. However, a control may have a legitimate purpose even where it appears repetitive. Test proposed changes with the people accountable for operational delivery and risk.

Compare a future structure with transition requirements

For each option, show which responsibilities disappear, which transfer and which require new capability. A wider span may be workable only after reporting is simplified, systems improve or team leaders receive support. Model recurring management cost separately from implementation costs and temporary capacity required during the transition.

Is a narrower hierarchy always better?

No. Removing a level can overload managers or push coordination work into informal roles. The right structure depends on work complexity, team capability, location and the consequences of error. Delayering should deliver a clearer operating model, rather than a predetermined number of levels.

How are benefits measured?

Agree measures before implementation: decision turnaround, duplicated approvals, manager workload and delivery performance, alongside cost. Review the structure after it has operated in practice. If escalation volumes rise or responsibilities become unclear, adjust the design. A spans and layers diagnostic provides the evidence, while organisation design connects the changes to business priorities.