What Happens When the One Person Who Knows Is Out?

← All Posts

If one person in your business is the answer to a category of question, you already know it, because everything in that category stops when they are out. That is not a succession problem you deal with someday. It is a Tuesday problem.

Most owners think about this as retirement. It shows up long before that. It shows up when they take a vacation, sit on a jury, get the flu, or win the lottery and text you from a beach.

Signs you have this

• A question gets asked and three people say "ask Dave"
• Work waits until someone gets back, and nobody thinks that is strange
• Somebody's vacation gets quietly scheduled around a busy season, not around their family
• A new hire takes months to become useful because the answers are not anywhere
• You have written procedures, and everyone knows they do not match what actually happens
• One person is doing a task that is technically below their role because retraining someone would take longer

Panopto's study of more than a thousand workers found that 42% of institutional knowledge is unique to the individual who holds it, meaning coworkers cannot do that portion of the job when that person leaves or is simply unavailable (Panopto).

Not gone forever. Just out today.

What is actually stuck in their head

It is rarely facts. Facts are the easy part and they are usually written down somewhere.

What is stuck is judgment:

• Which exception is fine and which one is a problem
• Which customer gets a call instead of an email
• What to check first when a thing goes wrong
• Which supplier to use when the usual one cannot deliver
• What the number should look like, so a bad one gets noticed
• Which rule to bend, and when

That is the part that took them fifteen years to learn, and it is the part no procedure document ever captures.

Why writing it down usually fails

Most businesses have tried this. It produced a folder nobody opens.

• It gets written once, during a slow week, and goes stale within a quarter
• It documents the steps, not the decisions, so it answers what but never which
• It is written by the person who already knows, so it skips everything obvious to them
• Nobody can find the right page at the moment they need it
• It never gets used in real work, so the gaps stay invisible

The problem was never that people would not write things down. It is that a document is a poor shape for judgment.

What works better

Capture the decisions, and let people ask questions instead of hunting through files.

• Start from the questions actually being asked. Every "go ask Dave" is a real entry
• Capture the reasoning, not just the answer. Why that supplier, why that threshold
• Build it from real work, in the moment, rather than in a documentation sprint
• Let people ask it in plain language, the way they would ask the person
• Keep one person responsible for what goes in, so it stays authoritative
• Let the expert correct it in seconds when it drifts, which improves it permanently

That last one matters more than it sounds. A system your expert can correct in passing stays true. One that requires a project to update goes stale like everything before it.

What should stay with the person

Not all of it should be captured, and a consultant who says otherwise is selling something.

• The relationship. The customer who calls Dave calls Dave
• The judgment that is still forming, on a process that is genuinely changing
• Anything where being mistaken damages trust rather than costing time
• The decisions that are the person's actual job, not their overhead

The goal is not to replace the person. It is to stop the business from stopping when they are out.

Where to start

Pick the single question your team asks that one person most often. Not the most important one. The most repeated one.

Capture how they answer it, including why. Let two people use it for a week. If it saves them a trip down the hall, you have your pattern, and you can do it again with the next question.

If you are looking at this across a whole business rather than one person, the wider version is what AI actually does department by department, and choosing which project to start with covers how to pick.