Managing a high performer who damages the team

This is the conversation managers avoid longest, and the arithmetic of avoiding it is worse than it looks. The visible cost of acting is one uncomfortable meeting and a small risk that a strong performer leaves. The invisible cost of not acting is everyone else quietly deciding that the rules apply to them and not to this person.

How do you know it is a real problem and not a personality clash?

Look for effects on work, not on atmosphere.

"He's abrasive" is a description of a personality, and reasonable people will disagree about whether it matters. "Two people have stopped flagging risks in the Tuesday review since he started dismissing them, and one of those risks landed on us in August" is a description of damage.

The signals worth acting on:

• People stop raising problems in settings where this person is present
• Someone asks to move team, or to work on something else, and the reason is vague
• Handovers to or from this person fail more often than others
• Colleagues route around them, duplicating work to avoid the interaction

If you cannot name an effect of that kind, wait and watch rather than act. If you can name two, you are already late.

Should you soften it because their results are good?

No, but you should say the results are safe, because that is the thing they are worried about.

Open by taking it off the table:

"I want to be clear at the start: this isn't about your numbers. Your numbers are the best on the team and that's not in question. This is about how the last few weeks have gone with the rest of the team, and it's important enough that I want to be direct."

That opening costs you fifteen seconds and prevents the most common derailment, which is the person spending the meeting defending performance nobody attacked.

What you must not do is trade. "Your results are great, but the behaviour needs work" invites a negotiation in which excellent output buys tolerance for how it is produced. It is not a trade, and saying so early is easier than unpicking it later.

What do you actually describe?

Incidents, in your own voice, with their effect on work.

"In the sprint review on the 12th you cut across Priya twice and said the approach was naive. In the client prep last week you rewrote Sam's section without telling him and he found out in the meeting. Since the 12th, Priya hasn't raised anything in that review, and she used to raise most of it."

Notice what is absent. No adjectives about their character. No "people are saying." No mention of who complained. Two events you can stand behind and one observable consequence.

If they dispute an incident, do not stack on a third. Settle the one in dispute — "that's what I saw; tell me how it looked from where you were" — and if you turn out to be wrong about a detail, say so. Being corrected on one point and holding the other is far stronger than retreating from both.

How do you frame the standard?

As a requirement of the job, stated once, without apology.

"How you work with the team is part of this role. It isn't a nice-to-have and it isn't my personal preference. It's the job."

The temptation is to justify it — to explain why collaboration matters, cite team dynamics, make a case. The moment you argue for it, it becomes arguable. Say it as a condition and move to what changes.

Some people will ask whether this is going on their record or affecting their bonus. Answer honestly. If behaviour is part of how performance is assessed where you work, say so. If it is not formally assessed but will affect your recommendation, say that too.

What if they get defensive?

Expect it, and expect it to be about fairness rather than fact.

The characteristic objection is some version of "I'm the one delivering here." That is a fairness claim, and responding with more incidents will not touch it. Acknowledge what they are protecting, then separate the two threads: "You are delivering, and that's real. It doesn't buy an exemption from how we work together. Both things are true." The full set of moves for a reaction like this is in what to do when someone gets defensive.

If the defensiveness is genuinely about a colleague rather than about you — a running feud with one person — the shape is different again, and closer to mediating conflict between two team members.

What change should you agree?

One observable thing, in a specific setting, within a fortnight.

Vague commitments — "be more collaborative", "work on my communication" — are unfalsifiable and will produce a second meeting in which you both argue about whether anything happened. Make it concrete: "In the Tuesday review, I want you to let people finish. If you disagree, take it after the meeting or raise it as a question."

Then say what you will do: you will be in that meeting, you will notice, and you will tell them privately either way.

What do you say to the people absorbing it?

Less than you want to, and more than nothing.

Colleagues who have been on the receiving end will often ask, directly or obliquely, whether anything is being done. You cannot tell them what was said — that conversation is confidential and repeating it would be a serious breach. But answering "I can't discuss it" and nothing else reads as a refusal to act, and it is why people conclude that raising things is pointless.

The usable middle is to confirm the process without the content: "I've spoken to him about it. I'm not going to go into what was said, but I want you to know it was raised and I'm watching it. If it happens again, tell me." That is honest, it protects the conversation, and it tells the person their account was taken seriously.

Then follow through visibly enough that they can see something changed. Not by announcing it, but by being present in the meetings where it was happening. People draw conclusions from whether the manager shows up.

Why does the follow-up matter more than the conversation?

Because the team is watching for evidence that behaviour has consequences, and the conversation is invisible to them.

If nothing changes and nothing further happens, everyone learns that results buy immunity — which is a far more expensive lesson than the original behaviour. If something does change, do not announce it, but do acknowledge it privately. People sustain effort they believe was noticed.

Check in within two weeks whatever happens. If it improved, say so specifically. If it did not, the second conversation is shorter and names what follows.

What if you decide the trade is worth it?

Then make that decision deliberately and know what you are paying.

There are situations — a fixed-term project, a specialist nobody can replace this quarter — where a manager reasonably concludes that the disruption of acting exceeds the damage of tolerating. That can be the right call.

What it cannot be is a decision made by default, six months at a time, because the conversation is unpleasant. If you are choosing to accept it, say so to yourself with a date attached, and be honest with the people absorbing the cost — at minimum by acknowledging privately that you can see it.

The structural version of this problem, and the habits that stop it developing, are covered in the complete guide to difficult conversations for new managers. The pattern is the usual one: the conversation is small if you have it in week two and enormous if you have it in month eight.