Succession planning for knowledge, not just roles

Most succession planning stops at the org chart. If this person leaves, that person is next in line. It's a reasonable start, and it answers a real question — but it's the easier of the two questions succession actually raises, and businesses tend to stop there because the harder question doesn't have an obvious owner.

The question succession plans usually skip

Who takes the title is a structural question with a structural answer. What that person actually needs to know to do the job well — the judgement calls, the relationship context, the unwritten exceptions — is a knowledge question, and knowledge questions don't fit neatly into an org chart at all.

A named successor with none of that context is in almost the same position as an external hire, except with higher expectations attached, because everyone assumes internal succession means a smooth transition. It often isn't, for exactly the reasons this cluster keeps coming back to: the job description and the reporting line transferred; the accumulated judgement did not.

Why this gap survives in even well-run businesses

Because succession planning is usually treated as an HR exercise focused on readiness and capability — is this person trained, do they have the right experience, do they have the confidence of the team. All of that matters, and none of it addresses whether the specific tacit knowledge currently held by the departing person has actually been transferred, as opposed to assumed to transfer through general competence.

Capability and knowledge transfer are different things. A capable successor without the specific context still has to rebuild it from scratch, the same way any new hire would — see rehiring the same knowledge twice.

What a knowledge-aware succession plan actually includes

An inventory of the judgement calls specific to the role, not the responsibilities. Responsibilities are in the job description already. Judgement calls are the things a person in the role decides based on experience that a newcomer would have no basis for deciding the same way.

A defined overlap period used for shadowing specific scenarios, not just general handover meetings. The value is in watching the current role-holder handle a real exception, not in a slide deck summarising their responsibilities.

Named relationships that need active introduction, not just a contact list. A vendor who trusts the current manager because of a history together doesn't automatically extend that trust to a successor. That relationship needs to be actively transferred, ideally with the current manager present for the handoff — see the vendor relationship that lived in one person's phone.

Why this matters more for planned departures than sudden ones

It's tempting to think succession planning is mainly insurance against sudden departures — an accident, an illness, an unexpected resignation. In practice, planned departures are where the gap does the most damage, because a planned departure creates the illusion that the transition was handled properly. Nobody scrambles, nobody panics, the handover meetings happen on schedule — and six months later the successor is still discovering context nobody thought to mention, because the process looked complete without actually being complete.

Building this into a plan you already have

Add one section to the existing succession plan: for each named successor, list what they would need to know that isn't in their current job description. This doesn't need to be exhaustive on day one — it needs to exist, and it needs to grow as gaps are noticed.

Treat the overlap period as knowledge transfer time, explicitly, not just a courtesy notice period. If the departing person's calendar during their notice period looks the same as any other month, the transfer almost certainly isn't happening.

Revisit the plan when the role changes, not just when the person does. A successor named two years ago may be prepared for a role that has since evolved. Succession plans age the same way configuration does — see configuration without a reason attached — and need the same kind of periodic review.

Common questions

What's missing from a typical succession plan?

Most succession plans name who takes over a role but stop short of documenting what that person needs to know that isn't in the job description — the judgement calls, relationship context, and unwritten exceptions the current role-holder has accumulated. Naming a successor answers a structural question, not a knowledge one.

Why is this gap more damaging in planned departures than sudden ones?

Because a planned departure looks handled — handover meetings happen, a notice period runs its course — which creates a false sense that the transition was complete. In reality, most of the deepest context doesn't surface in scheduled meetings, and the successor keeps discovering gaps for months afterward.

How do you build knowledge transfer into an existing succession plan?

Add an explicit inventory, for each named successor, of what they'd need to know that isn't in their job description. Use the overlap or notice period deliberately for shadowing real scenarios and introducing key relationships in person, rather than treating it as a standard notice period with a few handover meetings added on.

Should succession plans be reviewed on a schedule?

Yes. A named successor prepared for a role two years ago may not be prepared for how that role has since evolved. Succession plans need periodic review for the same reason any other configuration does — the reasoning behind them goes stale as circumstances change, even if nobody updates the plan itself.

Related: rehiring the same knowledge twice · the manager who is the process · the vendor relationship that lived in one person's phone