Every team has one. The top performer. The person who hits every number, ships early, never misses a deadline. On paper, they’re your best hire in years. In every one-on-one, you tell them how much you appreciate them, and you mean it.

And underneath that, your team is slowly falling apart.

Nobody wants to say anything, because how do you complain about your top performer? You’d sound ungrateful, or worse, like you’re punishing someone for being good at their job. So you don’t say anything. Neither does anyone else. The resentment just sits there, quietly compounding, while you keep pointing to the metrics as proof everything’s fine.

It isn’t fine. You’ve just been measuring the wrong thing, and it’s one of the reasons your team’s performance is stagnant.

Individual Excellence Isn’t Team Performance

Here’s where most leaders get tripped up: they treat team performance as the sum of individual performance. Add up enough strong individual scores and you should get a strong team score. Except teams don’t work like a spreadsheet. They work like an ecosystem, and one organism thriving at the expense of the others isn’t health. It’s a parasite that happens to look productive.

I’ve watched this play out the same way more times than I can count. A brilliant engineer who won’t document their work because “it slows them down.” A sales rep who hits quota by quietly poaching leads from teammates. A project lead who bulldozes every planning meeting because they’re usually right, and being usually right has taught them nobody else’s input matters.

Every one of those people would score a 10 out of 10 on individual output. Every one of them is actively taxing the team around them, and that tax doesn’t show up on a dashboard. It shows up six months later, when your second-best person quietly puts in their notice and tells you in the exit interview that they just couldn’t compete with someone who didn’t play by the same rules.

The Metric You’re Not Tracking

Ask yourself what you’re actually measuring when you call someone a top performer. If it’s purely output, revenue, tickets closed, code shipped, you’re measuring one axis of a two-axis problem.

The second axis is trust. Does this person make the people around them better, or worse? Do teammates go to them for help, or avoid working with them when they can? Would the team’s output actually drop if this person left, or would it just quietly go up once the friction disappeared?

That second question is the one most leaders are afraid to ask, because sometimes the honest answer is the one you don’t want. But if you’re serious about building a high-performing team instead of a talented one, you don’t get to skip it.

Why This Gets Worse in Technical Environments

This pattern shows up everywhere, but it’s especially common in STEM and technical teams, where individual expertise is easy to measure and collaboration is not. Engineering, IT, R&D, government program environments, anywhere the work itself rewards depth over breadth. The most technically skilled person in the room often gets a pass on behavior that would sink anyone else, because their competence buys them cover.

I’ve sat in enough leadership rooms across aerospace, defense, and IT portfolios to watch this exact dynamic play out at scale. Leaders protect their top technical talent because replacing that expertise feels impossible, and in the short term, it might be. But protecting the behavior instead of addressing it trains everyone else on the team that the rules are optional if you’re good enough. Once that lesson lands, you don’t have a high-performing team anymore. You have a hierarchy of who’s allowed to cause problems.

What To Do Instead of Nothing

You don’t fix this by firing your best performer the day you notice the pattern, and you don’t fix it by ignoring it either. You fix it the same way you’d fix any other performance gap: name it directly, tie it to a standard, and give the person a real chance to close the gap.

A conversation that actually works sounds something like this:

“Your output is genuinely excellent, and I want to be clear that I see that. I also need to talk about something separate from your output. I’ve noticed [specific behavior], and I’ve heard from more than one person that it’s affecting how the team works together. That’s part of the job too, not a side issue. I need to see that change, and I want to help you get there.”

Notice what that script does. It doesn’t pretend the output doesn’t matter. It doesn’t attack the person’s competence. It just refuses to let competence buy silence on the second axis.

Rebuilding Trust as a Team Metric

If you want a high-performing team and not just a team with one high-performing person, trust has to become something you actually track, not just something you hope for. That means paying attention to who people go to for help, who gets avoided in project assignments, whose name comes up when someone’s deciding whether to stay or leave.

None of that shows up in a quarterly report. All of it determines whether your team can actually operate at the level you need it to.

Your best performer might be exactly as good as their numbers say. But if the team around them is quietly bracing for impact every time that person walks into a room, you have a liability wearing a performance story as a disguise.

If you’re not sure whether this is happening on your team, or you know it is and don’t know how to address it without losing your best person, let’s talk. Book a discovery call at talktokellye.com and we’ll work through it together.