Capturing Tribal Knowledge Before It Walks Out the Door

Chapters 2 through 4 assumed you already know what needs documenting. This chapter covers a harder problem: knowledge that only exists in one experienced person's head, never written down anywhere at all. This is the more extreme version of Chapter 1's own central claim — here there isn't even a flawed document to fall back on, only what one person happens to remember.

Why This Is a Real, Common Risk

An experienced technician often "just knows" how to handle a specific recurring quirk without ever having written it down — it works fine as long as they're around, and becomes a serious gap the moment they're not, whether that's a resignation, a transfer, or simply being unreachable during an incident that happens to hit while they're on leave.

Why Simply Asking Isn't Enough

People are notoriously bad at fully verbalizing procedural knowledge they perform automatically — steps that have become second nature get silently skipped when someone's asked to just describe what they do, not because they're hiding anything, but because they genuinely stop consciously noticing those steps.

Watch, Don't Just Ask

The single most effective technique is watching someone actually perform the task and writing down what they actually do — not what they said they'd do beforehand. The gap between the interview answer and the observed reality is often exactly where the missing documentation was hiding all along.

Two Questions That Draw Out the Rest

• "What would you do if X specific thing went wrong?" — asked for several plausible failure variations, this draws out troubleshooting and rollback knowledge (Chapter 4's own territory), which tends to be the most tribal knowledge of all, since the failure paths are rehearsed far less often than the happy path
• "How would you know if this actually worked?" — draws out verification knowledge (also Chapter 4's own territory) that experienced people often check unconsciously without realizing they're doing it at all

Timing: This Is Proactive Work, Not an Emergency

Waiting until someone announces they're leaving is often too late to do this thoroughly — a rushed knowledge-transfer exercise days before someone's last day rarely reproduces the depth a calm, ongoing capture process would. This works best as a routine part of normal operations, not a crisis response.

Whose Knowledge to Prioritize

Start with the people who've been in a specific role or system the longest, and specifically anyone who's the only person who knows how to do a particular task — a genuine single point of failure in the team's own knowledge, worth identifying and addressing deliberately rather than discovering by accident when they're unavailable.

From Notes to a Real Document

Once captured, interview and observation notes are raw material, not a finished product — they still need to become an actual runbook or KB article, following Chapter 2's own document-type distinction and Chapters 3–4's own writing and structural principles, not left sitting as unstructured notes nobody else can easily use.

Hands-On Exercises