A team member can solve difficult tasks faster than anyone else, yet refuse to explain their approach, arrive unprepared for meetings, and leave colleagues to resolve repeated misunderstandings. Their individual results look excellent, but teamwork is suffering. As a manager, you need to recognize their expertise without overlooking the damage their way of working may cause.
The answer is neither to force a capable person to be sociable at all costs nor to excuse everything because they deliver strong results. Focus on specific workplace behaviors the team depends on, agree on measurable expectations, and check whether anything actually changes.
First, distinguish independence from a problem
Some people work best alone, skip informal lunches, and need quiet to tackle complex tasks. That is not a reason for criticism. Teamwork does not mean everyone has to speak just as often, contribute in the same way during meetings, or form personal friendships.
A problem arises when someone’s behavior prevents others from completing their work, creates unreasonable risk, or repeatedly breaks agreed rules. Examples include failing to share essential materials, changing a shared solution without warning, or dismissing colleagues’ questions.
Find out what is happening and who is affected
Before starting a difficult conversation, gather a few verifiable examples. “Everyone is complaining about you” is a weak starting point. Be more precise: the documentation was missing by the agreed deadline, two colleagues did not receive a response, and the customer handoff was delayed as a result.
For each example, note four things: what was agreed, what happened, what the impact was, and what you still do not know about the cause. Don’t mistake incomplete information for intent. Silence in a meeting might indicate disengagement, but it could also mean concentration. Missing information might reflect defiance, or unclear ownership.
When speaking with other colleagues, ask about the impact on work, not the person’s popularity. “What information were you missing to continue?” is more useful than “What do you think of them?” Also check whether the team expects this person to provide more informal help than others do.
Choose a response based on the behavior and its impact
Not every sign of poor collaboration is equally serious. The distinctions below can help you avoid two extremes: penalizing someone for a different work style or ignoring harmful behavior because of their results.
| What you observe | What to check | Appropriate next step |
|---|---|---|
| They prefer working alone and say little in meetings | Are they delivering the necessary work and information? | Allow independent work and set clear handoffs. |
| They fail to provide materials or bypass agreements | Do they understand the expectations, have enough capacity, and have access to the information? | Clarify the commitment, deadline, and how it will be checked. |
| They put colleagues down or reject reasonable questions | Which specific behaviors are recurring, and who is affected? | Set a clear boundary around respectful behavior immediately. |
| They put safety or confidentiality at risk, or seriously breach rules | Which internal procedures and obligations apply? | Act promptly through the appropriate process. |
Have a private conversation without labels or blame
Arrange to speak in private rather than raising the issue in front of the whole team. Start by acknowledging their genuine contribution, but don’t soften the message so much that the problem disappears. Two things can be true at once: their expertise is valuable, and the way they collaborate needs to change.
You might say: “You handle technical problems independently and to a high standard. But the last two handoffs were missing a description of the changes, so your colleagues couldn’t pick up the work. We need to agree on how you’ll share that information.” This describes what happened, its impact, and what you need. It does not judge their character.
Then give them room to respond. Ask what is getting in the way, whether their priorities are clear, and what would help them meet the team’s needs without unnecessary interruptions. Listening to an explanation does not mean automatically excusing the behavior. It helps you choose a solution that addresses the cause as well as the visible problem.
If the colleague argues that others are slower, bring the conversation back to the work: “You don’t have to do their tasks for them. But they do need to know what you changed so they can complete their part safely.” If they question the need to collaborate at all, explain which downstream work depends on it.
Agree on a minimum standard of collaboration you can verify
The conversation should not end with a vague promise to “be more of a team player.” That does not clarify what needs to happen or how either of you will recognize progress. Instead, agree on a few observable actions.
For a technical project, that could look like this:
- Handing over completed work: Add a brief description of changes and any risks for the next step to each completed task.
- Responding to a blocking question: Confirm that you received the request and say when you can address it. You do not have to be available all the time.
- Making shared decisions: Tell the people affected before making a change that impacts their work.
- Reviewing the agreement: After two weeks, go through specific handoffs together and identify what worked.
Adjust timing and frequency to the work. An operation that handles urgent incidents will need a different rhythm from an independent research project. Also agree on how the person should flag overload or conflicting priorities. An agreement they cannot meet will only create another dispute.
Don’t try to solve everything by changing the individual
A talented person may avoid collaboration partly because the work system does not support it. For example, the company may reward only the number of completed tasks, while time spent onboarding others, documenting work, or reviewing it goes unrecognized. Or different managers may send conflicting requests every day.
Review your own responsibilities too. Are decision-making boundaries clear? Does everyone know what to hand over and to whom? Are team meetings unnecessarily long? Does the specialist have enough uninterrupted time to focus? If the rules are missing, criticizing one person will not solve the problem.
Some tasks can be set up so that the person works mostly independently but has clear points of contact with the team. A specialist, for example, might prepare a proposal alone, then take part in a brief joint review before it goes live. Independence in how work is done is compatible with responsibility for handing it over.
A scenario involving a specialist everyone depends on
Example scenario: A four-person product team has an experienced developer who fixes the most difficult bugs. But they often deploy new solutions without a brief heads-up and dismiss junior colleagues’ questions as pointless. Gradually, the others stop contacting them. During the next change, they miss an important detail, and customer support cannot explain the resulting issue.
The team lead first separates evidence from impressions: she records two changes made without a handoff and the specific consequences for testing and support. In a private meeting, she asks what makes it difficult to communicate changes. The developer explains that frequent questions interrupt their work and make them feel they are losing time.
Together, they agree on a short update after each significant change, a regular time for questions, and immediate notification only when an issue is blocking someone else’s work. The team lead also makes clear that ridiculing colleagues is unacceptable, regardless of the quality of the technical results.
Don’t let the rest of the team pay for exceptions
Sometimes managers, afraid of losing a capable employee, shift that person’s communication responsibilities to others. One colleague writes up their notes, another smooths over conflicts, and a third stops asking questions. The team may appear to be functioning in the short term, but the real costs remain hidden.
Apply fair standards. If everyone is expected to hand over materials, the same rule applies to the most experienced specialist. The method does not have to be identical: one person might write a summary, while another gives a brief walkthrough. What matters is that colleagues receive the information they need, at the right level of detail and at the right time.
Tell the team about changes to the process, not the details of a private conversation. For example: “From now on, every significant change will include a brief handoff, and we’ll document shared decisions.” Don’t disclose personal assessments, individual complaints, or details of personnel matters.
What to do if the agreement is not followed
If the behavior does not change, don’t keep repeating general requests to “make more of an effort.” Compare the agreement with what actually happened. Work out whether the issue is an unclear process, lack of capacity, missing skills, or repeated refusal to meet a reasonable expectation.
Your next steps also depend on your authority. A project lead may be able to change how work is handed over, but may not be able to change someone’s role or decide on disciplinary action. If agreements repeatedly fail, involve the appropriate manager or HR team and follow internal procedures.
Do not wait for a trial period to end if there is humiliation, intimidation, discrimination, retaliation, or a safety risk. Use the available reporting and protective procedures. Being difficult to replace professionally is not a reason to tolerate behavior that puts people or trust at risk.
Check whether the team has made progress
At your next review, ask three questions: Are colleagues getting what they need to continue their work? Are specific disruptions becoming less frequent, or has the team simply stopped reporting them? Does the specialist understand what is expected and have the conditions needed to meet those expectations?
Start with one specific incident from the most recent project. Write down which commitment was missed, what the impact was, and the smallest change that would prevent it from happening again. That is a better starting point than trying to change a talented colleague’s entire personality.
