Get tribal knowledge out of one person's head

Signs you have a tribal knowledge problem

• There is a person everyone goes to when something odd happens.
• One person does the pricing, the scheduling or the billing and nobody else can.
• When that person is on vacation, work piles up or gets done wrong.
• New hires are told to ask a specific person instead of looking anything up.
• You have thought about what happens if they quit, then decided not to think about it.

Why it builds up

Tribal knowledge builds up because the fastest way to get something done is to ask the person who knows. Each answer saves five minutes and costs you a little more dependence. Over years, the knowledge concentrates in a few long tenured people, often the ones who are also the busiest.

It is common. Panopto (2018) found 42% of institutional knowledge is unique to one person. And people leave for reasons you cannot control: Work Institute (2025) lists career growth as the top exit reason at 18.9%.

What it costs when it walks out

When a key person leaves, you lose more than a seat. Customers notice slower answers. Mistakes go up while others guess. Senior people get pulled in to rebuild what was lost. And the replacement takes far longer to ramp because there is nothing to learn from except the people who are left.

Even without a resignation, the cost shows up daily in interruptions. The expert's own work slows down because they are the help desk for everyone else.

Build a simple risk map

1. List key people. Up to ten people whose absence would hurt most.
2. Count their tasks. For each, list the critical tasks only they do.
3. Score it. For each task: is it documented, is anyone cross trained, and how likely is this person to leave in the next year?
4. Capture first. Start with undocumented, single person tasks held by people with any flight risk.

The free Tribal Knowledge Risk Map worksheet walks through it.

What good looks like

When tribal knowledge is under control, every critical task has two people who can do it and a short document that a third person could follow. Your experts still hold the judgment, but the routine parts of their work are written down and taught. When someone goes on leave, the work continues at a slightly slower pace instead of stopping.

The test: pick your most knowledgeable person and ask what would break if they were gone for two weeks starting tomorrow. If the answer is a short list with a backup for each item, you are in good shape.

How we fix it

We spent years codifying frontline knowledge for large operations, and the method scales down well.

• Key person risk map across the roles that matter most.
• Structured extraction: interviews plus shadowing, because experts skip steps when they describe their own work.
• Short SOPs and training modules written from what was observed, then tested by someone else doing the task.
• A cross training plan so every critical task has a second person.
• A named successor who owns the knowledge system after handover.

The goal is not to make anyone replaceable. It is to let your experts take a vacation and spend their time on the work only they can do.

Questions owners ask