At some point in 2024, I had a nearly identical conversation with four different HR directors at mid-market companies. The details varied — one was in logistics, one in fintech, one in healthcare software — but the core problem was the same: headcount had grown 60–80% over three years, the director-to-VP layer had tripled, and the L&D budget had maybe grown 15%. The math doesn't work. You can't build a leadership pipeline for 40 people using resources that were designed for 12.
This isn't a budget argument. Most of these HR directors weren't asking for more money — they knew that conversation was closed. They were asking how to do more with what they had, and they were genuinely unsure whether that was possible without dropping the quality bar on development entirely.
I want to share what we've observed from the teams who are actually making this work, because there are real patterns worth naming.
The unit economics problem nobody is solving correctly
The standard model for executive development is: hire a coaching firm, assign one coach per leader, run 6–12 month engagements at $15K–$35K per leader per year. That model works well when you have 6 VPs and a healthy budget. It breaks immediately when you have 35 directors who need development and your total L&D budget is $180K.
What makes this harder is that the default alternatives are worse in different ways. Group workshops are cheap but produce near-zero individual behavioral change — the research on knowledge transfer from passive learning to on-the-job behavior is brutal. Generic online courses check a compliance box. Internal mentoring programs are beloved by HR and ignored by the participants after month two.
The teams who are actually closing this gap are doing something different: they're treating development as a practice activity, not a learning activity. That distinction matters more than any budget discussion.
Approach 1: Shift from coverage to depth on your highest-leverage leaders
The first pattern I see in HR teams that are making this work is a deliberate decision to stop trying to cover everyone. Instead of spreading development evenly across 35 directors, they identify the 8–12 people who are within 12–18 months of a VP promotion decision and concentrate resources there.
This sounds obvious, but in practice most HR programs resist it because it feels inequitable. "What about everyone else?" The answer is: everyone else still gets access to the lower-cost development resources, but you're not pretending those resources are producing VP-ready leaders. You're being honest about what deep development costs and making deliberate choices about where to apply it.
This approach works best when you have a defensible framework for identifying who belongs in the concentrated cohort. Gut feel from a CHRO leads to political problems. A structured readiness assessment — one that produces dimension-level scores rather than a single number — makes the selection process defensible and gives the selected leaders a clear picture of what they're working on.
Approach 2: Replace passive learning hours with active practice time
The second pattern is about the type of activity, not the volume. Most L&D programs measure success in hours: 40 hours of development per leader per year. The problem is that most of those hours are consumption — watching a video, attending a webinar, reading a framework document. Consumption time has almost no correlation with behavioral change at the leadership level.
Practice time — time spent doing the actual skill under conditions that produce feedback — has a much stronger correlation. But practice time for leadership skills is hard to create because real leadership situations don't repeat on a schedule. You can't say "we'll practice termination conversations every Tuesday."
Simulation changes this calculus. When a director can spend 30 minutes in a scenario that replicates a board challenge or a cross-functional negotiation, they're getting practice reps that would otherwise only come once every 6–12 months in real situations. The practice hour is more expensive to design than a webinar hour, but you need far fewer of them to move the needle on a specific skill.
We're not saying passive learning has no place — a conceptual framework session before a simulation session is genuinely useful. The issue is when passive learning is the majority of what a program delivers and leaders are expected to somehow transfer those concepts to behavior on their own. Most don't. The program looks good on paper and produces very little.
Approach 3: Build a measurement system that proves value to the CFO
The third pattern is about measurement, and it's the one most HR teams skip because it's uncomfortable. If you can't connect your development program to business outcomes, it will always be the first budget cut. This is not a criticism of HR — the connection is genuinely hard to measure. But "hard" and "impossible" aren't the same thing.
Consider a mid-size B2B software company — roughly 400 employees, 18 directors in the cohort — that ran a structured simulation-based development program for 10 directors it identified as VP candidates. Over 14 months, six of those directors were promoted. The average time from director to VP for participants in the program was 11 months, versus 19 months for directors who weren't in the program. That's a measurement you can take to a CFO. It's not perfect — there are selection effects, and the promoted directors might have been promoted anyway — but it's far more defensible than NPS scores from a post-workshop survey.
The teams doing this well are tracking three numbers: promotion velocity (time from director to VP for program participants vs. non-participants), retention of high-potential leaders at the 18-month mark, and internal fill rate for VP openings (percentage of VP hires that come from within rather than external). None of these are perfect metrics, but together they tell a story that finance can engage with.
Approach 4: Restructure the program cadence around skill gaps, not calendar intervals
Most L&D programs run on a quarterly or annual cadence because that's how budget cycles work. The problem is that leadership skill development doesn't work on a calendar. A director who scores well on Strategic Communication but poorly on Accountability Framing needs to work on Accountability Framing now, not in Q3 when the next cohort workshop is scheduled.
The teams that are getting real efficiency gains are restructuring around individual development velocity rather than group calendar cadence. This requires a diagnostic capability — you need to know what each leader's dimension-level profile looks like before you can assign targeted work. But once you have that, you can concentrate development time on the specific gaps that matter for each person's readiness, rather than running everyone through the same curriculum on the same schedule.
The efficiency gain here is significant. If a director needs work on three specific dimensions to be VP-ready, and you can identify those three dimensions and target them directly, you can potentially cut the development timeline from 18 months to 10 months. That's not budget efficiency — that's output efficiency. You're producing VP-ready leaders faster, which means fewer expensive external VP hires and faster time-to-contribution when promotions happen.
What this adds up to
None of these four approaches requires a larger budget. What they require is a different theory of how leadership development works. The core shift is from coverage to precision: fewer people served more deeply, with practice activities rather than passive ones, measured by outcomes rather than hours, and structured around individual gaps rather than group calendars.
The budget constraint is real and it's not going away. But the constraint forces a kind of discipline that might actually produce better outcomes than an unlimited budget would. When you have to choose where to concentrate resources, you get serious about which leaders need what, and you stop accepting activity as a proxy for development.
That discipline is what the most effective HR teams have in common — not a larger line item.