Your Middle Managers Are Not Failing. Your Structure Is.

Natasia Nolan-Hodge
17 hours ago
4 min read

middle manager at desk looking stressed out with employees around asking questions on work

When the Design Cannot Hold the Load, Something in the Middle Gives.

Think about what it looks like to step into a leadership role when the person before you just left, the team is mid-project, the goals were set without you, and your manager's version of onboarding is a thirty-minute calendar invite. The work is already moving and you are already behind.

I have seen this play out more times than I can count. And what strikes me every time is not that the manager struggles. It is that the organization is genuinely surprised when they do.

What Actually Happened to the Middle

The pressure to do more with less did not stay at the top of the organization. Roles have been eliminated, layers removed, and the expectation has been that the remaining people will absorb what left. In the middle of the organization, that has meant more people reporting to fewer managers, more complexity per person, and more accountability for outcomes that were previously shared across a broader layer of leadership.

The average number of direct reports per manager has risen 50% since 2013. The role expanded significantly while the support structure around it stayed largely the same. And when openings came up, the budget-friendly answer was to promote from within. Someone got a title, inherited the team, and was expected to figure out the leadership part while still delivering on the work.

What those managers inherited was a set of goals they had no part in setting, a team they had not built, and a list of responsibilities that looked nothing like what they had been doing before the promotion. Being excellent at the work is what got them the role. But the skills that make someone a strong individual contributor are not the same ones that make someone effective at leading people, developing a team, or managing in multiple directions at once.

That gap does not close on its own. And when organizations do not close it intentionally, it shows up as burnout, disengagement, and eventually attrition from the exact layer of the organization that holds execution together.

Why the Fixes Keep Missing

When this shows up in an organization, the response is usually a training program, a workload audit, or a conversation about prioritization. I understand why. Those are visible problems with available solutions. But they are aimed at the person when the problem is in the design.

A manager who is overextended does not need a workshop on time management. They need a structure that accounts for what the role actually requires. The same is true for someone who was promoted without the preparation to lead people. What closes that gap is real development, not another program aimed at helping them cope with a situation the organization created. When organizations keep solving for the symptom, the underlying condition does not change. It just finds a new way to surface.

What makes this particularly costly is where these managers sit. The middle of an organization is where strategy becomes execution. It is where culture is either reinforced or quietly dismantled, one team interaction at a time. When that layer is strained, the impact does not stay contained. It moves through every team those managers lead, often before leadership has any visibility into what is happening.

Another Perspective: This Is a Design Problem

The organizations I have worked with that have gotten this right did not start with a training vendor or a new performance framework. They started by asking honest questions about what they had actually built. How many people can a manager in this role realistically lead well, given the complexity of the work? Are the people we are putting into leadership positions being developed before the opening or after the problems start? When we cut roles, where did that work actually go?

Those questions are harder to sit with than they look. Answering them honestly means acknowledging that the burnout and attrition showing up in the middle of the organization traces back to structural decisions leadership made. That is a harder conversation than rolling out a new manager development program.

But it is the conversation that actually changes something. When you treat this as a design problem, span of control becomes a question you answer deliberately instead of a number you inherit by default. Building someone for a leadership role means real development before the title, not a training program after the problems start. The work that disappeared when roles were cut gets accounted for rather than quietly absorbed by whoever is left.

Where to Start

The conversation usually begins with three things.

First, look at how span of control decisions are actually being made. If the answer is that it grew because people left and were not replaced, that is worth examining. The right span varies by the complexity of the work, the maturity of the team, and how much coaching and development the role requires. A number arrived at by default is not a strategy.

Second, look at the pipeline. Who is being prepared for leadership roles, and what does that preparation actually look like? Identifying high-potential individuals six to twelve months before a role opens, giving them real exposure to what the role requires, and building the skills before the title arrives changes what those managers can do from day one.

Third, account for what was lost when roles were cut. The responsibilities did not disappear. They landed somewhere. Getting clear on where, and whether the people carrying them have what they need to carry them well, is where a lot of the hidden strain lives.

The managers in the middle of your organization are not the problem. The conditions they are working inside are. That distinction changes what you go looking for when execution starts to break down, and it changes what you build when you decide to fix it.