The High Performer Trap
Why the person who saves the day can become the manager who blocks the team.
The most dangerous promotion is not promoting someone incompetent. That one is usually easy to spot, painful as it is.
The more dangerous promotion is promoting someone extremely competent and assuming the job changed because their title changed.
It often did not. Not enough.
Their calendar still rewards rescue. Their status still comes from answer quality. Their manager still asks them to keep the hard parts close. Their team still routes uncertainty upward because that is where certainty lives.
Six months later, everyone is surprised that the new leader is exhausted, the team is dependent, and the bench is thinner than before.
I think this is one of the quietest traps in leadership development. High performance is not the problem. Unedited performance is.
The behaviours that make someone exceptional in a defined individual-contributor role - speed, precision, ownership, personal reliability - can become constraints when the role starts creating value through other people’s capability, coordination, judgement, and growth.
Preference is not performance. Output is not potential. Being the person everyone trusts with the hardest work is not the same as being the person who can make everyone else better at hard work.
The wrong debate is whether high performers make bad leaders
They do not, as a category. That framing is lazy.
A high performer often has useful raw material for leadership: credibility, discipline, pattern recognition, stamina, taste, and enough scars to know what good work looks like. In technical teams, that credibility matters. Engineers can smell fake authority through concrete.
The wrong debate is whether high performers are leadership risks. The useful question is what kind of performance the organisation is still rewarding after the promotion.
If the scoreboard remains personal throughput, the new manager will keep playing the old game. Not because they are vain. Because the system is clear.
The research base is blunt on this point. Firms often promote people for visible current-role performance even when management effectiveness depends on partially different signals. The classic Peter Principle problem is not that workers become stupid after promotion. It is that the selection system overweighted the wrong evidence for the next job.
This is why the star sales rep becomes the sales manager who still wants to close the largest deals personally. This is why the best engineer becomes the tech lead who quietly rewrites every design doc. This is why the reliable operator becomes the supervisor who turns every escalation into a referendum on their personal standards.
They are not failing because they stopped caring. They are failing because they care using the old mechanism.
The old scoreboard follows them upstairs
The first managerial transition is an identity shock disguised as a promotion.
Before the promotion, the question was: Can you solve the problem? After the promotion, the question becomes: Can the team solve more and better problems because of you?
That is a different production system.
The high performer wants to be useful. The new leader has to become useful in a less immediately satisfying way. Less rescue. More context. Less answer. More judgement transfer. Less personal polish. More team-owned quality.
This sounds obvious, but teams miss it all the time because the old scoreboard is so emotionally clean. Finishing a task feels productive. Coaching someone through a task feels slow. Rewriting a proposal feels safe. Letting someone else ship a merely good version feels like negligence.
The organisation often makes the trap worse. It promotes the expert, keeps half their old workload, widens their span, and then tells them to be more strategic. This is not a transition plan. It is a controlled burn in a room full of paper.
Recent workplace data makes this sharper. Larger spans of control are becoming more common in some organisations, and managers often still carry substantial individual-contributor work. In that design, execution fixation is not just a personal habit. It is a rational response to a badly defined job.
So the newly promoted high performer does what has always worked. They absorb ambiguity. They carry quality. They become the final reviewer, the escalation path, the shadow owner of every important decision.
The team gets faster for a while. Then it gets weaker.
The first symptom is that they help too much
The phrase that gives the game away is, ‘I can do it faster.’
Usually, they can. That is the trap.
If the only question is who can complete the task fastest today, the high performer should keep doing the work. But leadership is not optimised for today’s isolated task. It is optimised for the team’s future capacity to handle a class of tasks without heroic intervention.
That is why helpfulness can become harm.
The star engineer who jumps into every code review is not just improving code. She is teaching the team that quality lives in her head. The finance lead who rewrites every board deck is not just protecting standards. She is teaching the team that judgement is not delegated, only formatting. The product lead who approves every small decision is not just staying close to the work. He is making speed dependent on his attention span.
High standards are not the enemy. Standards are useful. Taste is useful. A leader with no quality bar is just a calendar with opinions.
The problem is tying the standard so tightly to one’s own method that no one else gets to own meaningful work. Perfectionism becomes especially expensive here. It can look like care from the leader’s side and infantilisation from the team’s side.
The cost is delayed. That is why organisations tolerate it for too long.
At first, the team looks protected. Deadlines are saved. Quality is maintained. Senior stakeholders feel calm because the old hero is still nearby. Then review latency rises. Decision queues form. The best people leave for places where they can actually make calls. Junior people learn compliance instead of judgement. Succession plans become fiction with nicer fonts.
The manager has not become lazy. The system has become leader-dependent.
Delegation is not a moral virtue. It is an operating system.
We talk about delegation as if it were mainly a personality trait. Some leaders ‘let go’. Others ‘struggle to let go’. Fine. But that is not operational enough.
Delegation fails when authority, quality, risk, and feedback are vague. A high performer will not release control into fog. Nor should they.
The practical move is to make delegation boringly explicit.
First, name the decision rights. Who decides? Who advises? Who must be informed? Which decisions can be made without approval? Which ones need a second pair of eyes because the risk is genuinely high?
Second, name the quality bar. Not ‘make it good’. That is useless. Good compared with what? What trade-offs are acceptable? What must never break? Where is style flexible? Where is accuracy non-negotiable?
Third, name the feedback loop. When does the leader inspect the work? Before the decision, after the decision, or only when an exception is triggered? How will learning be captured so the next decision requires less oversight?
This is the difference between delegation and abandonment. Delegation is not dropping work on someone and hoping maturity appears. It is transferring ownership with enough context, constraints, and review rhythm that judgement can grow.
In novice teams, safety-critical work, regulated contexts, or crisis conditions, more direct control can be legitimate. The problem is not control. The problem is control that never decays as capability rises.
A good leader should know the difference between a risk tier and a comfort blanket.
A concrete reset for the star who just became the boss
Imagine Priya, a senior engineer promoted to lead a platform team.
Before the promotion, Priya was the person you wanted on the worst incident and the ugliest migration. She could see around corners. She wrote crisp design docs. Her code reviews were annoying in the correct way. Naturally, she got promoted.
Three months in, the team looks busy but oddly smaller than it is. Every design waits for Priya. Every production issue pings Priya. The strongest engineer on the team has stopped proposing changes because Priya will improve the proposal anyway. The juniors are learning Priya’s preferences faster than they are learning engineering judgement.
The solution is not to tell Priya to care less. That would be silly. The solution is to redefine where her care should go.
Week one: run a calendar audit. Split her time into personal production, review and approval, coaching, hiring and staffing, stakeholder alignment, and strategic design. If personal production is still the dominant category, the promotion has not really happened. It is just a pay-band costume change.
Week two: build a decision ladder with the team. Level one: bring me the facts and I decide. Level two: bring me a recommendation and I approve. Level three: decide, inform me, and capture the reasoning. Level four: decide without me unless an exception is triggered. The point is not to push everything to level four immediately. The point is to make movement visible.
Week three: transfer one genuinely important work package, not only admin crumbs. This matters. Delegating only low-stakes scraps teaches the team that trust is decorative. Pick something material, define the quality criteria, agree on check-in points, and let the owner choose the method unless the method creates real risk.
Weeks four to eight: replace rescue with coaching. In one-to-ones, Priya stops asking only, ‘What is blocked?’ and starts asking, ‘What decision are you trying to make? What options did you reject? What evidence would change your mind? Where do you want me to be precise, and where do you want me to stay out?’
Month three: measure whether the team is less dependent. Not by vibes. Track review latency, decision escalations, rework rate, time spent in personal production, and whether at least one direct report can now handle a class of decisions that previously required Priya.
This is not glamorous. That is why it works.
The high performer gets to keep their standards. The team gets access to the judgement behind those standards. The organisation gets a leader instead of a heroic bottleneck with a nicer title.
What to promote for instead
Organisations should stop treating promotability as a victory lap for individual output.
Output matters. It should. But once someone is being considered for a role where value is created through others, the assessment has to move upstream into leadership-relevant behaviour.
Ask different questions.
How has this person improved someone else’s judgement in the last year? What can their team now do without them? When have they handed over an important task and accepted a result that was not their preferred method but still met the standard? What feedback about their impact has been hardest for them to hear? Do people bring them weak signals early, or only polished answers late? Who gets stronger after working with them?
These questions are harder to score than revenue, code output, tickets closed, utilisation, or delivery heroics. That is the point. The target job is harder to see from the old dashboard.
A better promotion process uses multiple lenses: structured behavioural interviews, work simulations, multi-rater feedback, evidence of coaching behaviour, and stretch assignments before the formal move. The aim is not to find a flawless person. The aim is to find someone who can learn the new game and whose old strengths will not automatically sabotage it.
This also means giving serious experts a respected specialist path. Many organisations quietly force excellent specialists into management because that is where status, compensation, and influence live. Then they act surprised when some of those people keep behaving like specialists. The org chart made the deal before the person did.
Dual ladders are not a kindness. They are risk management. They reduce the pressure to convert every master craftsperson into a people manager and then spend two years repairing the predictable damage.
The manager’s manager is part of the problem
A newly promoted high performer rarely changes alone.
Their manager has to stop buying the old product. This is where many transitions die quietly.
The senior leader says, ‘Delegate more,’ and then privately routes the hardest task back to the star because the deadline is important. They say, ‘Build the team,’ and then praise the new manager most loudly when they personally rescue the release. They say, ‘Be strategic,’ and then leave all the old production load in place.
People are not confused by speeches. They read incentives with excellent literacy.
If you want the high performer to become a leader, their manager has to change the contract. The new contract should make team capability the work, not a nice extra after the real work is done.
That contract should include an explicit reduction in individual-contributor load, a definition of decisions the team should make without the leader, a small set of coaching expectations, and a review of bench strength as part of performance. Otherwise, leadership development becomes theatre: everyone nods at the workshop, then returns to the same operating system.
The problem is usually not that the high performer refuses to grow. It is that the organisation keeps paying them in prestige for not growing.
The useful question
High performance should still matter. I do not want managers who have never done hard things. I do not want leaders whose main skill is narrating complexity from a safe distance. Technical respect, commercial judgement, operational discipline - these are assets.
But leadership potential is not a louder version of current performance.
The useful question is not, ‘Who is the best?’ It is, ‘Best at what production system?’
If the next role requires the person to create output through others, then the promotion question has to change: What happens to the system when this person gets more authority? Does work multiply through them, or queue behind them? Do people grow sharper around them, or more cautious? Does the team inherit their judgement, or only wait for their approval?
A high performer who learns to transfer judgement is dangerous in the best way. They bring standards without hoarding ownership. They bring taste without cloning themselves. They bring urgency without turning everyone else into spectators.
A high performer who cannot make that shift becomes something else: not a bad person, not a failed talent, but a ceiling with a track record.
So before promoting the person who saves the day, ask the slightly annoying question.
After they get the title, will there be more people who can save the next one?
* * *
Notes and References
1. Uploaded research brief: When High Performance Constrains Leadership Potential, May 2026.
2. Alan Benson, Danielle Li, and Kelly Shue, ‘Promotions and the Peter Principle,’ The Quarterly Journal of Economics, 134(4), 2019, 2085-2134; NBER Working Paper 24343, https://doi.org/10.3386/w24343.
3. Ben Weidmann, Joseph Vecci, Farah Said, Sonia Bhalotra, Achyuta Adhvaryu, Anant Nyshadham, Jorge Tamayo, and David Deming, ‘How Do You Identify a Good Manager?’ The Quarterly Journal of Economics, 141(2), 2026, 1581-1633, https://doi.org/10.1093/qje/qjag004.
4. Edward P. Lazear, Kathryn L. Shaw, and Christopher T. Stanton, ‘The Value of Bosses,’ Journal of Labor Economics, 33(4), 2015, 823-861.
5. Todd J. Maurer and Manuel London, ‘From Individual Contributor to Leader: A Role Identity Shift Framework for Leader Development Within Innovative Organizations,’ Journal of Management, 44(4), 2018, 1426-1452, https://doi.org/10.1177/0149206315614372.
6. Allan Lee, Sara Willis, and Amy Wei Tian, ‘Empowering Leadership: A Meta-Analytic Examination of Incremental Contribution, Mediation, and Moderation,’ Journal of Organizational Behavior, 39(3), 2018, 306-325, https://doi.org/10.1002/job.2220.
7. Gavin R. Slemp, Margaret L. Kern, Kent J. Patrick, and Richard M. Ryan, ‘Leader Autonomy Support in the Workplace: A Meta-Analytic Review,’ Motivation and Emotion, 42, 2018, 706-724, https://doi.org/10.1007/s11031-018-9698-y.
8. Amy C. Edmondson, ‘Psychological Safety and Learning Behavior in Work Teams,’ Administrative Science Quarterly, 44(2), 1999, 350-383, https://doi.org/10.2307/2666999.
9. Kathleen Otto, Martin Baluku, Amelie Schaible, Cemre Oflu, and Emily Kleszewski, ‘The Only Way Is Up? How Different Facets of Employee and Supervisor Perfectionism Help or Hinder Career Development,’ Psychological Reports, published online 2024, https://doi.org/10.1177/00332941241229204.
10. Jim Harter, ‘Span of Control: What’s the Optimal Team Size for Managers?’ Gallup Workplace, January 14, 2026.
11. Randall Beck and Jim Harter, ‘Managers Account for 70% of Variance in Employee Engagement,’ Gallup Business Journal, April 21, 2015.
12. DDI, ‘New DDI Study Signals Looming Leadership Exodus, with 71% Reporting Increased Stress,’ Global Leadership Forecast 2025 press release, January 22, 2025.
13. Barbara B. Gaugler, Douglas B. Rosenthal, George C. Thornton III, and Cynthia Bentson, ‘Meta-Analysis of Assessment Center Validity,’ Journal of Applied Psychology, 72(3), 1987, 493-511, https://doi.org/10.1037/0021-9010.72.3.493.