Most organizations have succession plans. Very few have succession readiness. Both sound like the same thing. They are not.
A succession plan is a document. It names someone as a potential replacement for a critical role, assigns a readiness rating, and satisfies the governance cycle. It tells you who comes next. Succession readiness is something different. It is the operational confidence that if a key person left tomorrow, the work would continue without a significant gap in judgment, decision-making, or relationships. A plan does not give you that confidence. It gives you a name.
The distinction matters because the cost of closing that gap falls on whoever runs the program, not on whoever ran the process.
The plan versus readiness
Most succession processes are designed to answer a governance question: do we have candidates identified for our critical roles? That is a reasonable question. It is also a different question from: are those candidates actually ready to step in?
The difference shows up in how readiness is assessed. In most succession processes, readiness is a rating assigned during a talent review. "Ready now," "ready in one to two years," "longer term." Those ratings are based on potential, trajectory, and current performance. They are not based on whether the candidate has made decisions in the hardest parts of the role, managed its key external relationships, or handled the situations that define what the role actually requires.
What a succession plan tells you
- Who is identified as a potential successor
- How far away they are estimated to be from readiness
- That the governance requirement has been met
- That a development plan exists on paper
What succession readiness requires
- The successor has made real decisions in the role's hardest dimensions
- Key external relationships have been transferred, not just introduced
- Critical knowledge has been actively documented and transferred
- The gap between now and full capacity has been measured honestly
The gap between these two things is not a failure of intent. It is a gap of design. Succession planning processes were built to surface talent and meet governance requirements. Operational readiness requires a different kind of investment, driven by different owners, on a different timeline.
Why operational leaders hold this risk
Succession is typically assigned to HR. Talent reviews happen once or twice a year. Names are discussed, ratings are assigned, development plans are drafted. The process runs its cycle and produces its outputs. From a governance perspective, succession is being managed.
But the operational leader is the one who knows which person's departure would actually stop a program, slow a decision, or leave a gap that no documented process can fill. And often, that person is not the most senior one on the team.
The roles that carry the most operational risk are frequently not the ones at the top of the org chart. They are the people who know how things actually work. The ones who hold the contractor relationships that took five years to build. The ones who understand which regulatory interpretation applies and why. The ones through whom decisions get made, escalations get resolved, and institutional knowledge flows.
"The roles that matter most operationally are often not the ones succession plans focus on. Seniority and operational consequence are not the same thing."
Succession planning, by design, tends to weight seniority and assessed potential. An operational lens requires a different question: if this specific person was gone in 30 days, which parts of the work would be most at risk? The answer to that question is rarely the same as the answer to "who is at the top of the succession matrix?"
This is not a criticism of HR-led succession processes. It is a description of a gap in ownership. HR manages the process. Operational leaders hold the knowledge of which roles are truly critical. The two need to be more connected than most succession cycles allow for.
The knowledge nobody transfers
There is a specific type of organizational knowledge that cannot be transferred through a job description, an onboarding document, or a structured handover. It does not live in systems or files. It lives in the person.
It is the knowledge of which counterpart at a regulator or partner organization to call when a decision needs to move. It is the understanding of why a particular process works the way it does, including the failed alternatives that led to the current approach. It is the judgment that comes from having been in the room when decisions were made, having seen which risks materialized and which did not, and having built a picture of the operating environment that no briefing note can fully reconstruct.
This is what departs when a long-tenured person leaves a critical role. And it is what takes 12 to 18 months or more to rebuild. Not because successors are incapable, but because knowledge of this kind can only be transferred through time, exposure, and deliberate investment. It cannot be accelerated past a minimum threshold, and that threshold is often longer than the transition timeline most organizations plan for.
The standard response to this problem is the "knowledge transfer" activity at the end of someone's tenure. Exit interviews. Documentation sprints. Handover meetings. These are better than nothing. They are not a substitute for the years of context being transferred through them. The knowledge transfer problem is not a departure problem. It is a planning problem, and the planning needs to happen well before the departure.
What readiness actually looks like
Succession readiness is not a rating. It is an operational state. A successor is ready, in an operational sense, when they have already done the hardest parts of the role in a context where it mattered, and when the people and systems around them have enough confidence in that to let them operate independently.
That definition is harder to satisfy than "ready now" on a talent matrix. It requires that successors have been in the room when the difficult decisions were made, not just briefed afterward. That they have been introduced to key external relationships as future leads, not as shadow attendees. That they have handled the exceptions, escalations, and edge cases, not just the standard work.
The operational readiness test
A useful question for calibrating actual readiness in your operation:
That number is the real readiness gap. If the answer is six months or less, and a credible successor is in place and prepared, readiness is in reasonable shape. If the answer is 18 months or more, the succession plan may exist but readiness does not.
Most operational leaders, asked this question honestly, find the answer is longer than they expected. That gap is the starting point for what needs to change.
The "ready now" rating in a succession matrix is often accurate as a statement of potential. It is less often accurate as a statement of operational preparedness. The difference is not about the individual. It is about how much deliberate investment has gone into building the conditions for readiness, not just the conditions for development.
Building it into your operational rhythm
Succession readiness does not happen through an annual process. It happens through operational decisions made on an ongoing basis. The good news is that building it does not require a separate program or a new budget line. It requires changing how existing work is assigned, who is in what rooms, and how knowledge is treated as an asset rather than an assumption.
For operational leaders, five things move the needle:
The role that would cause the most disruption if vacated unexpectedly is the one that needs active readiness investment. That role may not be on your formal succession plan at all.
Being present when decisions are made is different from making decisions. Successor readiness builds when the individual has operational responsibility for the difficult parts of the role, not just observation rights.
Key external relationships do not transfer through introduction. They transfer through sustained co-presence, demonstrated competence, and time. That process needs to start long before a departure is in view.
Documentation helps. It does not substitute for the years of context behind the documentation. The successor needs to accumulate their own version of that context, ideally while the person they are following is still there to provide it.
Assign the successor as lead on a bounded piece of work. See what gaps appear. Fill them while there is time. That feedback loop is more valuable than any readiness rating assigned in a talent review.
None of these require waiting for HR to run a succession cycle. They are operational decisions that sit entirely within the authority of the leader running the program.
The organizations that manage critical role transitions well are not the ones with the most sophisticated succession frameworks. They are the ones whose operational leaders have taken ownership of the readiness dimension, and started building it before the departure was on the calendar.
"The question is not whether you have a succession plan. Most organizations do. The question is whether the person named in it has been given the conditions to actually be ready."
A succession plan tells you who comes next. Succession readiness determines whether next is actually ready. The gap between those two things is an operational risk. And it is one that operational leaders are in the best position to close.