A team's output is rarely limited by how hard the people on it are working. More often, it's limited by how much can move through the manager above them.

Questions require their approval. Decisions wait for their input. Problems sit unresolved until they have time to address them. Team members become dependent on that one person even when they are more than capable of doing much of the work themselves.

When a manager is overloaded, the symptoms rarely look like a leadership capacity problem. Onstead, they look like slow decisions, missed handoffs, pushed deadlines, and a team that seems to be waiting around more than it should. Leadership often reads this as a problem on the team’s part: a motivation, prioritization, or skills gap issue. However, the problem doesn’t lie within the team. It’s in the current process.

Meanwhile, with work slowed down, leaders find themselves working harder when work falls behind, both in trying to get through the backlog while also attending more meetings and answering more questions revolving around solving the problem of their team’s underperformance, even as the workload continues to grow and the real problem remains unaddressed, meaning organizational capacity remains unchanged.

The Bottleneck Hides in Plain Sight

Here's what makes manager overload so hard to diagnose: the manager is usually the busiest person in the building. They're in back-to-back meetings, answering messages at all hours, putting out fires constantly. From the outside, that looks like commitment. From a systems view, it's a warning sign.

Human Performance Technology teaches us that performance is produced by systems. When critical work depends on a single individual, the system is limiting performance.

A manager who approves every decision, solves every problem, and answers every question becomes the narrowest point in the workflow. Every request waits in line and creates a dependency. A few dependencies are normal. A role design where dozens of dependencies converge on one person isn't a workload problem for that person alone. It's a structural constraint on everyone downstream of them.

The fix isn't telling the manager to delegate more, work faster, or get better at time management. Those are individual-level interventions aimed at a structural problem. The fix is asking a different question: What is currently required to flow through this person that doesn't actually need to?

As organizations grow, leaders must shift from doing the work to creating conditions where work can move without them. That requires clear outputs, defined decision authority, and performance support that allows people to act confidently.

Growth happens when capability expands beyond a single person.

Kate Graham

Principal, Humaneering Performance

Redesigning around a bottleneck starts with mapping what's actually flowing through the role, not what the job description says should be flowing through it. Job descriptions describe intent at a specific point in time. Workflows describe reality, and the two drift apart constantly.

A useful starting point is examining the work that consistently returns to the manager's desk.

Three categories tend to show up once you map out how decisions are happening:

The first category defines decisions that need to stay with the manager. The second category is where redesign work happens: Someone else needs the context, the authority, or both. The third category is often the largest, and the easiest to address once it's named. Habit-based routing is accumulated without real intent.

Redesign means redistributing decision rights that were centralized by default rather than by design. Sometimes it means documenting the context that currently only exists in one person's head, so that context stops being the bottleneck. Sometimes it means a role genuinely needs to be split, and the manager has been quietly absorbing the difference for months or years.

Whatever the redesign looks like, the goal is the same: reduce the number of things that have to pass through a single point before work can continue.

When leaders redesign the flow of work, they create capacity for both themselves and their teams. The end result is a system where accountability exists at every level.

Review your calendar from the last two weeks. Highlight activities that required your direct involvement. Then ask:

If the answer is no, the work may belong somewhere else in the system.

What work should stop flowing through me?

If you're a manager reading this, sit with that question honestly. What is actually creating a bottleneck for the people who depend on you? The answer often reveals your next opportunity to increase organizational capacity.