The Overloaded Manager

Three years ago she managed six people and ran the best team in the building. The org chart absorbed the growth. Nobody decided this on purpose — and now you're looking at her numbers wondering what changed about her, when nothing did.

Three years ago, she managed six people and ran the best team in the building. The work was good. The reviews were good. You promoted her because she'd earned it. Then the company grew, and grew again, and at some point in the last eighteen months she went from six direct reports to sixteen, without anyone formally deciding that should happen.

Nobody sat down and designed this. The org chart just absorbed the growth the way org charts do, by attaching people to the manager who was already there rather than building the layer that growth actually required. She didn't get worse at her job. Her job got bigger than any one person could do well, and you're now looking at the engagement numbers wondering what changed.

Nothing changed about her. The math changed around her.

A Math Problem Wearing a Manager's Name

This isn't a performance problem. Treating it like one is wrong, and it's what most leaders are most likely to do.

The instinct, when a previously-strong manager starts missing things (late feedback, thinner one-on-ones, a team that seems less held-together than it used to), is to look at the manager. Is she still good at this? Should we coach her? Should we replace her? Those are reasonable questions if the cause were capability. It isn't. You have direct evidence she could do this job well, because she did, at a smaller scope, recently. What you're watching is what happens when span of control outruns the structure meant to support it: not a skills gap, a capacity ceiling.

The tell is in the timing. If the decline tracks the headcount growth more tightly than it tracks anything about the person, you're not looking at a manager problem. You're looking at a math problem wearing a manager's name.

The Pipeline Two Layers Down

The direct cost is the easiest to see and the least important: a manager working at the edge of what's sustainable, putting in longer hours to compensate for a span that's structurally too wide, heading toward the kind of burnout that takes good people down quietly and all at once.

The cost that actually matters is downstream. Sixteen direct reports means each one gets a fraction of the attention six used to get. Feedback gets shorter and later. Development conversations get cut for triage. The people on that team who were going to become your next strong managers are instead getting the thin version of management: present, well-intentioned, structurally unable to invest in them the way the organization invested in their manager when she had room to be invested in.

You're not just straining one person. You're quietly degrading the leadership pipeline two layers down, and most of that damage won't show up in any number you're currently tracking.

What Gives It Away

The growth happened faster than the structure did. Headcount went up. The management layer didn't, at least not until after the strain set in. If you can point to a specific window where the team roughly doubled and the manager stayed the same, that's the signal, not a coincidence.

The manager has a real track record at a smaller scope. This is what separates Overloaded Manager from a genuine capability gap. She wasn't struggling before. The skill was there. The conditions changed.

Nobody decided this on purpose. Ask how the current span came to be and you'll get some version of "it just kind of happened": people got added as they were hired, attached to whoever already had a team, because building a new layer felt like a bigger decision than it should have. That absence of deliberate design is the pattern's signature.

Why She Won't Be the One to Say It

The reason this stays unaddressed longer than it should is that the manager experiencing it is usually the last person who'll name it.

Saying "I have too much on my plate" reads, in most cultures, like a complaint about capability: exactly the impression a strong performer least wants to give, especially one who got the larger team because she was good. So she doesn't say it. She just absorbs it, works longer, triages harder, and hopes the gap doesn't show. It shows anyway. It shows in her team's engagement scores, in the slow attrition of people who feel under-managed, in her own trajectory toward burnout, everywhere except the one conversation that would actually surface the cause.

And from where you're sitting, the symptoms look exactly like a performance issue, because that's the only frame most organizations have for "things got worse." The structural explanation requires someone to ask a different question than the one the symptoms suggest.

What Diagnosis Doesn't Solve

None of this means the larger scope was a mistake. Roles evolve. Sometimes they get harder, legitimately, because the business got bigger or more complex, and there was no version of events where this manager's job stayed the same size while everything around it grew. Naming the structural cause doesn't undo that. It just tells you where the strain is actually coming from.

And naming it isn't the same as fixing it. If the organization genuinely cannot expand the structure right now, no amount of correctly identifying "this is a span problem, not a skill problem" changes what's in front of the manager tomorrow morning. Diagnosis tells you what's true. It doesn't, by itself, tell you what to do when the obvious fix, add a layer, split the team, isn't available yet. That's a separate conversation, and a harder one, about what a manager and an organization do in the gap between knowing the cause and being able to resolve it.

What Actually Moves It

There are two real levers here, and most organizations only ever pull one.

The first is structural: restructuring the span, adding a layer, splitting the team, redistributing the load, so the manager who proved she's good at this gets to do it at a scope where being good at it is actually possible again. When the organization can do this, it's usually the cleanest fix, because it removes the cause rather than asking someone to absorb it.

The second lever matters when the first one isn't available yet, or when the business has decided, for real reasons, that this span is the new normal. What got someone through six direct reports well doesn't automatically scale to sixteen, and that gap is closeable, to a point. The skills that change are specific: what to delegate and what to hold onto, how to run a one-on-one in fifteen minutes that used to take forty-five, how to spot which of sixteen people actually needs attention this week without checking in on all of them equally, how to build systems and rhythms that don't require the manager to personally touch everything. None of that is mysterious. Most of it can be taught, practiced, and gotten better at deliberately, the same way any other operational skill improves with the right support and repetition.

What it isn't is a substitute for structure when the math has genuinely broken. There's a real ceiling on how wide a span one person can manage well, no matter how skilled they get, and an organization that keeps widening spans and calling the result a development opportunity is going to run past that ceiling eventually. Building capacity buys time and raises the limit. It doesn't remove it.

The honest sequence is usually: figure out which lever you actually have available right now, invest in it deliberately rather than by accident, and keep watching for the point where capacity-building alone stops being enough and the structural conversation becomes unavoidable again.

That requires someone to ask the question the symptoms don't ask on their own: not "is this manager still effective," but "did we ever actually decide this was the right span for this role, and have we actually prepared anyone for what spans like this require." Most organizations haven't asked either half of that question, because nobody owns asking it. It falls in the gap between operations, who see the headcount, and HR, who see the engagement scores, and neither one is positioned to connect the two.

If a manager who used to be excellent is suddenly struggling, and you can't point to anything she's actually doing differently, look at what's around her before you look at her.

Worth a conversation before the next review cycle does the deciding for you.