When Your Best Player Makes Your Team Worse
Elena was the kind of employee every manager wants.
Fast, sharp, completely unflappable under pressure. When equipment went down, Elena had already called maintenance before I got the radio call. When a new associate couldn’t find her footing in the second week, Elena had quietly paired her with someone who could show her the ropes. When a quality exception surfaced mid-shift, Elena had flagged it, documented it, and started the corrective action before anyone else had fully registered there was a problem.
The team ran beautifully. I attributed it to good culture, consistent training, and the systems we’d built. What I hadn’t noticed—not clearly, not yet—was how much of it was Elena.
Then Elena got promoted. Rightly so, deservedly so, a move I’d advocated for. But over the following two weeks, something became apparent that I hadn’t seen coming.
Nobody else knew how to do half of what Elena had been doing.
Not because they were incompetent. They’d been working alongside Elena for months. They’d watched everything. They just hadn’t done it, because Elena was always there first, answering the question before anyone else had time to think, solving the problem before anyone else had to work through it, making the judgment call before the situation had a chance to develop anyone else’s judgment.
Elena hadn’t been building a team. Elena had been running the team. And I had let it happen, because the results looked so good.
This Isn’t a Performance Problem
The first thing to understand about this dynamic is that it’s nobody’s fault in the conventional sense.
Elena wasn’t undermining the team’s development on purpose. Elena was doing exactly what a high performer does: stepping up, taking responsibility, solving problems as fast as possible. Every individual decision was correct. The cumulative effect—a team that had learned to route everything through Elena rather than develop its own capacity—was a management problem, not an Elena problem.
That distinction matters enormously when it comes to what you do about it.
This isn’t a conversation about asking your best performer to do less. It isn’t about punishing excellence or engineering mediocrity. It’s about a specific management failure: allowing a star’s individual performance to become a substitute for your team’s collective development. Those are different things, and conflating them leads to the wrong solutions.
Individual excellence and team capability are not the same thing. A team with one exceptional performer and nine people who’ve learned to defer to her is less capable, less resilient, and less developable than a team where the excellence is more evenly distributed, even if it looks better in the daily numbers.
A star’s individual performance is not a substitute for your team’s collective capability. The first can mask the absence of the second for a long time.
Three Ways Stars Unintentionally Block Development
The mechanism is different in each case, which means the management response has to be different too.
The Answer Machine
Your most experienced associate is the first person everyone asks when something comes up. She knows the process cold. Her answers are always right. When a new associate has a question, she responds before the team lead has a chance to. When a problem surfaces, she names the solution in thirty seconds.
The natural result is the team stops thinking. Not lazily—rationally. If the answer is always available in thirty seconds from the same source, investing effort in developing your own judgment has no payoff. Over time, the team’s problem-solving capacity doesn’t just stall, it atrophies. The associates who would have developed strong operational judgment instead develop the habit of asking Elena, and Elena becomes the answer to every question whether she intends to be or not.
The Pacer
Your fastest sorter sets a pace nobody else can match. She isn’t trying to demoralize anyone; she’s just doing her job at the level she’s capable of. But the gap between her output and everyone else’s is visible, constant, and demoralizing in a way that doesn’t show up in your metrics. Associates who might otherwise push their own pace stop trying, because the comparison is always unfavorable. The implicit standard on the floor becomes “as fast as the fastest person,” which is a standard most people have concluded they can’t meet.
The paradox here is that your fastest associate’s performance may be holding your floor’s average down. As I explored in How to Raise the Floor, Not Just the Ceiling, your throughput is set by your average, not your best. If your best performer’s visible excellence is causing your middle to disengage from the effort to improve, you have a net negative—and it started with your star.
The Shield
Your best team lead handles problems so completely that the associates working under her never have to develop the capacity to handle those problems themselves. She doesn’t mean to shield them; she’s being thorough, responsible, doing her job well. But her competence creates a protected environment where no one else has to struggle through difficulty, and struggle is exactly what develops capability.
This is the version I encountered with Elena. It’s subtler than the first two because the star’s behavior looks like strong leadership. The team lead who handles everything seamlessly is easy to praise and hard to critique—until she’s promoted and the seam shows.
The Research Behind the Pattern
This isn’t just a floor-level observation. Research published in Personnel Psychology by Elizabeth Campbell at the University of Minnesota found that high performers positively influence their non-star teammates—up to a point. Above that point, the returns don’t just diminish, they reverse.
Campbell’s team found that the optimal team composition sits around 25% star performers and 75% non-stars. Spread out, stars lift the people around them; newer employees especially benefit from working alongside someone exceptional. But stack too many stars on one team, and the dynamic shifts. The positive influence flips negative, and collective performance drops below what you’d expect given the talent in the room.
The implication for floor-level management isn’t about team composition so much as about what concentration of excellence in one person does to everyone around them. When one performer is so far ahead of the rest that the gap feels uncrossable, the motivational lift disappears and something closer to learned helplessness can settle in. Your star stops being an example and starts being a ceiling.
What to Do About It
The goal isn’t to restrain your star. It’s to channel her differently.
The most important move is giving Elena a development mandate alongside her performance mandate. She could have been doing exactly what she was doing—but with a specific expectation attached: her job isn’t just to solve problems, it’s to develop the people around her by letting them work through problems first. That’s a genuinely different job description. Elena couldn’t have made that shift without being told it was the expectation, and that conversation is the manager’s job to initiate.
This connects directly to the Strategic Delegation framework—the most powerful development tool you have is assigning the right responsibility to the right person with the right support structure. For a star performer, that sometimes means assigning them the responsibility of not doing something, because their restraint creates the space others need to develop.
From there, protecting space for struggle is the practical application. When Elena is on shift, make it explicit that associates should attempt to work through problems before going to her—and that Elena should let them. Not letting problems compound unaddressed, but building a ten-minute window where the person with the question tries to reason through it before the answer appears. That ten-minute window is where development happens.
It also means separating Elena’s performance from the team’s performance in your own thinking. Look at what your floor produces without her present. That picture, the honest one, is the team you’ve actually built. If there’s a significant gap, the development work isn’t finished regardless of what the daily numbers say while she’s there.
The pacing problem has its own lever. When a star’s visible pace is demoralizing rather than inspiring, the answer isn’t to slow her down, it’s to build recognition around rate of improvement rather than absolute performance. An associate who moves from 85% to 95% productivity has done something worth recognizing, even if the person next to her is running at 110%. As I explored in Why Positive Feedback Comes First, recognition shapes what people believe they’re capable of. Calibrating it to growth rather than comparison is the management move that fixes the pacing problem without penalizing the star.
The Conversation You Need to Have
At some point, all of this requires a direct conversation with your star.
Not a critique—she hasn’t done anything wrong. A reframe of what excellence at her level actually looks like.
The conversation I wish I’d had with Elena earlier sounds something like this: “You’re doing everything right. The floor runs well because of what you’ve built. What I want to talk about is what the next level of impact looks like for you—and I think it’s in what you create in the people around you, not just what you do yourself. The question I want us to think about together is: what would this floor look like if everyone around you was developing at the rate you developed?”
That conversation does several things at once. It frames development as part of Elena’s job, not a limitation on it. It positions restraint and coaching as advanced skills rather than reduced contribution. And it ties Elena’s success to a metric (the capability of the people around her) that didn’t exist before.
Stars who are ready for the next level respond well to this framing. It gives their excellence somewhere to go. The ones who resist it are often telling you something important about whether they’re ready for more responsibility, or whether they’ve confused individual performance with leadership.
This is a thread I’ll pull further in the next article in this series, which looks at what psychological safety actually means in an operational environment and why the behavior of your highest-confidence performers is one of its biggest determinants.
Summary
Your best performer isn’t a problem. But the way you’re deploying them might be.
When a star’s excellence becomes the answer to every question, the pace everyone else is measured against, or the shield that keeps the rest of the team from having to work through difficulty—individual performance has become a substitute for collective capability. That substitution looks fine in the daily numbers and shows up clearly the moment the star is gone.
The highest expression of individual excellence in an operational leader isn’t what she produces. It’s what she makes possible in everyone around her.
The management move isn’t to restrain excellence. It’s to channel it: give your star a development mandate alongside her performance mandate, protect space for the team to struggle productively, and have the conversation that reframes her impact in terms of what she creates in others, not just what she produces herself.
From Theory to Action
Run the Elena test. Think about your strongest performer right now. If she were promoted or transferred tomorrow, what would the team be able to handle? What would stall? Be specific. The gap between those two lists is where your development work needs to go.
Watch for the Answer Machine pattern this week. Pay attention to who fields questions on your floor and how quickly. When your star answers before anyone else has had five seconds to think, that’s a data point. It’s not a problem yet, but it will be if the pattern holds for months. What would it look like to build a five-minute “try it first” norm before the answer becomes available?
Check your recognition for comparison traps. Pull your last two weeks of recognition moments. Were any of them framed in a way that implicitly benchmarked others against your star? “Great job! That’s the standard I want everyone at” sounds positive, but it sets a ceiling in the same breath. Recognition that focuses on individual improvement doesn’t carry that cost.
Have the development conversation with your star. Not as a critique , but as a reframe. What would it look like if her job included developing the capability of the people around her, not just performing at a high individual level? What would she need from you to make that shift? Listen to the answer carefully. It tells you a lot about where she is in her own development.
Build in structured struggle. Pick one category of problem that your star currently handles by default and explicitly hand it to someone else for the next month. Your star is available as a resource if things go sideways, but the first attempt belongs to someone else.
Look at your floor’s performance distribution. The research from the University of Minnesota points to 25% stars as the rough optimal. You probably can’t engineer that number precisely, but the direction matters: are your stars concentrated on one shift or spread across the operation? Concentrated star power tends to create a dependent floor. Distributed star power tends to lift the average.
Revisit this conversation quarterly. The “let me develop the people around me” mandate isn’t a one-time reframe—it’s a new part of your star’s job description that needs to be tracked and recognised. In your one-on-ones, ask what she’s specifically done to develop someone else’s capability this month. The question signals that it counts. Signals are how culture gets built.
This post is part of the Building High-Performance Teams arc, following How to Raise the Floor, Not Just the Ceiling and The Culture You’re Building Without Knowing It.
Next: Psychological Safety on the Production Floor—what it actually means in a warehouse environment, and why your highest-confidence performers are one of its biggest determinants.