There is no single “right” way to handle conflict — only a right match between the style and what’s actually at stake.
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.
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.
| Style | Wins when | Cost / risk |
|---|---|---|
| Competing | Issue matters, relationship less; or a fast, decisive call is needed | Bruises relationships; breeds resentment if overused |
| Collaborating | Both the outcome and the relationship matter, and there’s time | Slow and effortful; wasteful on small things |
| Compromising | Moderate stakes, roughly equal power, need a result now | Nobody fully satisfied; can settle too shallow |
| Avoiding | The issue is trivial, or tempers need to cool first | Real problems fester; reads as disengaged if overused |
| Accommodating | You’re wrong, or the relationship far outweighs the point | You give up the substance; becomes a doormat pattern |
“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.”
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?