When one person is the only one who knows, the business is running on a single unrecorded copy of its own operation. The day that person is sick, on leave, or gone, the work does not slow down gracefully — it stops, while customers wait and staff guess.

What actually happens when the only person who knows leaves?

It rarely looks like a catastrophe. It looks like a bad week.

  • The WhatsApp group goes quiet because the replies used to come from one person at 18:00.
  • Jobs get quoted from memory, and the quotes are wrong by the amount that used to be corrected without thinking.
  • A supplier relationship stalls because the contact, the history and the terms were all in one head.
  • Your best people absorb the gap, work longer hours, and start interviewing elsewhere.
  • Two to six weeks later you realise you cannot even work out what you lost.

The financial damage is real, but the harder problem is that you cannot price it. There is no document to hand an insurer, no process to hand a buyer, and no way to tell a new hire how long this should take.

How do you find out which knowledge is trapped in a person?

Write one list: for every role in the business, the name of the person who would have to be next to the new person for that job to happen correctly. Anyone who appears more than once is a risk, and anyone who appears on every list is the risk.

Then score each one by reach and by how long a replacement would take:

What the person holdsWho is affected if they are unavailableHow long to replaceScore
Client pricing rulesEvery quote, every margin decisionDays to guess, weeks to fixCritical
Machine or plant setupProduction stops entirelyMonths, if parts must be sourcedCritical
Supplier contacts and termsOrdering, disputes, deliveriesDaysHigh
The maintenance scheduleCompliance and breakdownsWeeksHigh
Who can be trusted to open the shopTrading hours, securityDaysHigh
Historical customer grievancesReputationHard to rebuildMedium
The standard morning checklistQuality, overtimeDaysMedium

Score it, do not guess it. Reach times difficulty is the only ranking that matters: a low-difficulty item that affects everyone is still urgent.

How do you run the "walk out the door" test?

Sit down with the person and ask one question: if you were not here tomorrow, what would stop working within the first week? Push until you reach specifics, because the first answer is always "nothing much".

  • What is the first task you do every morning, in order?
  • Which three customers do you handle differently from the rest, and how?
  • What do you check that nobody has ever thought to write down?
  • What do you know that would surprise a new person?
  • If you got hit by a bakkie on the way to work, what would nobody else know to do?
  • What are you asked most often that you have answered so many times you no longer notice?

Answer those six questions and you have the outline of a process. Twenty questions and you have most of one.

Do it kindly and do it while they are still there. This is not a performance review. Say that, or the exercise becomes a resignation letter.

How do you capture knowledge from someone who hates writing?

Nobody who is good at a job enjoys writing about it. Make writing optional and recording mandatory.

  • Record a voice note while they work. Twenty minutes per process, in the workshop, on site, in the van. The ambience does not matter.
  • Type it up yourself the same day. Their words, not yours. Being listened to carefully is a better experience than being asked to produce prose.
  • Send it back with one question: what did I get wrong? People correct their own words far more willingly than they produce new ones.
  • Add the photographs while you have the moment, taken on the actual site with the actual tools.
  • Do one process per session. Thirty minutes a week for a month is a habit. Three hours in one afternoon is not.

The test of capture is simple: hand the page to someone who has never done the job and see whether they can do it without phoning anybody.

What about WhatsApp groups, voice notes and photographs?

In a small business most institutional knowledge already exists, in the wrong format. A WhatsApp group is a searchable archive nobody can search. A voice note is a procedure with no index. A photograph of a labelled shelf stops working the moment somebody moves a bottle.

Convert them, do not migrate them:

  • Anything asked in a group more than twice becomes a one-page written answer, pinned in the group as text.
  • Keep voice notes only for instructions that need a demonstration, and add a two-line text summary above them.
  • Photograph the actual layout of your own workshop, van and stock shelf. Label the photo itself with what matters.
  • Keep one place for answers, not twelve. A search box beats a folder tree.
  • Anything read at 05:30 in the dark from a van seat also needs a printed copy in the cab.

At Midlands Berry Farm, a 60-person operations team, the knowledge that had been sitting with individuals was turned into answers anyone could open — cutting onboarding from four weeks to four hours, 3x faster onboarding, 40% more time saved, and answers available at any hour.

Which processes should you document first?

Not the important ones. The expensive ones. Rank by how often a wrong answer costs you something.

Start with the things that satisfy customers directly, because a mistake there is visible and expensive: pricing, quoting, the client you handle differently, the complaint you get every month. Then the things that stop money arriving: invoicing, banking access, the backup restore. Then the things that stop the business trading at all.

Leave alone, for now, anything done once a year. It can wait until it nearly kills you.

How do you know the knowledge has actually left the person's head?

Three checks, none of them a survey.

  • The handover test. Can the person who is not the expert do the task, on a normal day, without phoning the expert? If not, the knowledge is still in the head.
  • The error rate. Count the corrections your best people make for new people each month. That number should fall as the written process improves. If it does not, your written process is wrong, not your staff.
  • The leave test. Book two weeks of leave for the person and see what actually breaks. It is far cheaper than a resignation, and the closest thing to a real rehearsal you will get.

What is the cheapest insurance against losing a key person?

Not a policy. A habit. Spend one hour a week, permanently, capturing what one person knows. That is roughly a day per quarter, and it is the difference between a business that absorbs a departure and one that stops.

If you would rather find out which of your processes are single-threaded before it costs you, book a free strategy session and we will work through it with you.