The handover problem — what happens when your best person leaves

There is a particular kind of bad day that almost every growing business eventually has. A key person leaves — they resign, they move, occasionally something worse — and within a week you discover how much of your company was living quietly inside their head. The thing only they knew how to do. The client only they had the relationship with. The system only they understood. None of it was written down, because they were always there, so why would it be.

This is the handover problem, and it is one of the largest unmanaged risks in a small business. Not because people leaving is unusual — it is inevitable — but because almost no one prepares for it until it happens to them once, expensively. This essay is about finding that risk on purpose, while everyone is still here, and defusing it before it picks its own moment.

The single-point-of-failure person

In every small team, knowledge concentrates. Someone becomes the only person who really understands the billing, or the one supplier relationship, or how the main system actually works under the surface. It happens naturally and it usually looks like a strength — "thank goodness for so-and-so, they just handle it." The handling is real and valuable. The danger is that it has become invisible and singular.

That person is a single point of failure, in exactly the engineering sense: a component the whole system depends on, with no backup. The system runs beautifully right up until that component is gone, and then it does not run at all. The better and more reliable the person, the more the business has quietly leaned its full weight on them, and the harder the fall when they step away.

The cruel irony is that your most capable people become your largest handover risks, precisely because they absorb so much and make it look effortless. Effortless is what hides the dependence.

Find it before it finds you

You can locate this risk deliberately, with one uncomfortable exercise. Go through the critical functions of your business and ask, for each: if the person who handles this vanished tomorrow, could we carry on? Be honest. The functions where the answer is "no, only they know how" are your single points of failure, and now you have a list.

A sharper version of the question: for each key person, what would actually break if they did not come in for a month? The answers map your hidden dependencies precisely. The things that would break are the things that live only in that person's head, undocumented, unbacked-up — the knowledge that walks out of the building every evening and might, one evening, not walk back in.

This exercise is unsettling, which is why almost no one does it until forced. Do it anyway, calmly, now — because the alternative is doing it in a panic, after the person has already gone, with no time and no goodwill to recover what they knew.

Defusing it: spread the knowledge, do not hoard it

Once you have the list, the fix is to move critical knowledge out of single heads and into places and people where it is shared. The tools are ones I have written about before, pointed at this specific risk:

• Document the critical functions. The procedures only one person knows get written down — not perfectly, just enough that a competent colleague could pick them up. The decision logs, the onboarding-style "how this works" notes, the access lists. This is the durable defence: knowledge in writing survives any departure.
• Cross-train deliberately. For the most critical functions, make sure at least two people can do each. This is not distrust of your key person; it is basic resilience. Rotate, pair, have the second person actually do the task occasionally so the knowledge is live, not theoretical.
• Document the relationships, not just the procedures. The hardest handovers are not technical — they are relational. The supplier who trusts one specific person, the client who deals only with them. Capture the context of these relationships and, where you can, broaden them so the business's relationship does not rest entirely on one individual's rapport.

The conversation about hoarding

One delicate point. Sometimes knowledge concentration is not accidental — a person has, consciously or not, made themselves indispensable by keeping what they know to themselves, because being the only one who can do something feels like security. This is human and understandable, and it is also dangerous to the business and, ultimately, to them.

The way through is culture, not confrontation. Make sharing knowledge something the business visibly values and rewards, rather than something that threatens a person's standing. Reassure your key people that documenting what they know makes them more valuable, not more replaceable — because it frees them to grow into bigger work instead of being trapped forever guarding the one thing only they can do. The person hoarding knowledge out of insecurity needs to be shown that openness is the safer path for them too. Handled well, defusing the single point of failure is good for the company and a relief for the person who was carrying it alone.

What to do this week

Run the exercise. List your business's critical functions and, for each, ask whether you would survive the sudden loss of the person who handles it. Pick the single scariest "no" — the function whose loss would hurt most — and start there: have that person document it, this month, and have a second person learn enough to cover it.

You will not close every gap at once, and you do not need to. You need to stop being one resignation away from a crisis in your most critical function. The handover problem is not a matter of if; it is a matter of when, and whether you prepared. Prepare while everyone is still here and still willing. That window does not stay open.