You can cut the layer. You can't cut the coordination.
Gartner projects that one in five companies will cut more than half their middle management layer by the end of this year. The efficiency story writes itself. Fewer layers, faster decisions, lower payroll. Boards approve it in one meeting.
What the projection does not show is where the work goes once the people doing it are gone.
What happens to the coordination work when a company cuts middle management?
It does not disappear. It moves up to a senior leader who is already at capacity, or it stops happening entirely. Either outcome shows up months later, not on the day of the layoff, which is exactly why the decision looks good on the spreadsheet that made it.
One tech company cut seventy percent of its engineering managers and saved 3.2 million dollars a year. The math looked clean. The VP of Engineering who absorbed that layer now has forty seven direct reports. He approves decisions in Slack between meetings, with no time to ask why a call was made or coach anyone through a bad one. Six months in, the team's strongest senior engineer resigned. The exit interview was blunt: "Nobody here knows what I'm working on or why it matters." The VP had been too underwater to notice the engineer had already checked out.
That is not a story about one bad VP. It is a story about what happens when coordination work gets treated as overhead instead of infrastructure.
The savings are real. So is what they were paying for.
Middle managers did not only approve time off and run status meetings. They translated what leadership meant into what a team should actually do. They caught a bad decision before it shipped. They noticed when someone was quietly drowning, weeks before it became a resignation. None of that shows up on an org chart as a line item, which is exactly why it is the first thing companies stop counting once the role is gone.
A logistics company cut sixty five percent of its regional managers in 2023 and saved 2.3 million dollars. Last year they needed a VP of Operations badly. Nobody internal was close to ready, because the layer where that readiness used to get built had been eliminated three years earlier. Two external searches failed. Nobody wanted to join a company known for cutting its middle. They promoted their strongest director into a role she needed three more years to prepare for, and operations have been unsteady since.
The pattern repeats because the cost of cutting coordination does not land on the quarter that made the cut. It lands two or three years later, on a different line item, reviewed by a different person, who has no reason to connect it back to the original decision.
This is not only a Fortune 500 problem
Scale it down and the exact same failure shows up in a twelve person company that never had a middle layer to cut, because it never staffed one in the first place. The founder is the VP with forty seven direct reports, except there are no direct reports on paper, just every decision, every handoff, and every piece of context that nobody else was ever given the authority to hold.
The symptom looks different at each size. A senior engineer quits because nobody explained why the work mattered. A founder cannot take a week off because nothing runs without them. A fund manager's LP update goes out a day late because there was no one whose actual job was to own it. Underneath all three is the same structural gap: the coordination function was never actually staffed as its own thing. It was either eliminated to save money, or it was never built because nobody thought of it as a real function to begin with.
What a properly staffed layer actually catches
The fix is not adding management titles back onto an org chart. Gartner's own data shows companies are not going to reverse this trend, and a Fortune 500 is not going to un-flatten itself because one commentator made a good argument. The fix is recognizing that coordination is a function, not a layer of headcount, and building it back deliberately instead of assuming it will get absorbed by whoever is left standing.
A properly staffed operating layer holds the things a middle manager used to hold almost by accident: someone notices the senior person is underwater before they quit. Someone catches the decision that needed a second look before it went out. Someone owns the update that has to go out on schedule regardless of how the week is going. That is not bureaucracy. It is the difference between an organization that runs and one that is quietly accumulating a bill it will not see until the person holding everything together leaves.
You do not have to be a company Gartner tracks to have this problem.
You only have to be carrying coordination work that nobody was ever actually assigned to own.
If that sounds like where you are, the place to start is mapping what is actually sitting with you right now, not adding a title to an org chart. That is what the strategy session is for.