What is Key-Person Dependency?
Key-person dependency (also: bus factor = 1) exists when critical knowledge, skills, or relationships are concentrated in a single individual.
Key-person dependency (also: bus factor = 1) exists when critical knowledge, skills, or relationships are concentrated in a single individual. If that person leaves, gets sick, or becomes unavailable, the organization suffers disproportionate disruption.
In technology: a single engineer who understands the legacy billing system, the architect who designed the core platform, the DevOps engineer who manages production infrastructure without documentation. In M&A due diligence, key-person dependencies are critical risk factors.
Mitigation: documentation requirements (architecture decision records, runbooks), knowledge sharing (pair programming, tech talks), cross-training programs, and retention packages for identified key persons during M&A.
Why It Matters
Key-person dependency is a hidden risk multiplier. A $100M platform with a bus factor of 1 for its core architecture is worth significantly less than the same platform with documented knowledge across 5 engineers.
Frequently Asked Questions
What is key-person dependency?
When critical knowledge or skills are concentrated in one person. Also called "bus factor = 1." If that person leaves, the organization suffers disproportionate disruption.
How do you reduce key-person dependency?
Documentation (ADRs, runbooks), pair programming, cross-training, tech talks, and rotation of responsibilities. In M&A, identify and create retention packages for key persons during due diligence.
Related Terms
Need Expert Help?
Richard Ewing is a Product Economist and AI Capital Auditor. He helps companies translate technical complexity into financial clarity.
Book Advisory Call →