Team Leadership
When Everyone Depends on You at Work: How to Stop Becoming the Bottleneck
A team that runs smoothly because one person holds it together isn't a well-run team. It's a single point of failure that hasn't failed yet.
If your team's performance depends on one person being available, informed, and unbothered, you don't have a strong team. You have a fragile one that's currently getting lucky.
Every manager has had this moment, usually with a mix of relief and unease: a request comes in, and there's exactly one person who can handle it properly. They know the history, the exceptions, the person to call, the thing that broke last time. It feels like good fortune to have someone that capable on the team. It rarely gets examined as what it actually is — a structural risk that has been quietly allowed to grow, one reasonable decision at a time.
This article is written from the manager's side of the problem, because the fix doesn't live with the reliable person alone. It lives in how the team and its systems were built around them.
Short Answer
Bottlenecks around one person aren't usually caused by that person hoarding control. They're caused by managers routing the hardest, highest-stakes work to whoever handles it best, over and over, without ever building a second path. The dependency isn't a personality problem — it's a systems gap, and systems gaps get fixed with systems, not with asking the bottleneck to work harder.
- The bottleneck usually forms through good decisions made repeatedly, not bad ones
- It's invisible until the person is unavailable — then it's an emergency
- Fixing it is a management task, not a favor the reliable person owes the team
How Over-Reliance Builds Without Anyone Deciding It
No manager sets out to build a team with a single point of failure. It happens through a long sequence of individually sensible calls. A tricky client issue comes in, and it goes to the person who's handled tricky issues before, because that's the fastest route to a good outcome today. A new process gets designed, and the person who understands the old one best ends up owning the new one too, because onboarding someone else would slow things down this quarter. None of these choices is wrong in isolation. Compounded over a year or two, they produce a team where one person's calendar has become critical infrastructure, and nobody remembers deciding that on purpose.
The warning sign isn't that this person is skilled — skill is exactly what you want concentrated somewhere. The warning sign is that the skill has nowhere else to go. There's no second person who could plausibly cover the gap on short notice, and the team's actual resilience is much lower than its day-to-day performance suggests.
The Real Cost to the Team, Not Just the Person
The conversation about over-reliance usually centers on the individual carrying the load — their stress, their stalled title, their risk of burning out. That cost is real and worth taking seriously. But there's a second cost that's easy to miss because it's diffuse rather than personal: the team itself becomes brittle. Deadlines quietly start depending on one person's health and mood. Institutional knowledge sits in one head instead of being distributed, so a single resignation can erase months of context overnight. Cross-training stalls, because there's never a low-stakes moment to justify slowing down long enough to teach someone else. The team looks capable right up until the exact day it isn't, and that day tends to arrive without warning.
Why the Pattern Is Hard to Interrupt
Once a bottleneck forms, it resists being unwound, and it's worth understanding why before trying to fix it. Delegating the work out usually means accepting slower or rougher output in the short term while someone else climbs the learning curve — a trade that's easy to keep postponing when there's always a more urgent fire burning. The reliable person, for their part, often has genuine ambivalence about giving pieces away: being needed feels good, and handing off ownership can feel like handing off relevance. And because the current arrangement works, technically, there's rarely a forcing event that makes the fix feel urgent instead of merely wise. The bottleneck doesn't get solved. It gets managed around, indefinitely, until it can't be.
Why the Bottleneck Gets Worse Over Time
- High-stakes work keeps getting routed to the person who handles it fastest and best.
- That person accumulates more context and judgment calls that live only with them.
- Delegating any of it now requires an upfront time cost nobody wants to spend.
- The team quietly defers cross-training again, since the current setup "still works."
- The gap that would open if this person left grows larger, making the fix even harder to start.
Building Systems Instead of Single Points of Failure
The fix is not asking your most reliable person to want less responsibility, and it isn't hoping the risk resolves itself. It's a deliberate, manager-led redesign of how work and knowledge move through the team — treating redundancy as a requirement, not a luxury to add once there's spare time.
- Map where the risk actually concentrates. For each critical function, ask plainly: if this person were out for a month, what breaks first? That list is your real priority order, not the org chart.
- Turn tacit knowledge into documented process. Anything that currently exists only as "ask them" needs to become a written procedure, a recorded walkthrough, or a shared reference — while the person who knows it is still there to check it for accuracy.
- Build in deliberate rotation. Assign a second person to shadow or co-own each critical task, even before there's a visible need. Redundancy built in a calm quarter is far cheaper than redundancy built during a crisis.
- Protect the reliable person's growth explicitly. Make it clear, out loud, that reducing their bottleneck status is what earns them the next role — not a quiet demotion in relevance. This reframes delegation as advancement instead of loss.
- Review dependency risk on a schedule, not just after a crisis. Put a recurring check on the calendar — quarterly is enough — to ask who has become irreplaceable since the last review, before the answer gets tested by an actual emergency.
A team that only works because one person never gets sick, never gets promoted, and never leaves isn't a well-run team. It's a bet the manager hasn't noticed making.
Is your team's stability resting on one person's shoulders? See where the pressure is really concentrated.
Take the Self-Boost DiagnosticResilience Is a Design Choice, Not an Accident
Every team ends up with people who are more capable than others, and that's not the problem this article is about. The problem is a team whose day-to-day functioning has come to depend on one specific person being present, informed, and willing — a condition that was never decided on purpose and that nobody is actively managing. Fixing it isn't about asking your best people to do less. It's about building a team that would still hold together on the one day your best person can't be there. That's not a favor to them. It's the actual job of running a resilient team.
No comments:
Post a Comment