Middle Management Isn't Broken. It Was Never Properly Built.

The most overburdened layer in most organizations was designed to do one thing. We've asked it to do everything.

Middle management has a reputation problem.

Too slow. Too bureaucratic. Too focused on process and not enough on people. In downturns, it's the first layer to go — framed as bloat, as unnecessary overhead, as the expendable middle. And yet it keeps growing. Middle managers now make up 13% of the U.S. labor force, up from 9.2% in 1983. Organizations keep cutting the layer and rebuilding it, often larger than before.

That pattern is worth examining. Because it suggests the problem isn't the people in the middle. It's what we've built around them — and what we keep loading onto them without the authority or resources to match.

What middle management was actually designed to do

Middle management didn't originate in the corporate world. It has military roots — Prussian reformers developed layered staff structures specifically to route information and pre-compute decisions across complex organizations at scale. That model entered business through American railroads in the mid-1800s, where informal management styles were failing catastrophically as organizations grew. Train collisions were killing people. The solution was structured hierarchy: defined reporting lines, layers of authority, formalized information flow.

The function was precise and limited. Manage the gap between strategy and execution when scale made direct oversight impossible. Route information. Maintain alignment. That was the job.

Everything else middle management now carries — talent development, culture stewardship, change management, employee wellbeing, organizational problem absorption — was loaded onto it over time. Without a corresponding increase in authority. Without adequate resourcing. Without anyone formally redesigning the role to hold what was being asked of it.

What it became

In mission-driven organizations, this accumulation takes a particular form.

Middle managers become the place problems go when no one has the appetite to solve them properly. The friction between programs that don't communicate. The strategic decision that never got made cleanly. The cultural tension leadership would rather not name. The underperforming colleague no one wants to address directly. These land in the middle — to be managed, absorbed, navigated around — without the authority to actually resolve them.

The result is a layer that is simultaneously over-burdened and under-powered. Expected to translate strategy downward, surface reality upward, hold teams together laterally, and absorb the gap between what the organization says it is and what it actually does — all while being evaluated on whether their team is hitting deliverables.

The perception of middle managers as unexceptional mediocre supervisors has been around for decades — reinforced by a persistent cultural distinction between leaders as visionaries and managers as administrators. That distinction has consequences. It shapes how organizations invest in the layer, how they evaluate it, and how quickly they reach for it when cuts are needed. 

The layoff reflex

When pressure mounts, middle management gets cut. It is framed as efficiency. As flattening the organization. As removing bureaucracy to get closer to the work.

What actually happens: the problems the middle was absorbing don't disappear. They land directly on whoever is left — usually senior leadership, who didn't want to own them before, and frontline staff, who don't have the positional authority to resolve them. The organization becomes simultaneously leaner and less functional. Six months later, it starts rebuilding the layer it just eliminated.

In mission-driven organizations this is compounded by the talent dimension. Middle management, whatever its limitations, is where organizational knowledge lives. It is where rising staff learn to lead, where institutional memory is held, where the translation between mission and operations actually happens day to day. When it goes, that goes with it. The cost doesn't show up immediately. It shows up when the organization can't understand why nothing is moving.

The fix

Middle management doesn't need to be eliminated or defended. It needs to be designed.

That means being honest about what the layer is actually being asked to do — and whether it has the authority, resources, and clarity to do it. It means treating the middle manager role as a design problem rather than a performance problem. It means building the layer intentionally rather than letting it accumulate responsibilities it was never equipped to carry.

Get clear on what the gap between strategy and execution actually requires. Design the middle to close that gap — with defined authority, reasonable span of control, and explicit accountability. Stop loading organizational dysfunction onto a layer and then blaming the layer for struggling under the weight.

The middle isn't the problem. It's where the problem lands.