How to Build a Leadership Pipeline for Roles That Don't Exist Yet

Traditional pipeline development maps current roles to current high-potential employees and builds development plans around closing the gap between the two. That approach breaks down when the target role is genuinely unknown — you can't develop someone into a job that hasn't been defined, like 'AI orchestration lead' or whatever emerges next.

What works instead is investing in transferable meta-capabilities: the ability to learn a new domain quickly, comfort operating without a precedent to copy, and strong foundational judgment. Enterprises building genuinely future-proof pipelines are testing candidates against ambiguous, novel problems rather than well-defined case studies, because the ability to perform well on a known case study says little about how someone handles a genuinely new situation.

One concrete method some organizations use: rotate high-potential employees through genuinely unfamiliar problem spaces on purpose — a finance leader spending a stretch embedded with the product team, an operations lead taking on a customer-facing project — specifically to observe how quickly they orient in unfamiliar territory. The rotation itself matters less than the observed pattern of how fast someone builds competence from a standing start, which turns out to be a strong proxy for readiness in roles that don't exist yet.

This also requires a cultural shift in how 'readiness' gets assessed. Instead of asking whether someone has already done something similar before, the better question is whether they've shown a track record of figuring out things they hadn't done before.

Pipelines built on that criterion are far more resilient to the fact that the roles at the top keep changing shape — and they tend to surface a different, often overlooked set of candidates than pipelines built purely on past performance in a fixed role, because comfort with ambiguity and past role performance don't always correlate.