The Hidden Cost of Unwritten Rules (And How to Extract Tribal Knowledge)
Key Takeaways
- Every company runs on two operating systems: the documented one and the actual one.
- Tribal knowledge is fine when small, dangerous at scale.
- Onboarding suffers when day-three feedback contradicts day-one documentation.
- Shadow tenured employees instead of asking them to write SOPs from scratch.
- Workarounds usually point to a broken official process worth fixing.
Every company runs on two operating systems — the one written in the manuals and the one people actually use. The second is tribal knowledge: unwritten rules that live in tenured employees' heads. It's fine at small scale and becomes a serious liability as you grow. Extract it deliberately, before "Ask Bob" becomes your business model.
The Two Operating Systems Every Company Runs
Every company runs on two operating systems: the one written down in the official manuals, and the one people actually use. The second is entirely made of unwritten rules — the subtle "how things are actually done around here" knowledge that exists only in your oldest employees.
When the company is tiny, tribal knowledge is fine. As you scale, it's a massive liability.
Why Tribal Knowledge Becomes a Liability
When processes aren't documented, accuracy relies entirely on memory and presence. If the person who holds the unwritten rules takes a vacation, operations grind to a halt.
Worse, it creates a toxic onboarding experience. You hand a new hire the formal documentation on Monday. By Wednesday, a veteran pulls them aside and says, "Oh, we don't actually do it that way. Just ignore page 4." You've instantly eroded the new hire's trust in everything you've built.
The "Ask Bob" Bottleneck Explained
Identify the "Ask Bobs" in your office. They're the folks who get interrupted 30 times a day because they hold the keys to the unwritten rules. Need an unusual approval? Ask Bob. Want to know how the billing software actually works? Ask Bob.
Bob is a hero. Bob is also your biggest operational bottleneck.
How to Extract Unwritten Rules Without Burning Staff Out
Extract tribal knowledge without making employees feel they're being replaced by a flowchart:
- Shadow them. Don't hand them a homework assignment. Sit next to them or watch on Zoom and observe. Ask why they deviate from the official SOP at each step.
- Find the why. Unwritten rules usually exist because the official process is broken. When you spot a workaround, investigate the original failure.
Why Workarounds Reveal Broken Processes
The deviation isn't the problem — it's the diagnostic. Every workaround you find is a free piece of feedback about where your documented process has drifted from reality. Fix the official version, and the workaround stops being necessary.
Frequently Asked Questions
What is tribal knowledge in business?
Tribal knowledge is the unwritten, undocumented information that experienced employees carry in their heads — how things actually get done, who to ask, and which official rules can be ignored. It works at small scale and becomes a liability as the company grows.
How do you extract tribal knowledge from employees?
Extract tribal knowledge by shadowing experienced staff while they work, recording their workflow, and asking why they deviate from the documented SOP. Don't hand them a blank document and expect them to write a procedure from memory.
Why is tribal knowledge dangerous at scale?
Tribal knowledge becomes dangerous at scale because operations depend on the presence of specific people. When the holder of unwritten rules is on vacation or leaves, the company loses execution capacity it didn't know it had outsourced to a single brain.
Essoflo Team
The Essoflo team writes about operations, process design, and scaling teams without burning them out.