Succession in Small Teams: Ending Dependence on Key Individuals
Diagnosing Dependence
- The vacation test: if one role takes a week off, what stops? That’s the dependency.
- The knowledge test: what information lives only in someone’s head or personal phone?
- The client test: which clients recognize only one person?
The A/B-Role System (minimal viable version)
- Every critical post gets A and B: A owns, B backups to temporary-substitution level.
- Rotation windows: B actually fills in at least once a quarter — real operation, not paper backup.
- Documentation: A-role essentials live in the knowledge base (the KB).
The Minimal Development Ladder
- One focus per year: small teams have finite resources — develop one “next manager / next mentor” annually.
- Project exposure: give ladder members one complete project (e.g., owning an event end to end).
- Visibility and endorsement: put ladder members in front of clients and HQ.
The Owner’s Own Replaceability
- Founder dependence is the largest valuation discount a small clinic carries — owner replaceability equals asset value.
- Three steps: process documentation (the KB) → institutionalized relationships (clients trust the brand, not the person) → mechanized decisions (clear delegation interfaces).
FAQ
Can a 5-person team afford A/B roles?
The smaller the team, the more it needs them — in a 5-person shop any departure is a 20% capacity loss. A simplified version (cross-training checklist) is acceptable; zero is not.
Trained backbone poached away?
Development is itself the core retention tool (visible growth); being poached proves your training works — the mechanism that builds teams outlasts the individuals it retains.