Leadership development fails in large organizations not because companies lack programs, but because those programs treat leadership as a knowledge problem when the real issue is behavioral and systemic. More content doesn’t fix a feedback vacuum. More training doesn’t survive a culture that never changes. What actually works is a diagnostic-first approach that identifies what leaders genuinely need, then builds the conditions that make change stick.
Key Takeaways
- Most corporate leadership programs fail not from poor content, but from a missing accountability and feedback infrastructure around each leader
- Effective development requires distinguishing between leaders who need skill-building and those who need behavioral recalibration, since the interventions are completely different
- Meaningful behavioral change takes 18 to 36 months, not the three-day offsite most organizations budget for
- Manager accountability and senior leadership modeling aren’t program enhancements; they’re prerequisites
- Organizations that build development into operating rhythms consistently outperform those that treat it as a one-time event
What’s Actually Breaking Down in Corporate Leadership Development?
The uncomfortable reality is that most organizations aren’t bad at running programs. They’re bad at diagnosing what their leaders actually need before those programs begin.
That’s not a vendor problem. It’s a design problem. And it repeats itself because leadership development gets budgeted as an event, when behavioral change is not an event. It requires repeated exposure, real-time feedback, psychological safety to try new behaviors, and meaningful consequences tied to how leaders actually show up. When you fund a three-day offsite but don’t fund the accountability structures that follow it, you’re not building a development system. You’re building documentation that development happened.
Over 32 years of organizational leadership, including two decades as CHRO of a $13 billion food and pet food company, Steve Degnan watched this pattern repeat across cohorts, succession cycles, and transformation initiatives. Some programs were well-designed and well-facilitated. They still didn’t produce the leaders organizations needed at the next level. The gap wasn’t content quality. It was that the development environment around each leader never changed.
That repeated observation became the foundation for the Promotable and Fireproof framework, which begins not with curriculum design, but with the diagnostic question most organizations skip entirely: what kind of problem does this leader actually have?
Why Does the Same Gap Keep Showing Up Year After Year?
There’s a structural mismatch at the heart of most enterprise leadership development, and it’s worth naming directly.
Most programs treat all high-potential leaders as a single population with the same developmental need. They don’t have the same need.
A high-performing director who avoids giving critical feedback needs something fundamentally different from a high-performing director who lacks the strategic frameworks to scale her team. Lumping them into the same cohort doesn’t serve either one. Yet organizations consistently group leaders by performance rating rather than by the nature of their development gap, which means the intervention is designed for a population that doesn’t actually exist.
“Communication skills” as a development area is nearly useless. “Withholds critical feedback from direct reports to protect relationships at the expense of team performance” is something you can actually work with.
The Promotable and Fireproof framework addresses this by segmenting leaders into distinct profiles based on specific behavioral gaps before any development intervention is designed. That’s the difference between a program that looks credible in a board presentation and one that actually changes who gets promoted.
What Does Effective Leadership Development Actually Look Like?
Effective leadership development is a system, not a program. That distinction matters more than any content decision.
Consider a typical scenario that plays out across large organizations. A company runs a strong cohort program for high-potential directors. Participant satisfaction scores are excellent. The facilitators are experienced. The content is current. Eighteen months later, only a few participants have advanced, some have left for competitors, and the rest are sitting in identical roles with no clearer path forward than when they started. The program wasn’t the problem. The follow-through infrastructure never existed, and the participants’ managers weren’t part of the process at any stage.
That gap is the thing Steve’s advisory work is specifically built to close. The components that consistently distinguish programs that change behavior from programs that generate high satisfaction scores include the following.
Behavioral assessment before content delivery. Prescribing solutions before diagnosing problems is exactly as ineffective in leadership development as it is in medicine. Assessment surfaces what specific behavioral conditions need to change and for whom, which changes every decision that follows.
Manager accountability built into the architecture. Research from the Center for Creative Leadership points consistently to the manager relationship as a more powerful driver of behavioral change than any formal program. If the leader’s direct manager isn’t setting development goals, observing progress, and closing feedback loops, the program is operating in isolation from the only environment that actually matters.
Timelines calibrated to how change actually works. Meaningful behavioral change in leaders typically takes 18 to 36 months when the development system includes real-time feedback and accountability structures. Organizations that expect visible transformation inside a single fiscal quarter are usually measuring the wrong things: satisfaction scores instead of behavioral shifts, or completion rates instead of promotion readiness.
The work Steve does with large organizations on leadership development is built on these same principles, applied to the specific pipeline challenges each organization actually faces.
How Does a Diagnostic-First Approach Compare to Going It Alone?
| Approach | What It Addresses | What Gets Missed | Likely Outcome |
| Waiting or doing nothing | Avoids short-term discomfort | Pipeline erosion, repeated attrition, compounding gaps | Same talent review findings year after year, at growing organizational cost |
| One-time offsite or cohort program alone | Frameworks and content delivery | Behavioral accountability, manager involvement, follow-through | Short-term engagement, low retention of change |
| Generic e-learning platform | Content at scale | Real-time feedback, application context, any accountability loop | Completion rates, not capability development |
| Diagnostic-first advisory with Steve Degnan | Specific behavioral gaps, systemic conditions, manager accountability, pipeline readiness | Not designed for organizations seeking a compliance event or a one-day motivational lift | Sustainable pipeline development and measurable leader readiness |
The question isn’t which approach looks most credible in a board deck. It’s which approach is actually designed to solve the problem your organization has. A well-produced program that doesn’t change who gets promoted isn’t an investment. It’s an expense with good photography.
Who Gets the Most From This Approach, and Where Does It Have Real Limits?
This work delivers the most value when a genuine pipeline problem exists: high-potential leaders stalling before senior levels, unexpected attrition at the director and VP level, or a business transformation that requires a fundamentally different kind of leadership than the current culture produces. If your talent review surfaces the same gaps year after year, that’s not a coincidence. That’s a system producing exactly what it’s designed to produce.
It’s also the right fit when senior leadership is genuinely willing to be part of the solution, not just the sponsor of it. The most common reason leadership development fails isn’t program quality. It’s that the C-suite sends leaders to be fixed while the culture that created the problem stays exactly as it was.
Steve’s approach requires executives to model the behaviors being developed, not just approve the budget line. That’s a real commitment, and it’s worth naming honestly.
Where this approach has genuine limits: it isn’t designed for organizations that want a compliance event or a motivational keynote with no follow-through infrastructure. If your organization isn’t ready to treat leadership as a strategic system, this methodology will feel like more than you need. But if your pipeline is genuinely at risk, it’s probably the most important investment you’re not yet making.
The most expensive leadership decision most organizations make isn’t the one they make badly. It’s the one they keep postponing.
Understanding the workplace trends reshaping what effective leadership requires adds useful context here. Development systems built for the environment of five years ago often aren’t calibrated to the pressures leaders are carrying today.
Where Do You Actually Start?
Organizations that consistently build stronger leadership pipelines don’t begin with another program. They begin by understanding why previous programs didn’t change behavior.
That’s where Steve’s advisory work starts: with diagnosis before design. If you want to understand what’s driving the gaps you’re seeing in your own pipeline, the Promotable and Fireproof assessment is a practical starting point. Or you can learn more about Steve’s background and advisory approach to get a clearer sense of whether this is the right fit for your organization.
If you’re considering bringing this conversation to your leadership team or a broader audience, the speaking and keynote work covers these frameworks in a format built for executive and senior leadership audiences.
Frequently Asked Questions
How long does it actually take to see meaningful results from a leadership development program?
Meaningful behavioral change typically takes 18 to 36 months when the development system includes real-time feedback, manager accountability, and a culture where practicing new behaviors is safe. Organizations that expect visible transformation inside 90 days are usually measuring satisfaction scores rather than behavioral shifts, which tells you how people felt about the experience, not whether it changed how they lead.
What makes the Promotable and Fireproof framework different from a standard high-potential program?
Most high-potential programs are content-delivery vehicles. The Promotable and Fireproof framework begins with a diagnostic step that segments leaders by their actual development need rather than their performance rating. That distinction changes who gets which intervention and why, which is the difference between a program that looks good on paper and one that actually changes who gets promoted.
Why do so many programs fail even when the content and facilitation are strong?
Content quality is rarely the problem. Programs fail because they operate in isolation from the conditions that shape behavior: the norms a manager reinforces daily, the cultural signals about what gets rewarded, and the accountability structures (or absence of them) that follow the program itself. Strong content delivered into a system with no follow-through produces good feelings and very little change.
How do you know if your organization has a pipeline problem versus a hiring problem?
If you’re consistently promoting high-performing individual contributors who stall once they take on leadership roles, that’s a development and selection problem. If you’re losing high-potentials to competitors before they reach senior levels, that’s a retention and progression problem. Both are pipeline problems, and both require a systemic response rather than another standalone program.
Can a single business unit run this kind of development system without company-wide buy-in?
A single business unit can absolutely run a more disciplined leadership development system than the rest of the organization. In fact, business units that do this well often become the proof-of-concept for broader change. What doesn’t work is running a development system inside a unit whose senior leader isn’t willing to visibly model the behaviors being developed. That contradiction undermines everything else.
What role should the C-suite actually play in making leadership development work?
The C-suite’s role isn’t to attend the program. It’s to make the behaviors being developed visible, consequential, and normal in the organization’s actual operating environment. When senior leaders recognize and reinforce those behaviors in real decisions, the development system works. When they sponsor the program budget but don’t change their own behavior, even the most thoughtfully designed intervention dies on contact with the culture.
How is Steve Degnan’s background different from a typical executive coach or organizational consultant?
Steve Degnan spent 20 years as CHRO of a $13 billion company and served in the U.S. Army before entering the corporate world. His frameworks weren’t developed by observing organizations from the outside. They were built from operating inside them, leading succession planning, managing enterprise talent reviews under genuine business pressure, and being held accountable for outcomes at scale. Most executive coaches have coached. Steve has led, built, and been responsible for what happened next.
Steve Degnan is a keynote speaker and organizational advisor specializing in leadership development, promotable leader frameworks, and cultural transformation for large organizations. With 32 years of experience including two decades as CHRO of a $13 billion company, he works with Fortune 500 executives, CHROs, and senior leadership teams to build the conditions that produce resilient, promotable leaders and high-performing organizational cultures.
