How Do You Reduce Key Person Dependency Before Someone Leaves?
The instinct is to address key person dependency after a departure reveals it. By then, it is reactive and expensive. The most effective approach is reducing dependency while the key person is still present and engaged, which feels unnecessary until the moment it suddenly is not.
Start With a Dependency Map
Before applying any of the three levers, map the current dependency clearly. For each member of the revenue-facing team, list:
- Which processes does this person know in ways that are not documented?
- Which client or ally relationships are primarily with this person?
- Which decisions require this person's involvement that could be handled independently?
For most companies at the $5M-$20M stage, this exercise reveals that two or three people carry significant concentrated dependency risk, usually the founder, the top sales performer, and a key customer success person.
Lever 1: Proactive Documentation
The documentation lever is the most straightforward but requires consistent commitment over time. Work through the highest-risk undocumented processes in order of dependency risk and revenue impact.
The priority stack:
- Processes owned by one person that would stop or significantly degrade when that person is unavailable
- Processes that involve critical institutional knowledge not captured anywhere
- Processes executed infrequently enough that they will not be reconstructed from memory alone when needed
For each process: write an SOP, have someone other than the author validate it by executing the process from the document alone, and store it where it will be found when needed.
Lever 2: Relationship Distribution
Relationship distribution is the deliberate effort to build company-level relationships rather than individual-level relationships with key clients and allies. Tactics:
- Multi-person touchpoints: Key client check-ins and QBRs should include at least one person beyond the primary account owner. The additional person is introduced, adds value, and begins building their own relationship with the client.
- Leadership touchpoints: Regular senior leader check-ins with top accounts, not to manage the account but to build a direct relationship at the leadership level that provides continuity through transitions.
- Documented relationship context: CRM records for key accounts should include not just activity history but relationship context, what the client cares about, the history of the relationship, and who the key stakeholders are.
Lever 3: Decision Delegation
Decision delegation requires explicit grants of authority that allow team members to make specific categories of decisions without the founder or senior leader's involvement. For each type of recurring decision, specify:
- What is the decision?
- Who has authority to make it up to what threshold without escalation?
- What triggers escalation to a higher level?
The first time a team member makes a decision using delegated authority they have not used before, the founder's instinct is often to review it anyway. Resisting that instinct, trusting the delegation, is the hardest part of the lever.
A Realistic Timeline
- Month 1-2: Dependency map complete, top 3-5 documentation priorities identified, first SOP drafts complete.
- Month 3-6: Top documentation priorities completed, relationship distribution plan in place for top 5 accounts, first decision rights framework drafted.
- Month 6-12: Significant reduction in documentation dependency, relationship distribution active across top client and ally base, decision delegation functioning without regular override.