Your Best Employee Is a Single Point of Failure
Every small business has one. Often it's the owner. Sometimes it's the person who's been there longest and quietly knows everything.
They're reliable, they fix things, and they're the reason nothing has fallen over.
They're also the reason the business can't take on more work, can't onboard anyone useful quickly, and becomes fragile the moment they're unavailable.
This isn't a criticism of them. It's a description of what happens when competence substitutes for structure.
How it happens
Nobody designs this. It accumulates.
Someone is good, so they get the difficult cases. Being given the difficult cases makes them better. Being better means they get more of them.
Meanwhile nothing gets written down, because they don't need it written down — they know. And asking them to document what they do takes time away from the work only they can do.
Within a couple of years, a large part of how the business operates exists only as their behaviour.
The symptoms
Questions route to one person. Including questions that aren't about their job. They're asked because they'll know.
Their holiday requires preparation. Not coverage of their tasks — a project.
New hires take months to become useful. Because training means shadowing, and shadowing is slow and incomplete.
Certain work waits for them. Even when others are available.
You can't describe what they do. You can describe their role. The gap between those two is the problem.
Why it's expensive even when nothing goes wrong
The risk of them leaving is the obvious cost, and the least interesting one.
They're the ceiling. The business can take on as much work as they can personally touch, and no more. Everything else queues behind them.
Nobody else develops. The hard cases are where people learn. If those always go to one person, everyone else stays at the same level indefinitely.
They can't be promoted. Moving them means losing the thing they do. So the most capable person in the business is structurally stuck.
Decisions get worse. Not because they're wrong — because one person's judgement, unchallenged and undocumented, drifts without anyone noticing.
That last one is subtle and real. Undocumented expertise can't be reviewed.
Why the usual fixes don't work
"We'll cross-train." Shadowing transfers the obvious parts and misses the judgement. The learner picks up the steps and not the decisions, so they can handle the routine cases — which weren't the problem.
"We'll hire someone senior." Now you have two people who know things nobody wrote down. The dependency is halved and the underlying problem is identical.
"They'll document it when things calm down." Things don't calm down, and the reason they don't is this exact situation.
What actually works
Start with their decisions, not their tasks
The tasks are the easy part and they're usually half-visible already.
What matters is the judgement: how they decide which supplier, when to escalate, what makes a case unusual, how they tell a problem is developing before it's visible.
Sit with them and ask. "What made you choose that?" repeatedly, for an afternoon. Most of the answers turn out to be rules nobody had stated.
Document with them, not about them
They know how the work is really done. Anyone writing it from outside will produce the version that sounds right and isn't.
This also matters for how it's received. Documentation done to someone reads as preparation for replacing them. Done with them, it's a record of their expertise — and it's what finally lets them stop being stuck with it.
Give the hard cases to someone else, with them watching
The reverse of the usual arrangement. The learner does it; the expert reviews.
Slower for a few weeks. It's the only approach that transfers judgement, because judgement develops by making decisions, not by watching them.
Fix the routing
If questions arrive at one person by habit, change where they arrive. A shared channel, a rota, a documented answer in a findable place.
The habit is often the whole dependency. People ask them because that's what you do, not because nobody else could answer.
If it's you
Most of the time, in a small business, it is.
Everything above applies, with one addition: you're the hardest case, because you can always justify doing it yourself. It's faster, you'll do it properly, and there's something urgent.
All true, and it's how a business stays the size of one person.
The test is the week-away question. If a week without you means a week of cleanup when you return, the dependency is structural, and it won't resolve by working harder.
What to expect
This is slow. Not because documentation is slow — because transferring judgement requires someone to make decisions badly for a while, with supervision.
Budget a few months per significant dependency. The payoff isn't that the work gets done faster. It's that it stops being attached to a person.
Capability that only exists in one person isn't an asset. It's a constraint wearing a compliment.
Want to find out where your business is dependent on one person?
A free systems audit maps what's documented, what isn't, and where the business actually narrows.