When the person who knows leaves

Every small operation has one. The person who knows which supplier invoices always arrive wrong, which client pays late but pays, and what the workaround is for the thing in the system that has never worked properly.

While they are there, this looks like competence. The month closes, the payroll runs, nobody has to ask. It only looks like risk on the day they give notice, and by then you have two weeks to extract several years of undocumented judgment from somebody who is already thinking about their next job.

It is a documentation problem, not a hiring problem

The instinct is to hire earlier, or to keep the person happier. Both are reasonable and neither fixes it. A second hire who also keeps it in their head just gives you two single points of failure.

What actually removes the risk is boring: the work written down while it is being done, by the person doing it, in enough detail that someone competent but new could follow it. Not a policy document. A runbook, in order, with the exceptions listed.

Write down four things

For any recurring piece of work, capture:

1. The steps, in order. What happens first, what happens next, what finishes it.
2. The exceptions. The supplier who invoices differently. The client who needs the extra reference. The step you skip in the last week of the quarter.
3. The judgment. Where the person decides rather than follows, and what they weigh. This is the part that never gets written down and the part that costs the most to lose.
4. Where it lives. Which login, which folder, which inbox, and who else has access today.

If you only do one, do the exceptions. Steps can be reconstructed by watching. Exceptions are invisible until they bite.

Test it before you need it

A runbook nobody has used is a guess. The test is simple: have somebody else run it once, from the document, while the usual person stays quiet and takes notes on everything they had to ask.

Whatever they had to ask is the missing part. Add it, and run it again next cycle. Two rounds of that and the work is genuinely portable.

What this looks like when it is working

Cover is not a person on standby. It is a documented process plus somebody who has actually run it. In our own delivery that means an account manager who knows the work, a second person who has run it at least once, and the runbook that both of them follow, which is why an absence or a resignation does not become your problem.

You can build the same thing internally. It costs a few hours per process, once, and it turns your most valuable person from a risk into what they should have been all along: someone whose knowledge is in the business rather than only in their head.