How to handle conflict at work: the conversation most people avoid (and why they shouldn't)
March 18, 2026
A misunderstanding turns into a missed handoff. The missed handoff becomes resentment. Resentment becomes avoidance. Six months later, you're working around someone instead of with them, and everyone on the team can feel it.
The conversation that could have fixed it takes 20 minutes. You've been putting it off for half a year.
Why we avoid conflict at work
Work conflict is uniquely loaded because:
- The other person isn't going away. You'll see them at the next meeting
- Power dynamics make disagreement feel risky
- You've spent enough time with the person to accumulate grievances, which makes the conversation feel bigger than it is
- You don't want to seem difficult, emotional, or not a team player
So you wait. You drop hints. You mention it to a colleague who knows both of you. You hope the other person figures it out.
They don't. The friction compounds.
A framework for the direct conversation
Name the pattern, not the person
The most common mistake in conflict conversations is leading with the person's character rather than the specific behavior.
Character-focused (avoid): "You never listen to feedback." / "You always take credit for other people's work." / "You're not being a team player."
Behavior-focused (use this): "In the last three design reviews, I've raised a concern about the navigation and it hasn't made it into the next iteration. I want to understand if there's a reason for that, or if I'm not communicating it clearly."
Character judgments put people on the defensive. Specific behaviors open a conversation.
State the impact from your perspective
After naming the behavior, explain what it creates for you, without claiming you know their intent.
"When that happens, I feel like my input isn't being weighted, and I find myself pulling back from contributing in those sessions. I don't think that's what either of us wants."
You're not accusing. You're reporting. The other person can dispute intent, but not your experience.
Ask what they see
Before proposing solutions, ask them to share their perspective. You might be missing context. You might have contributed to the dynamic yourself. Even if their perspective doesn't change what needs to change, giving them the space to share it is what makes the conversation collaborative rather than one-sided.
"I wanted to share that first, but I'm also genuinely curious what you're seeing from your side. Is there something about how I'm raising the concern that isn't landing for you?"
Agree on what changes
Don't end the conversation without a clear, specific agreement on what will be different.
Vague: "Let's just communicate better going forward."
Specific: "Going forward: if you hear a concern I've raised and you're intentionally not moving on it, can you let me know why in the session? That way I know it was received, even if we're choosing not to act on it. And if I raise it and it's not clear, ask me to clarify. Does that work?"
Follow up
After the conversation, send a short message that reflects what you agreed to. Not a legal record. A signal that you're treating it seriously.
"Good conversation earlier. Thanks for making the time. I'll keep raising things in the way we discussed, and I appreciate you committing to loop me in when there's a reason for the call."
When to have it directly vs. when to involve someone else
Have it directly when: - It's a peer or someone on a project with you - The issue is a pattern of behavior that's affecting your ability to work - You haven't told them directly that this is a problem
Involve someone else (manager, HR) when: - You've had the direct conversation and nothing changed - The behavior involves power dynamics (someone above you, or behavior that constitutes harassment) - It involves a policy violation, not just a working style difference - You're not safe having the direct conversation
The bar for involving HR or a manager is higher than most people think. Before you go that route, ask yourself: "Have I told this person, directly and specifically, what behavior is a problem and what I need to change?" If the answer is no, the first step is the direct conversation.
The hardest version: conflict with your manager
This is the conversation people are most afraid of, and the one that most needs a different approach.
When the conflict is with your manager, the direct conversation still applies, but the framing shifts. You're not holding them accountable. You're expressing what you need to do your best work.
Instead of: "You micromanage me and it's undermining my confidence."
Try: "I do my best work when I have room to make decisions on execution and come to you with the result. I've noticed I'm checking in more frequently than feels natural to me, and I wanted to understand if that's coming from somewhere specific, or whether there's a way to build more trust on the path forward."
You're not challenging their authority. You're advocating for your working conditions. That's a conversation most managers will respect.
What most people get wrong
They wait too long. Conflict conversations are easier when they're small. Waiting until you're resentful means you're having the conversation with a full backlog of grievances behind it. The sooner, the better.
They have it over Slack. Don't. Text strips out tone, pace, and body language: the things that keep a hard conversation human. Do it live, even if it's a video call.
They rehearse what they'll say, but not what they'll hear. They walk in with a speech. The other person says something unexpected. They get defensive or shut down. Prepare for the response, not just the opening.
They confuse directness with bluntness. Being direct means being clear about what behavior is a problem and what you need. Being blunt means being careless about how you say it. You can be precise and kind at the same time.
The cost of not having the conversation
When you don't have the conversation, you don't avoid the conflict. You just move it somewhere else: into passive behavior, into venting to colleagues, into a slow erosion of the working relationship.
The other person often has no idea there's a problem. They go on doing what they're doing. You go on being frustrated. At some point it escalates into something that requires HR, or you leave, or the project suffers in a way that's visible to everyone.
The 20-minute conversation you're avoiding would have cost less than all of that.
Part of our How to Handle Conflict at Work guide: See all conflict at work resources →
Put it into practice
Try a free communication drill. Type your response, get AI feedback on clarity, confidence, and structure — no signup needed.
Try a free drill →