Tribal knowledge is everything a long-tenured employee knows about how the work really gets done that no one ever wrote down: the trick to starting the temperamental machine, the supplier who actually ships on time, the early warning sign that a batch is about to fail. [4] The term comes from anthropology, by analogy with the way customs and skills pass between members of a tribe. [1] It is how operations actually run, but it is invisible on org charts, missing from training material, and at risk every time someone retires, quits, or transfers. [1] [2]
Key characteristics
- Lives in people's heads, not in any documentation. [2] [4]
- Is shared informally, through shadowing, mentorship, or word of mouth. [4]
- Is concentrated in a small number of long-tenured employees, sometimes only one. [1]
- Disappears with turnover, retirement, and shift changes. [1] [4]
- Is often the difference between a process running well and running badly.
Example
The retiring maintenance technician
A 30-person packaging plant has one maintenance technician, Marko, who has been there 18 years. Whenever line 2 jams, Marko walks over, listens for two seconds, and adjusts a guide rail by exactly 4 mm. The line restarts. Nothing about that fix is written down. When Marko retires, the plant spends 3 weeks of unplanned downtime relearning what he knew by feel. The cost of not capturing his knowledge before he left is roughly six figures. The fix afterwards is a 2-minute video showing the symptom, the fix, and the expected outcome, attached to the line as a QR code. Now the next operator can do what Marko did.
Comparison
Tribal knowledge vs tacit knowledge
| Aspect | Tribal Knowledge | Tacit Knowledge |
|---|---|---|
| Origin | Business and operations jargon, by analogy with human tribes in anthropology. [1] | Academic and philosophical term that became widespread in management literature after the early 1990s. [3] |
| Framing | Often pejorative: implies the team has not bothered to write things down. | Neutral: describes a type of knowledge that resists explicit description. [1] |
| Where it lives | In specific people on a team, often the most experienced. [2] | In any person's hands-on skill, regardless of role or tenure. |
| Can it be written down? | Usually yes, with the right capture tools and time. | Some of it cannot be fully captured (recognizing a face, judging a smell). |
| Why teams care | It is an operational risk. The bus factor lives here. [1] | It is a concept used in knowledge management theory and education research. |
How SOPX handles this
SOPX removes the writing step: an experienced worker films the task on a phone, and AI turns the recording into steps with descriptions and trimmed clips. For the full method, see how to capture tribal knowledge in manufacturing.
Related use case: Knowledge Capture →Frequently asked questions
01 Why is tribal knowledge a risk?
02 How do you capture tribal knowledge?
03 Is tribal knowledge the same as tacit or institutional knowledge?
04 Who should be responsible for capturing tribal knowledge?
05 When should we start capturing knowledge from a senior worker?
Sources
Statements above draw on the references below. Numbers in the text link to the matching entry.
- [1] Tribal knowledgeWikipedia · Accessed 2026-04-28
- [2] Tribal KnowledgeiSixSigma · Accessed 2026-04-28
- [3] Google Books Ngram: institutional knowledge, tribal knowledge, tacit knowledge, institutional memory (1940-2019)Google Books Ngram Viewer · Accessed 2026-04-28
- [4] Tribal KnowledgeDocket · Accessed 2026-04-28