TL;DR: Difficult team behaviour rarely fixes itself. The leader’s job is to name the pattern privately, set the bar clearly, give a real chance to change, and follow through. Done with empathy and discipline, the conversation is one of the most respectful things a leader can do, for the team and for the person whose behaviour is causing harm. Done poorly, it amplifies the damage. This is a craft, not a script.
You’ve watched the pattern for weeks now. Maybe months. One person on the team is consistently behaving in a way that’s dragging everything down. The check-in is tense. Other team members are quietly working around them. You’ve thought through five different ways to address it and every one of them ends badly in your head, so you’ve waited.
The waiting is making it worse.
This post is about how to lead through difficult team behaviour without making the situation worse than it already is. The behaviour is the problem, not the person, and that distinction is doing real work in every step that follows.
If you’re holding this in right now, you’re in good company. Leaders who genuinely care about their teams put off difficult team behaviour conversations more than any other type of feedback they could give. It’s not weakness. It’s reasonable risk-assessment. The conversation has more failure modes than success modes, and most of the failure modes are public. Almost all of the avoidance comes from not having a framework that doesn’t end in someone leaving angry.
This post is that framework.
A quick note before we go further. This is the companion piece to our pillar on toxic work culture and why OKRs won’t fix it. The pillar covers what to do when the broken patterns are spread across the team. This one covers the harder, narrower case: the behaviour is coming from one or two people you manage, the rest of the team is healthy, and you’re the one who has to address it.
What Counts as Difficult Team Behaviour?
Difficult team behaviour is a recurring pattern of conduct from a team member that harms the team’s ability to do the work. It is not a single bad day, a disagreement that got heated, or a personality difference that two adults can navigate. It is a pattern that other team members have started to organize their work around. That last part is the test. When peers are quietly routing around someone, the behaviour has stopped being a private matter.
Common patterns of difficult team behaviour to watch for:
- Undermining decisions in private that the person agreed to (or didn’t object to) in the meeting where the decision was made
- Public criticism that targets people, not the work, especially when the criticism gets sharper when the target is not in the room
- Information hoarding where someone uses their access to a piece of context as leverage, and refuses to share what the team needs to move
- Pessimism and cynicism that go beyond a healthy reality check and start to function as a brake on every initiative
- Chronic blame deflection where mistakes are always someone else’s fault and the same patterns keep repeating
- Quietly working against shared agreements, like skipping the check-in, ignoring the cadence, or refusing to use the agreed tools
You don’t need all of these. A single pattern that the rest of the team is now working around is enough.
The word “difficult” is doing real work here. We are deliberately not calling the person difficult. We are calling the behaviour difficult, because behaviour is something that can change. The distinction matters in how you think about the conversation, and it matters even more in how you talk to the person. People can change behaviour. They cannot change being told that they themselves are the problem.
Why Leaders Avoid the Conversation (and What It Costs)
Most leaders avoid the difficult team behaviour conversation because they have lived through versions of it that went badly. They have watched a colleague try to address a peer’s behaviour and end up sidelined for it. They have given feedback that landed as a personal attack and now have a damaged relationship with no behaviour change to show for it. They have seen another founder lose a quarter rebuilding trust after a heavy-handed conversation.
The avoidance is rational in isolation. The cost is what makes it irrational over time.
When a leader avoids addressing difficult team behaviour, three things happen. The team learns that the leader will tolerate it, which makes raising the bar later harder for everyone. The strongest team members lose faith and start to disengage, because they are the ones absorbing most of the friction. And the person whose behaviour is the problem rarely figures it out on their own, because nobody in the room is honest enough with them to name what they are doing.
Research from Gallup on engagement consistently finds that the people most likely to leave first are the strongest performers in healthy teams who are being asked to absorb the cost of difficult team behaviour from peers. The leader’s conversation that feels scary in the moment is the cheaper option compared to losing the team members who are doing the work.
The Playbook: A Leader’s Roadmap for Difficult Team Behaviour
What follows is the sequence I keep coming back to for navigating difficult team behaviour. It is not the only sequence that works, and parts of it will need to bend to your specific situation. But the order matters, and skipping steps is how leaders end up making the situation worse.
1. Name the Pattern to Yourself First
Before you raise the difficult team behaviour with the person, get specific in writing first. What is the behaviour? When does it happen? What is the impact you have observed? Three concrete examples is the floor. “He’s been hard to work with lately” is not a specific enough premise to walk into a conversation with. “In the last three check-ins, he has interrupted Maya within a minute of her starting to speak, and twice he has walked back decisions in DMs after agreeing to them in the meeting” is.
Specificity does two things. It clarifies your own thinking, so you stop reacting and start observing. And it gives you something concrete to share in the conversation, which is what makes the difference between feedback that lands and feedback that escalates.
2. Anchor Expectations in Your Values, Not Your Mood
Before you raise it, ground what you are about to ask for in something bigger than your reaction. Your team’s mission, vision, and values should already do this work. Naming a behaviour as “out of step with how we agreed to work” lands differently than naming it as “something that bothers me.” If you do not have explicit team behaviour standards, this is your sign that the pillar post on toxic work culture is worth reading first.
If your values include something like “we name problems early” or “we disagree in the room, not the hallway,” you have the bar already. Anchor there. The conversation becomes about a shared agreement the person already signed up for, not a personal preference of yours.
3. Raise It in Private, Sooner Than You Want To
Pick a one-to-one setting. Pick a time when neither of you is rushing into the next thing. Open with care. The phrasing that lands most often is some version of: “I want to share something I have been noticing, because I would rather raise it now than let it become a bigger thing.” Then share the three specific examples. Then say what impact you have observed: “When this happens, I notice [outcome].” Then stop talking. Let the silence do its work.
Kim Scott’s Radical Candor framework is useful shorthand here: the conversation works when it is both caring and direct. Lose the caring and feedback lands as attack. Lose the directness and it lands as nothing at all. Most leaders default to one side or the other under stress, so naming the balance for yourself before the conversation is worth the thirty seconds it takes.
The single biggest mistake leaders make at this step is rehearsing a whole speech and delivering all of it before the other person has a chance to respond. The conversation is a conversation. Treat it like one.
4. Get the Person’s View, and Actually Listen
A surprising amount of difficult team behaviour comes from a context you cannot see from where you sit. The person may be drowning. They may be navigating something at home you do not know about. They may have had a recent experience with a peer that you have not heard their side of. They may genuinely not realize the pattern exists, because nobody has ever named it to them before.
None of this excuses the behaviour. All of it shapes what comes next. Ask. Listen. Then respond.
5. Set the Bar Explicitly and Tie It to Specific Behaviours
Once you’ve heard the person out, what needs to change about the difficult team behaviour, and by when? Be specific. “I need to see the disagreement happen in the meeting, not after it” is something you can both verify. “Be more of a team player” is not. Pick two or three concrete behaviour changes, name them, and agree on what success looks like over the next four to eight weeks.
The check-in is the natural place to track this. Not the OKR-scoring check-in, but a one-to-one cadence specifically focused on the behaviour shift. Weekly for the first month, then less often. We covered the mechanics of running a check-in that actually changes what happens in our piece on the OKR check-in template. Same principle applies here: cadence, not events.
6. Document the Conversation, Quietly
Send a follow-up message after the conversation that captures the substance: what you raised, what you both agreed to, what success looks like, and when you will check in next. This is not a paper trail for HR. It is a memory aid for both of you, and it makes sure neither of you walks away with a different version of what was agreed.
If the behaviour does not change and you find yourself a few months in needing to escalate to exit, you will be deeply grateful that the early conversations are documented. If the behaviour does change, the documentation becomes a record of someone growing. Both versions of the future thank you.
7. Use the Check-In Cadence as the Lever, Not the Scoreboard
The weekly check-in is the smallest, fastest tool you have for tracking change in difficult team behaviour over time and modeling the new bar. Ask “from what, to what?” on the behaviour the person is working on, not just the metrics. “Last week we agreed on X. What did you notice this week?” Ask what they tried, what made it easier or harder, what they want to try next.
Do not weaponize the cadence. Do not turn the check-in into a performance review by stealth. The check-in is where the work gets adjusted, not where verdicts get issued. If the cadence is the place the person dreads, you have made it the wrong tool.
8. Make the Exit Decision Clean if the Change Doesn’t Happen
Sometimes the conversation works. Sometimes it doesn’t. If you have been clear about what needs to change, given a real chance over a real timeframe, and documented the conversations, and the behaviour still hasn’t shifted, you have your answer.
The exit conversation, when it comes, should not be a surprise. If your team member is surprised, you skipped one of the earlier steps. The exit should be calm, dignified, and quick. Drag it out and you punish the rest of the team. Make it harsh and you damage your reputation as a leader. Treat the person with the respect they deserve as a human being, and treat the team with the respect they deserve by acting on what you said you would.
This is the part of the job nobody writes about in the founder essays. It is also the part of the job that separates the leaders the strongest people want to work for from the ones the strongest people quietly leave.
What “Making It Worse” Actually Looks Like
Five patterns reliably amplify difficult team behaviour rather than addressing it. None of them feel obviously wrong in the moment.
- Venting to other team members. It feels like getting support. It functions like building a private case against someone who has not been told there is a case being built. The team you vent to loses trust in you faster than you think.
- Raising it in a group setting first. Public correction without prior private feedback is a violation, full stop. The person will not hear what you are saying. They will hear that you ambushed them in front of their peers.
- Avoiding the conversation but punishing the behaviour through other channels (cold-shouldering, withholding opportunities, slow no’s on requests). You are still in conflict with the person. You have just made the conflict less honest.
- Outsourcing the conversation to HR or a peer. Sometimes HR involvement is appropriate, especially in larger orgs. But the first conversation should come from the leader, not from a third party. If your team member finds out about the concern from HR first, the relationship has already taken a hit you cannot undo.
- Going from no feedback to exit. Some founders, having avoided the conversation for too long, jump directly to firing when they finally act. The team does not see the months of frustration that led there. They see a person who was on the team last week and gone this week, with no warning. That is the move that breaks trust most.
When the Behaviour Is Coming From a High Performer
This is the version of difficult team behaviour most leaders hesitate longest on. The person is brilliant at the work. They ship more than anyone else. They have a relationship with a key customer or own a critical part of the codebase. And they are also undermining the team.
The honest answer is that the high performer makes this conversation harder but does not change what the conversation has to be. The cost of tolerating the behaviour rises with the person’s influence, not the other way around. A junior team member who undermines decisions is a manageable problem. A senior team member who undermines decisions reshapes the team’s norms in their image.
The “we can’t afford to lose them” framing usually loses sight of what the team is already paying to keep them. Run the math both ways before you decide.
Run a Better Check-In While You’re Working Through This
The weekly check-in is the cheapest place to track behaviour change over time, without making it feel like a performance review. Our free check-in template walks teams through the three questions that matter most: from what, to what; what’s blocking; and what we learned this week. Use it as the framework for the one-to-one cadence while you and the team member are working through the bar change.
Get the free Check-In Template →
Frequently Asked Questions
What if the difficult team behaviour is from a high performer? Address it the same way you would address it from anyone else, with the same playbook. The cost of tolerating the behaviour rises with the person’s influence, not falls. A high performer who undermines decisions, hoards information, or sets a bad tone reshapes the team’s norms in their image. The “we can’t afford to lose them” math usually misses what the team is already paying to keep them. Run the numbers both ways before you decide.
How do I know when to escalate to exit? You have escalated to exit when you have named the pattern clearly, given a real chance to change with a specific timeline, documented the conversations, and the behaviour has not shifted in a meaningful way. If you have done all of that and the behaviour persists, you have your answer. The exit should not be a surprise to the person at that point. If it is, an earlier step got skipped.
Should I bring HR in early? In larger orgs with formal HR functions, looping HR in before any documented conversation can save everyone trouble later. They can advise on documentation, employment law, and process. The conversation itself should still come from you, the leader, not from HR. Your team member finding out about a concern from HR first is a relationship hit you cannot easily undo. In smaller orgs without dedicated HR, your employment lawyer is the equivalent first call.
What if I’m worried about retaliation or a hostile response? This concern is worth taking seriously, especially in cases that touch on protected categories or where there is any history of unsafe behaviour. If you have real fear of a hostile response, talk to an employment lawyer before the first conversation, not after. For the more common case, the fear of retaliation is usually larger than the reality. A well-prepared, private, specific conversation almost always lands as care, not attack. The framework above is designed to reduce the surface area for escalation.
What if I realize the behaviour is partly my fault, or the role’s fault, not just the person’s? Then say so in the conversation. “I want to name something I have noticed, and I want to acknowledge that part of what made this possible is [the way the role was set up / the lack of clear expectations / the change in the team’s priorities]. We both share responsibility for getting this right.” That kind of honesty makes the conversation easier, not harder. It signals you are not building a case. You are solving a problem together.
The Conversation Is the Job
Strategy is easy. Focus is hard. Execution is the work. And the part of execution most leaders do not budget time for is the hours spent in one-to-one conversations addressing the small fractures that, untreated, become the fractures that break a team.
The leaders the strongest people want to work for are the ones who can have these difficult team behaviour conversations well. Not the ones who avoid them. Not the ones who deliver them as ultimatums. The ones who can sit across from a team member and say, with care and with clarity, “Here is what I am noticing. Here is what needs to change. Here is what I will do to support you. Here is what happens if it doesn’t.” And then mean every part of it.
That is the craft. It does not get easier with practice. It just gets less avoidable.
If you’re ready to run a check-in cadence that helps you address the small fractures before they become big ones, see how OKR Leader works →
