Your Best Employee Just Gave Notice. Now What?
The email hits your inbox on a Thursday afternoon. Two weeks notice. Your best engineer, your operations lead, the person who's been holding three systems together with duct tape and deep knowledge — they're leaving.
You have 10 business days to capture what took them 3 years to learn.
Don't panic. But also don't waste time.
The first 48 hours
Don't start with a knowledge dump. The instinct is to sit them down with a blank doc and say "write down everything you know." This doesn't work. They'll stare at the screen, write some obvious stuff, get bored, and stop. Knowledge dumps produce documents that are simultaneously too long and too incomplete.
Instead, make a list of questions. Ask the team: "What do you ask [person] about?" Ask their manager: "What breaks when [person] is on vacation?" Ask adjacent teams: "What do you depend on [person] for?"
This gives you a targeted list of knowledge to capture, prioritized by what actually matters.
Identify the critical paths. Not everything they know is equally important. Focus on:
- Processes only they can do
- Systems only they understand
- Relationships only they maintain
- Decisions only they can make
If a process is documented elsewhere and other people can do it, skip it. You're triaging.
Week 1: Structured capture sessions
Do 2-3 sessions of 30 minutes each. Not one marathon session. People forget things, then remember them in the shower. Multiple sessions with gaps between them produce better results.
Record the conversations. With permission. You'll catch things in playback that you missed live.
Ask "what happens when..." questions. The edge cases are where the real knowledge lives.
- "What happens when the build fails on this step?"
- "What happens when a customer sends data in the wrong format?"
- "What happens when two people approve at the same time?"
- "What's the dumbest thing that can go wrong, that actually has?"
Don't let them hand-wave. When they say "oh, you just restart the service and it's fine," dig deeper. Which service? How do you restart it? How do you know it's actually fine afterward? What if restarting doesn't fix it?
Week 2: Validation and handoff
Have someone else try to follow the documentation. Not the departing employee — someone who'll actually need to do the work. If they get stuck, the doc is incomplete. Have them note where they got confused.
Do a shadow day. Have the replacement (or whoever will absorb the work) watch the departing employee do their actual job for a day. The mundane stuff — the morning routine, the way they scan alerts, the muscle memory of which dashboard they check first — is hard to articulate but easy to observe.
Get the contact info. After they leave, you'll have questions. Most people are willing to answer a text or two in the first few weeks. Don't abuse this, but don't be too proud to ask.
Tools that help
Understudy is built for exactly this scenario. Instead of blank-page documentation, it runs an AI-guided interview. The departing employee talks about what they do, the AI asks follow-up questions to surface edge cases and decisions, and the output is a structured playbook.
A typical knowledge capture session takes 15 minutes per process. For someone who owns 5-6 key processes, that's under 2 hours total — and you get playbooks that cover steps, decisions, exceptions, and context.
Compare that to asking them to "write everything down" and getting 3 pages of bullet points that miss all the important stuff.
The real lesson
Knowledge capture shouldn't be an emergency. If you're only doing it when someone gives notice, you're already behind.
The fix: make it part of how you work. Every time someone builds a new process, figures out a workaround, or becomes "the person who knows how X works," capture it. Not in a wiki nobody reads — in a conversation that produces something useful.
Two-week notices are a symptom. The disease is assuming institutional knowledge will persist because nobody's leaving right now.
Capture your first process playbook →
Related Resources
Understudy for your industry:
See how Understudy compares: