How to Handle a Toxic High Performer: What to Say to Your Best Person

Here is the sentence most managers use, and it is the reason nothing changes.

"Your work is incredible. I just wonder if sometimes, in reviews, you could be a little more mindful of how you come across." That is how most managers handle a toxic high performer: a compliment, a hedge, and nothing on the record.

Your best person hears the first sentence. The second arrives wrapped in "I wonder" and "a little" and "sometimes," which is how English signals that something is optional. They leave feeling good about the meeting. Two weeks later they talk over the same junior designer in the same review, and you have spent your opening and bought nothing with it.

This conversation is hard for a specific reason. Two things are true at once: they are the best person on your team, and their behavior is costing you other people. Most managers pick one and lead with it. Lead with the praise and the feedback never lands. Lead with the criticism and all they hear is that you do not value them, which is the outcome you were most afraid of.

Most advice on giving negative feedback to an employee assumes the work is the problem. Here the work is why you are stuck. You have to hold both truths in the same thirty seconds, without letting either one cancel the other.

Why you have not said anything yet

Be honest about this part, because it changes what you do next.

You need their output, and their work really is the best on the team. Underneath that, you are afraid that if you push they will leave, and you will be the manager who lost them. So you wait for a calmer week. That week has not arrived in eleven months.

The cost is being paid anyway, just not by them. The junior designer stopped bringing early concepts and now shows only finished work, so you find out about problems a week later than you used to. Two people route things through you first so they arrive pre-approved. Someone updated their profile in February.

Nobody names a colleague in an exit interview. They say they wanted a new challenge. So the cost stays invisible until it arrives as a backfill, and by then it is bigger than the conversation ever was.

You are not choosing between keeping this person and losing them. You are choosing which people you lose.

There is a popular name for this person, the brilliant jerk employee, and the label is part of the problem. It turns a colleague into a type, and you cannot have a conversation with a type. You can only have one with the person across from you on Thursday, who thinks they are doing their job well, and who is partly right.

Two or three moments, written down

Do not walk in with a pattern. Walk in with moments.

"You steamroll people in reviews" is a characterization, and characterizations are arguable. Your best person will argue, well, and you will spend the meeting debating whether they are a good colleague instead of talking about Thursday.

Write down two or three occasions, and for each one: which meeting, what was actually said, and what happened afterward.

That last part is what managers leave out, and it is what turns a complaint about manners into a fact about how the team ships. "You cut her off" is etiquette. "You cut her off, and she has not brought unfinished work to a review since" is a business problem.

Two or three is enough. Do not bring a file. A file reads like a case being built, and someone who feels like a defendant behaves like one.

Bring only what you saw yourself, or what a person has agreed you can name. "A few people have mentioned it" loses you the room, because it is unanswerable and you both know it. They ask who. You will not say. From there, you are the evasive one.

The shape here, open cleanly, bring evidence, leave with an agreement, is the same as any difficult conversation with an employee. What makes this one different is that the thing you value most about the person is the thing stopping you from starting.

The opening, where you hold both things

The conversation is decided in the first thirty seconds, by whether both truths survive them.

One word does most of the damage. "Your work is great, but" tells the listener that the first half was throat clearing. Use "and" instead. It is a small change, and it is the difference between holding two things together and trading one for the other.

Notice what that does not do. It does not ask them to be nicer, and it never mentions attitude. Attitude is a verdict on a person, nobody can check it, and it puts a smart person on the defensive inside one sentence. Everything above is actions in a specific room, and what followed them.

The pushback you should expect

They are smart, they have already had this meeting in their head, and they will have answers ready. Three come up almost every time.

"The work actually was weak"

Often true. Do not argue about the work. You will either lose or win badly, and either way you spent the meeting on the wrong subject.

Concede it completely, then put the two things back where they belong. "You may well be right about the work, and that is not what I am asking you to change. The bar stays where it is. What has to change is that after that review, Priya stopped showing anyone anything unfinished. I need both: your standard, and people still willing to bring you rough work."

"We had a deadline"

This is an argument that the cost was worth paying. Answer it with the cost they are not counting.

"We did, and there is another one next month. If the only way we hit them is you taking the pen at minute four, that is not a plan, it is a single point of failure with your name on it. I would rather have four people who can carry a review than one who has to."

"So I am the problem now"

The cold one. Flat voice, arms folded, temperature drops. It is a test, and what it tests is whether you will back off.

Most managers fail here instantly, with "no, no, that is not what I am saying at all," then spend twenty minutes walking it back. The retreat is the failure. It teaches your best person that going cold makes you fold, and that lesson waits for you in every conversation after this one.

Do not retreat and do not escalate. Answer the literal question.

The same three moves show up in other rooms, with other people. There are more examples of difficult conversations at work if you want to see them run.

What a real agreement sounds like

Here is where an otherwise good conversation quietly fails.

They say "you are right, I will try to be more mindful in reviews." It sounds like agreement. It has the shape of agreement. You both feel better and you leave.

Do not accept it. Nobody can observe it, so there is nothing to follow up on, and in six weeks you are back here with less credibility than you had the first time.

A real agreement passes three tests. It names an action, not a mood. It happens in a named meeting. And a third person in the room could tell you whether it happened.

Next to "I will try to be more mindful," these are agreements:

• I do not speak until the presenter has finished.
• I ask one question before I give an opinion.
• I do not share my screen during someone else's presentation.

Get it from them rather than assigning it. A behavior they named is one they have to defend. One you assigned is one they can comply with badly.

The part you have to do in public

The agreement does not survive its first test unless you enforce it in the room, in the moment, in front of everyone. Every person at that table is quietly checking whether the thing you said in private was real.

You do not need a speech. You need one short sentence with no heat in it.

"Hold on. Let Priya finish."

Then move on immediately. Do not explain it, do not apologize for it, do not glance over for approval. The shortness is the point: it is a correction, not a scene, and treating it as small is what keeps it small.

Send one line privately the same day so it does not sit and grow. "I cut you off in there on purpose. That is the thing we talked about, nothing more."

Skip this and the private conversation was theater to everyone who was in the room, including the person you had it with.

This does not work if the person is genuinely irreplaceable this quarter. When the company cannot afford to lose them before a launch, every conversation you have is advisory and they know it, so the honest sequence is to make the work replaceable first and have the conversation second. That takes months, which is why the problem is usually years old.

Knowing the words is not the same as saying them

On a page this looks obvious. In the room it is different, because the person across from you is someone you like, whose work you depend on, who has just asked flatly whether they are the problem.

The opening usually goes fine. You rehearsed it in the car. What fails is the middle. They push back once, you hear yourself saying "look, it is not a big deal, I just wanted to flag it," and the meeting is over with twenty minutes still on the clock.

What fixes that is having said the sentences out loud, to someone who pushes back, before the version that counts. This is the conversation Valor gives away, the Give Hard Feedback scenario. Jordan is a senior designer who opens with "Hey. You wanted to talk? I've got a review in twenty minutes, so what's up?" and gets less accommodating as the stakes climb: HR in the loop at one level, a public blowup at the next.

The first time you say "No. You are not the problem. What happens in reviews is a problem" should not be the time it counts.