7 signs tribal knowledge lives in one person's head

You know the feeling before you can name it. A question comes up in a meeting and every head turns to the same chair. Not because that person is the most senior or the loudest, but because they're the only one who knows.

Key takeaways

• Tribal knowledge is know-how held by one person or a small group that was never written down.
• The signs show up in daily work: paused meetings, "ask Priya" steps, onboarding that is only shadowing.
• Each sign is a cost you pay in full when that person leaves.
• If you recognise three or more, capture what they know in their own words while they are still here.

That's tribal knowledge: the know-how a team runs on that nobody wrote down. The workarounds, the reasons behind old decisions, who to call when something breaks. It doesn't show up on an org chart. It shows up in the ten seconds of silence after someone asks, "Wait, how does this actually work?"

Here are seven signs that too much of your team's tribal knowledge sits with one person. One on its own is normal. If you recognise three or more, start now, while that person is still here.

1. The meeting pauses when one person is out

The Tuesday stand-up runs long because the person who normally unblocks things is on holiday. A decision that should take four minutes takes forty. Everyone waits, politely, for the answer to arrive by message.

That pause is the sign: the work is waiting for one person.

2. "Ask Priya" is a real process step

Somewhere in a runbook, a checklist or a Slack channel, there's a line that says, more or less: check with the person who has been here the longest.

It might even be written down that way. When a human name is a documented step, you've turned a person into infrastructure. Infrastructure gets upgraded. People resign.

3. Onboarding means shadowing, not reading

A new hire spends the first week following someone around, taking notes and asking the same questions three times. There is no guide. There is a guide-shaped person.

Shadowing is good. But when it's your only method, the knowledge never lands anywhere that lasts. It lands in the new hire's head, half of it, badly.

4. Two people give different answers to the same question

Ask how the discount approval works and you get one answer from sales and a different one from ops. Neither is lying. Both are working from memory of a system that was never written down.

When the answer depends on who you ask, what you have is folklore.

5. One absence costs a whole day

A production run stalls. A shipment goes out wrong. A client call goes sideways. Afterwards the story is familiar: the one person who knew the workaround was unreachable, and nobody else could work it out.

This is the clearest sign of all. It happens on production lines as often as in offices, and it costs a full day of work because one person was away.

6. Nobody can explain the workaround

There's a step in your process that exists only because something broke two years ago and someone fixed it in a hurry. Everyone uses it. Nobody can say why it's there.

That workaround is tribal knowledge in its purest form. It survives on habit alone. When the person who set it up leaves, the reason goes with them, and the original problem comes back.

7. Departures come as a shock, then a scramble

The resignation email arrives. It's warm, professional and gives a month's notice. Within an hour a small panic begins. Someone starts a document titled "Things only Marcus knows" and it grows all afternoon.

That scramble is where the real cost shows up: in the weeks after the goodbye.

What it costs when that person leaves

On their own, these signs are an inconvenience. Together, they carry a price you pay in the weeks after a departure.

• Ramp-up takes longer. The successor rebuilds relationships and context that used to be handed down.
• Decisions slow down. Without the person who "just knew", everything gets argued again.
• Clients feel it. The new contact asks questions the client already answered, and a quirk that was fine for years starts to look like a problem.
• Morale dips. The team sees how much one exit disrupted and starts wondering who is next.

You don't need all seven signs to have a problem. Most teams recognise three or four. For a number that fits your own team, count the cost of one departure.

How to capture tribal knowledge before someone leaves

The instinct is to build a giant knowledge base. Don't. Most of those projects stall long before they're finished, and they teach everyone that documentation is a chore.

Start smaller, and start with the person.

1. Pick the one role that would hurt most to lose this quarter.
2. Sit with that person and ask what a successor would need on day one. Not everything they know, just what would unblock someone else.
3. Capture it in their own words, in conversation, while they're still there to correct you.
4. Review it with the successor and the manager, then keep it somewhere people actually search.
5. Do the next role. Then the next.

You're not trying to write everything down. You're making sure a departure takes the person and leaves behind the way everything worked.

What OakHive does

OakHive is knowledge transfer software. Before someone leaves, an AI interviewer talks with them about the work, by voice and in their own language. No script, no form to fill in. What comes back is a handover guide for the successor, a summary for the manager that lists what wasn't covered, and a chat the team can ask questions, in OakHive or in Microsoft Teams. See how it works.

Start with the person you'd miss most. The best time to capture what they know is while they're still here to tell you.

Frequently asked questions

What is tribal knowledge?

Tribal knowledge is the know-how a team depends on that was never written down: workarounds, the history behind decisions, and who to ask when something breaks. It lives in people's heads, so it leaves when they do.

How do you capture tribal knowledge before someone leaves?

Interview the person about their work while they're still there, in their own words, and focus on what a successor needs on day one. Then review it with the successor and the manager, and keep it where the team actually looks.

How long does a handover interview take?

With OakHive, up to two hours, in one sitting or a few shorter ones, with nothing for the person leaving to prepare. Smaller roles finish well inside that. More answers in the FAQ.