08 Difficult Hiring Moments
Leaving Without
Breaking the Team
Good exits protect continuity.
The exit continuity system
Notice
Departure announced with time to prepare
Transfer
Knowledge, relationships, and decisions handed over
Clarity
Coverage and ownership confirmed before exit
Continuity
Team operational without disruption
The quality of an exit is measured by how well the team operates after it. Good offboarding is not courtesy — it is operational design.
Why this matters
Exits are routine. The disruption they cause is not.
Every organisation experiences exits. How those exits are managed — the quality of the transition, the completeness of the knowledge transfer, the clarity of coverage assignments — determines whether they become operational disruptions or routine personnel changes.
Most organisations invest heavily in onboarding and very little in offboarding. This is an asymmetry that accumulates cost: with every poorly managed exit, the organisation loses institutional knowledge that was never captured, relationships that were never transitioned, and processes that were never documented.
Good exits don't just protect continuity — they signal to the remaining team what the organisation values. A departure handled with care demonstrates that people matter beyond their immediate utility. This has a direct effect on how confident the remaining team feels about their own position and the company's character.
Founder reality
Design the offboarding system before the next exit, not during it:
Do we have a structured offboarding process — or does each exit happen differently depending on the circumstances and the individual?
When someone leaves, is there a systematic knowledge capture — or does the knowledge leave with them?
Are there currently people in the organisation whose departure would be significantly more disruptive than a headcount gap — because of undocumented knowledge or informal dependencies?
Do departing team members receive the same quality of attention as new joiners in terms of the transition they're facilitated through?
After an exit, does the team receive a clear explanation of what happened to the person's responsibilities?
An organisation that treats offboarding as a system — rather than a circumstantial event — is significantly more resilient to the exits it hasn't yet anticipated.
The system
Four components of a well-managed exit
Apply to voluntary and involuntary exits alike. Adapt the timeline and the tone — not the structure.
01
Knowledge transfer — capture what exists only in the departing person's experience
In the first week after notice: structured knowledge capture sessions. Map the processes they manage, decisions they regularly make, contacts they maintain, and context they hold that isn't documented. Priority: what is most time-sensitive and least documented. The goal is not a perfect record — it is enough that the gap doesn't create operational failure.
02
Relationship transition — warm handoffs for significant external relationships
Every external relationship the departing person maintains — customer contacts, partner relationships, vendor management — should receive a warm handoff before the exit. A joint introduction (email or call) from the departing person endorsing the incoming contact. Cold handoffs lose relationships. Warm handoffs preserve them.
03
Coverage clarity — explicit assignment before the exit date
Before the last day, every significant responsibility should have a named coverage owner. Not 'the team' — a specific person, with a specific scope, who has agreed to the coverage. This should be communicated to the team before the exit, not after. Ambiguity about coverage in the gap period produces dropped work and resentment.
04
Team communication — transparent and prompt
The remaining team should hear about the departure from leadership, not from the departing person's farewell email. The communication should cover: who is leaving, why (at the level of honesty appropriate to the situation), what happens to their responsibilities, and what the plan is. The absence of any of these elements produces rumour that fills the gap.
Common mistakes
01
No structured offboarding for senior exits
Junior exits produce limited disruption from poor offboarding. Senior exits with large knowledge and relationship portfolios produce significant disruption. Invest the most structured offboarding resources where the exit risk is highest.
02
Counting the notice period as a courtesy window rather than a transition window
Notice periods are often spent on a social farewell — lunches, goodbyes, a gradual fade. The notice period should be spent on knowledge transfer, relationship handoffs, and coverage design. The farewell is a day, not a fortnight.
03
Team communication after the fact
When the team learns about a departure through the individual's out-of-office or a colleague's message, leadership has missed the communication window. The team communication should happen on the same day as the departure announcement — ideally before the departing person has spoken to their immediate colleagues.
04
No post-exit review of the coverage design
Coverage assignments made before an exit often need adjustment in the first two weeks after it. A structured 2-week post-exit check-in with the coverage owners reveals what's working, what's strained, and what needs redesign before the gap becomes a problem.
Example scenario
A 30-person engineering team. Senior engineer giving 4 weeks notice. Long tenure: 3 years. Significant knowledge of the legacy codebase and two major customer integrations. No documentation of either.
The offboarding design (week 1)
Knowledge sessions: 4 × 90-minute sessions with the departing engineer and a junior engineer who would manage the legacy systems.
Output: documented architecture decisions, 12 recurring maintenance processes, list of 8 undocumented 'gotchas' in the codebase.
Customer integrations: two joint calls with the respective customer technical contacts. New primary contact introduced and endorsed.
The coverage and communication
Coverage: two engineers given named ownership of specific system areas. Scope defined in writing.
Team communication: engineering manager briefed the full team the day of the resignation announcement. Coverage assignments shared. Questions answered.
Farewell: final day — team lunch, acknowledgment of contribution, genuine celebration of tenure.
The outcome
Two-week post-exit check-in: both coverage owners reported clear ownership and manageable load. No customer incidents attributable to the transition. Legacy system documentation rated 'sufficient for independent management' by the junior engineer who inherited it. Engineering manager: 'This was the best exit we've ever managed.'
Takeaway
Good exits protect what the person built — and the team they're leaving behind.
Capture the knowledge, transition the relationships, design the coverage, communicate clearly. The notice period is a transition window — use all of it.
Related thinking
Continue reading
Recovering from Hiring Mistakes