Key takeaways
- Key-person dependency is a daily operating cost, not just a departure risk.
- The expert becomes a queue: work waits on one person’s availability.
- Constant interruption degrades the expert’s own output — and their job satisfaction.
- Shared memory removes the need to route every question through one human.
The person everyone has to ask
Every organisation has one. The person who’s been there longest, or who built the thing everyone depends on, or who simply remembers how it all fits together. They’re usually excellent, usually generous with their time, and usually the reason a dozen things quietly keep working.
They’re also, structurally, a bottleneck — and everyone has agreed not to say so, because saying so sounds like criticism. It isn’t. It’s a description of how work flows.
The hidden queue
Watch where work actually waits and a pattern appears. A decision can’t be made until she’s back from leave. A project can’t start until he’s had a look at it. An unfamiliar problem stalls for two days, not because it’s hard, but because the only person who’s seen it before is in back-to-back meetings.
None of this shows up as a bottleneck on any dashboard. It shows up as things generally taking longer than they should, and as a strange fragility whenever one particular person takes a holiday.
When one person is the only route to an answer, your throughput is capped by their calendar.
What it costs the expert
The cost lands hardest on the person you can least afford to lose.
Their day fragments into interruptions. The deep work they were hired for gets squeezed into the edges. They repeat the same explanations to different people, month after month. Over time, capable senior people start to feel like a help desk for their own history — which is, not coincidentally, one of the more common reasons they eventually resign.
So the dependency compounds the risk it creates: the more indispensable someone becomes, the more draining the role gets, and the more likely you are to face the departure you were worried about in the first place.
Why “just write it down” fails
The standard response is to ask the expert to document what they know. It rarely works, and it’s worth being honest about why.
First, it adds another task to the schedule of the most overloaded person. Second, they genuinely don’t know what to write — the knowledge is invisible to them because it just feels like knowing how things work. Third, whatever they do write covers the tidy general case, while the questions people actually ask are about the exceptions.
So the document gets written, is briefly celebrated, and people keep walking over to ask anyway — because the answer they need was never in it.
Removing the bottleneck without removing the person
The goal isn’t to make your expert less valuable. It’s to stop the business routing every question through a single human simply because that’s the only place the answer exists.
That changes when context accumulates in the business as work is done — the reasoning, the exceptions, the history, captured where the work happens rather than in a documentation drive. The common questions get answered from what the company already knows. The expert gets consulted on the genuinely hard, genuinely new problems — which is the work they actually want to be doing.
The measure of success is simple: the number of things that stall when one person is unavailable. If that number is high, you don’t have a staffing problem. You have a memory problem wearing a staffing costume.
Common questions
What is key-person dependency?
When critical knowledge or decision-making sits with one individual, so work routes through them and stalls when they are unavailable. It is a daily throughput constraint, not only a risk that materialises if they leave.
Why is this a cost even when the expert is still employed?
Because work waits on one person's availability. Decisions queue behind a single calendar, and the expert's own high-value work is fragmented by constant interruptions.
Why doesn't asking the expert to document everything work?
It adds work to your most overloaded person, they cannot easily see what they know, and what they write covers the general case while people actually ask about exceptions.
How do you reduce key-person dependency?
Let context accumulate in the business as work happens, so routine questions are answered from what the company already knows and the expert is reserved for genuinely novel problems.
Free your experts from being the help desk
EdgeX11 keeps the reasoning and history in the business, so routine questions don’t need to queue behind one person’s calendar.
Talk to us