# Conflict Handling at Work: 9 Ways to Have the Conversation You've Been Avoiding

Canonical URL: https://headwayskills.com/knowledge/teamwork/conflict-handling/
Markdown URL: https://headwayskills.com/knowledge/teamwork/conflict-handling.md
Entity type: Article
Last updated: 2026-07-07
Language: en
Primary audience: professionals improving teamwork at work
Owner: Headway Skills
Contact: https://headwayskills.com/contact/

## Short answer

Conflict handling is a set of learnable moves, not a personality type. Nine ways to raise a problem with a colleague without damaging the relationship.

## Key facts

- Title: Conflict Handling at Work: 9 Ways to Have the Conversation You've Been Avoiding
- Category: Teamwork
- Primary skill: Teamwork
- Related skills: Communication, Building Resilience
- Primary keyword: conflict handling
- Source page: https://headwayskills.com/knowledge/teamwork/conflict-handling/

## What this page covers

- Conflict handling is a set of learnable moves, not a personality type. Nine ways to raise a problem with a colleague without damaging the relationship.
- Practical guidance for conflict handling
- How this topic connects to Teamwork

## Detailed explanation

You have rewritten the message three times and sent none of them. The thing your colleague did is still sitting there, and every day you leave it, raising it gets harder. Conflict handling is the set of moves you use to bring a disagreement into the open and settle it without damaging the working relationship: raise it early, describe the behavior rather than the person, listen before you argue, and agree on one specific change. It is a set of habits rather than a temperament — and the reason it feels impossible is usually that nobody explains the mechanics behind the advice.

## What conflict handling actually asks of you

The phrase itself comes from the Thomas-Kilmann Conflict Mode Instrument, developed by Kenneth Thomas and Ralph Kilmann, which plots [five conflict-handling modes](/knowledge/teamwork/conflict-management-styles/) on two independent axes: assertiveness, meaning how far you pursue your own concerns, and cooperativeness, meaning how far you pursue the other person's. Most articles turn that into a quiz. The more useful part is the geometry — those are two separate dials, not one. You can press for your own position and protect the relationship at the same time, which unpicks the assumption most people are stuck on: that raising a problem and keeping a good working relationship are a trade-off, so the safe move is to say nothing.

Saying nothing has a price. Harvard Business School Online and HR-side sources describe unaddressed disagreement as something that does not stay contained — it works its way into morale, productivity, and trust, and the version you eventually have to deal with is larger than the one you avoided. What separates that from a good outcome is not nerve. It is a sequence of fairly ordinary moves, every one of them learnable, and here they are in roughly the order you would use them.

## 1. Raise it while it is still about one specific thing

Nearly every guide leads with "address it promptly," and Indeed's career guide is typical: discuss it as soon as you have concluded there is an issue. The reason is mechanical rather than moral. A problem raised in week one is about a missed handover; the same problem raised in month three is about what kind of person your colleague is. There is one carve-out the sources agree on: if it has just blown up, wait until you have both cooled down. The rule is early, not immediate.

## 2. Test your version of events before you act on it

