Why Eliminating Middle Managers Backfires
The fastest way to break an organization
There’s a popular move in leadership right now. Flatten the org. Cut the middle. Move faster.
The logic sounds clean: fewer layers means faster decisions, less bureaucracy, more empowerment. Analysts at Gartner predict that by the end of this year, twenty percent of organizations will use AI to eliminate more than half of their middle management positions. The operating theory is that technology can handle coordination, reporting, and status tracking — the stuff middle managers supposedly spend their time on — and the people doing the actual work can just… self-organize.
I’ve watched this play out. At one organization, the decision was straightforward cost reduction dressed up as organizational agility. The math looked clean on paper — fewer managers, fewer salaries, flatter structure, faster execution. The reality was anything but.
Within months, the damage was visible to anyone paying attention. Within a year, it was undeniable. And the cost of rebuilding what was cut far exceeded what was saved.
What middle managers actually do
The problem with eliminating middle management is that most senior leaders don’t fully understand what middle managers do. They see the meetings, the status reports, the one-on-ones. They see overhead. What they don’t see is the translation work.
Middle managers translate strategy into execution. They take the broad direction from senior leadership — “we need to improve retention” or “we’re shifting our go-to-market approach” — and convert it into something a team can actually act on. They break it down, prioritize it, sequence it, and make the dozens of small judgment calls that connect a strategic objective to daily work.
They also translate upward. They take the reality from the front line — what’s actually working, what’s breaking, where the friction is — and synthesize it into something a senior leader can act on without drowning in detail. When this layer disappears, senior leaders either get no information or get all of it, unfiltered. Neither is useful.
And in technical organizations, the translation work is only part of it. Middle managers in support, engineering, and services teams aren’t just managing — they’re working. They’re often the most technically skilled people on the team, promoted in part because they were strong troubleshooters who also demonstrated leadership ability. They handle escalations personally. They step in on complex customer issues. They act as technical leads for their teams, making judgment calls on approach and methodology that their direct reports aren’t yet equipped to make. They often manage relationships with smaller clients — the ones who don’t meet the threshold for a dedicated customer success rep but still need a human being who knows their environment and their history.
When you eliminate that layer, you don’t just lose management capacity. You lose your best escalation path, your technical backbone, and the relationship coverage for a segment of your customer base that nobody else is staffed to serve. The spreadsheet that justified the cut didn’t account for any of that because none of it had a line item.
In organizations where customer experience is paramount, the middle layer doesn’t slow things down — it enhances them. It’s the layer that catches the issue the front line can’t resolve, makes the judgment call the script doesn’t cover, and preserves the customer relationship when something goes sideways. The alternative is to empower the front ranks to do far more than they normally can. In theory, that sounds like the right answer. In practice, it rarely works — especially when the front line is offshore.
I’ve written before about how offshore teams can be genuinely excellent when they’re invested in and developed. But the reality in most organizations is that frontline offshore teams are trained to follow specific scripts and processes to the letter. That’s by design — it’s how you maintain consistency at scale. Those teams are not set up to take initiative, exercise judgment on exceptions, or navigate ambiguity with a frustrated customer. They were never asked to, and nobody trained them for it. When you remove the middle layer and expect the front line to absorb that work, you’re asking people to do something the organization explicitly trained them not to do. The customer feels it immediately.
This isn’t overhead. This is the connective tissue of the organization.
What breaks when you cut the layer
I’ve observed organizations make this cut. The same things break every time.
Communication collapses in both directions. Strategic intent stops reaching the teams doing the work. It’s not that the CEO’s message isn’t clear — it’s that nobody is doing the work of translating it into context that a specific team, with specific constraints, can act on. Meanwhile, signals from the front line stop reaching leadership. Problems that a middle manager would have caught, contextualized, and either resolved or escalated now either fester silently or arrive at the executive level as crises.
Escalation disappears as a function. Middle managers are the early warning system. They catch problems when they’re small — a team conflict, a process breakdown, a customer pattern that doesn’t look right — and they resolve most of them before anyone else needs to know. Remove that layer and problems don’t get smaller. They get invisible until they’re too big to ignore. Senior leaders find themselves drowning in operational detail they shouldn’t be touching, and the things that need their strategic attention get crowded out.
People development stops. Coaching, mentoring, career development, performance feedback — this is relationship work that happens in the one-on-ones and hallway conversations that middle managers have every week. Senior leaders don’t have the time, the proximity, or the context to do this at the individual level across large teams. When the middle layer goes away, people feel abandoned. They stop growing. The best ones leave.
The leadership pipeline dries up. This is the quiet catastrophe. Middle management is where future senior leaders learn to lead. It’s where they make their first hiring mistakes, run their first difficult performance conversations, learn to manage up and across, and develop judgment through repetition. Cut that layer and you’ve eliminated the proving ground. Two years later, you need a VP and your bench is empty because nobody got the reps.
The AI replacement fantasy
The current version of this argument adds a new wrinkle: AI can do the coordination work. AI can handle status tracking, resource allocation, summarization, and reporting. So the human in the middle is redundant.
This misunderstands the job. The parts of middle management that AI can replace — the administrative, the mechanical, the routine — are the least valuable parts of the role. They’re also the parts that were already the weakest justification for the position.
The parts AI cannot replace are judgment, relationships, and context. The ability to look at a team and know that someone is struggling before they say it. The judgment to decide that a directive from above needs to be adapted rather than implemented literally. The political awareness to know which cross-functional relationship needs attention this week. The coaching instinct to give someone a stretch assignment at exactly the right moment.
If anything, AI should be freeing middle managers to spend more time on the human work by handling the administrative burden. Instead, organizations are using AI as justification to eliminate the role entirely and hoping the human work just… happens on its own.
It won’t.
What good middle management looks like
The answer isn’t to defend bad middle managers. Every organization has them — the ones who add a layer without adding value, who schedule meetings to feel important, who pass information up and down without adding context or judgment. Those aren’t middle managers. Those are relay stations.
Good middle management is the hardest job in most organizations. You’re accountable upward for your team’s results and downward for your team’s experience. You have to implement decisions you didn’t make and sometimes don’t agree with, while maintaining credibility with the people executing them. You have to manage the gap between what leadership wants and what the team can deliver, often absorbing the pressure from both sides.
The organizations that get this right don’t eliminate the middle. They invest in it. They develop middle managers deliberately. They give them authority that matches their accountability. They treat the role as a critical leadership function, not as an administrative necessity.
The uncomfortable truth
Flattening your organization feels decisive. It looks like action. It shows up immediately on the cost line. And it destroys capability that took years to build, in ways that won’t show up on any dashboard for twelve to eighteen months.
By then, the senior leaders who made the cut have either moved on or forgotten the connection between the decision and the consequences. The institutional knowledge is gone. The early warning system is gone. The coaching layer is gone. The pipeline is gone.
And someone, somewhere in the organization, is putting together a slide deck explaining why they need to hire middle managers.
— Bruno