Succession is the work of making the organization less fragile while giving
people honest opportunities to grow. It is not a secret list of replacements
or a promise that a named person will receive a future role.
A healthy succession system identifies responsibilities whose loss would
materially hurt the organization, develops more than one plausible option,
and uses real assignments to gather evidence. The aim is continuity and
capability, not certainty about a future org chart.
Map responsibilities before people
Start with the work that must continue: decisions, relationships, technical or
commercial knowledge, coordination, and trust. A role title alone hides the
dependencies that make a departure dangerous.
For each critical responsibility, ask:
- What would stop, slow, or become unsafe if the current owner left?
- Which knowledge or relationships are concentrated?
- What level of judgment is actually required?
- How long would credible readiness take?
- Can the work be redesigned so it is less dependent on one person?
Sometimes the strongest succession move is documentation, shared ownership,
or a better team boundary rather than preparing a like-for-like replacement.
Use evidence, not reputation
Readiness should be supported by observed work at an appropriate scale.
Visibility, similarity to current leaders, or confidence in meetings is weak
evidence. Define the decisions and conditions the future responsibility
requires, then identify which have been demonstrated and which remain
untested.
Use multiple perspectives and inspect patterns in who receives sponsorship,
stretch work, and benefit of the doubt. A succession process can reproduce
unequal access while appearing neutral if the evidence opportunities are not
examined.
Develop through consequential assignments
Training can provide vocabulary. Readiness grows through bounded ownership:
leading a cross-team decision, managing an operating review, hiring for a
critical role, handling a difficult stakeholder trade-off, or acting in the
role with clear support.
For each assignment, name the capability being tested, the boundary of
authority, available coaching, failure containment, and the evidence to review
afterward. Do not create a stretch assignment that quietly transfers a senior
role without recognition, authority, or support.
Keep the conversation honest
Tell people what is being developed and why without promising a vacancy or
promotion you cannot guarantee. Discuss aspirations, constraints, and
alternative paths. A person can be a valuable succession option without
wanting the role; a development plan should not treat their consent as
automatic.
Succession information is sensitive. Share it only with people who have a
legitimate role in development and continuity decisions.
Practice with five critical responsibilities
Create a succession map for five responsibilities whose loss would create
material risk.
- Describe the responsibility and the consequence of an unexpected gap.
- Name current concentration in decisions, knowledge, and relationships.
- Identify at least two continuity options, including redesign where useful.
- Record demonstrated evidence and the most important readiness gap.
- Assign one bounded development opportunity with a sponsor and review date.
- Audit who receives these opportunities and whose evidence may be missed.
Keep the working map access-controlled. Store only a de-identified version as
a learning artifact.
Use resources with context
The CIPD succession-planning guide provides a current overview of critical
roles, talent pools, development, and changing practice. The Manager’s Path
makes leadership transitions and their different demands tangible for
technology organizations.
Neither source turns a prediction into a fact. Finishing Core resources
contributes to route completion, but readiness must be supported by observed
work; Supplemental resources remain optional.
Evidence of Practice
You may be ready to record Design when you can:
- identify critical responsibilities and the real consequence of a gap;
- reduce concentration through redesign as well as individual development;
- distinguish demonstrated readiness from reputation or sponsorship;
- create bounded assignments that produce relevant evidence;
- discuss development without making an implied promotion promise;
- audit access to stretch work for systematic bias; and
- show more than one credible continuity option for material responsibilities.
These prompts support a proficiency decision; they are not an automatic
completion checklist.
Continue through the tree
Leading leaders & management systems
creates the coaching and accountability context for development.
Organization design & team topology can reduce
structural key-person risk, while
Decision rights & governance makes authority
available before a transition becomes urgent.