Your succession chart looks solid on paper. You’ve got a high-potential program, a development budget that survived the last round of cuts, and a roster of names everyone agrees represent the future. And yet, the people you were counting on are quietly entertaining recruiter calls, updating their profiles, or staying physically present while mentally checking out two levels below where you needed them to land.
This isn’t a talent problem. It’s a development architecture problem. Most organizations don’t see it clearly until the seat is already empty.
Key Takeaways
- Being labeled “high potential” without a specific development path is more corrosive than no label at all. It creates expectations the organization quietly doesn’t plan to fulfill.
- The departure decision forms well before the resignation letter arrives, during the silence when a leader stops believing their next move exists inside the organization.
- Development that runs alongside real work instead of inside it produces polished candidates who can’t perform under actual pressure when it counts.
- A promotable leader and a high-performing leader are not the same thing. Organizations that treat them as interchangeable end up losing both.
- The real cost of losing a senior-ready leader isn’t the replacement fee. It’s the compounding drag from whoever fills the seat without the institutional knowledge and trust that leader had already built.
What Actually Causes High-Potential Leaders to Leave?
The mechanism is specific, and it’s worth tracing precisely because the real intervention point is earlier than most organizations ever look.
A capable manager gets tagged in the succession system, typically a few years into their tenure. Someone signals, in some form, that they have a bright future. They’re invited into a cohort with other high-potentials. They engage genuinely because they’re motivated and they believe the label means something concrete.
Then twelve months pass. Nothing’s changed. There’s still no clear picture of what the next level actually requires of them, specifically. Their manager, stretched thin, hasn’t had a real development conversation in several quarters. The program delivered solid content and a few useful relationships, but no one connected any of it to how decisions actually get made inside their business unit.
By month eighteen or so, they’ve stopped waiting. They update their profile. When a recruiter calls with something concrete, the organization has already lost the argument.
The resignation letter isn’t the decision. The decision was made during the silence.
The retention problem, at its core, is a communication problem wearing a development costume. You can go deeper on the structural conditions that create this pattern in Steve’s writing on what actually works in leadership development inside large organizations.
Why Does Succession Planning Keep Producing Vacancies?
Most succession planning is backward-looking. It identifies who’s performing well today and assumes that performance predicts readiness for the level above. It doesn’t, and the reason is precise.
The skills that make someone exceptional in their current role often get in the way two levels up. A strong functional manager is rewarded for knowing the answers, executing reliably, and controlling their domain. A senior leader has to be comfortable not knowing, distributing authority, and making consequential calls with incomplete information in front of people who are watching to see if they flinch.
Those aren’t variations on the same skill set. They’re almost opposite orientations.
When succession programs don’t name this transition explicitly and build development work around it, they promote leaders who are excellent in their current role right up until the moment they’re promoted, and then struggle visibly in the new one. The organization blames the individual. The real failure was in how the promotion was prepared.
It’s worth naming a genuine limitation here: this framework assumes the organization already has a functioning performance management system. If your performance infrastructure is itself broken, or if managers lack the skills or standing to deliver honest feedback, start there before investing in succession architecture. Layering a promotability framework onto a system where no one gets straight feedback produces noise, not insight.
Promotable vs. High-Performing: Why Mixing Them Up Is Expensive
This distinction is worth slowing down on, because it’s where most organizations spend money in the wrong direction.
A high-performing leader produces strong results in their current role. A promotable leader produces results and demonstrates the specific behaviors, judgment calls, and relational credibility the organization needs at the next level. These can overlap. Frequently, they don’t.
Your performance management system is built to surface the first type. Most development programs reward it. The succession process then fills up with leaders who are exceptional where they are but genuinely not ready to move, sitting alongside leaders who are capable of more but haven’t been given the experiences that would make that visible to anyone evaluating them.
Sorting this out requires someone willing to have a direct conversation about the difference. That’s exactly the kind of conversation that gets avoided in organizations where feedback has been softened to protect short-term engagement scores. Steve’s work on becoming promotable and fireproof builds a practical framework for leaders who want to understand what actually gets them to the next level, not just what looks good on a development plan.
What Does a Development Architecture Actually Look Like When It Works?
The organizations that consistently retain their senior-ready leaders share a few structural characteristics. None of them are complicated. All of them are consistently underdone.
First, there’s a named person accountable for each high-potential leader’s development, and that person isn’t only the direct manager. It’s someone with visibility across the organization, the standing to open doors, and accountability that gets reviewed regularly against real business decisions, not just development check-ins.
Second, the development experiences live inside the real work. Stretch assignments, genuine exposure to senior decision-making, accountability for outcomes the business actually cares about. Not workshops. Not workbooks. Learning happens through work with real stakes, which means the feedback is immediate rather than hypothetical and consequence is built in.
Third, this is the piece that gets skipped most often: the organization tells these leaders directly what they need to develop and why.
Not “you need broader exposure.” That’s noise.
Something closer to: “Your credibility with the finance function is the specific gap between you and the VP role. Here’s the assignment that will close it, and here’s how we’ll know it has.”
That level of candor is rare. It’s also what high-potential leaders consistently describe when they reflect on managers and organizations that actually held onto them.
The Cost Equation Most Organizations Get Wrong
When a senior-ready leader walks out, the replacement cost is visible and quantifiable. It’s also the smallest part of the actual cost.
Consider what that leader carried: institutional knowledge about how the business actually operates, cross-functional relationships built over years, a team that trusts them and performs accordingly, and a working understanding of where the organizational landmines are buried. None of that transfers in an onboarding packet.
Their replacement, even a talented one, spends the first year operating at a fraction of the organizational effectiveness the departing leader had built. Decisions that would have taken an afternoon take a month. Credibility that would have unlocked a cross-functional partnership has to be earned from scratch. That compounding drag is invisible in the budget and very visible in performance.
This is the real argument for treating senior-ready leader retention as a financial priority, not an HR priority. The assessment tool on Steve’s site is one practical place to start surfacing where your pipeline gaps actually sit before committing budget to another initiative.
Deliberate Pipeline Investment vs. Hoping the Status Quo Holds
| Factor | With Deliberate Development Architecture and Advisory Support | Waiting, Going It Alone, or Running Generic Programs |
| Pipeline clarity | Leaders know specifically what “next-level ready” means for their role and timeline | “High potential” is a label without a path, a timeline, or named accountability |
| Retention timing | Development is active before the departure decision has already formed | Retention conversations start after the resignation, when they’re functionally too late |
| Promotion readiness | Leaders are developed for the job they’re moving toward, not just the one they’re in | Promotions are based on past performance in a different role, producing visible struggles after the fact |
| Development ROI | Investment is tied to specific capability gaps and real business outcomes | Program completion is measured, not behavior change |
| Cost of attrition | Reduced by proactive architecture with named accountability at each step | Absorbed quietly until the vacancy makes the full expense impossible to ignore |
The speaking and advisory work Steve Degnan offers is built around exactly this kind of pipeline diagnosis, connecting the organizational conditions that predict attrition to practical interventions that address them before the damage compounds.
What to Actually Do About This
If you’re a CHRO, a business unit leader, or a CEO looking at a succession plan that doesn’t hold up under honest scrutiny, the first move is diagnostic rather than programmatic.
Before adding another development initiative, get honest answers to three questions: Do your high-potential leaders know specifically what they need to develop and by when? Do they each have a named advocate with organizational standing who is actively opening doors for them? Are your development experiences happening inside real work with real stakes, or in a safe parallel environment where the only consequence is not getting a certificate?
If those three questions produce uncomfortable answers, you don’t have a budget problem. You have an architecture problem. Adding more program content won’t fix it.
You can stay current with Steve’s ongoing thinking about these issues through the leadership newsletter and his broader perspective on where the next era of workplace leadership is heading.
The high-potential leader who left last year didn’t leave because they found a better company. They left because your organization stopped making their future feel visible inside it. That’s fixable. But it requires straight talk about what’s actually broken, not a new cohort program to buy time before the next vacancy.
About the Author
Steve Degnan is an executive keynote speaker and organizational consultant with 32 years of real corporate experience, including 20 years as CHRO at a $13B food and pet food company. He works with Fortune 500 companies, business units in transformation, and senior leadership teams to build promotable, resilient leaders and cultures that perform under pressure. He’s a U.S. Army veteran and serves on multiple non-profit boards, including as Board Chair. Learn more at stevedegnan.com.
Frequently Asked Questions
Why do high-potential leaders leave even when the organization invests in their development?
Because development without clarity reads as stalling. When a leader is labeled high-potential but can’t answer what “next-level ready” specifically means for them, how long the path is, or who is genuinely advocating for them inside the organization, the label creates expectations the organization quietly doesn’t plan to fulfill. That gap between the signal and the substance drives the departure decision, often well before any external offer arrives.
What’s the real difference between a high-performing leader and a promotable one?
A high performer delivers strong results in their current role. A promotable leader demonstrates the specific behaviors, judgment, and relational credibility the organization needs at the next level up. The two can overlap but often don’t. Performance systems are built to identify the first. Most promotion decisions require the second. Organizations that treat them as identical promote people into roles they’re not prepared for and then wonder why the results don’t follow.
When does a high-potential leader actually decide to leave?
The departure decision typically forms well before the resignation, often during a stretch of silence when the leader has stopped receiving meaningful signals about their future and concluded the organization doesn’t have a real plan for them. By the time a recruiter calls with something concrete, the psychological departure is already complete. Retention conversations that start after the letter arrives are rarely successful.
What separates a succession plan that works from one that just produces a list of names?
A succession plan that works connects identified leaders to specific capability gaps, assigns named accountability for their development, and builds experiences inside real work rather than alongside it. It tells leaders directly what they need to develop, with a timeline and a mechanism for knowing when that development has happened. A succession plan that produces vacancies identifies who’s performing well now and assumes that predicts readiness for a fundamentally different kind of role, without ever addressing the transition itself.
Is this framework useful if our organization doesn’t yet have formal succession planning in place?
It’s most useful as a tool for organizations that have a functioning performance management system and at least some structured approach to identifying high-potential leaders. If those foundations are absent, building them is the right first step. Applying a promotability framework to an organization where managers lack the skills or standing to deliver honest, specific feedback tends to produce more confusion than clarity.
How does an organization tell the difference between a development architecture problem and a genuine talent problem?
If your high-potential leaders are performing well in their current roles and leaving anyway, it’s almost always an architecture problem. If they’re struggling in their current roles, you may have a talent calibration issue. The diagnostic question is whether the people you’re losing would have succeeded at the next level with the right preparation. If the honest answer is yes, the organization failed the architecture question, not the talent question.
What’s the right first step for a CHRO or business unit leader who suspects the pipeline is weaker than the succession chart suggests?
Start with a direct conversation before launching a new program. Ask your top three high-potential leaders what they think they need to reach the next level, who they believe is actively advocating for them inside the organization, and whether they can see a real path from where they are to where they want to go. Their answers will tell you more about the state of your development architecture than any survey instrument. Vague or uncertain answers aren’t a personality assessment. They’re your diagnosis.
