The core idea
Talent management coordinates how an organisation attracts, develops, deploys and retains people with capabilities it needs. Some approaches focus on a selected group; others emphasise the potential contribution of the whole workforce. Armstrong and Taylor discuss the choices behind these approaches. Succession planning is one application: preparing credible cover and longer-term capability for important roles.
Source and attribution [1]Using it in practice
Identify roles or capabilities whose absence would create a significant problem. Distinguish immediate cover from readiness for a future role. Define what evidence of readiness looks like, include more than one route to development and discuss aspirations with employees. Review plans regularly as strategy and personal circumstances change. Make broad development access visible even when some roles require targeted investment.
An example, not a reported case
Worked example · illustrative
A regional operations role has only one obvious successor. Instead of labelling that person as guaranteed to progress, HR creates cross-site assignments and supported deputy responsibilities for several interested employees. Readiness is reviewed through evidence from the work. The organisation improves cover while employees gain useful experience without a promise of promotion.
What to watch for
Potential is uncertain and context dependent. A strong performer in one role may not want or suit another. Closed nomination processes can reproduce existing networks and stereotypes. Avoid presenting talent labels as permanent identities or disclosing speculative ratings more widely than necessary.
Identify the work at risk before naming successors
CIPD’s succession-planning guidance covers business-critical roles as well as future leadership. Begin with a disruption question: what important work would become difficult if a role holder were unavailable? Consider scarce technical knowledge, customer relationships, authorisations and decision responsibilities, rather than salary or seniority alone. Separate the risk of an immediate vacancy from a capability the organisation will need in two years. A role can be critical without its holder being irreplaceable, and a highly visible leader may have better cover than a specialist working quietly in a small team.
Use maturity labels to examine the process
AIHR’s Succession Planning Maturity Model describes reactive, emerging, structured and strategic approaches. Use the labels to ask whether planning is repeatable and connected to development, rather than to award the HR function a prestige score. An original diagnostic question is whether a named successor has a current development plan, an opportunity to gain the missing experience and a recorded interest in the work. A polished chart without those conditions is weak protection. This is a practice framework, not evidence that a particular maturity label predicts business performance or that every organisation needs the same machinery.
Keep emergency cover separate from longer-term readiness
An emergency cover plan answers who can keep essential work going now, what authority they need and where important instructions are stored. A development plan answers who could become ready for a broader role and what evidence would support that judgement. Do not assume that the best short-term cover is the best long-term appointment. Record the limitations of cover, including decisions that must be escalated. Test access and handover arrangements before they are needed. Avoid placing all cover responsibilities on one reliable employee who would become the next point of failure.
Define readiness using evidence and a time horizon
Replace a vague label such as high potential with the demands of the possible role. For an operations lead, these might include allocating resources across sites, interpreting service risk and developing supervisors. Assess demonstrated experience, areas needing development and the conditions under which readiness could improve. A statement such as ready after successful cross-site responsibility is more useful than an unexplained rating. Record who made the assessment and what evidence could change it. Do not turn a tentative forecast into a permanent identity or promise a promotion that depends on future vacancies and selection decisions.
Worked example: the only person who understands a client process
Invented example: a contract specialist is the only person who can reconcile a client’s unusual reporting requirements. The immediate plan documents the process and gives two colleagues supervised practice with non-live examples. The longer-term plan asks one interested colleague to coordinate a reporting cycle and explain exceptions to the account manager. The specialist checks the output and identifies gaps. Success is demonstrated independent handling of an agreed set of cases, not attendance at a shadowing session. Review the specialist’s workload too: knowledge transfer requires planned time, and should not depend on unpaid effort or the assumption that they are about to leave.
Give people a fair route into development
Ask employees about their aspirations and constraints rather than assuming everyone wants management or geographical mobility. Explain how development opportunities are allocated and allow interested people to put themselves forward. Check whether part-time work, remote location or a quieter communication style is being treated as lack of ambition. Compare access to stretch assignments, not just the ratings produced after those assignments. A second reviewer can challenge unsupported judgements, but a meeting alone does not remove bias. Keep the evidence relevant to the role and provide feedback that helps the person progress even when they are not selected.
Make development produce new evidence
Choose an assignment that closes a specific gap and has a realistic support arrangement. If the gap is managing competing priorities, observing a senior meeting may introduce the issue, but owning a bounded piece of cross-team work gives stronger evidence. Agree authority, workload adjustments and feedback before the assignment begins. Review what the employee learned and which decisions they can now handle, including where they still need support. Provide alternatives if the opportunity disappears. Development should leave useful capability behind even if the anticipated vacancy never arises.
Review coverage and the quality of the pipeline
A simple coverage percentage can hide weak plans. Report how many critical roles have tested interim cover, how many development actions actually occurred and which assumptions remain uncertain. Track whether appointments succeed after transition, while recognising that job design and organisational support also influence outcomes. Review plans when strategy, role requirements or employee preferences change. Limit access to identifiable assessments and explain their purpose. Connect succession to workforce planning, knowledge management and fair recruitment; it should support those processes rather than become a private list that silently predetermines every appointment.
Take it into your next conversation
Three useful questions.
- Which essential work has untested cover?
- What evidence supports the readiness judgement?
- Does the person want this possible role?
Related terms
Go to the evidence
Sources & attribution
Further reading: Michael Armstrong with Stephen Taylor (2023), Armstrong’s Handbook of Human Resource Management Practice, 16th edition, chapters 28. Edition & reading notes ↗
[1] Armstrong & Taylor (2023), 16th edition, chapters 28 — reading notes ↗
[2] CIPD, Succession planning (5 December 2025); consulted 28 September 2026 ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Original ADM HR teaching guide with attributed background reading. Practical sections expanded on 28 September 2026 following the CIPD and AIHR reading listed in the sources. Worked examples, suggested review periods and decision aids are original editorial illustrations, not validated models or universal standards. Member resources are linked for further reading; their documents and templates are not reproduced here. The original overview review date is retained; this expansion is not a fresh legal review of every linked article.
Published 2026-09-25 · Reviewed 2026-09-25. Editorial approach