The Closing Guide Series

How to Get Tribal Knowledge Out of People's Heads

The practical method for turning what your best people know into documented processes the whole team can use.


The Reframe

Your best employee is also your biggest risk.

The person who knows everything is the person whose absence would break your business. That knowledge needs to live somewhere other than their head.

Tribal knowledge is the information that exists only because specific people have been doing the work long enough to learn it. The shortcut in the billing system. The client who prefers email over phone. The supplier who gives better pricing if you mention the account number. None of it is written down.

This knowledge accumulates over years and it feels like an asset. It is, until that person leaves, goes on vacation, or gets sick. Then it's a liability. The business suddenly can't do things it's been doing for years because the instructions left with the person.

Extracting tribal knowledge is a structured conversation. You sit with the person, ask them to walk through their most important task, and you write it down as they talk. It takes 30-60 minutes per process. The result is a document that the rest of the team can follow.

The Framework

The knowledge extraction process

Step 1: Identify your knowledge holders

List the people on your team who get asked the most questions. The ones who 'just know' how things work. These are your tribal knowledge risks. Start with the person whose absence would cause the most disruption.

Step 2: Schedule 30-minute walk-throughs

Book time with each knowledge holder. Ask them to walk through their most important recurring task as if they were teaching a brand new hire. Record the conversation (with permission) or take notes in a shared doc.

Step 3: Write the SOP during the conversation

As they talk, write numbered steps in a Google Doc. After each step, read it back and ask: 'If someone followed this step exactly, would they get the right result?' Their corrections become the detail that makes the document actually useful.

Step 4: Test with a non-expert

Give the documented process to someone who has never done the task. Watch them follow it. Where they get stuck is where the document needs more detail. Update and repeat until the process runs without the original knowledge holder.

Take Action

Start here

  1. 1
    List your top 3 knowledge holders. Who does your team go to most often with questions? Write their names down. Next to each name, write the task they're most known for knowing how to do.
  2. 2
    Schedule one walk-through this week. Pick the most critical task from your list. Book 30 minutes with the person who owns it. Bring a blank Google Doc and write as they talk.
  3. 3
    Test the resulting document within 48 hours. Hand it to someone else on the team. If they can complete the task using only the document, you've successfully extracted that piece of tribal knowledge.

Ready to map your processes?

Work with me

6 weeks to map and document your processes across all 4 departments, build SOPs in your existing tools, and layer AI on the parts that are ready. $4,997 for the full engagement.

See how it works →