The VP of Engineering resigned on a Tuesday. Two weeks’ notice, personal reasons, nothing dramatic. By Thursday, the CEO had asked HR a question that did not have a good answer: “Who takes over on day 15?”
Nobody did. The three senior engineering managers had never been told they were being considered for the role. One was already interviewing elsewhere. Another had been quietly told, eighteen months earlier, that they were “on the path” for this job, but nothing had been written down and no development had been funded. The third had been hired from outside and had no context on the internal politics of the role.
The company hired externally. The new VP took four months to close and seven months to ramp. During those eleven months, three senior engineers left because they had expected one of the internal candidates to get the job. A major customer renewal slipped. The total cost, by the CFO’s later estimate, was somewhere around $2.3 million.
That is what succession planning is supposed to prevent. This guide covers what it actually looks like when you are the HR leader holding the spreadsheet, not the consultant selling the framework.
What is succession planning for managers, in practice?
The textbook definition: succession planning is the process of identifying and developing internal talent to step into key roles when incumbents depart. Accurate, but not useful when you are trying to explain to a CFO why you need budget for it.
The practitioner definition is tighter. Succession planning is a documented, time-bound plan that answers three questions for every role you cannot afford to leave vacant: who is the incumbent, who is the named backup, and what is the backup missing before they could step in without a six-month productivity dip.
Notice what is not in that definition. No talk of “pipelines” in the abstract. No pool of high-potentials floating around without assigned roles. No nine-box grid as the main artifact. Those tools can help, but they are not the plan. The plan is the named, ranked, time-bound list of backups for specific roles.
At a 200-person company, this list has maybe 8 to 12 roles on it. At 2,000 people, it has 80 to 120. The difference goes beyond scale. It shows up in what breaks and how.
Why does succession planning actually matter to HR teams?
Three things make this worth the calendar time it takes to do properly.
The first is cost avoidance. External replacement of a manager-level role runs 150 to 200 percent of annual salary once you add recruiting fees, ramp time, and the productivity dip for their team. For a director earning $180,000, that is $270,000 to $360,000 per unplanned departure. A functioning succession plan cuts that by roughly 60 percent because internal hires ramp in 3 months instead of 9 and do not require search fees.
The second is retention of the people you did not lose. Every unplanned departure at the manager level triggers a small wave of secondary departures, usually two to four people within six months. When the incoming person is an unknown external hire, the wave is bigger. When it is a respected internal person, the wave barely exists.
The third is that the exercise itself reveals what is broken before it breaks. The first time you do this properly, you will find two or three roles where there is no viable internal backup and no plausible path to creating one. That is information you needed eighteen months ago. Better to have it now.
What does succession planning look like at a 200-person company versus 2,000?
The frameworks consultancies sell assume you are a 10,000-person enterprise. Most HR leaders are not. Here is what changes by size.
| Dimension | 200-person company | 2,000-person company |
|---|---|---|
| Critical roles to cover | 8 to 12 | 80 to 120 |
| Time for first pass | 6 to 12 weeks | 9 to 12 months |
| Primary artifact | Single spreadsheet, one tab | Talent management system with workflows |
| Review cadence | Quarterly, 90-minute leadership team meeting | Monthly working sessions plus quarterly board review |
| Who owns it | Head of People plus CEO | VP Talent plus Chief People Officer plus CEO |
| Assessment method | Manager judgment plus one 360 per successor | Structured assessments, external validation, calibration sessions |
| Typical failure mode | The spreadsheet gets stale because nobody updates it | The system is pristine but disconnected from actual promotion decisions |
| Budget needed | $5K to $20K (assessments, some coaching) | $200K to $800K (platform, consultants, development programs) |
| Realistic readiness rate | 40 to 60 percent of roles have a named, developing successor | 60 to 80 percent, but with variance by function |
The temptation at 200 people is to skip the exercise because it feels premature. That is almost always wrong. At 200 people, one unplanned VP departure is a 10 percent leadership shock. You can feel it across the whole company for months.
The temptation at 2,000 people is to buy a platform and treat that as the plan. Also wrong. The platform is a storage layer. The plan is what the leadership team actually does with the information, which requires calendar discipline that no software enforces for you.
What does a realistic succession planning timeline look like?
The honest answer: 18 to 24 months from “we should do this” to “the plan survived a real departure without chaos.” The calendar below applies to a company doing this for the first time.
Months 1 to 3 are the identification phase. You list the roles that would hurt if vacant, get the CEO and function heads to agree on the list, and identify one to two candidate successors per role. This phase stalls when leadership cannot agree on which roles are critical. Force the conversation with one question: “if this person resigned on Tuesday, what breaks by Friday?”
Months 4 to 9 are assessment and gap analysis. For each named successor, you identify what they are missing. Usually it is some combination of exposure (never run a P&L, never managed managers), skill (weak on financial modeling, weak on executive communication), or experience (never led through a reorganization, never hired senior talent). Most of the gap is experience, not skill, which matters because experience gaps are the slowest to close.
Months 10 to 18 are development. This is where most plans die, because development means real calendar time and real budget. A successor being developed for a VP role needs stretch assignments, exposure to board-level conversations, coaching, and roughly two hours per week of sustained development time. If that is not protected, nothing happens. The incumbent gets busy, the successor stays in their current role, and eighteen months later you have the same plan on paper with nobody actually ready.
Months 19 to 24 are validation. The successor takes on components of the target role, leads initiatives outside their comfort zone, and gets tested on the specific situations that made the incumbent valuable. By the end of this window, you know whether they are actually ready. The shortcut version, where someone goes from “identified” to “ready” in six months, only works when they were already doing 60 to 70 percent of the role informally. That happens, but it is not the typical case.
Who should own succession planning inside an HR team?
The clean answer: HR owns the process, the CEO owns the top 10 to 15 roles, and line managers own their teams’ pipelines. This split breaks down in predictable ways. When HR tries to own the decisions, the calls are wrong because the data that matters (is this person actually ready, do their peers trust them) sits with managers. When the CEO delegates the top roles to HR, the top of the plan becomes guesswork. When managers treat the work as an HR compliance task, updates arrive late and look suspiciously similar quarter to quarter.
The fix is to make succession a named agenda item on the leadership team’s monthly meeting, owned by the CEO, with HR providing the structure. A strong leadership development framework underneath supports the conversation but does not replace it.
Five tips that actually work
1. Start before you think you need to
The companies with working succession plans started them when things did not feel urgent. The companies scrambling started after the first unplanned senior departure. The gap in outcomes between those two groups is large.
For a 200-person company, “before you need to” means around 75 people, when you have your first layer of managers below the founders. For a 2,000-person company, it means at every major growth inflection: post-Series C, post-acquisition, post-IPO. Each inflection changes which roles are critical.
The first pass does not need to be good. It needs to exist. A bad first pass at 75 people becomes a competent second pass at 150 and a real plan at 300. Waiting until 300 to start means building the muscle during a crisis.
2. Invest in retaining the successors you have named
Telling someone they are a named successor creates a promise, spoken or not. If nothing changes in their role, compensation, or development over the next year, they will read that as the promise being hollow. About 30 percent of named successors leave within 18 months when nothing visible happens after the conversation.
The fix is not to over-promise. Make the development concrete. A new stretch project within 90 days. A specific skill gap being closed with budget attached. Exposure to a board meeting or customer escalation. These signal that the company is investing in their trajectory.
At the same time, be careful about naming someone as a successor and then not hiring them when the role opens. If you are going to name people, be honest about their readiness and give them an actual shot when the window opens. Individual development plans are the standard artifact here, and they work when tied to real calendar commitments from both the employee and their manager.
3. Build a deliberately diverse pipeline
The most common way succession pipelines become homogeneous is not malicious. Managers nominate people who look like themselves, have a similar career arc, and communicate in ways the manager recognizes as leader-like. Over three or four rounds, this produces a pipeline that mirrors the current leadership layer.
The fix is structural. Build the pipeline list first based on role requirements, then check the demographics, then ask specifically what is missing. If every named successor for your VP roles came up through the same two functions, you have a concentration risk. If everyone communicates in the same register, you have a perspective risk.
Programs like leadership development for women exist because the default pipeline process under-identifies women for senior roles by a measurable margin. That under-identification is not about individual capability. It is about how the process runs.
4. Build the company culture that makes succession possible
Succession planning works in cultures where internal promotion is the default and external hiring is the exception. It struggles in cultures where external hires are treated as inherently more credible than internal candidates.
The tell is in the compensation data. If external hires at a given level are systematically paid more than internal promotions to the same level, your culture is signaling that external is better. Fix that gap, and the succession pipeline becomes more valuable to the people in it.
The other tell is in how departures are communicated. When a leader leaves and the company immediately announces an external search, the message to every named successor is that they were not really in contention. When the announcement instead names two internal candidates being considered, the signal is entirely different. Even if the eventual hire is external, the process matters.
5. Build the next layer down, not just the top
The common mistake is to focus succession planning entirely on the VP and director layer. The layer that actually determines whether the plan works is the one below: the manager and senior manager roles that produce the directors you will need in three years.
A functioning pipeline has depth. For each VP role, you want one ready-now backup, one ready-in-18-months backup, and two or three ready-in-3-years candidates at the manager level. Without the manager layer, the pipeline narrows to nothing within one promotion cycle.
This is also where the talent pipeline work connects to succession planning proper. The pipeline is how you build the bench. The succession plan is how you deploy from it. They are not the same activity, but neither works without the other.
What breaks succession planning most often?
Four failure modes account for most of the damage.
The named successor leaves before the incumbent does. This happens when the successor was told informally they were next in line, saw no movement for 18 to 24 months, and got recruited into a higher role elsewhere. The fix is making the development concrete and visible.
The incumbent never transfers tacit knowledge. This happens when the succession conversation is purely about the future and never about what the incumbent actually knows. Before any leader departs, you want a structured 90-day knowledge transfer covering customer relationships, vendor contracts, informal influence maps, and unwritten decisions they have made.
The successor was picked for loyalty rather than capability. This is the hardest mode to catch because it often comes from a well-meaning incumbent who trusts their deputy. The fix is outside validation: at least one person outside the incumbent’s direct influence should assess the successor’s readiness.
The role changes shape. Reorganizations or strategic pivots can turn a VP of Sales role into a VP of Revenue role overnight, and the original successor may not be a fit. Review the plan after every significant organizational change, not just on the calendar cadence.
Resistance from stakeholders, which older treatments focus on heavily, turns out to be less of a problem than these four in most companies. Most executives understand succession planning conceptually. They just do not do it rigorously without structure and calendar pressure from HR.
How do you support the managers running pipelines for their teams?
The managers nominating and developing successors need two things that usually do not come with the territory. First, the frame: most first-time managers think about their team as a set of individual contributors delivering work, not as a pipeline producing the next layer. That shift is a skill. Top skills for a new manager overlaps with this but does not cover it specifically.
Second, the coaching muscle. Developing a successor means giving stretch work, watching it be done imperfectly, and coaching through the gap without rescuing. Most managers default to either rescuing (doing the work themselves) or abandoning (letting the stretch fail without support). Neither builds a successor.
This is where tools like Merlin become useful. A manager preparing for the “you are being developed for the VP role” conversation with their deputy can rehearse it and practice the hard questions the deputy is likely to ask. The same applies to the harder conversation: “you were considered for this role but we are going externally, and here is why.” That conversation, done badly, costs you the person. Try Merlin free to see how this works.
How do you assess whether your managers are ready to develop successors?
Before you invest in the formal process, it is worth checking whether your manager layer has the capability to run it. Two assessments give you a read.
The leadership assessment tells you whether your directors and VPs have the strategic and people-development skills to identify and grow their successors. If this assessment shows weakness in feedback, delegation, or development orientation, your succession plan will struggle because the people running it cannot do the core work.
The manager assessment gives you the same read one layer down, for the managers who are producing your next generation of directors. This is usually where the bigger gap sits, because first-time managers rarely get training on how to develop people.
Both assessments give you data you need before the succession plan can work. Skipping this step means building the plan on top of a manager layer that cannot execute it.
Putting it together
Succession planning works when it is a habit, not a project. The companies that handle unplanned departures smoothly are not the ones with the fanciest frameworks. They are the ones where the leadership team has been looking at the same spreadsheet for three years, updating it quarterly, and having honest conversations about who is actually ready.
Start small. Eight to twelve roles for a 200-person company, with named successors and honest readiness windows. Review it quarterly. Invest in the development of the people you have named. The first two years will feel bureaucratic. The payoff shows up the first time someone resigns on a Tuesday and by Friday you have a plan.
The broader context for this work sits inside effective team management and leadership development more generally. Succession planning is one specific outcome of doing those two things well over time, not a separate activity you can bolt on if the foundation is not there.
Ready to build the manager layer that makes succession planning actually work?
Start with the leadership assessment to see where your current leaders stand, or try Merlin free to give your managers daily coaching as they develop the next layer.
Frequently asked questions
How long does succession planning actually take to show results?
Expect 18 to 24 months before a named successor can step in without a 6-month productivity dip. Shorter timelines exist only when the successor has already been running 60 to 70 percent of the role informally. At a 200-person company with 8 to 12 critical roles, you can complete a first pass in about 90 days; at 2,000 people with 80 to 120 critical roles, the first pass alone takes 9 months.
Who owns succession planning, HR or the CEO?
HR owns the process and the calendar. The CEO owns the top 10 to 15 roles and signs off on successor readiness. Line managers own their team’s pipeline. When HR tries to own the decisions, it fails because the data sits with managers. When the CEO tries to own the process, it fails because there is no one chasing updates.
What is the minimum viable succession plan for a small company?
A one-page spreadsheet with every role that would cause pain if vacant, the current holder, one to two named potential successors, their readiness window (ready now, ready in 1 year, ready in 2+ years), and the gap holding them back. Reviewed quarterly by the leadership team. That is it. Anything heavier at 100 to 300 people becomes shelfware.
What breaks succession planning most often?
Four things, in order: the named successor leaves before the incumbent does; the incumbent never actually transfers tacit knowledge; the successor was picked for loyalty rather than capability; and reorganization changes the role’s shape so the succession plan no longer applies. Every HR team we speak with has been burned by at least two of these.
How do you handle succession planning when the CEO resists it?
Reframe it as business continuity, not replacement planning. Ask the CEO which three departures would cause the most customer or revenue damage in the next 12 months. Build the plan around those three roles first. Once one of those roles does turn over and the plan holds, expansion gets easier. Starting with a top-down 40-role exercise almost always stalls.