Capture Tribal Knowledge Before a Key Tech Leaves

Why this matters

Every shop has one or two people who carry critical knowledge only in their heads: which customers have the weird panel, where the shutoff is at the old commercial accounts, the workaround for the equipment line that always fails the same way. The day that person retires, quits, or gets hurt, that knowledge walks out the door, and you relearn it the expensive way through callbacks and angry customers. You cannot wait for a two-week notice to start capturing it. This is how to pull the knowledge out before you need it, and faster when you are out of time.

Step 1: Identify who holds what before there is a crisis

Do not wait for a resignation. Once a year, ask a blunt question about each experienced person: if this person vanished tomorrow, what would we not know how to do? List the gaps. Common buckets:

• Tricky accounts and their quirks (access, history, who to ask for).
• Workarounds for recurring equipment problems.
• Relationships: which supplier rep actually picks up, which inspector wants what.
• Undocumented "the way we do it here" steps that never made it into any SOP.

The people with the longest gap lists are your highest knowledge-risk. They get captured first.

Step 2: Capture in the format that costs the least friction

The fastest capture method is the one the tech will actually do. Ranked by ease:

1. Record them working and talking. Have them narrate a real job or a real account walk-through on their phone. Five minutes of "here is the thing you have to know" beats an hour of them staring at a blank document.
2. Interview them and you write it down. You ask, they talk, you draft. Removes the writing burden from the person who hates writing.
3. Have them brain-dump into a list. For people who write fine, just "list everything a new person would get wrong on your accounts."

The goal is extraction, not polish. Get it out of their head and into a file. Clean it up later.

Step 3: Use a question set that surfaces the hidden stuff

People do not know what they know. The right questions pry it loose. Ask:

• "Walk me through a job where everything went sideways. What did you know that saved it?"
• "What do you check that the manual does not tell you to check?"
• "Which customers or sites would trip up a new tech, and why?"
• "What do you wish someone had told you on day one?"
• "Who do you call when you are stuck, inside and outside the company?"
• "What is the workaround for the thing that always breaks?"

These open-ended prompts get you the judgment and the shortcuts that no checklist captures.

Step 4: Prioritize by risk when the clock is running

If the person has already given notice, you cannot capture everything. Triage hard:

• Capture first: anything that is high-frequency and only-they-know. The daily and weekly stuff with no backup.
• Capture second: high-stakes rare events where getting it wrong is expensive or dangerous.
• Skip or accept loss: rare, low-impact knowledge you can relearn cheaply. Let it go and spend the time on the critical items.

Spend the limited days on the knowledge that will hurt the most to lose.

Step 5: Pair them with a successor while they are still here

Documents capture facts; a person captures judgment. If you can, assign the departing tech a shadow for their final weeks. Have the successor do the work with the veteran watching and correcting. Even a few ride-alongs transfer pattern recognition that no document can. The veteran's job in their last weeks shifts from production to teaching, and that is the right trade.

Step 6: Bank it where the next person will find it

Captured knowledge that lives in a folder nobody opens is lost again. Put it where it gets used:

• Account quirks go on the customer record, not in a side document.
• Equipment workarounds go in the knowledge base under the equipment type.
• Process steps go into the relevant SOP.

If it is searchable from where the work happens, the next person will find it. If it is a standalone file titled "Mike's notes," it disappears.

Step 7: Make capture a habit, not a fire drill

The real fix is to stop letting knowledge accumulate only in heads. Build small habits: when a tech solves a nasty problem, they add a short note to the knowledge base. When an account has a quirk, it goes on the record that day. A shop that captures continuously never faces the all-at-once panic.

References

• See related: Your First Operations Manual: What to Document First
• See related: Document a Process at the Right Level of Detail
• SBA guidance on small-business succession and continuity planning
• Trade-standard practice for technician onboarding and knowledge transfer