How to Handle Conflict at Work (With Scripts)

Almost everyone avoids workplace conflict until it has grown into something bigger than it needed to be. The good news is that most conflicts at work are small, specific and solvable if you have words ready for the first awkward conversation.

What workplace conflict is, and why it matters

Conflict is any situation where you and someone else want incompatible things, or believe the other is getting in the way. It might be a teammate who keeps missing handoff deadlines, a manager who changes priorities weekly, or a peer who takes your work as their own. Left alone, small friction turns into avoidance, gossip and quiet resentment, and the work suffers.

Handling it well is a visible skill. Interviewers ask about it directly, and managers notice who can raise an issue calmly versus who lets it fester or explodes.

Separate the person from the problem

This idea is popularised in the book Getting to Yes by Roger Fisher and William Ury, and it is practical. When something goes wrong, our instinct is to explain it by who the person is: lazy, careless, political. That explanation is a guess about intent. What you can actually observe is behavior and its effect.

Interests vs positions

A position is what someone says they want: 'We must use the new framework.' An interest is the reason behind it: 'I'm worried the old one will be unsupported and I'll be stuck maintaining it.' Two positions can be incompatible while the interests are perfectly compatible. This is another idea from Fisher and Ury.

Example: an analyst wants the report done by Monday; a data engineer says it cannot be done by Monday. The positions clash. Ask about interests and you learn the analyst needs numbers for a Tuesday meeting, and the engineer needs time to validate a data source. The solution, delivering a clearly labelled preliminary version Monday and a validated one Wednesday, serves both.

"What's the most important thing for you here?"
"What are you worried will happen if we do it the other way?"
"What would a good outcome look like for you?"
"What constraint am I not seeing?"

A step-by-step conversation structure

Use this sequence for a one-to-one conversation about a specific issue. Choose a private, unhurried time, and ask for the conversation instead of ambushing someone in a channel.

1. Ask for time and set a neutral frame: 'Can we talk for ten minutes about how we hand off tickets? I'd like us to find something that works for both of us.'
2. Describe the specific situation and its effect, without judgment about the person.
3. Share your side briefly: what you need and why.
4. Ask for their view and listen. Summarise it back: 'So what I'm hearing is...'. Do not rebut until they confirm you understood.
5. Look for interests on both sides, then generate two or three options together.
6. Agree on one concrete next step with an owner and a date.
7. Follow up in writing and check back after a week or two.

Opening:
"Hi Karan, do you have ten minutes today? I want to talk about how we handle code reviews. I think we can make it smoother."

Situation and effect:
"The last three PRs I opened sat for about two days before a review. I had to hold the release on Thursday because of that."

Your side:
"I need reviews within a day when something is blocking a release, otherwise I can't plan."

Their view:
"How does it look from your side? Is there something making reviews hard to get to?"

Reflect:
"So you're getting pulled into incidents and my PRs are large and hard to review quickly. That makes sense."

Options and next step:
"What if I keep PRs under 300 lines and ping you with a priority tag when something is blocking? Could you commit to a same-day look on those? Let's try that for two weeks and check in."

When to escalate

Try a direct conversation first for ordinary disagreements, because going over someone's head without talking to them damages trust. But some situations should go to a manager, mentor or HR sooner.

"I'd like your help with something. I've spoken with Karan twice about review delays; we agreed on a same-day rule and it hasn't held. The impact is that two releases slipped. I'm not looking to blame anyone. Could you help us agree on priorities for reviews?"

Common mistakes

• Waiting until you are furious, so the first mention comes out as an accusation.
• Venting to colleagues instead of the person involved. It feels like progress but solves nothing.
• Using words like always and never, which invite a defensive argument about examples.
• Arguing about who is right instead of what to do next.
• Having the conversation by chat, where tone is easily misread.
• Skipping the follow-up, so the agreement quietly fades.

How this shows up in interviews and on the job

'Tell me about a conflict you had with a coworker' is one of the most common behavioral questions. Interviewers are checking that you address issues directly, stay respectful, and focus on outcomes. Do not claim you have never had a conflict; it sounds evasive. Pick a real, modest example, and tell it using the STAR structure from Behavioral Interview Questions and the STAR Method. Spend most of your time on what you said and did, and end with the result and what you learned. Avoid stories where the other person is simply the villain.

Related pitfalls are covered in Common Interview Mistakes to Avoid. On the job, the same structure helps with stakeholders, customers and managers, not just peers.

How to practice

Think of one small, unresolved friction in your current work or study group. Write the script for it using the template above, say it out loud once, and then have the real conversation within the next few days. Low-stakes practice makes the high-stakes version much less scary.