08 Difficult Hiring Moments
Replacing Someone
Critical
Replacing one person can quietly affect the whole system.
The critical departure system
Dependency
Person holds knowledge, relationships, or decisions
Departure
Planned or unplanned exit announced
Transition
Knowledge transfer and coverage designed
Redesign
Role and system rebuilt for sustainability
Critical departures expose structural dependencies that existed before the person left. The exit reveals the fragility — it doesn't create it.
Why this matters
When someone critical leaves, the organisation discovers how much was held by one person.
Every organisation has people who carry more than their job description suggests. They hold institutional knowledge that was never documented. They maintain relationships that aren't formally theirs. They make decisions that others defer to without the decisions being explicitly assigned. When these people leave, the gap they create is larger than the role description would predict.
The critical departure is one of the most operationally revealing moments in a company's growth. It exposes every undocumented process, every informal dependency, and every decision that was made by one person rather than by a system. The departure doesn't create these fragilities — it makes them visible.
Managing a critical departure well requires two simultaneous efforts: the immediate transition work (knowledge transfer, coverage, continuity), and the structural work (redesigning the role and the processes around it so the next person inherits a more stable foundation).
Founder reality
Map the dependencies before designing the transition:
What specific knowledge does this person hold that exists nowhere else in the organisation?
Which relationships — customers, partners, vendors, team members — are primarily maintained by this person?
Which decisions are currently made by or deferred to this person — and is that authority formally assigned or informal?
What would break in the first week if this person left tomorrow — and is there a plan for each of those things?
Is the role designed in a way that the next person would also become this single point of failure?
The last question is the most important. A transition that doesn't address the structural dependencies produces the same fragility for the next person.
The system
Four components of a critical departure transition
Run all four simultaneously. The timeline is usually shorter than it feels.
01
Knowledge mapping — document what lives in this person's head
Work with the departing person to produce a knowledge inventory: processes they manage, decisions they make, contacts they maintain, context they hold. This is not a replacement for the person — it is the minimum required to prevent operational breakdown. Priority: what is most time-sensitive and least documented.
02
Relationship transition — warm handoff for critical relationships
For every significant external relationship this person holds — customer, partner, vendor, investor — a warm handoff should occur before their departure. Not an email introduction — a joint call or meeting where the departing person endorses the incoming contact. Relationships transferred cold rarely hold.
03
Coverage design — who manages what between departure and replacement
There is almost always a gap between departure and replacement. Map what needs to be covered, assign specific coverage to specific people, and communicate those assignments explicitly. Diffuse coverage ('the team will handle it') produces dropped work and resentment. Named coverage produces accountability.
04
Role redesign — rebuild the role to be less person-dependent
Before opening the replacement search, redesign the role. What should this role own? What should be distributed to others? What systems should exist to reduce the dependency on one person's knowledge? The replacement search is an opportunity to fix the structural fragility that the departure revealed.
Common mistakes
01
Starting the replacement search before completing the transition
Rushing to hire the replacement before completing knowledge transfer produces a new person who inherits an undocumented role. They become the same single point of failure — without even the experience of the person they replaced.
02
Assuming the departing person will document everything
Left to themselves, most departing people document what they think is important. This is rarely the complete picture. The knowledge mapping should be driven by the organisation — structured conversations about what needs to be captured, not a document the person writes alone.
03
No post-departure systems review
After the immediate transition, a structured review of which processes broke, which dependencies were unexpectedly large, and which decisions were unclear reveals the structural work needed before the next critical departure.
04
Treating critical departures as emergencies when they're actually structural revelations
The emergency response to a critical departure focuses on immediate coverage. The structural response focuses on why the departure was so disruptive — and changes the organisation so the next one isn't. Both are needed.
Example scenario
A 40-person SaaS company. Head of Engineering giving 4 weeks notice after 3 years. First engineering hire. Held architectural knowledge, key vendor relationships, and informal authority over most significant technical decisions. No documentation of any of it.
The first week
Knowledge mapping session: CEO and departing engineer, 3 hours over 2 days. Output: 14-page process document, decision log of 30 recurring decisions with context and rationale, contact list of 12 key technical vendors with relationship notes.
Coverage assignments: two senior engineers given named ownership of specific decision domains for the transition period.
Customer introductions: 3 joint calls arranged with key customer technical contacts in week 1.
The role redesign (before search opened)
Architecture decision process redesigned: key decisions documented as processes rather than owned by an individual.
Engineering lead role created below VP level to distribute management responsibility.
VP Engineering role redefined: strategic and external focus, with internal technical authority distributed.
The outcome
Transition period (8 weeks without a VP Engineering): operationally stable. No customer incidents attributable to the gap. Replacement search: VP hired in 6 weeks. New VP inherited a documented role rather than an undocumented one. First 90 days described as 'the smoothest engineering leadership transition' the company had experienced.
Takeaway
Critical departures reveal dependencies. Managing them well redesigns the system.
Map the knowledge, transition the relationships, design the coverage, and rebuild the role before opening the search. The departure is expensive — make sure the recovery produces something more structurally sound than what existed before.
Continue reading
How to Let Someone Go Respectfully