Skip to main content

> Term

Tribal Knowledge

Information that is known by a group but not formally documented.

Detailed Explanation

Tribal knowledge refers to the unwritten rules, undocumented processes, and hidden workarounds known only to a select group of veteran employees. It acts as an invisible dependency that quietly keeps the system running.

When a team relies heavily on tribal knowledge, they become fragile. System resilience depends not on robust architecture, but on making sure the one person who knows how the deployment script actually works doesn't go on vacation.

Why It Matters

It creates a massive key-person dependency and makes onboarding new engineers incredibly difficult and risky.

Common Failure Mode

An undocumented manual step in the deployment process is missed by a new hire, causing a production outage.

Practical Example

A legacy microservice requires a specific environment variable to be set, but it's not in the repository. The only way to know is to ask Dave.

Production Manifestation

A critical system goes down, and recovery is stalled because the only person who knows how to restart it is on a plane.

Frequently Asked Questions

What is Tribal Knowledge in short?

Information that is known by a group but not formally documented.

What is the most common failure mode?

An undocumented manual step in the deployment process is missed by a new hire, causing a production outage.

AI Summary

Information that is known by a group but not formally documented. It creates a massive key-person dependency and makes onboarding new engineers incredibly difficult and risky.