Your Top Performer Is a Bottleneck

Your Best Person May Be Costing You More Than You Know

This Issue at a Glance

The symptom: Everything is better when they touch it. And nothing moves without them.

The real problem: You built the system around one person instead of building a system they could transfer.

The fix: Start documenting what they know before you need it. Measure their success by what the team can do without them.

This week: Ask your top performer what three things only they know how to do. That list is your organizational risk register.

Full version below. Video attached.

There is someone on your team you rely on more than anyone else. Their work is exceptional. Their judgment is trusted. When something important needs to happen, they are the person you think of first. Clients ask for them. Leaders defer to them. The team routes to them when things get complicated. What you may not have calculated is what that dependency is actually worth — and what it costs when it disappears. The standard replacement cost of one to two times annual salary applies to roles the organization can function without temporarily. This is not that. When a key-person dependency breaks — whether through departure, illness, or burnout — you are not filling a vacancy. You are absorbing the loss of undocumented knowledge, relationships that existed only in their head, and decisions nobody else knows how to make. The productivity loss is not 30 to 40 percent. It can be total in certain functions. And it does not recover on a hiring timeline. It recovers on a rebuilding timeline, which is an entirely different thing. Most leaders only discover the real number after the resignation letter arrives. By then the calculation is academic.

The signal that something is wrong is usually visible well before the crisis. Watch for it in these patterns. Decisions wait until they are available. Projects stall when they are traveling. Other team members stop developing because it is faster to route to them than to build the skill independently. And the person themselves starts showing signs of exhaustion, because an organization has quietly placed its operational weight on their shoulders. None of this happened by design. It happened because they were excellent and the organization kept giving them more, because more kept getting done.

The structural problem is a knowledge and authority concentration that the organization never intentionally built but allowed to develop over time. When one person becomes the answer to too many questions, two things happen simultaneously. The organization becomes fragile in ways it cannot see. And that person becomes a ceiling on their own career, because they are too embedded in current operations to be elevated, developed, or moved without the whole system feeling the shift. Being indispensable sounds like a compliment. Operationally, it is a liability — for the organization and for them.

The fix is not removing them from what they do well. It is building a system that does not depend on them exclusively. And the first person you need in that conversation is them.

This only works if they are part of it. Not informed after the fact. Not managed around. Actually brought in as a partner in solving it. Most high performers in this position already feel the weight of it. They know everything routes through them. They know the organization would struggle without them. Many of them want to change it but do not know how, or have never been given permission to hand things off because the organization keeps rewarding them for holding on.

Start by having an honest conversation with them about what you are trying to build. Not "we need to reduce your dependency" framed as a risk conversation. But "I want to develop the team around you and I need your help to do it." That framing changes everything. They go from feeling like a liability being managed to feeling like a leader being invested in.

Then build the system together. What do they know that exists only in their head? Processes, relationships, judgment calls, historical context — all of it needs to live somewhere the organization can access without going through them. Let them identify it. Let them decide how it gets transferred. They will do it better than anyone else and they will do it with more care if they own the process.

Then assign deliberate transfer with their involvement. Someone learns by working alongside them on real problems, not in a training session. The goal is not to duplicate them. It is to distribute enough of what they carry that the organization can function if they are unavailable, promoted, or gone. They should be choosing who learns from them and shaping how.

Finally, change how you measure their success — and tell them you are doing it. Excellent individual output is not the goal anymore. A team that can operate without them is. That shift, communicated directly and honestly, is also one of the most meaningful things you can say to a high performer. It means you are investing in their growth, not just their output.

If your organization cannot function without one person, that person is not your greatest asset. They are your greatest single point of failure. Three questions worth sitting with.

What would break in the first 30 days if they left?

Does that person know how central they are to things you have never formally told them they own?

And what would it take to change that before you need to?

If your organization has a key-person dependency you have never formally addressed, that is a structural risk worth mapping before it becomes a crisis. Reply and let's look at where the concentration is.

Reply and tell me how you like this video......

​