Five conflict styles and when each wins

There is no single “right” way to handle conflict — only a right match between the style and what’s actually at stake.

The idea

Every response to conflict is a point on two dials: how hard you push for your outcome (assertiveness) and how much you tend to their outcome (cooperativeness). Five named styles sit at the corners and centre of that grid.

No style is best everywhere. You choose by weighing two things: what the issue is worth and what the relationship is worth. Avoiding is smart for a trivial nit and a disaster when your credit is on the line.

Try it — match the style to the stakes

scenario 1 of 4
issue worth: relationship worth:
cooperativeness → assertiveness → competing collaborating compromising avoiding accommodating
issue resolved
—
relationship kept
—
choose a style to see how it plays out — fit —
Drag the marker (or tap a style) to where you’d place your response. The two meters show what it cost and what it kept.

How it works

Read the two stakes, then pick the corner that fits:

                 low cooperativeness   high cooperativeness
high assertive   COMPETING             COLLABORATING
                 (I win)               (we both win — but slow)
low  assertive   AVOIDING              ACCOMMODATING
                 (nothing happens)     (you win)
   centre    ->  COMPROMISING (we each give a little — fast, fair-enough)

pick by:  issue worth   vs   relationship worth   vs   time
  issue high, rel low, urgent      -> competing
  issue high, rel high, time to spare -> collaborating
  both moderate, need it now       -> compromising
  issue trivial                    -> avoiding
  relationship >> issue (or you're wrong) -> accommodating

Collaborating produces the best outcome on both dials — but it’s the most expensive in time and energy. That’s why it’s overkill for a trivial nit and exactly right when both stakes are high.

When to use it

StyleWins whenCost / risk
CompetingIssue matters, relationship less; or a fast, decisive call is neededBruises relationships; breeds resentment if overused
CollaboratingBoth the outcome and the relationship matter, and there’s timeSlow and effortful; wasteful on small things
CompromisingModerate stakes, roughly equal power, need a result nowNobody fully satisfied; can settle too shallow
AvoidingThe issue is trivial, or tempers need to cool firstReal problems fester; reads as disengaged if overused
AccommodatingYou’re wrong, or the relationship far outweighs the pointYou give up the substance; becomes a doormat pattern

Watch out for

Worked example

“Tell me about a conflict with a coworker and how you handled it.”

“A teammate kept reformatting my code in ways that broke my open PRs. My first instinct was to just let it go — but the issue wasn’t trivial: it was costing me a day a week, and the relationship mattered because we’d keep working together. So I chose to collaborate rather than avoid. I asked to talk, learned he was enforcing a style guide he thought was mandated, and we agreed on a shared formatter config that ran automatically. Both of us got what we actually wanted. Had it been a one-off cosmetic preference, I’d have simply let him have it — but the stakes here justified the effort.”

Check yourself

A coworker wants the alert email to say “warning” instead of “caution.” It changes nothing. What’s the sensible style?

Production is down, the on-call team is split, and a call is needed in two minutes. Which style fits?