Diane has been here for more than 20 years. She has seen this team through two system migrations, a merger, outsourcing, a division reorg, and an office closure. Ask five people what she does and you will get five different answers, because she knows how this whole division works, and why.
Her job description was last updated eight years ago. Most of what she actually does is not written down anywhere.
Now retirement is on the horizon, and a quiet dread sets in. You cannot say what will stall when she is gone, only that it could be bad.
Succession planning is not just about finding the next person to fill in a box on the org chart. It is about making sure the work a critical person does keeps getting done after their last day.
That means mapping everything they do, deciding where each block of work goes, and capturing how they do it, including the judgment and history behind it, while they are still here. Do that first, and filling the slot becomes the easy part.
Key takeaways
A named successor does not guarantee business continuity.
Start with the work, not the org chart. Decide who gets the title after you know what has to be covered.
Succession planning is not just for executives. It should happen for all key roles.
Succession planning is not static. It is a dynamic way to develop and retain talent.
The learner leads. The person being developed should be able to see what they are taking on, from whom, and to what standard, and drive the process.
HR and the business both have a job, and they need one shared framework with a named owner for every action.
What is succession planning, and why isn't it about the title?
Succession planning is the practice of preparing for a critical person's departure so the business keeps running smoothly. Most programs focus on creating a leadership pipeline and then naming a successor for a title. That is only a small part of what is needed. The undocumented "real" work behind the title, who depends on it, and how it is actually done are what the business loses if no one plans for them.
This is where most succession plans fall short. A named successor tells you who is next in line. It does not tell you whether anyone knows everything the person does, what other teams rely on them for, or where the work will go on day one.
The gap shows up in the research. Gartner found that 72% of HR leaders struggle to close successor capability gaps, meaning the person named is often not ready for the work they are about to inherit. In our experience, that is because the plan was built around the title and rarely around the work.
Why doesn't the job description tell you what leaves with them?
A job description lists responsibilities. It does not capture the decisions a person makes, the exceptions they handle, the relationships they hold, or the work they quietly do because no one else does. When a long-tenured expert leaves, those unlisted pieces of work leave with them, and the business often finds out only when something stalls.
Three things tend to be missing from a title-based plan:
The full picture of the work. What the person does across a week or a quarter, including the tasks that no system or document records.
The dependencies. Which other teams, projects, and customers rely on this person.
The how and the why. The reasoning, history, and judgment that let the person do the work well, not just do it.
This is why the first step is a map of the work, not a list of candidates. Until you can see what the person does and who depends on it, you cannot tell whether a successor is ready, or what else has to move.
Who needs a succession plan?
Anyone whose departure would leave critical work undone, delayed, or at risk needs to be in the plan, whatever their level. Succession planning is not just for executives. The question is not how senior the person is. The question is how much the business depends on what they know and do.
Most plans are built too narrowly. Gartner found that 61% of HR leaders say their succession plans are too focused on senior roles, and its guidance is to prioritize business-critical and hard-to-fill roles, not only the top of the org chart.
A three-question test helps you find the people who belong in the plan:
What is the work that has to be done to execute the strategy at every level?
Who are the individuals who have a unique role in doing that work?
What would happen if they couldn't come to work tomorrow?
If the answer to any of those questions gives you pause, that person needs a plan, whether or not they have a leadership title.
The coverage gap is wide. In its 2025 benchmarking, SHRM found that only 22% of HR leaders reported having a formal succession plan, with just 16% of smaller organizations compared with 44% of extra-large ones. For many organizations, the first step is simply deciding which roles deserve one.
How does Steve Trautman Co. approach succession planning?
We start with the work. We map the blocks of work a critical person owns, decide where each block goes, free up the people who will absorb it, capture how the expert does it, and let the learner lead the transfer. The steps below turn a succession plan from a list of names into a transition that is finished before the last day.
Map all of the work. List every block of work the person does, including what other teams depend on. This is the foundation, and it is what a job description leaves out.
Find a new home for each piece. Decide who will take each block of work. Different pieces can go to different people. Not everything belongs with a single successor.
Free up the people who absorb it. Taking on new work means something else comes off a plate. Decide what, so the transition does not rely on people simply working harder.
Capture how the expert does it. Document the process along with the judgment, history, and reasoning behind it, while the expert is still here and can explain it.
Let the learner lead. The person taking over owns the transfer. When they can see what they are taking on, from whom, and to what standard, they know what "ready" means. Succession plans often stall when there is no real, measurable plan in place.
Finish before the last day. Set a date, track each action to completion, and confirm the work has transferred before the person leaves.
Every action in the plan has a named owner and is tracked to completion. The standard is set and validated by the people who do the work, which is what makes the result measurable.
How do you prepare a new leader to step in quickly?
A new leader needs two things to step in quickly: clarity on current-state strategy and priorities, and a clear view of the work their teams do. The first tells them where the business is going right now. The second tells them what the teams do, who does it, where the risks are, what has to be protected in the short term, and what they are building toward in the longer term.
Most onboarding covers the first and skips the second. A new leader may hear the strategy in week one and still not know which team members are the only ones who can do certain work. That is the knowledge that determines how fast they can make decisions.
At Steve Trautman Co., we create a Knowledge Silo Matrix for each team. It gives the incoming leader:
The work. The blocks of work the team owns.
The workforce. Who sets the standard for each block, who works independently meeting that standard, and who is ready to learn it.
The risks. Where there are single points of failure, unclear standards, overburdened team members, inconsistent results, and more.
The priorities. Which blocks matter most to the business strategy.
With that in hand, a new leader spends less time discovering what the team does and more time helping the team deliver on the strategy and mitigate risks.
How does succession planning protect business continuity?
Succession planning protects business continuity when it plans for the work, not only the person. Continuity means projects keep moving, customers keep getting served, and other teams keep getting what they need. A named successor does not guarantee any of that. A plan that moves each block of work to a ready owner, before the departure, does.
Think of it as three questions a leader can ask about any critical role:
Do we know everything this person does, including what other teams depend on?
Have we decided where each piece goes, and what comes off the plates of the people who absorb it?
Have we captured how the expert does it, with the judgment and exception handling, while they are still here?
If any answer is no, the business is at risk. Gartner's data suggests many organizations are in that position: only 38% of CHROs are confident in their succession plans. Confidence follows from being able to see the work, the owners, and the dates.
Who should lead succession planning, HR or the business?
Both, with different jobs. HR brings the process, the talent data, and the cross-company view. Business leaders know the strategy, what the work is, and who is ready to learn it. However, Gartner reports that 40% of HR leaders struggle to get business leaders to follow through on development.
A shared framework closes that gap because it gives both sides the same thing to look at: the work, the owners, the dates, and what gaps will exist given a surprise departure. In practice that means:
HR sets the process, hires when necessary with a clear view of what the new role will do, and rolls results up to the enterprise level.
Business leaders identify the blocks of work, validate the standard with the people who do the work, and own the actions.
Every action has a named owner and is tracked to completion.
What if the person has already left, or leaves suddenly?
If the person has already left, or leaves with just two weeks' notice, you can still rebuild the work. The approach shifts from capturing knowledge from the expert to reconstructing it from what remains: the people who worked alongside them, the records they left, and the work itself.
That is a different situation from planned succession, and it calls for a different process. At Steve Trautman Co., we cover it as a separate service, Emergency Knowledge Transfer, built for departures that happen before a plan exists.
The lesson for planned succession is simple. Every week you wait, the options narrow. Capturing how the work is done while the expert is still in the building is faster, less stressful, and far more complete than reconstructing it afterward.
Frequently asked questions
What is the difference between succession planning and knowledge transfer?
Succession planning decides who takes over a role or its work. Knowledge transfer moves the know-how, the judgment, and the history that make the work possible. A succession plan without knowledge transfer names a person but leaves the knowledge behind. STC treats them as one process.
How early should you start succession planning?
Start as soon as a role is critical, well before someone announces they are leaving. Planning early gives you time to map the work, move pieces gradually, and let the learner build skill alongside the expert. Waiting until a departure date is set shrinks every option and puts pressure on both people.
It also balances workloads, creates growth opportunities, and can serve as a tool for retaining key talent.
Does succession planning only apply to executives?
No. It applies to any role where other teams depend on the person and the knowledge is not written down. Gartner found that 61% of HR leaders say their plans are too focused on senior roles. Business-critical and hard-to-fill roles belong in the plan too.
How do you measure whether a succession plan is working?
Measure whether the work has successfully moved. Each block of work should have a new owner, a standard validated by the people who do the work, and a date by which the transfer is complete.
Who should own succession planning, HR or the business?
Both. HR owns the process and the organization-wide view. Business leaders own the work, the standard, and the follow-through. A shared framework with named owners for every action keeps the two aligned, so neither side is left carrying it alone.
What is the first step in succession planning?
Map the work. List every block of work the critical person does, including what other teams rely on them for. Until you have that map, you cannot decide who should take what, what has to come off other people's plates, or what knowledge needs to be captured.
Where to start
Pick one critical role and test it with three questions: do other teams depend on this person, would work stall without them, and is what they know written down? If the answers worry you, map their work first and decide who gets the title after. If it would help to see how this works on a real role, reach out to STC and we will walk through one real example with you.