The High-Potential Development Playbook: A Recipe for Accelerating Your Best People
Most companies identify their high-potential employees. Few do anything systematically useful with the identification.
The employee gets labeled HiPo in a talent review. Their manager knows. Maybe the employee hears a vague signal that they're "being invested in." Then nothing changes. The employee gets the same work, the same feedback cadence, the same development conversations they'd get otherwise — just with higher stakes if they leave.
Within 18 months, many of them have.
This playbook gives you a recipe for developing high-potential employees in a way that actually accelerates their trajectory — not through expensive programs, but through structured experiences that build the specific capabilities they need at the next level, fast.
The Recipe at a Glance
Outcome you're trying to achieve: A high-potential employee who, within 12–18 months, is operating at the next level — with documented evidence of the development, not just the manager's impression.
Ingredients:
- A clear definition of what "high potential" means at your organization (capability + trajectory + commitment)
- A skills gap analysis for the specific path you're accelerating them toward
- Two or three targeted development experiences (not a program — experiences)
- Increased feedback frequency during development, not just at review time
- Explicit conversations with the employee about what you see in them
When to use this: After a talent review identifies an employee as high-potential, or when a manager has a strong conviction that an employee is operating below their ceiling.
When NOT to use this: For high performers who aren't necessarily high potential. High performance is about what someone does at their current level. High potential is about what they could do at the next two or three levels. These often overlap but don't always — a technically excellent individual contributor may have no interest in management and that's fine.
Step 1: Be Clear About What You're Accelerating Toward
High-potential development fails when it's general. Accelerating toward "a more senior role" is not a plan. Accelerating toward a specific role, or a specific type of leadership, with specific capability requirements — that's something you can build toward.
Before designing any development, answer:
What is the two-step target? If the employee is currently a Senior Engineer, what does their path look like to Staff Engineer and then Principal — or to Engineering Manager? High-potential development is most effective when it prepares someone for two levels up, not just one.
What capabilities are currently the gap? Compare where they are now against what the target level requires (using the promotion criteria from your organization). The gap is what needs closing. These are the development priorities.
What is the timeline? High-potential development isn't indefinite. A 12–18 month window with a specific destination is more actionable than "we're investing in your career." Set a nominal target date. It can move. But having it creates urgency.
Write this down. Share it with the employee. High-potential status is worth nothing if the employee doesn't know they have it and doesn't understand what you're building toward.
Step 2: Assign Targeted Experiences, Not Generic Development
High-potential employees rarely benefit from training programs designed for the average employee. They develop faster through targeted experiences — work that forces the specific capability they're building.
The most effective development experiences for high-potential employees:
Cross-functional exposure: Assign them to a project that requires working with a part of the organization they've never touched. High-potential employees who will eventually need to lead across functions need to understand how other functions operate, what their priorities are, where the conflicts emerge. A six-week cross-functional project builds more organizational literacy than a semester-long leadership course.
Presenting upward: Give them opportunities to present work to senior leaders, not as support for their manager's presentation but as the primary presenter. The feedback loop is faster, the stakes are higher, and the calibration against executive expectations happens directly.
Owning a consequence-bearing decision: Find a decision that genuinely matters — one where the wrong call has a real cost — and give them ownership. Not nominal ownership with a manager safety net that overrides every call. Real ownership, with coaching available if they ask for it. This is different from a stretch assignment with a clear right answer. High-potential development requires experience with ambiguity and accountability.
A formal mentoring relationship with someone two levels up: Not the employee's manager. Someone whose job is to help the employee understand what operating at the target level actually looks like, from the inside. This is different from job shadowing — the mentor should be giving candid feedback on the employee's thinking and decisions, not just demonstrating.
Pick two or three of these, not all four. Focus beats breadth for development.
Step 3: Increase Feedback Frequency During Development
High-potential employees develop faster when feedback is frequent and specific, not when it's more positive.
The standard feedback cadence — performance reviews twice a year — is too slow for accelerated development. By the time annual feedback reaches the employee, the behavior being discussed is months old. They can't connect it to anything they remember or change it in context.
During an active development window, increase feedback to:
Weekly: A brief observation at the end of the 1:1. "In the meeting on Tuesday, I noticed you let the engineering lead frame the trade-offs before you weighed in. That's the right instinct — here's what I'd add to it." Takes three minutes.
After any high-stakes event: Feedback within 24 hours of a presentation, a difficult client call, or a consequential decision. The window for useful feedback after a significant event is short. Day-of is best. Week-later is close to useless.
Calibrated against the target level: Every piece of feedback should be framed against the target level, not the current level. "That was a good call given where you are" is less useful than "at the Staff level, that would be the expected call — here's how a Principal-level decision would look different."
This requires the manager to be paying closer attention than usual. If the manager can't point to three specific observations per week during a development window, they're not positioned to give the feedback the employee needs.
Step 4: Have the Explicit Conversation
Many high-potential employees don't know that's what they are.
Their manager says things like "I see big things for you" or "you're going to go far." The employee appreciates it and has no idea what it means.
Have the explicit conversation. It should include:
What you see. Specific capabilities — not "you're amazing." "I've watched you navigate ambiguous stakeholder situations three times in the past quarter. Every time, you found alignment without escalating. That's a skill most people at your level don't have yet."
What the path looks like. "I think you're on track for [level] within [timeline]. The capabilities you need to build to get there are [X] and [Y]. I want to invest in helping you get there."
What the development plan is. "Specifically, here's what I'm going to do to help you develop those capabilities over the next 12 months." (Not a generic commitment — a specific plan.)
What you need from them. "This only works if you're willing to take on work that's uncomfortable and ask for feedback when you're uncertain. That's the expectation."
This conversation shifts the relationship from passive investment (you're being invested in) to active partnership (we're building toward something together). Employees who know what they're building toward are far less likely to leave for an opportunity that looks like the same destination but arrives sooner.
Step 5: Review Progress Quarterly, Not Annually
Twelve-month development plans that only get reviewed at month twelve produce twelve-month surprises. Either the employee developed faster than expected and is ready early. Or they ran into barriers in month three that nobody caught.
Quarterly reviews of a high-potential development plan should answer:
Which experiences have actually happened? Not were planned — happened. If cross-functional exposure was on the plan and we're at month three with nothing, that's a problem to surface now.
What feedback has the employee received? If you can't point to specific feedback given in the past 90 days, the manager hasn't been doing the work.
Where are they against the target capabilities? Using the same behavioral descriptions from your promotion criteria — where are they now versus 90 days ago? What's the evidence?
Is the timeline still realistic? If the answer is "we need more time," identify why — was the target too ambitious? Were the development experiences not happening? Did something change in the employee's situation?
Adjust the plan at the quarterly review. Don't wait for the annual cycle to course-correct.
Common Failure Modes
Confusing high performance with high potential. High performance is about results at the current level. High potential is about ability to operate effectively at higher levels — which often requires different skills than what made someone successful at the current level. An excellent individual contributor may not have the leadership capabilities required at the manager level. Identify the gap early.
Development without the employee knowing why. The manager assigns cross-functional projects, arranges executive presentations, finds mentors — but the employee thinks they're just busy. The connection to their development trajectory is never made explicit. When an outside offer arrives, the employee doesn't weigh their internal development investment against it because they don't know it exists.
Too many high-potentials. When 40% of a team is labeled high-potential, the label means nothing. Selective identification forces you to be specific about who actually has the potential to operate two levels up. If everyone does, you haven't done the work.
Development without accountability. The manager designs a development plan, shares it with the employee, and then leaves execution to the employee. High-potential development requires the manager to actively create experiences, not just assign them and wait.
What a Healthy High-Potential Pipeline Looks Like
In organizations with effective HiPo development:
- Every high-potential employee can articulate where they're being developed toward and why.
- Every high-potential employee has had a development experience in the past 90 days — not just a plan.
- Promotion rates for employees identified as high-potential are meaningfully higher than for the broader employee population.
- High-potential employees who don't get promoted within the expected window receive a clear explanation of what's different from the original timeline.
- Voluntary attrition among identified high-potential employees is tracked explicitly, and departures are treated as development failures, not inevitabilities.
How Confirm Supports This Process
Identifying high-potential employees is only useful if the data behind the identification is trustworthy. Impressions-based talent reviews produce inconsistent HiPo designations — employees with visible managers get labeled, employees in quieter roles get missed.
Confirm uses organizational network analysis and structured performance data to surface employees whose impact extends beyond what their manager can directly observe. This matters particularly for high-potential identification, where the employees most worth investing in are often the ones doing work whose value is hardest to see from a single vantage point.
See how Confirm surfaces hidden high-potential employees →
FAQ
Should you tell an employee they've been identified as high-potential?
Yes. The alternative — investing in their development without telling them — creates confusion and misses the motivational effect of the explicit conversation. Some organizations worry that telling employees they're high-potential creates entitlement or disappointment if timelines don't work out. That's a risk worth taking. The alternative risk — that the employee leaves because they don't know you're invested in them — is much larger.
What happens when a high-potential employee's performance dips?
Development windows are inherently stressful. Employees taking on stretch responsibilities sometimes struggle. A performance dip during an active development window is usually a signal that the challenge level is calibrated correctly, not that the employee isn't high-potential. Monitor it, increase feedback, adjust the stretch if the dip persists for more than one quarter.
How many high-potential employees should a manager have at once?
Most managers can actively support one or two high-potential development relationships at a time. More than that and the increased feedback cadence, active experience creation, and quarterly reviews become unsustainable alongside normal management responsibilities. If you have five employees you want to develop aggressively, sequence them.
What if the high-potential employee wants to go in a different direction?
Find out early. The explicit conversation in Step 4 should include a question about what the employee wants — not just what you see in them. High-potential development that's heading toward a management path for an employee who wants to stay an individual contributor is well-intentioned misdirection. The best development plans are built on what the employee wants to become, not just what you think they're capable of.
