Why this is harder than it sounds

The instinct is to hand your most knowledgeable person a blank document and say “write down how you do this.” You’ll get back a thin list of obvious steps and none of the value. Not because they’re holding back — because they genuinely can’t see what they know.

It’s called the curse of expertise. When someone has done a thing ten thousand times, the hard parts have become automatic. They skip right past the judgment calls, the exceptions, and the “obviously you’d never do it that way” moments — the exact parts that are worth capturing. Ask them to document it and they’ll give you the skeleton and leave out the brain.

So you can’t just ask. You have to extract.

The wrong way

A blank template and a deadline. “Write your SOPs by Friday.” You’ll get steps written from memory, with no exceptions, no reasoning, and no way to tell which parts actually matter. It satisfies the checkbox and helps no one. A binder full of these is how businesses end up believing they’re documented when they’re not — documentation alone doesn’t equal stability.

The right way: watch, then ask why

The reliable method is to capture the work as it happens, with someone else driving the questions.

  1. Watch real work, not a description of it. Sit with the person while they do the actual task on a real case — not a clean demo. The messy real version is where the knowledge lives.
  2. Ask “why” at every fork. Every time they make a choice — skip a step, double-check something, handle this customer differently — stop and ask why. That answer is the part you’re really after.
  3. Have a non-expert capture it. The person who doesn’t know the process is better at writing it down, because they have to ask about the things the expert would assume. Pair them up.

Document the decisions, not just the steps

A list of steps tells someone what to click. It doesn’t tell them what to do when reality doesn’t match the steps — which is most of the time. The durable version captures the judgment:

A process documented at the level of decisions survives a new hire. A process documented as clicks falls apart the first time something unusual happens.

Capture the exceptions on purpose

Ask directly: “When does this not work? When do you break the rule?” Experts handle exceptions so smoothly they forget exceptions exist. Those edge cases are usually where the real institutional knowledge sits, and they’re the first thing a replacement gets wrong.

Keep a running list of them as you go. It will be the most valuable page in the whole document.

Keep it usable, or it dies

Two more things, or the work is wasted:

  • Give it a home people actually open. A document buried in a drive nobody checks is the same as no document. It belongs where the work happens.
  • Name someone to keep it current. Processes drift. Without an owner, your documentation is accurate for about a month and then quietly becomes fiction.

The goal was never “we have documents.” It’s knowledge the business can use without the original person in the room.

Where this fits

Extracting one person’s process is doable on your own. Knowing which processes are worth the effort — the ones that would actually hurt if they walked out the door — is harder to judge from the inside. That prioritization is a core part of an operations diagnostic. If you’ve got knowledge trapped in a few key heads and aren’t sure where to start, a short strategy session will help you aim the effort at what matters first.