Client:
“I have an employee who is incredibly good at their job. They hit goals, solve problems fast, and honestly, they’re one of the strongest performers on the team. The problem is… they leave a trail of damage behind them. They’re dismissive, impatient, and people are starting to avoid working with them. How do I deal with a high performer who’s harming the team?”
Consultant:
When someone produces strong individual results, it is tempting to excuse the behavior that comes with it. After all, they are getting things done. The problem is that performance is not just about what gets done. It is also about how the work gets done and what it costs the rest of the team.
An employee who damages trust, shuts people down, or creates tension is not really a high performer. They may be delivering in one lane while undermining the larger success of the organization.
Client:
“That makes sense, and I worry I may have let it go too long because their work product is so strong. How do I start addressing it now without sounding like I’m punishing excellence?”
Consultant:
Start by separating output from behavior. You can acknowledge their strengths and be very clear that technical skill does not excuse conduct that hurts teamwork.
You might say:
“You bring strong skills and valuable results to the team, and I want to be equally clear that how you work with others matters just as much. I need to talk with you about the impact your approach is having on the team.”
That opening does two important things: it recognizes reality, and it signals that this is not a personality critique. It is a workplace expectation conversation.
Client:
“What if they say, ‘I’m just direct,’ or ‘I’m not here to babysit people’s feelings’?”
Consultant:
That response is common. People who pride themselves on being blunt often frame the issue as everyone else being too sensitive. Do not argue about intent. Stay focused on impact.
Try this:
“I understand that you may see your style as direct and efficient. What I need you to understand is that the impact is creating tension, shutting down collaboration, and making it harder for the team to work effectively. Regardless of intent, that impact needs to change.”
That keeps the conversation grounded in observable workplace effects rather than a debate over personality.
Client:
“What kinds of behaviors should I be talking about? I do not want to be vague.”
Consultant:
Specificity matters here. General statements like “people feel uncomfortable” are easy to dismiss. Focus on examples of observable behavior.
For example:
- interrupting others in meetings
- dismissing ideas before discussion
- sending sharp or overly critical emails
- correcting coworkers in a way that embarrasses them
- refusing collaboration because they believe others are slower or less capable
You could say:
“In the last two team meetings, you interrupted others before they finished their thoughts. I have also seen email responses that came across as dismissive rather than solution-focused. Those behaviors affect trust and teamwork.”
The clearer you are, the harder it is for them to write it off as vague feedback.
Client:
“What if the rest of the team is quietly tolerating it because this person is so good at the work?”
Consultant:
That happens all the time, and it is exactly why this issue matters. Teams will sometimes adapt around a difficult high performer by avoiding them, withholding ideas, or keeping concerns to themselves. On the surface, things may still look productive. Underneath, you are losing collaboration, innovation, and psychological safety.
This is where managers have to remember a foundational truth: performance is not only individual production. It includes contribution to the work environment. If one employee’s brilliance causes others to disengage, the team is paying a price.
Client:
“So I need to make it clear that teamwork is part of the job, not some bonus trait?”
Consultant:
Exactly.
You might say:
“Your role is not only to produce strong work. It also includes working in a way that supports the team’s success. Collaboration, professionalism, and respect are part of performance expectations here.”
That helps reposition the conversation. You are not asking them to be less capable. You are asking them to be fully effective.
Client:
“What if they push back and say the rest of the team just needs to perform at a higher level?”
Consultant:
Even if there is some truth buried in that frustration, it does not excuse poor conduct. High standards and disrespect are not the same thing.
You can say:
“If there are performance concerns with others, that is something management can address. What I am talking with you about today is your responsibility for how you communicate, collaborate, and contribute to the team dynamic.”
This keeps them from hijacking the conversation and turning it into a complaint session about coworkers.
Client:
“How do I avoid making this a one-and-done conversation that changes nothing?”
Consultant:
You need to define what improvement looks like. “Be nicer” is too fuzzy. Give them concrete expectations.
For example:
- allow others to finish before responding
- ask at least one clarifying question before disagreeing
- give feedback privately when possible
- use solution-focused language in meetings and email
- raise concerns without sarcasm, ridicule, or dismissal
You might say:
“Moving forward, I need to see respectful communication, stronger collaboration, and a more constructive approach when you disagree with others. Let’s talk specifically about what that looks like in your day-to-day interactions.”
This creates a path forward instead of just a warning.
Client:
“Should I document this, even though they are technically a strong performer?”
Consultant:
Yes. Absolutely.
When behavior affects the team, documentation matters. Note the specific concerns discussed, examples shared, expectations set, and follow-up timing. Documentation is not only for poor technical performers. It is also for employees whose conduct is creating workplace problems.
In fact, high performers can be harder to address later if there is no record, because people tend to point to the good results and overlook the interpersonal cost.
Client:
“What if they improve for a week or two and then slide right back into old habits?”
Consultant:
Then you treat it like any other repeated performance issue. Coaching first, then accountability. Improvement has to be sustained, not temporary.
You could say:
“We talked about the need for more constructive interactions, and I saw some early improvement. I am now seeing the same behavior patterns return. This needs to become a consistent change, not a short-term adjustment.”
That reinforces that the expectation did not expire after the first conversation.
Client:
“And if they still do not change?”
Consultant:
Then the organization has to decide whether it truly means what it says about culture, teamwork, and respect. If someone continues to harm the team after clear coaching, examples, expectations, and follow-up, the issue moves from coaching to corrective action.
You might say:
“We have discussed the impact of your behavior, and I have not seen the consistent improvement needed. At this point, this is a performance issue, and continued concerns will lead to formal corrective action.”
That is not punishing talent. That is holding someone accountable for the full scope of their job.
Client:
“So the bottom line is that strong results do not cancel out harmful behavior?”
Consultant:
Exactly. A truly strong performer adds value without making everyone around them pay for it. Managers get into trouble when they confuse technical excellence with overall effectiveness.
The goal is not to lower standards. The goal is to make sure high standards and healthy workplace behavior can exist at the same time. That is where real team performance lives.
And if you need help sorting out whether you are looking at a coaching issue, a conduct issue, or the beginning of formal corrective actions, we can help.