The Revenge of Middle Management and Why Organizations Should Pay Attention

Middle management spent several years absorbing a sustained critique. Too many layers. Too much bureaucracy. Blockers of information, protectors of turf, obstacles to the agility that modern organizations supposedly required. The flattening movement that followed removed significant portions of the middle management layer from organizations across sectors — with consequences that are now visible enough that the critique itself is being quietly reconsidered.

What is emerging in the organizations that cut deepest is a recognition that middle management was performing functions that did not disappear when the titles did. Coordination, context translation, team development, operational problem-solving, and the essential work of connecting strategic intent to daily execution were all happening inside that layer — invisibly enough that their value was not recognized until it was gone.

What Middle Managers Actually Do That Nobody Noticed

The functions that middle management performs sit in an organizational space that is difficult to see clearly from either direction. Senior leaders see the layer between themselves and execution. Frontline employees see the layer between themselves and authority. Neither vantage point provides a clear view of the connective work happening in the middle.

That work includes translating organizational strategy into operational terms that frontline teams can act on — a function that sounds simple and is genuinely complex, requiring simultaneous understanding of strategic intent, operational reality, team capability, and the specific context that determines which aspects of the strategy are immediately actionable and which require preparation. When this translation does not happen — because the layer responsible for it was eliminated — strategy stays abstract and execution stays disconnected from direction.

It also includes absorbing and managing the organizational friction that accumulates between functions, priorities, and people. Middle managers are the shock absorbers of organizational life — the people who take a policy from above that does not quite fit the situation on the ground and find a way to implement the spirit of it in conditions its designers did not anticipate. Without that absorption capacity, friction travels further and lands harder.

Why the Flattening Critique Got Middle Management Wrong

The critique was accurate about the dysfunctions of badly designed middle management. It was not accurate about what middle management is for. These are different things, and the policy response — elimination rather than redesign — reflected a misdiagnosis.

The middle management layer that deserved elimination was the one adding process without adding value: creating approval requirements that slowed decisions without improving them, hoarding information to protect positional relevance, and replicating rather than resolving complexity. That version exists and causes real organizational damage.

The middle management layer that did not deserve elimination was the one providing genuine operational leadership: developing team members, making real-time judgment calls that senior leaders cannot make from a distance, maintaining team function through organizational turbulence, and ensuring that the people doing the work had what they needed to do it effectively. Eliminating both because the first was dysfunctional was organizational surgery performed without distinguishing between the tissue causing the problem and the tissue performing essential functions.

What Rebuilding Looks Like Done Well

The organizations rebuilding middle management capacity after the flattening experiment are doing so with more intentionality than the layer they originally dismantled had been designed with.

Roles are being defined around specific functions rather than traditional title hierarchies — with clarity about what the role exists to do, what authority it carries, and how success gets measured. This clarity is producing middle management that can be held accountable for its contribution in ways that the vaguely defined, process-oriented version that preceded the flattening never could.

The most important design element is scope. The spans of control that made middle management unworkable in the first place — managers responsible for twenty or more direct reports who could not receive genuine development or attention — are being replaced with spans that allow the relational and developmental work that middle management at its best actually involves. Smaller spans cost more. They produce the coordination, development, and operational leadership that the larger spans were delivering in neither version — the old bloated one or the absent post-flattening one.