How to Capture Tribal Knowledge Before You Need It: A Register, a Backup Person, and a 20-Minute Interview

This article is AI-generated.

Every team has things that only one or two people know. How to restart the label printer when it jams. Which customer needs certificates in a particular format. Why a step in the month-end process is done in that odd order. None of it is written down because it never seemed worth writing down, until the person who knows is on holiday, off sick, or gone.

The usual advice is "document everything," which is why it rarely happens. This guide takes a narrower approach: find out what only one person knows, decide which of it matters, and capture it in short, repeatable sessions.

Step 1: Ask the right question to find it

Tribal knowledge is hard to list because people don't notice they have it. Instead of asking "what do you know?", ask questions that surface it:

• "What do people come to you for that they can't get anywhere else?"
• "If you were away for two weeks, what would go wrong first?"
• "What do you do that isn't in any procedure?"
• "Which questions do new starters ask you most often?"

Ask these of each team member in a 15-minute conversation. Write each answer as a short topic, for example "Restarting label printer after jam" or "Certificate format for customer X."

Step 2: Build a knowledge register

Put the topics into one sheet, one topic per row.

Column	Content	How it's filled
A	Topic	Manual
B	Who knows	Manual
C	Backup person	Manual, can be blank
D	Written down?	Y or N
E	Last checked	Date the write-up was last confirmed
F	Status	Formula

Illustrative data (placeholders):

Topic	Who knows	Backup	Written?	Last checked
t1	Ana	Raj	Y	2026-08-01
t2	Ben		N
t3	Cy	Dee	N
t4	Ana	Ben	Y	2025-12-01

Status (F2)

=IF(D2="Y",IF(TODAY()-E2>180,"STALE","COVERED"),IF(C2="","SINGLE POINT","AT RISK"))

• SINGLE POINT: not written down and nobody else knows it. Highest priority.
• AT RISK: not written down, but at least a second person knows it.
• STALE: written down, but nobody has confirmed it in six months. Processes drift; old notes can be worse than none.
• COVERED: written and recently checked.

With 2026-10-15 as today, t1 is COVERED, t2 is SINGLE POINT, t3 is AT RISK, and t4 is STALE because its last check was more than 180 days ago. Change 180 to suit how fast your processes change.

Count the most urgent rows with:

=COUNTIF(F:F,"SINGLE POINT")

Step 3: Prioritise

You won't capture everything, and you don't need to. Add a column for impact, a simple 1–3, and ask: if nobody could do this tomorrow, how bad would it be? Start with SINGLE POINT rows that score 3. A team that captures its top ten topics has done more than one that writes a hundred-page manual nobody reads.

Step 4: Run a 20-minute capture interview

Experts are usually busy, and asking them to "write it up" tends to stall. Instead, have someone else interview them and do the writing. A structure that works:

1. When does this come up? (2 minutes) What triggers the task or question.
2. Walk me through the last time. (8 minutes) Concrete steps, in order. Ask "then what?" repeatedly.
3. What goes wrong? (5 minutes) Common mistakes, warning signs, and what to do about them.
4. Who else is involved? (3 minutes) People, systems, and files you need.
5. What would you tell someone doing it for the first time? (2 minutes) This often surfaces the most useful line in the whole note.

The interviewer writes it up the same day, keeping it short: a title, when it applies, numbered steps, and a "watch out for" section. The expert reviews it, then the register is updated: D becomes Y and E gets today's date.

Step 5: Turn a backup into a real backup

Writing something down is half the job. For SINGLE POINT and AT RISK topics, name a backup person and have them do the task once, using the write-up, while the expert watches. Anything they get stuck on goes back into the note. Then put the backup's name in column C.

Step 6: Keep it alive

• Quarterly: filter for STALE and ask the person who knows to confirm or update each note.
• When someone changes role or gives notice: filter the register by their name. Every row where they are the only person who knows becomes this month's priority.
• When a new starter asks a question twice: check whether it should be a topic in the register.

Common questions

Where should the write-ups live? Wherever your team already looks for documents. A note in a place nobody visits is still tribal knowledge.

What about knowledge that's hard to write down, like judgment calls? Capture the examples. "Last time we saw X we did Y because Z" is far more useful than an abstract rule.

Start with the register and one interview this week. The first SINGLE POINT you close is the one you won't be scrambling for later.