The star performer everyone dreads: is the output worth it?

The numbers look excellent. The colleague closes important deals, solves difficult technical problems or knows a system nobody else understands. Meanwhile, people rehearse before talking to them. Meetings get quieter. Managers say, “That is just how they are,” as if personality were an exemption printed in the employment contract.

How should you manage a high performer whose behaviour harms colleagues? Begin by assessing the whole contribution and establishing facts. The objective is a workable, fair environment in which strong results and acceptable behaviour belong in the same definition of performance.

Describe the behaviour before choosing the label

“Toxic” is a popular word with an unhelpfully wide meaning. Direct disagreement, an unpopular decision and serious misconduct can all end up in the same sentence. Start with observable actions: interrupting, withholding essential information, publicly insulting someone, bypassing agreed controls or taking credit for another person's work.

Ask what happened, when, who was involved and how work was affected. Separate accounts from established findings. Someone accused of harmful behaviour deserves a fair opportunity to respond. A manager's dislike is not evidence. Neither is a glowing revenue report evidence that a complaint cannot be true.

Do not diagnose the person or infer motives from a style difference. Language, communication preferences and professional disagreement can affect how an interaction feels. Assess relevant behaviour against clear standards while taking context seriously. You can require respectful conduct without requiring everyone to sound like the same colleague.

The visible output is only part of the contribution

A useful working lens is direct results plus contribution to other people's work, minus the costs created around the person. This is a reasoning tool, not a precise accounting formula. Some effects are difficult to measure, and serious harm must not become acceptable merely because a spreadsheet remains positive.

The Housman and Minor working paper, Toxic Workers, examines harmful conduct and organisational performance in a specific dataset. It gives a reason to consider damage alongside productivity. Its findings do not provide a universal price for a difficult colleague or a shortcut to judging an individual.

Look for work delayed because people avoid asking questions, errors hidden to avoid ridicule, repeated repair by colleagues and knowledge deliberately kept inaccessible. Check evidence rather than adding rumours to a cost estimate. Invite examples privately through appropriate channels, and avoid creating a public vote on someone's employment.

Do not confuse high standards with humiliation

A demanding colleague can improve a team. They may expose an unrealistic plan, reject poor-quality work or insist on evidence. Those actions can be uncomfortable and useful. The relevant distinction is how they challenge the work and whether others can respond, learn and carry out their responsibilities.

“This estimate misses the integration work; let's revise it” is specific criticism. “You always have no idea what you are doing” attacks the person. Leadership should protect the first kind of challenge and address the second. Otherwise everyone learns that raising standards requires behaving badly.

Check whether expectations were clear to begin with. A colleague asked to rescue every failing delivery may have legitimate frustration. That does not excuse insults, but the workload pattern may need repair alongside the behaviour. Accountability works better when the company also examines the conditions it created.

Have a concrete conversation when the situation allows it

For an appropriate performance discussion, describe an observed incident and its impact: “In yesterday's review, you interrupted the analyst repeatedly and called the proposal stupid. We need objections explained against the work, and colleagues need time to answer.” State the standard without adding a personality verdict.

Ask for their account. They may supply important missing context, dispute the details or recognise the problem. Record what is agreed and what requires further investigation. An open conversation can be direct. You do not need to decide whether someone is secretly a good person before requiring better conduct.

Agree observable changes, support and a review point. Examples include sharing relevant information, challenging proposals without personal attacks and using an agreed escalation route. Avoid vague instructions to be more positive. A permanent smile does little for the colleague whose work is still being undermined.

Some situations require a formal route immediately

Allegations of bullying, harassment, threats, discrimination, fraud or serious misconduct should be handled through the relevant qualified process. Do not improvise a team workshop or ask affected people to resolve a serious complaint over coffee. Protect people and seek appropriate HR or legal guidance for your location and circumstances.

Acas guidance on approaching complaints emphasises seriousness, fairness, sensitivity and keeping an open mind. Its legal context is the United Kingdom. The practical principles are useful, while formal procedures and obligations must be checked for the place where your team works.

Keep information limited to those who need it and avoid promising absolute secrecy you cannot provide. Consider risks of retaliation and how people can raise further concerns. Do not treat a request for help as evidence of disloyalty or force someone to keep working through an unsafe interaction.

A hypothetical example: the irreplaceable architect

Imagine a senior architect who solves critical problems quickly but dismisses questions and refuses to document decisions. In this hypothetical example, releases depend on their availability, and colleagues stop proposing improvements. The manager has been praising speed while ignoring the growing dependency around it.

The response has two tracks. Address disrespectful interactions with specific expectations. In parallel, allocate time for documentation, shared review and backup ownership. Protect the architect's focus by reducing random interruptions, then provide a reliable route for necessary questions. The system should support collaboration rather than merely demand it.

If behaviour improves, recognise the change with the same seriousness as technical output. If it does not, follow the appropriate process and consider the role's future. Dependency reduction remains valuable either way. A company should not need someone's permanent presence to maintain basic access to its own knowledge.

Change the reward system that made the exception attractive

Review how promotions, bonuses and public praise are decided. If only individual output counts, managers may quietly reward conduct that undermines the team. Include relevant cooperation, information sharing and responsible delivery in role expectations. Use job-related evidence and explain standards in advance.

Do not replace measurable output with a popularity contest. Quiet employees, unconventional thinkers and people who challenge management can make excellent contributions. Evaluate how work is done and what it enables, not whether the person attends every social event or agrees with the leader most often.

For everyday tensions, my guide to difficult workplace interactions offers practical conversations. The essay on why valuable employees leave explores the cost of allowing work friction to become normal.

I can help teams clarify responsibilities, decision routes and ways of working when product delivery depends on people avoiding one another. My contribution is practical alignment and work design, alongside your qualified HR support. Describe the recurring situation, and we can identify what needs a facilitated conversation and what belongs in a formal process.

Questions people ask

Can someone be a high performer and still harm the team?

Yes. Strong individual results can coexist with behaviours that obstruct colleagues, damage trust or create operational dependencies. Examine observable conduct and its effect on work rather than relying on a personality label. Include collaboration and responsible delivery in relevant role expectations. Serious harm requires an appropriate response even when the person generates revenue or has valuable technical knowledge.

How should a manager address a high performer who behaves badly?

Establish facts, use specific examples and explain the expected working behaviour. Give the person a fair opportunity to respond, agree observable changes and review them. Examine workload and incentives too. Serious allegations require an appropriate formal process with qualified support. Avoid public confrontation, amateur diagnosis or a blanket assumption that difficult communication means the person is guilty of misconduct.

Should a company dismiss a harmful high performer?

There is no universal answer without the facts, applicable obligations and a fair process. Consider the seriousness of conduct, the evidence, steps already taken and whether improvement is realistic. Use qualified HR or legal support for formal decisions. Reduce operational dependence separately. Productivity should not exempt anyone from standards, but a manager should not turn a complaint into an automatic finding.