**Source:** https://heykiku.com/glossary/tribal-knowledge

# Tribal Knowledge

"Ask Sarah, she knows how that client likes their reports." "Check with Mike, he remembers why we set it up that way." "Oh, that's just how we've always done it." These phrases signal tribal knowledge—**critical information that lives in people's heads** instead of documented systems.

Tribal knowledge isn't inherently bad. It's a natural result of people learning and adapting. The problem is when it becomes the only way information is stored. When Sarah goes on vacation, who answers the question? When Mike leaves for another job, **that knowledge leaves with him**.

The **real cost of tribal knowledge is invisible** until it's not. Projects stall because the one person who knows something is unavailable. Quality suffers because new team members don't know the nuances. Clients get inconsistent experiences depending on who's handling their account.

Capturing tribal knowledge doesn't require a documentation project. It requires **making capture effortless**. Voice notes instead of writing. AI that surfaces answers when people ask questions. Role-based access so the right knowledge reaches the right people. When capturing knowledge is as easy as explaining something once, tribal knowledge becomes documented knowledge—without changing how your team works.

## Related terms

- [Standard Operating Procedures](https://heykiku.com/glossary/standard-operating-procedures)
- [Handoff](https://heykiku.com/glossary/handoff)
- [Retrospective](https://heykiku.com/glossary/retrospective)
- [Institutional Memory](https://heykiku.com/glossary/institutional-memory)
- [Knowledge Silos](https://heykiku.com/glossary/knowledge-silos)
- [Knowledge Decay](https://heykiku.com/glossary/knowledge-decay)
- [Key Person Risk](https://heykiku.com/glossary/key-person-risk)
- [Account Handover](https://heykiku.com/glossary/account-handover)