You will arrive at this with a settled story about why they did it, and that story is more often the error than the event was. Indeed's advice to understand the motives behind a colleague's actions is really an instruction to hold your interpretation loosely — they were overloaded, they were never told, they read the brief differently than you did. Writing down the three most plausible explanations before the conversation tends to expose how thin the evidence is for the one you have been carrying around. Your own pattern is just as hard to see from the inside — whether you tend to go quiet or push too hard — so it can be worth a few minutes to [read your own reflexes](https://assessment.headwayskills.com/) rather than guess at them; either habit is adjustable.

## 3. Choose the setting deliberately

Face-to-face and private is close to universal across the top results, with enough time blocked that neither of you is watching the clock. Two mechanisms sit behind it. Written messages strip out tone, and they forward. A group setting makes the other person defend their position in front of an audience, which turns a solvable disagreement into a status contest they cannot step back from without losing face. How you ask matters as much as where you meet: "do you have twenty minutes this week?" has a scope attached to it, while "can we talk?" reads as a summons and gives them two days to build a defense.

## 4. Open on the behavior and its effect, not on the person

This is the most repeated rule on the subject and the one most often stated without an example. In practice it is the difference between "you do not respect other people's time" and "the file came in after the deadline twice, and I had to redo the summary both times." The first is a judgment your colleague has to dispute in order to protect themselves. The second is a fact they can simply address. Sources also note that staying on behavior keeps the other person from turning defensive, which protects the rest of the conversation rather than just the opening line.

## 5. Spend the first half listening, not waiting

[Active listening](/knowledge/communication/active-listening-workplace/) here is described as listening with intent and reading nonverbal cues — not as a courtesy you perform before making your real point. There is a blunt test for whether you managed it: if you finish their explanation holding exactly the view you walked in with, you were rehearsing rather than listening. One move does most of the work. Say their position back in your own words and ask whether you have understood it correctly, before you respond to any of it. It costs fifteen seconds and turns the rest of the conversation from two prepared statements into an exchange.

## 6. Buy yourself time instead of trying to feel calm

"Stay calm" appears in almost every article on this topic and is explained in almost none of them, which is why it fails in the room. The University of Washington's Husky Experience Toolkit offers the one mechanism worth carrying: the aim is to get out of the impulse-driven part of the brain and into the prefrontal cortex, where you can think rationally. You cannot get there by deciding to feel differently on demand. You get there by buying seconds — a pause, a sip of water, "let me think about that for a moment." Composure also outlasts the disagreement: it leaves you known as someone who can hold their temper.

## 7. Say what you want to happen next, in one sentence

Most conflict conversations that go nowhere end in mutual understanding and no change. Two weeks later the same thing happens, and you conclude that conflict handling does not work. A conversation is only finished when there is a specific, observable, agreed change: who does what, by when. The Thomas-Kilmann model is explicit that full collaboration is expensive and a poor fit for minor disagreements: on a small issue, a partial split both of you can live with is the correct outcome, not a failure of ambition.

## 8. Repair the relationship in the days after

Harvard Business School Online and others report that conflict handled well can leave colleagues closer than they were before. That does not happen by itself; it is decided in the following week. The content is small and specific: resume normal contact quickly instead of going quiet, give them credit in the next meeting where credit is due, and do not [re-litigate it with third parties](/knowledge/professional-behaviors/workplace-gossip/). That last one undoes all the others: discussing a settled conflict with other colleagues turns a resolved issue into a reputational one, and your colleague will hear about it.

## 9. Know the threshold where this stops being yours to handle

Minor conflicts get resolved person to person; a manager or HR is the right instrument when things escalate — and then straight away, before the situation gets away from you. The judgment worth having is where that line sits: [a clear agreement](/knowledge/teamwork/how-to-hold-someone-accountable/) that gets broken again, anything touching harassment, discrimination, safety, or policy, or a power imbalance that makes a direct conversation unsafe. It is also worth knowing why so much of this advice reads oddly: a large share of the material on conflict handling, including SHRM's and HR Acuity's, is written for managers and HR staff handling other people's disputes, and quietly assumes an authority you do not have.

## What actually makes conflict handling easier

Read back over those nine and notice how few of them are really about conflict. Raising something early, describing what happened instead of judging who did it, hearing an explanation you were not expecting, agreeing on a change and then following through — these are ordinary working behaviors that simply matter most when the temperature rises. Which is why some people find disagreements manageable and others dread them: a few habits are doing quiet work underneath.

**Teamwork** supplies the governing idea: disagreement is necessary work, not a relationship failure. That means engaging the disagreements that need engaging rather than letting them accumulate, keeping the exchange anchored to the topic instead of the person, and noticing the moment trust drops so you can stop and reset. It also covers what comes after: implementing what you agreed even where you would have chosen differently, and going back promptly when a commitment gets missed.

**Communication** is how any of it actually gets executed. Choosing a live conversation over a message thread because the topic is sensitive, saying the specific thing rather than the softened version of it, giving the other person your full attention instead of loading your next reply, and knowing how to handle someone who is angry or apologize cleanly when part of the fault is yours — these are the moves that carry the charged twenty minutes itself.

**Building Resilience** governs what your own reaction does to you while it happens. The chain runs event, then automatic thought, then reaction, and the reaction comes from the interpretation rather than the event — which is why the same remark lands differently on different days. Learning to catch the thinking errors in that middle step, and to separate what your colleague does from what is actually yours to control, is what keeps you steady enough to run the other eight moves at all.

Which of those three is your weak link is genuinely hard to call from the inside, and it is rarely the one you would nominate. The **free** Work Skills Test measures all twelve of the work skills this framework covers, resilience among them, and will [show which skill is weakest](https://assessment.headwayskills.com/) so you can practice something specific instead of trying to get better at conflict in general.

## None of this asks you to be a different person

Some of this may already describe how you work — the listening part coming easily while the raising part stalls, or the other way around. That split is common, and it is information rather than a verdict. None of these nine moves requires you to become more confrontational, or more accommodating, than you actually are; they are behaviors you add to how you already operate, and the ones you have not built yet are gaps rather than limits. It does get more consequential as you go: the disagreements you are part of grow along with your responsibilities, and the ones you leave alone grow with them. You have already done the part most people skip, though — going to look for how to handle this rather than waiting for it to resolve itself.

## Find out which part is yours to work on

So the only thing left is an honest read on where you currently stand. The Work Skills Test is a **free** self-assessment of the everyday skills sitting underneath all nine of these moves — how you work through disagreement with other people, how clearly you say the difficult thing, and how you handle your own reaction when it lands badly. It scores you across all twelve work skills and points to the one or two that would change the most about how your next disagreement goes. It takes about seven minutes and there is nothing to prepare — you answer as you are, not as you would like to be. If a particular colleague came to mind while you were reading, this is the low-key way to work out what to change before you have that conversation.

## Who this is for

- Professionals building practical workplace skills
- Readers looking for specific, usable work advice
- Managers, educators, and coaches supporting career readiness

## Common questions

### What is this guide about?

Conflict handling is a set of learnable moves, not a personality type. Nine ways to raise a problem with a colleague without damaging the relationship.

### Which Headway skill does this connect to?

This guide connects primarily to Teamwork. It also relates to Communication, Building Resilience.

### What is the recommended next step?

Use the free Work Skills Test to reflect on which work skill to improve next.

## Related pages

- https://headwayskills.com/knowledge.md
- https://headwayskills.com/knowledge/teamwork.md
- https://headwayskills.com/knowledge/communication.md
- https://headwayskills.com/knowledge/resilience.md
- https://headwayskills.com/work-skills-test.md

## Citation guidance

Use the canonical page when citing this content:
https://headwayskills.com/knowledge/teamwork/conflict-handling/

Preferred summary:
"Conflict handling is a set of learnable moves, not a personality type. Nine ways to raise a problem with a colleague without damaging the relationship."

## Change log

- 2026-07-07: Content collection version published.
