All posts

How to Document Processes Before Someone Leaves (A Realistic Guide)

Your best employee just gave two weeks' notice. They run three critical processes that nobody else understands. You have 10 business days to extract everything in their head before they're gone.

Most "knowledge documentation" guides assume you have months. You don't. Here's the realistic playbook.

Why Traditional Documentation Fails Under Pressure

The standard advice is: "Have them write everything down." This fails for three reasons:

  1. People can't articulate what they know. Experts operate on autopilot. Ask a 15-year accounts payable person to document their process and they'll give you 20% of what they actually do. The other 80% is muscle memory — workarounds, judgment calls, exception handling — that they can't even identify as "knowledge."

  2. Writing takes forever. A thorough process document takes 4-8 hours per process. If someone runs 10 processes, that's 40-80 hours of writing. In two weeks, while they're still doing their actual job and wrapping things up? Not happening.

  3. Documents go stale immediately. A 30-page process guide written in week one is partially outdated by week three. Systems change, contacts change, exceptions pile up. Static documents are born dying.

The 10-Day Knowledge Extraction Plan

Days 1-2: Map the Territory

Don't start documenting yet. Start by cataloging. Sit with the departing employee for 30 minutes and ask:

  • "What do you do every day that nobody else does?"
  • "What do you do every week/month/quarter?"
  • "Who calls you when something breaks?"
  • "What passwords/logins only you have?"
  • "What would break if you disappeared tomorrow?"

Write down every answer. You now have a knowledge inventory — a list of everything that needs to be captured.

Days 3-7: Interview, Don't Write

Here's the counterintuitive part: don't ask them to write documents. Interview them instead.

For each critical process:

  1. Have them walk through it while you (or a replacement) watch
  2. Record the session (screen recording + audio)
  3. Ask "why" at every decision point
  4. Pay attention to the moments where they say "oh, and you also need to..." — those throwaway additions are the most valuable knowledge

This is dramatically faster than writing and captures the stuff they'd never think to document.

Days 8-9: Fill the Gaps

Review your recordings and notes. Identify gaps — the "what if X happens?" scenarios that didn't come up during walkthroughs. Go back to the departing employee with specific questions:

  • "What happens when [vendor] is late?"
  • "How do you handle [edge case]?"
  • "Who do you call when [system] breaks?"

Day 10: Create the Safety Net

You won't capture everything. Accept that. Instead, ensure:

  • Their contact info is saved (most people will answer a question or two after leaving)
  • All passwords and accesses are transferred
  • The most critical processes have at least a recorded walkthrough
  • Someone is designated as the "owner" for each orphaned process

The Better Approach: Don't Wait for the Two-Week Notice

The scenario above is damage control. The real solution is capturing knowledge continuously — before anyone gives notice.

This is what Understudy does. It conducts AI-powered interviews with your team members, asking the right questions to extract the processes, workarounds, and context that live in their heads. Not as a one-time emergency project, but as an ongoing practice.

Think of it like insurance: you don't buy fire insurance while the building is burning. You buy it when things are calm.

The Cost of Waiting

The average cost of replacing an employee is 50-200% of their annual salary. A huge chunk of that cost isn't recruiting or training — it's the productivity gap while the new person figures out what the old person knew.

If a $60K/year employee leaves and it takes their replacement 6 months to reach full productivity, that's $30K+ in lost output. Multiply that across an organization with normal turnover rates, and you're looking at hundreds of thousands in invisible costs.

Or you could capture the knowledge before it walks out the door.

Try Understudy free →


Related Resources

Understudy for your industry:

Get early access to Understudy

Turn your team's tribal knowledge into structured playbooks. Join the waitlist — we're onboarding teams now.