There's a size band — roughly 200 to 2,000 employees — where the VP pipeline problem is most acute and least well-served by existing solutions. Too big to rely on informal mentoring and founder proximity. Too small to justify a dedicated people-development infrastructure with dedicated L&D staff, a custom curriculum, and a full-time executive coach on retainer. Companies in this band are creating VP roles faster than they're producing VP-ready leaders, and the gap is getting filled with expensive external hires that often underperform because they don't know the business.
I've spent time with HR and L&D leaders at about two dozen companies in this size range over the past year and a half. What I want to share here are the structural patterns I've observed in the ones that are actually building functional VP pipelines — not best practice platitudes, but the specific choices these teams are making about how to identify, assess, and develop director-level leaders who are approaching VP readiness.
The pipeline failure pattern: identifying late and developing too slowly
The most common pattern in mid-market companies that struggle with VP pipelines is a combination of late identification and diffuse development. Leaders are identified as VP candidates 6–9 months before the role needs to be filled, which leaves almost no time for meaningful development. And when development happens, it's usually a generic leadership program — a cohort workshop series, a book list, a 360 feedback tool — rather than targeted skill-gap remediation.
The result is predictable: the internal candidate isn't ready, the company hires externally, the external hire costs 30–40% more in total compensation than an internal promotion would have, and the institutional knowledge gap the external hire creates takes 12–18 months to close. Meanwhile, the internal director who wasn't promoted is evaluating whether to leave, which usually means the company loses the person they needed to develop for the next VP role two years from now.
The companies building functional pipelines have solved the late identification problem first, because no amount of development quality fixes a timeline that's too short.
Pattern 1: Starting the clock 18–24 months out, with formal succession tagging
The consistent first move in companies that have functional pipelines is shifting from reactive succession planning ("we need a VP of Product, who's closest?") to proactive identification ("who do we want to be VP-ready by Q3 next year?").
This sounds obvious. In practice, it requires explicit process change because the organizational default in growing companies is to defer succession conversations until a role opens. The costs of that deferral are invisible until the role opens and the pipeline is empty — at which point the pressure to hire externally becomes overwhelming.
The companies doing this well have three things: a formal succession map that's reviewed at least quarterly at the CHRO level, explicit "VP candidate" tagging in their HCM system with an expected readiness date, and a development program activation trigger that fires as soon as someone is tagged. The first two are about visibility. The third is about converting visibility into action before the window closes.
One mid-size cloud infrastructure company — around 650 employees — implemented this as a quarterly talent review where every director-level role has a named succession candidate with a readiness assessment attached. The CHRO owns the review. The output of each quarterly review is a prioritized list of directors whose development programs need to be started or accelerated, with the specific readiness gaps noted. That output goes directly to the L&D function for activation.
Pattern 2: Structured readiness assessment with dimension-level output
The companies that are making real progress on VP pipeline development are using a structured, behavior-based readiness assessment rather than relying on manager perception. Manager perception is the standard approach — the hiring manager's subjective sense of who is "almost ready" — and it has well-documented limitations: it over-indexes on communication style, under-indexes on less visible skills like cross-functional influence and strategic judgment under pressure, and introduces various forms of affinity bias.
A structured readiness assessment doesn't eliminate bias, but it shifts the conversation from "I think she's ready" to "she scores 7.1 on Strategic Communication and 4.3 on Accountability Framing — let's look at what's driving the Accountability gap before we make a decision." That shift is significant because it makes the development conversation specific and actionable, rather than a vague "she needs to grow into the role."
The assessment format matters. A 360-degree survey that asks people to rate "demonstrates strategic thinking on a scale of 1–5" doesn't produce useful diagnostic information — everyone gets a 3.7 and no one knows what to do with it. An assessment that involves the leader performing in a realistic scenario and being scored on observable behaviors within specific dimensions produces information you can actually develop against.
Pattern 3: Development that directly addresses identified gaps, not a generic curriculum
Generic leadership programs — cohort workshops, lecture series, curated reading lists — have their place in building shared vocabulary and cultural alignment around what leadership means at a given company. But they produce almost no individual behavioral change because they're not designed to. They're designed to be broadly relevant to all participants, which means they're not precisely targeted at any individual's specific gaps.
The mid-market companies building functional pipelines are pairing generic curriculum with targeted individual work. The generic curriculum runs at the cohort level — quarterly or monthly — and handles the conceptual and cultural layer. The targeted individual work runs between sessions and is driven by each person's readiness assessment data.
In practice, this means a director whose readiness profile shows a gap in Conflict Navigation is doing focused practice work on conflict scenarios every two to three weeks, not waiting for the cohort workshop in Q3 where conflict is one section of a broader leadership effectiveness module. The targeted work closes the gap faster, and the cohort curriculum reinforces the framework while providing context for why the skill matters at VP level.
The HR teams getting this right are explicit that the two layers serve different purposes and they don't try to collapse them. They've stopped expecting generic curriculum to produce individual skill change, and they've stopped expecting individual drill work to build the shared leadership culture that the cohort curriculum creates. Both are necessary; neither substitutes for the other.
Pattern 4: Tracking promotion velocity as the primary program metric
The last pattern I want to highlight is about measurement, and it's the one that often gets the least attention because it requires the most patience. VP pipeline programs have long feedback loops — you invest in a director today and see whether they're ready for a VP role 12–24 months from now. That makes it tempting to measure what's immediately available: program completion rates, post-session NPS, assessment score improvements.
Those metrics are useful as leading indicators, but the lagging indicator that actually matters is promotion velocity: how long does it take from a leader entering the development program to being promoted into a VP role? And secondarily: what percentage of VP roles are being filled from the internal pipeline versus external hiring?
The companies that have been running structured VP pipeline programs for 2–3 years are starting to see signal in these numbers. Internal fill rates for VP roles at companies with formal pipeline programs tend to run 15–25 percentage points higher than at comparable companies without them. That's a business outcome that justifies the investment, and it's the kind of number that makes the CHRO's conversation with the CFO significantly easier.
We're not saying that running a pipeline program guarantees a higher internal fill rate — selection effects are real, and companies that invest in pipeline programs also tend to have other talent-positive practices that contribute to the outcome. But the correlation is strong enough that if you're running a pipeline program and your internal fill rate for VP roles isn't improving over time, that's a signal worth investigating.
The organizational condition everything else depends on
All four of these patterns assume one underlying condition that isn't always present: a CEO and leadership team who genuinely believe that developing internal talent is a strategic priority, not a nice-to-have. In companies where VP roles get filled externally by default — because it's faster, or because external candidates are seen as bringing "fresh perspective," or because the CEO simply hasn't thought about the costs of not developing internally — none of the patterns above will take hold, because the organizational incentive structure doesn't support them.
The HR directors I've talked to who are making the most progress on VP pipelines all have some version of an explicit leadership team commitment to internal development as a preference. Not a mandate — external hires still happen, and sometimes that's the right decision. But a stated preference for internal candidates when an internal candidate is at least 80% ready. That preference, when it's real and consistent, changes everything about how development programs get funded, prioritized, and measured.
Without it, a pipeline program is a tree planted in concrete. The infrastructure can be excellent and the development quality can be high, but the organizational conditions won't let it grow.