How to Document Processes Before Your Best Employee Quits

You know who this person is. Every company has one.

They're the one who "just knows" how to handle the weird edge case in billing. The one who has a relationship with that difficult vendor. The one new hires are told to "ask Sarah, she knows everything."

Sarah is a single point of failure. And she will leave eventually.

Not because she's unhappy (though she might be). Because that's what people do. They get a better offer, move cities, start their own thing, retire, have a baby, burn out. The reason doesn't matter. What matters is that the day Sarah leaves, years of institutional knowledge walk out with her.

The time to prevent this is not during her two-week notice. It's right now.

Why This Doesn't Happen Naturally

Every manager knows they should document processes. Almost nobody does it well. Here's why:

"We're too busy." The people who know the most are also the people doing the most work. Asking them to stop working and write documentation feels like asking them to stop producing value — which, in the short term, it is.

Documentation is boring. Nobody went into operations, accounting, or project management because they love writing SOPs. The task gets deprioritized perpetually because it's important but not urgent.

Experts don't know what they know. The most dangerous knowledge is unconscious competence — the things Sarah does automatically that she can't articulate because she doesn't realize she's doing them. She doesn't think of "how she handles vendor disputes" as a process. It's just... what she does.

Written docs go stale. Even when someone writes a great process doc, it's outdated within six months. Processes evolve, tools change, exceptions get added. Nobody updates the wiki.

The Extraction Framework

Stop thinking about "documentation" as a project. Think about it as knowledge extraction — an ongoing practice, not a one-time effort.

1. Identify Your Key-Person Dependencies

Make a list of every person on your team. For each one, ask:

If they were gone tomorrow, what would break?
What do they know that nobody else knows?
What questions does the team ask only them?

The answers reveal your risk map. The people with the longest lists are your biggest vulnerabilities.

2. Shadow, Don't Interview

Asking an expert "can you write down how you do X?" produces bad documentation. They'll skip steps they consider obvious, use jargon they don't realize is jargon, and miss the edge cases that are actually the hard part.

Instead, shadow them. Watch them work. Ask "why did you do that?" in real time. Record the conversation (with permission). The gap between what people think they do and what they actually do is enormous.

AI tools have made this dramatically easier. Services like Understudy can capture these conversations and turn them into structured playbooks automatically — no writing required from the expert.

3. Focus on Decisions, Not Steps

The most valuable part of any process isn't the steps. It's the decision points.

"Enter the data into the spreadsheet" is a step anyone can follow. "When a vendor disputes an invoice over $5,000, escalate to finance; under $5,000, handle it yourself unless the vendor has a history of disputes, in which case loop in the account manager" — that's the knowledge that actually matters.

Document the if/then logic. The judgment calls. The "it depends" moments. Those are what make Sarah irreplaceable, and they're what you need to capture.

4. Build It Into the Workflow

Documentation shouldn't be a separate activity. It should happen as part of doing the work.

New process? Document it as you build it.
Exception handled? Add it to the playbook.
Question asked twice? Write the answer once, link to it forever.
Mistake made? Update the process so it doesn't happen again.

The goal is to make documentation a reflex, not a project. When "write it down" is part of how work gets done — not something tacked on after — it actually stays current.

5. Test the Documentation

Here's the brutal test: can someone else follow your documentation and produce the same result?

Hand the process doc to someone who has never done the task. Watch them try. Where they get stuck, the documentation has a gap. Where they make a wrong decision, the decision framework is incomplete.

This is uncomfortable. It reveals how much undocumented knowledge exists. But that discomfort is exactly the point — you're finding the gaps now, while Sarah is still around to fill them, rather than after she's gone.

The Cost of Waiting

The Society for Human Resource Management puts the cost of replacing a mid-level employee at 6–9 months of their salary. But that number only captures hiring and ramp-up costs.

It doesn't capture:

The client relationship that weakened because nobody knew the history
The process that broke for three weeks until someone figured out Sarah's workaround
The vendor who stopped giving you preferential pricing because Sarah was the one who negotiated the deal
The new hire who made a $40,000 mistake because nobody told them about the exception to the standard procedure

Undocumented knowledge doesn't just disappear when someone leaves. It decays — slowly, invisibly, expensively.

Start With One Person

You don't need to document everything at once. Pick the person who represents your biggest risk — the one where you feel a knot in your stomach when you imagine them giving notice — and start there.

One hour of shadowing per week. One process captured per session. In a month, you'll have the critical stuff covered. In three months, you'll have built a habit that compounds.

The best time to start was a year ago. The second best time is before their LinkedIn profile suddenly gets a new headshot.

Understudy captures your team's knowledge through conversation — no writing required. Turn what your best people know into playbooks your whole team can use. See how it works →

Related Resources

Understudy for your industry:

See how Understudy compares: