When a High Performer Refuses to Collaborate

A team member produces genuinely excellent individual work, consistently exceeding expectations on their own output, while showing little genuine willingness to collaborate, share credit, or support colleagues. This creates a real and uncomfortable dilemma for any team or manager — the individual talent is real and valuable, but the refusal to collaborate carries genuine costs that pure output metrics don’t fully capture, making this a situation that requires careful, honest navigation rather than either uncritical tolerance or a rigid demand for a working style that doesn’t come naturally.

Why This Situation Is Genuinely Difficult to Navigate

The immediate, visible value of strong individual output creates real pressure to overlook collaboration problems, especially when that output is genuinely difficult to replace. At the same time, a persistent unwillingness to collaborate carries real costs to team cohesion, knowledge sharing, and the working experience of colleagues — costs that are often less immediately visible than individual output but accumulate meaningfully over time. Holding both of these truths honestly, rather than dismissing either, is the genuine starting point for addressing this well.

The Real Costs of Tolerating Non-Collaboration

Team cohesion and trust erode gradually but genuinely. A consistent pattern of one person operating apart from the team, unwilling to genuinely share knowledge or support others, can erode team cohesion and trust over time, even when that person’s individual output remains strong.

Other team members’ morale and sense of fairness are genuinely affected. Colleagues who observe a high performer receiving latitude that wouldn’t be extended to others can reasonably develop a genuine sense of unfairness, affecting their own morale and willingness to collaborate in turn.

Knowledge and expertise remain siloed rather than genuinely shared. A high performer who doesn’t collaborate often holds valuable knowledge and expertise that never gets genuinely shared with the broader team, creating a real, ongoing dependency and vulnerability if that person eventually leaves.

The genuine message sent to the rest of the team matters. Tolerating persistent non-collaboration, without any honest conversation or expectation, sends a real message to the rest of the team about what’s actually valued, potentially undermining a broader collaborative culture the organisation claims to prioritise.

How to Address This Honestly and Constructively

Have a direct, honest conversation about the specific behaviour and its impact. A clear, honest conversation that names the specific collaboration gap and its genuine impact — rather than a vague, general request to “be more of a team player” — gives the person something concrete to actually respond to.

Distinguish genuinely between collaboration style and collaboration refusal. Some people genuinely collaborate differently, through written contributions or asynchronous support, rather than through frequent meetings or visible teamwork — honestly distinguishing a different but genuine style of contribution from an actual unwillingness to support the team matters for a fair assessment.

Connect collaboration explicitly to the team’s actual, genuine goals. Framing collaboration not as an abstract virtue but as something that concretely serves the team’s real, shared goals — better outcomes, reduced risk, shared learning — can help someone genuinely see why it matters beyond just being told to comply.

Set clear, honest expectations with real consequences if the pattern continues. If honest conversation doesn’t produce genuine change, being clear about concrete expectations going forward, including honest consequences if the pattern continues, treats the person as a genuine adult capable of choosing differently, rather than indefinitely accommodating behaviour that carries real costs.

Why Talent Doesn’t Exempt Someone From Genuine Team Expectations

It’s worth being direct that individual talent, however real and valuable, doesn’t exempt someone from genuine expectations around how a team functions together — treating a high performer’s non-collaboration as an acceptable trade-off for their output implicitly communicates that talent buys exemption from expectations others are held to, a message that can genuinely undermine trust and fairness across a team over time, regardless of how talented any one individual is.

Recognising When the Root Cause Deserves Honest Attention

Sometimes non-collaboration reflects a genuine, addressable factor rather than pure unwillingness. Honest exploration of why someone isn’t collaborating — a past experience where sharing credit or ideas didn’t go well, a genuine skills gap in collaborative work, an environment that hasn’t actually rewarded collaboration — can reveal something worth addressing directly, rather than assuming pure unwillingness is the only explanation.

Distinguish honestly between someone who can’t collaborate well and someone who won’t. Someone who genuinely struggles with the skills of effective collaboration, rather than actively refusing it, may benefit from real support and coaching, distinct from someone who understands what’s expected and simply chooses not to comply.

Balancing Fairness to the Individual and the Team

Give genuine, honest space for the person to actually change before assuming they won’t. A fair process involves genuine space and support for change after a direct conversation, rather than assuming immediately that the pattern is fixed and unchangeable, respecting the person’s real capacity to adjust.

Protect the team’s genuine experience throughout this process too. While working with the individual, honest attention to the team’s own experience — validating their observations, being transparent about the fact that the issue is being addressed — matters for maintaining their trust throughout a process that may take real time to resolve.

A Practical Scenario

