Skip to content
SkillPass

Tribal Knowledge: Meaning, Examples and How to Capture It

Tribal knowledge is knowledge that a group or a few people in a company have but that is not written down anywhere: workarounds, contacts, exceptions and the reasons behind decisions. It is passed on by asking and watching. That makes it fast and useful, and risky when the people who hold it leave. You capture it by finding the tasks only one person can do, asking that person specific questions, writing the answers down in a usable form and checking them.

Author: Kevin Baur BSc

Published on

Contents
Title card: tribal knowledge, what only a few people know, with meaning, examples, risks and six steps to capture it

Every team has it: the person who knows why the invoice run has to start before 9 a.m., which customer gets special terms that were agreed on the phone years ago, and which supplier only answers on one particular number. None of it is written down. It works fine until that person is on holiday, gets sick or hands in their notice. This guide explains what tribal knowledge is, how it differs from tacit and institutional knowledge, where the risk lies and how to capture it in six steps.

What does tribal knowledge mean?

Tribal knowledge is knowledge that is known within a group but unknown outside it. In a company it usually means everything that is necessary for the work but is not adequately documented. Wikipedia describes it as a subset of institutional memory that survives only through mentoring, apprenticeship, on the job training and continuity of staff. The name is an analogy to tribes as studied in cultural anthropology, where knowledge is passed on by telling and showing rather than by writing.

Typical features:

  • Undocumented: it lives in heads, chat messages and habits, not in a manual or a system.
  • Held by few: often one or two people, sometimes a single team.
  • Passed on informally: by asking, by watching and by "let me just do it for you".
  • Not always correct: some of it is a proven shortcut, some of it is a habit nobody has questioned.

The term comes up in many kinds of teams, and the Six Sigma community uses it for knowledge that is "known" but has never been checked with data. If you prefer a more neutral term, institutional knowledge or undocumented knowledge describe much the same thing.

Tribal knowledge vs tacit, explicit and institutional knowledge

The terms overlap, but they look at knowledge from different angles. Tacit and explicit describe whether knowledge can be put into words. Tribal and institutional describe who holds it.

Four related types of knowledge
TermWhat it meansCan it be written down?Example
Tribal knowledgeKnown inside a group, not documentedOften yes, nobody has done it yetWhich export settings the month end report needs
Tacit knowledgePersonal know how that is hard to put into wordsOnly in partHearing that a machine is about to jam
Explicit knowledgeKnowledge that is documented and shareableIt already isA written procedure in the SOP folder
Institutional knowledgeEverything an organization knows collectively, written or notPartly documented, partly in headsWhy a product was discontinued in 2019

Wikipedia notes that tribal knowledge has a lot in common with tacit knowledge: both form through personal experience, mentoring and in person training, and both are hard to pass on. The practical difference is that a large part of tribal knowledge could be written down tomorrow. Nobody has asked for it yet.

Examples of tribal knowledge

The following examples are typical, not taken from a specific company:

  • Finance: the accounting export only balances if a certain filter is set first, and only the person who found the workaround knows which one.
  • Customer service: a key account gets a discount that was agreed by phone and never entered in the CRM.
  • Production: a machine needs ten minutes to warm up in winter, otherwise the first parts are rejects.
  • Purchasing: a supplier reacts to emails within days, but to a call to the warehouse manager within an hour.
  • IT: a nightly script restarts a service that would otherwise crash, and nobody remembers who wrote it.
  • Approvals: "Ask Maria before you give more than 10 percent discount" is a rule nobody wrote down, but everybody follows.

Each of these makes daily work faster. Each one becomes a problem on the day the person who knows it is not there.

Why tribal knowledge is a risk

The bus factor

Software teams have a blunt name for the risk: the bus factor (also truck factor or lottery factor). It is the minimum number of team members who would have to suddenly disappear before a project stalls. A bus factor of one is a single point of failure. Studies of 133 popular GitHub projects, cited on Wikipedia, estimated that about 65 percent had a bus factor of two or less. Tribal knowledge is one of the main reasons the number is that low: if the only people who know something leave, the team loses the ability to do that part of the work.

Silos and slow onboarding

Knowledge that sits with a few people creates information silos. New colleagues have to ask the same questions again and again, experienced colleagues lose time explaining, and changes take longer to reach everyone. When someone resigns, the notice period is often too short to pass on years of shortcuts. That is how knowledge loss when employees leave happens.

Loss of institutional memory

Wikipedia describes institutional memory as dependent on continuity: it needs the ongoing transmission of memories between members of a group. If everyone left at once, the replacements would have to rediscover the workarounds, and the organization would operate less efficiently until they did.

Where tribal knowledge helps

Tribal knowledge is not bad in itself. It is often the fastest route to an answer, it carries context that documents lack, and in improvement projects it is a good source of ideas for what to test. The risk is not that it exists, but that it is held by too few people and has never been checked.

How to find tribal knowledge in your team

Tribal knowledge is hard to find because the people who hold it often do not see it as special. Three questions help:

  1. The holiday test: What would stop or slow down if this person were away for four weeks without a phone?
  2. The "who do we ask" test: For which questions does the team always go to the same person?
  3. The bus factor count: List the critical tasks and count how many people can do each one without help. Every task with a one is a priority.

A skills matrix makes the count visible: tasks in rows, people in columns, and you see at a glance where only one person has a mark.

How to capture tribal knowledge in 6 steps

  1. Prioritize. Start where the bus factor is one and where someone is about to leave, retire or change roles.
  2. Ask instead of asking for documents. "Please write down what you know" rarely works, because people do not notice what they know. Specific questions work better: Walk me through the last month end. What goes wrong most often? Who do you call when it does?
  3. Watch and do it together. Some knowledge only appears in action. Let a colleague shadow the work and then do it while the expert watches. Job shadowing is a simple format for this.
  4. Write it down in a usable form. Recurring tasks become step by step instructions (see these SOP examples), processes become a process documentation, contacts and exceptions go into a handover document.
  5. Check it. Tribal knowledge can be wrong or out of date. Let a second person follow the instructions once and correct what does not work.
  6. Store it where the work happens and give it an owner. A document nobody can find is just a new silo. Name someone who updates it when the process changes.

The countermeasures software teams use against a low bus factor point in the same direction: document processes and keep the documentation current, cross train team members, work in pairs and simplify systems where possible.

Make sharing worth it

Capturing tribal knowledge is also a question of culture. Wikipedia mentions the "tribal knowledge paradox": management says success depends on what employees know, while the structures of the organization discourage the free flow of information. If people have no time to document, are judged only on their own output or worry that sharing makes them replaceable, they will keep their knowledge to themselves. Plan time for it, appreciate it in reviews and make it normal to ask. Sharing knowledge as part of everyday knowledge management is far easier than a rescue operation in a notice period.

Conclusion

Tribal knowledge is what keeps many teams running: shortcuts, contacts and exceptions that nobody wrote down. It becomes a risk when only one person holds it. Find it with the holiday test and the bus factor count, capture the critical parts by asking, watching and writing down, check what you wrote and give it an owner. And when someone with a bus factor of one resigns, start with their knowledge first, while they are still there to answer questions. For the bigger picture, see the guide to knowledge transfer.

Frequently asked questions

What is tribal knowledge?
Tribal knowledge is knowledge that is known within a group but not documented, for example workarounds, informal rules, contacts or the history behind decisions. It is passed on by asking, mentoring and working side by side, and it is lost when the people who hold it leave.
Is tribal knowledge the same as tacit knowledge?
Not quite. Tacit knowledge is personal know how that is hard to put into words, such as judging when a machine is about to fail. Tribal knowledge is defined by who holds it: a small group, without documentation. Much tribal knowledge could be written down easily, it simply has not been.
What is an example of tribal knowledge?
A typical example is a report that only balances if a certain filter is set first, and only one person knows which. Others are discounts agreed by phone and never entered in the CRM, or the one phone number a supplier actually answers.
Why is tribal knowledge a problem?
Because it lowers the bus factor: if the few people who hold it are absent or leave, work slows down or stops. It also creates information silos, makes onboarding slower and can contain errors nobody has checked.
How do you capture tribal knowledge?
Prioritize tasks only one person can do, ask that person specific questions about real cases, let a colleague shadow the work, write the result down as instructions or a handover document, have a second person test it and give the document an owner who keeps it current.
What is the difference between tribal knowledge and institutional knowledge?
Institutional knowledge is everything an organization knows collectively, documented or not. Tribal knowledge is the part of it that is not documented and is held by a few people. Some teams use the terms interchangeably.

Sources

Back to overview