Rebuilding Middle Management After Years of Flattening

Organisational flattening has been fashionable for several years, and much of it was justified. Layers that existed only to relay information were genuine overhead.

What has become clear is that some of what was removed was doing work nobody had named, and its absence is now showing up in ways that are hard to attribute.

Spans of control quietly became unmanageable

Removing a layer typically doubles or triples the number of direct reports for those remaining. A manager with twenty-five reports is not managing them. They are processing exceptions.

Coaching, development and performance conversations are the first casualties, because they are the only activities with no immediate deadline attached.

Strategy stopped being translated

One of the least visible functions of a middle layer is converting organisational intent into work that makes sense locally.

Without it, strategy arrives as a presentation and teams interpret it individually. The resulting effort is well-intentioned, uncoordinated and frequently contradictory, and it takes a long time for anyone to notice.

Nobody is developing the next cohort

The pipeline of people capable of taking senior roles was largely built through supervised responsibility at the middle level. Removing those roles removed the development path.

Organisations are now recruiting externally for positions they would previously have filled internally, at higher cost and with a lower success rate.

Rebuild the role, not the layer

The answer is not to reinstate what was removed. Much of it genuinely was overhead.

What is worth rebuilding is a role defined around developing people, maintaining delivery quality and translating direction into local priorities. That is a smaller job than the one that was cut, and a more specific one.

Do it deliberately

Start by measuring actual spans of control rather than the ones on the chart. Anything above eight to ten direct reports in a role that requires development responsibility is a signal.

Then be explicit that the reinstated role is about capability rather than coordination, and resource it accordingly. Organisations that simply add managers back without redefining the job recreate the overhead they removed, and the second reorganisation is considerably harder to justify than the first.

Protect the time as well as the role. A manager given development responsibility and a full delivery load will deliver, because delivery has deadlines and development does not. If the job is genuinely about building people, the workload has to say so.