The Return of the Manager Is Not a Step Back

I would put this question in front of any executive team flattening work right now: What did we ask managers to carry before we decided we needed fewer of them?

That question matters because the manager conversation is changing.

For years, many organizations talked about flattening layers, increasing speed, empowering teams, and reducing bureaucracy. Some of that made sense. Too many layers can slow decisions, blur accountability, and keep leaders too far from the work.

But removing layers does not automatically remove the work those layers were doing.

Someone still has to translate strategy.

Someone still has to notice capacity.

Someone still has to coach judgment.

Someone still has to resolve conflict, explain tradeoffs, hold standards, protect quality, and help people understand what changed and what did not.

If that work is not designed intentionally, it does not disappear.

It spreads.

Often onto the same people already carrying too much.

Current workplace research keeps pointing back to the same truth: managers matter. Gallup's 2026 reporting on AI and workplace culture found that many CHROs saw AI as strategically important while lacking confidence in managers' ability to guide employee AI use. Microsoft also emphasized in its 2026 Work Trend Index that manager support, culture, talent practices, and operating model influence whether AI creates meaningful impact.

That is not only an AI point.

It is a structure point.

The more work changes, the more human coordination matters.

The more AI enters the workflow, the more people need clarity about judgment, review, risk, accountability, and trust.

The more organizations move quickly, the more someone must help teams understand what deserves speed and what deserves care.

The industry response is starting to show a correction. Organizations are rethinking manager training, spans of control, leadership layers, AI enablement, and the role of middle management. Some are realizing that what looked like overhead was also the connective tissue between executive intent and employee reality.

That does not mean adding layers for the sake of hierarchy.

It means being honest about coordination.

Executives may set direction, but managers make direction livable.

They hear where the message does not land.

They see where the process breaks.

They know which priorities are colliding before the dashboard shows it.

They can build trust or drain it depending on how prepared, supported, and empowered they are.

So the question is not, "Do we need more managers?"

The better question is, "What management work is required for this strategy to become real?"

Once leaders answer that, they can decide structure with discipline.

What work needs coaching?

What work needs decision rights closer to the team?

What work needs escalation?

What work needs a standard process instead of another meeting?

What work needs to stop living inside one exhausted manager's memory?

I would ask executive teams to map one major change from announcement to daily execution. Then identify every place where a manager is expected to translate, absorb, clarify, enforce, coach, decide, or repair.

If the list is long, do not pretend the layer was the problem.

The unsupported load may have been the problem.

The return of the manager is not a step back when the work requires human coordination.

It is a chance to design leadership honestly.