A manager has a team member who consistently produces excellent individual work but shows little genuine willingness to share knowledge, support colleagues, or participate in collaborative problem-solving. Rather than continuing to tolerate the pattern because of strong output, or dismissing the person’s genuine talent, she has a direct and honest conversation naming the specific collaboration gaps and their real impact on the team, while genuinely exploring what might be behind the pattern.

She discovers that the team member had a genuinely difficult experience sharing credit at a previous role, contributing honestly to their current guardedness. She connects collaboration explicitly to the team’s actual shared goals, sets clear and honest expectations going forward, and gives genuine space for change while also protecting the rest of the team’s experience by being transparent that the issue is being actively addressed. Over several months, genuine change occurs, though gradually — a direct result of addressing the situation honestly and specifically, rather than either indefinitely tolerating a costly pattern or dismissing real talent without a fair, honest process.

Common Mistakes

Tolerating persistent non-collaboration indefinitely because of strong individual output. This sends a real message that talent buys exemption from genuine team expectations, potentially undermining trust and fairness across the team over time.

Giving a vague, general request to “be a team player” rather than naming specific behaviour. This gives the person little concrete to actually respond to, making genuine change considerably less likely than a direct conversation about specific patterns and impact.

Failing to distinguish a different genuine collaboration style from actual refusal. Some people contribute genuinely through different channels, and conflating this with actual unwillingness produces an unfair assessment.

Assuming pure unwillingness without honestly exploring the root cause. Sometimes non-collaboration reflects a genuine, addressable factor — a past experience, a skills gap — that deserves honest exploration rather than an assumption of simple refusal.

Action Steps

  1. Have a direct, honest conversation naming the specific collaboration gap and its genuine impact on the team.
  2. Explore honestly what might be behind the pattern, distinguishing a genuine skills gap or past experience from pure unwillingness.
  3. Connect collaboration explicitly to the team’s actual, shared goals, rather than framing it as an abstract virtue.
  4. Set clear, honest expectations with real consequences if the pattern continues after genuine conversation.
  5. Protect the rest of the team’s experience throughout this process, being transparent that the issue is being actively addressed.

Key Takeaways

  • The immediate value of strong individual output creates real pressure to overlook collaboration problems, but persistent non-collaboration carries genuine costs beyond output metrics.
  • Team cohesion, colleague morale, siloed knowledge, and the broader message sent to the team all suffer when non-collaboration is tolerated indefinitely.
  • Direct honest conversation about specific behaviour, distinguishing style from refusal, and connecting collaboration to real goals all help address this constructively.
  • Individual talent doesn’t exempt someone from genuine team expectations, and treating it as though it does can undermine trust and fairness across a team.
  • Honestly exploring the root cause, and distinguishing someone who can’t collaborate well from someone who won’t, matters for a fair and effective response.

Conclusion

A brilliant individual contributor who won’t collaborate creates a genuine dilemma, since the individual talent is real while the refusal to collaborate carries genuine costs that output metrics alone don’t capture. Having a direct and honest conversation about specific behaviour, exploring the genuine root cause, connecting collaboration to real shared goals, and setting clear expectations with real consequences all help navigate this well, protecting both the team’s genuine experience and the person’s fair opportunity to change.

Frequently Asked Questions

Should I tolerate a high performer who won’t collaborate because their output is so valuable?
Generally not indefinitely — persistent non-collaboration carries genuine costs to team cohesion, colleague morale, and knowledge sharing that accumulate over time, even when individual output remains strong.

How can I address this without alienating a genuinely talented team member?
Have a direct, honest conversation naming specific behaviour and its real impact, rather than a vague general request, and genuinely explore what might be behind the pattern before assuming pure unwillingness.

What if someone collaborates differently rather than not at all?
Honestly distinguish a genuine but different collaboration style, such as contributing through written work rather than meetings, from actual refusal to support the team — conflating the two produces an unfair assessment.

Why does tolerating non-collaboration affect the rest of the team?
Colleagues who observe a high performer receiving latitude others wouldn’t get can reasonably develop a genuine sense of unfairness, and the broader team may conclude that individual output matters more than genuine collaboration.

Is it possible someone doesn’t know how to collaborate well rather than refusing to?
Yes, sometimes — someone genuinely struggling with collaborative skills, rather than actively refusing, may benefit from real support and coaching, distinct from someone who understands expectations and simply chooses not to comply.

What should happen if honest conversation doesn’t produce genuine change?
Set clear, honest expectations with real consequences going forward, treating the person as a capable adult rather than indefinitely accommodating a pattern that carries genuine costs to the team.

Subscribe to Our Newsletter

Scroll to Top