Where operational knowledge actually lives. Documented and findable, or in someone's head and leaving with them when they go.
CODIFIED VS TRIBAL
A new hire can find most answers without asking a veteran. Processes are written down because writing them down is how the org thinks. The org functions when the expert is on vacation.
Knowledge lives in relationships and relationships have single points of failure. When the expert leaves, the knowledge goes with them. Onboarding isn't a process. It's a relationship you have to earn.
Tribal knowledge looks like institutional wisdom until someone retires. Then it looks like starting over.
Teams running on tribal knowledge look efficient because their veterans move fast. New people take months to get useful. That onboarding cost is invisible because it's distributed across hundreds of conversations. Document it and the cost becomes obvious. Don't, and you pay it forever. Most orgs choose not to see it.
Time to productivity in documented orgs
Time to productivity in tribal knowledge orgs
Fully remote, fully documented. The handbook is the org. New hires are productive in days because institutional knowledge is accessible, not personal.
Docs are the default communication layer. If it's not written down, it didn't happen.
Proprietary stack with years of institutional knowledge baked in. Implementation takes months because knowledge transfer is the product.
Siloed across business units. Knowledge lives in relationships and org charts, not systems. Each unit operates as its own black box.