Tribal Knowledge Risk Assessment: How Exposed Is Your Company?
Every company has knowledge that exists only in people's heads. The question isn't whether you have tribal knowledge — you do. The question is how much risk it creates.
Here's a framework for measuring your exposure and deciding what to do about it.
The Five Warning Signs
1. Single Points of Failure
Can you name someone in your organization where, if they quit tomorrow, a critical process would stop? If yes, that's a single point of failure — and it's your biggest risk.
Score yourself: Count the number of processes that only one person can do. Under 3? You're fine. Over 10? You're sitting on a time bomb.
2. "Just Ask Sarah" Culture
When new employees ask how to do something, is the answer frequently "just ask [specific person]"? That means the knowledge is stored in a person, not a system.
Score yourself: How many times per week does someone get directed to a specific person for process questions? Track it for a week. You'll be surprised.
3. Vacation Panic
What happens when a key person takes a week off? If the answer is "things pile up" or "we just wait until they're back," you have a knowledge concentration problem.
Score yourself: During the last vacation of your most critical employee, how many things were delayed? Each delay represents a knowledge gap.
4. Onboarding Takes Forever
If new hires take 6+ months to become fully productive, it's usually not because the job is complex — it's because the knowledge required to do the job isn't written down anywhere.
Score yourself: How long does it take a new hire to work independently? Under 3 months is healthy. Over 6 months means too much knowledge is trapped in people.
5. The Retirement Cliff
Look at your team's age distribution. If multiple senior people with deep institutional knowledge could retire in the next 5 years, you're facing a knowledge cliff.
Score yourself: How many employees with 10+ years of tenure could realistically leave in the next 3 years? Each one represents a potential knowledge loss event.
The Risk Matrix
Plot your knowledge risks on two axes:
Impact (if this knowledge is lost, how bad is it?):
- Low: Minor inconvenience, someone else can figure it out
- Medium: Days of disruption, customer impact
- High: Weeks of disruption, revenue loss, compliance risk
Probability (how likely is the knowledge to be lost?):
- Low: Person is new, engaged, and not going anywhere
- Medium: Normal turnover risk
- High: Person is near retirement, disengaged, or in a hot job market
Anything in the High Impact + High Probability quadrant needs immediate attention.
What to Do About It
Tier 1: Emergency (High Impact + High Probability)
- Schedule knowledge extraction interviews this week
- Record screen shares of critical processes
- Create a knowledge backup plan
Tier 2: Important (High Impact + Medium Probability)
- Begin systematic documentation within 30 days
- Cross-train at least one backup person
- Set up regular knowledge capture cadence
Tier 3: Monitor (Medium Impact + Any Probability)
- Add to documentation backlog
- Capture opportunistically during normal work
- Review quarterly
Tier 4: Accept (Low Impact)
- Not everything needs documenting
- Some knowledge can be re-learned if lost
- Focus your energy on Tiers 1-2
The Understudy Approach
Traditional documentation projects fail because they're boring, time-consuming, and always deprioritized. Nobody wants to spend their Friday afternoon writing SOPs.
Understudy flips the model: instead of asking people to write, it interviews them. A 30-minute conversation captures more actionable knowledge than a week of writing. And because it's conversational, it surfaces the "oh, one more thing..." insights that never make it into formal documentation.
Start with your Tier 1 risks. One conversation per critical process. Build from there.
Related Resources
Understudy for your industry:
See how Understudy compares: