Resolving conflicts with coworkers effectively
Workplace conflict handled badly follows you. Handled well, it builds more trust than if the conflict never happened. Here's the sequence that actually works.
The instinct when a coworker conflict surfaces is to avoid it and hope it resolves itself. This works occasionally. More often, the avoidance creates a low-grade friction that persists for months, or worse, surfaces at the worst possible moment in a high-stakes meeting where you’d rather it didn’t.
Conflict at work is normal. The people who handle it well become the people others want to work with. The people who avoid it accumulate unresolved tension until it leaks.
What workplace conflict actually is
Most coworker conflict isn’t personal. It’s structural. Two people have different information, different incentives, different definitions of done, or are optimizing for different outcomes. When those differences collide on a deadline or a decision, it reads as conflict even when neither person is being unreasonable.
The other category: genuine friction from a personality clash or a pattern of behavior that’s built up over time. This is less common but not rare, and it requires a different sequence.
What the other party is trying to do
This is the question most people skip: what does your coworker actually want in this situation? In most cases, they want the same thing you do: to do their job well, to be treated with respect, and to not have this friction persist.
When conflict feels personal, assume structural misalignment first and test it before concluding it’s malice. The test: ask yourself, “if I had their information and their incentives, would I behave the same way?” If yes, this is a coordination problem. If no, there may be something more personal going on.
What good resolution looks like
A well-resolved coworker conflict ends with three things: a shared understanding of what caused the friction, a clear agreement about how to handle similar situations going forward, and no residual weirdness in the relationship. The last one takes the longest.
A badly resolved conflict “ends” with one person winning the argument while the other person shuts down and starts routing around them in future decisions. If you won the argument and lost the relationship, you didn’t resolve the conflict.
The step-by-step sequence
Step 1: Wait 24 hours. If you’re in the heat of it, don’t have the conversation today. The version of you that’s frustrated or defensive is not the version of you that resolves things. Sleep on it. Write down what happened, what you think caused it, and what you actually want from the conversation. That clarity is harder to access when you’re still in the feeling.
Step 2: Ask for a private conversation. Not in a group meeting. Not over Slack where tone is invisible. Directly: “Hey, do you have 15 minutes this week? I want to clear something up between us.” Private and specific. If they decline or keep deferring, you have additional information.
Step 3: Open with the shared problem, not your grievance. Start the conversation from the premise that you’re both trying to solve something, not that you’re there to explain why they were wrong.
“I wanted to talk about [project/situation], because I think we ended up in a confusing spot and I want to make sure it doesn’t happen again.”
Not: “I want to talk about what you said in that meeting.”
Step 4: State your perspective, then ask for theirs. Say what you observed and how it affected your work. Then stop and ask what their experience was. “Here’s how I saw it from where I sat. What was going on from your side?” Listen to the answer. This step resolves more conflicts than any other, because the explanation you hear is almost never what you expected.
Step 5: Agree on the going-forward rule. The point of the conversation is not to relitigate what happened. It’s to establish a clearer way of working together going forward. End with something explicit: “So going forward, if X happens, we’ll do Y. Does that work?” Simple, concrete, agreed.
What to do if step 4 reveals a real pattern
If the conversation surfaces a genuine, repeated behavior issue rather than a one-time misalignment, the sequence changes. Document what’s happened (dates, specifics, impact), raise it again with your direct manager framed as a work-effectiveness issue, and ask for their help facilitating. Going to your manager is not escalation in the pejorative sense. It’s using the system correctly.
The version of this that backfires: going to your manager without having the direct conversation first. It reads as going around the person, which creates more friction than the original conflict. Have the direct conversation first. If it doesn’t resolve, then involve others.
Conflict handled well is not a tax on the relationship. It’s an investment in it. I’ve had coworkers I got along with superficially for months and genuinely trusted only after we’d had one direct conversation about something that wasn’t working. The conversation is always the thing.
Further reading
Filed under: Collaboration , Career Development
Cubicle To Corner Office
The 317-page playbook for the transition from student to professional.
Related pieces
Promotion pathways: the 3 levers that matter (even if no one says it)
Most promotion advice tells you to 'do great work.' Here's what actually moves the needle: scope, visibility, and advocacy from people who aren't your direct manager.
Cross-time-zone collaboration: the async-first rules that prevent burnout
If every question becomes a meeting, you'll never breathe. Here's how to work effectively across time zones without destroying your schedule.
Expat first job: the unspoken rules you need to learn fast
In a new country, 'professionalism' may look nothing like what you expected. Here's how to decode the unwritten norms before they decode you.
Join the conversation
Real readers (and Mike) reply in here. The number next to each comment is its upvote score — sign in with just a display name to add your vote or post a reply. No email or password required.