Knowledge Transfer Prevention
A five-step framework for avoiding the 70% family business mortality rate, based on lessons from failed successions like Trattoria Bella Vista.
A five-step framework for avoiding the 70% family business mortality rate, based on lessons from failed successions like Trattoria Bella Vista.
When to Use Knowledge Transfer Prevention
When planning founder or key executive succession, when knowledge holder is truly irreplaceable, when tacit knowledge is the business, when failure risk is existential.
How to Apply
Recognize that critical knowledge is tacit
Audit what critical knowledge exists only in key people's heads
Questions to Ask
- What crises have you navigated?
- What customer patterns do you see?
- What relationships are critical?
Outputs
- Tacit knowledge inventory
- Risk assessment by knowledge holder
Require extended transition periods
Mandate 3-5 year working-together period before key person departs
Questions to Ask
- Has successor experienced at least one full crisis cycle under guidance?
- Is decision quality approaching key person's level?
Outputs
- Multi-year transition plan
- Phased responsibility handoff
Teach the 'why,' not just the 'what'
Require departing person to explain reasoning and principles, not just transfer contact lists
Questions to Ask
- Can successor articulate decision-making principles?
- Can they explain 'why' for major decisions?
Outputs
- Decision principles document
- Scenario-based teaching sessions
Create knowledge transfer checkpoints
Test successor's capability before key person departs
Questions to Ask
- Can successor navigate 8/10 realistic crisis scenarios?
- Does independent evaluator confirm readiness?
Outputs
- Crisis scenario assessments
- Readiness certification
Maintain access to founder post-transition
Keep departing person available for 2-3 years for rare/complex situations
Questions to Ask
- Is consulting agreement in place?
- Is consultation frequency decreasing appropriately?
Outputs
- Post-departure consulting arrangement
- Decreasing dependency plan