High-Potential Flag on a Struggling Performer
A talent review calibration session is underway. A mid-level engineer, 'R,' was flagged as high-potential (HiPo) last year based on strong project delivery. This year R's manager rated them 'meets expectations' overall but noted declining engagement, two missed deadlines, and friction with a new team lead. R's skip-level believes R is 'still HiPo, just in a bad stretch.' Another calibration participant notes R has not been promoted in four years and peers have advanced. The nine-box grid currently places R in 'high performance / high potential.' The company uses the HiPo designation to allocate development budget, mentorship, and succession slates. HR facilitates the session and must recommend how to handle R's placement.
1. Should R remain in the HiPo pool? Provide a reasoned recommendation.
Read the worked answer
Recommendation: move R out of the active HiPo pool this cycle, with a documented re-entry path.
Reasoning:
- HiPo designation is a forward-looking judgment about trajectory, but the current evidence (declining engagement, missed deadlines, friction, no promotion in four years) contradicts the 'high potential' signal. Keeping R in the pool based on last year's data or a skip-level's optimism is a recency/confirmation-bias error.
- The nine-box placement is inconsistent: 'meets expectations' performance does not support 'high performance.' At minimum, R should move to the 'moderate performance / moderate potential' cell pending evidence.
- Scarce development resources (budget, mentorship, succession slots) should follow demonstrated trajectory; misallocating them to R deprives a genuinely rising employee.
Re-entry path: define observable criteria (sustained performance, resolved team friction, engagement signals) and a review date. The designation should be a status, not an identity.
2. How should HR communicate the decision to R and the manager, and what risks must be managed?
Read the worked answer
Communication principles:
- To the manager: explain the calibration rationale in behavioral terms (evidence, not labels), and confirm the manager's role in the development conversation. Do not let the manager hear it as a punishment.
- To R: frame around development, not demotion. Be honest that the HiPo pool has specific criteria R is not currently meeting, share the observable criteria, and offer a concrete development plan (e.g., mentorship, a stretch assignment with support). Avoid vague 'you're still valued' messaging that contradicts the decision.
Risks:
- Engagement/retention: R may disengage further or leave; the conversation should include a retention check.
- Legal/equity: ensure the decision is documented and applied consistently across similar cases; inconsistent HiPo removal can look discriminatory.
- Manager trust: the manager may feel overruled; clarify that calibration is a shared decision.
- Confidentiality: HiPo status should not be discussed with peers; leaked removal damages trust.
The judgment: transparency about criteria reduces the risk of perceived unfairness far more than softening the message.