What Should You Do When a Key Team Member Leaves?
A key team member departure is one of the most revealing stress tests of a revenue organization's Internal engine maturity. Companies with strong Internal engines experience departures as manageable disruptions. Companies with weak Internal engines experience them as crises, because the knowledge, relationships, and processes dependent on that person have no structural home.
The first 72 hours of a departure determine a significant amount of what the next 90 days look like.
Track 1: Knowledge Extraction (Hours 1-48)
The highest-priority action in the first 48 hours is a structured knowledge debrief with the departing team member. The debrief covers five areas:
- Relationships: Who are the key relationships this person manages? For each: what is the relationship status, what is the history, what does this person know about the contact that is not in the CRM?
- Active commitments: What has been promised to clients, prospects, or allies that has not been delivered? What deadlines exist? Who needs to be notified of a transition?
- Processes: Which processes does this person own or know in ways that are not documented?
- Access and systems: Which systems, tools, or accounts require this person's credentials or access? What needs to be transferred or revoked?
- Institutional knowledge: What does this person know about the history of the business, specific clients, or ongoing situations that is not documented anywhere?
Record everything. Document it. Assign owners for each element before the person leaves.
Track 2: Relationship Stabilization (Days 1-7)
Clients, allies, and key stakeholders who had a primary relationship with the departing team member need to hear from leadership before they hear about the departure through informal channels.
The outreach should:
- Be personal — a phone call or personal email, not a form letter
- Acknowledge the transition directly rather than burying it
- Introduce the new point of contact by name
- Express genuine continuity of commitment to the relationship
- Invite any questions or concerns
Prioritize outreach based on relationship value and risk: highest-value clients and most at-risk relationships first.
Track 3: Process Gap Assessment (Days 3-14)
Within the first two weeks, audit which processes were dependent on the departing team member's knowledge. For each process they owned or significantly contributed to:
- Is there an SOP? If yes, is it current?
- If no SOP exists, who is the temporary owner and what is the plan for documentation?
- What is the risk to revenue operations if this process degrades during the transition?
Prioritize based on revenue impact and knowledge gap severity. Processes with high revenue impact and no documentation are the immediate priority for SOP development.
The Longer-Term Response
A departure is also valuable diagnostic data about the Internal engine:
- Was this departure a surprise, or were there signals the company missed?
- Did the departure reveal SOP debt that was not visible before?
- Did it reveal relationship concentrations that need to be distributed?
- Does the departure reflect a cultural or structural problem that needs addressing?
Using the departure as a diagnostic, not just managing the immediate disruption, is the difference between treating the symptom and improving the system.