# Conflict Resolution Examples: How Common Workplace Clashes Get Resolved Canonical URL: https://headwayskills.com/knowledge/teamwork/conflict-resolution-examples/ Markdown URL: https://headwayskills.com/knowledge/teamwork/conflict-resolution-examples.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 See five conflict resolution examples in action—from work-style clashes to underperformance—and the simple approach that settles each without anyone 'winning.' ## Key facts - Title: Conflict Resolution Examples: How Common Workplace Clashes Get Resolved - Category: Teamwork - Primary skill: Teamwork - Related skills: Communication, Building Resilience - Primary keyword: conflict resolution examples - Source page: https://headwayskills.com/knowledge/teamwork/conflict-resolution-examples/ ## What this page covers - See five conflict resolution examples in action—from work-style clashes to underperformance—and the simple approach that settles each without anyone 'winning.' - Practical guidance for conflict resolution examples - How this topic connects to Teamwork ## Detailed explanation Most conflicts at work aren't dramatic showdowns. They're a teammate who keeps missing deadlines, a colleague whose style rubs against yours, or an email that lands the wrong way and sits in your chest all afternoon. Conflict resolution examples show how those ordinary clashes actually get settled: you pick a deliberate approach—collaborating, compromising, accommodating, competing, or avoiding—and run the conversation so both people reach an outcome they can live with, rather than one person "winning." There's no single right move for every situation, which is exactly why examples help more than rules. Here are the five recognized approaches, each shown in a realistic scenario. ## Five conflict resolution approaches, with examples In the early 1970s, Kenneth Thomas and Ralph Kilmann studied how people react to conflict and found that most responses fall into five patterns, sorted by two things: how hard you push for your own needs (assertiveness) and how much you work to meet the other person's (cooperativeness). Every example below is one of those five. Before any of them works, though, the same short sequence applies—pause long enough to notice what's actually setting you off, engage by listening for what the other person really needs, then address the problem together. The people who resolve conflict well look past what each side is demanding to [the need sitting underneath it](/knowledge/professional-behaviors/active-listening/). That's usually where a solution both people accept has been hiding the whole time. ### Collaborating: building a solution that fits both sides Two designers are assigned the same project. One cares most about how it looks; the other only about whether it works. Left to harden, that becomes a standoff. Collaborating breaks it: instead of one overruling the other, they name the need behind each position—visual impact versus reliable function—and design something that delivers both. It's the only approach that fully satisfies everyone, which is also why it costs the most: it needs time, trust, and genuine give-and-take. Reserve it for the conflicts where both the outcome and the relationship really matter. ### Compromising: meeting in the middle A manager's weekend shifts always seem to go to the same few people, and the rest of the team reads it as favoritism. A full collaborative redesign of the schedule would take weeks nobody has. Compromising fits better: everyone gives a little, a rotation is agreed, and no one gets exactly what they wanted but everyone gets something workable. It's faster than collaborating and lands on a fair-enough middle ground. The trade-off is that it leaves some needs only half-met, so it suits moderate-stakes disputes more than the ones that really count. ### Accommodating: giving ground on purpose A colleague feels strongly about how a shared document should be formatted. You don't, really. Accommodating means yielding on purpose—you let them have it, preserve the goodwill, and save your energy for a disagreement that matters more. It's high on cooperation and low on assertiveness, and it's the right call when you're simply wrong, or when the issue is trivial to you and important to them. The risk is making it your reflex: if you accommodate everything, your own needs never make it into the room, and quiet resentment builds instead. ### Competing: standing firm when it counts A safety corner is about to be cut with no time to debate it, and you know you're right. Competing—pushing your position assertively, even at the other person's expense—is the approach that fits. It's fast and decisive, and it earns its place in emergencies, on genuine matters of principle, or when a quick call from someone with the authority to make it is what the moment needs. As an everyday habit it does real damage: win-lose repeated often enough teaches people to stop bringing you their side at all. ### Avoiding: stepping back, and its limits A teammate keeps turning in [half-finished work](/knowledge/teamwork/accountability-workplace/), and everyone quietly cleans up after them because raising it feels awkward. That's avoiding—and the scenario shows its cost. Sidestepping a conflict is sometimes the smart move: for genuinely trivial friction, or to let a hot moment cool before you speak. But important problems don't resolve themselves. Tension builds, assumptions harden, and colleagues absorb the slack until someone burns out. When a conflict actually matters, avoidance just postpones it—here the real fix is [a calm, specific conversation](/knowledge/communication/difficult-conversations-at-work/) about what was expected and what will change. Notice that the five examples differ less in the problem than in the response. Handled well, these conversations barely register; dodged or fumbled, they quietly drain a team. Unresolved conflict is regularly named as one of the biggest hidden costs in organizations—a widely repeated 2008 estimate put it at $359 billion a year in lost U.S. productivity, and while that figure is old and rarely re-checked, what it points at is real: the expensive part of a conflict is seldom the disagreement itself, but everything that curdles when no one deals with it. The catch is that the hard part isn't learning five labels—it's spotting which one a situation calls for and catching your own default reaction before it chooses for you. Most of us lean on one or two of these modes automatically, so it's worth knowing [which ones you reach for](https://assessment.headwayskills.com/) [under pressure](/knowledge/confidence/stay-calm-under-pressure/). ## The skills that make these conversations easier Look across the five approaches and the same handful of abilities keeps doing the quiet work—reading the situation, holding steady, and talking it through cleanly. Three of them carry most of the weight. **Teamwork** is what keeps the relationship intact while you disagree. The people you clash with are usually people you'll keep depending on, so engaging the real issue while staying off the person, committing to what you jointly decide even when you argued the other way, and holding each other to it without letting things fester—that matters as much as who turns out to be right. **Communication** does the in-the-moment work. Every example above turns on a conversation you'd rather not fumble: listening for the real need beneath the stated position, saying your part clearly without tipping into attack, and choosing a live conversation over a cold email when the subject is sensitive. It's less about the right words than about landing a hard message without setting off an escalation. **Building Resilience** is the internal side. The conflicts that rattle us most are the ones where we feel wronged, and resilience is what stops a flash of "they're attacking me" from driving the response—separating what you can control from what you can't, questioning the story you're telling yourself about their motives, and not taking friction personally. None of these is a fixed trait you either have or don't; they're ordinary work skills that strengthen with practice, and they sit among the twelve the framework tracks across almost any job. Since they're learnable, the useful move is knowing which already work for you and which would repay some attention—something a free Work Skills Test can [map in a few minutes](https://assessment.headwayskills.com/). ## What this means for you Reading back through those examples, you may already have spotted your own instincts—the approach you reach for first, the one you'll do almost anything to dodge. None of it is fixed. People who handle conflict well aren't a calmer breed; they've practiced a few moves until the moves became reflexive, and you can build the same ones while staying entirely yourself. This tends to count for more, not less, as you take on responsibility—more people to coordinate, higher stakes when something goes sideways—so it's worth growing now rather than later. And the fact that you went looking for how conflicts actually get resolved, instead of just bracing for the next uncomfortable one, already puts you ahead of most. The useful next step is simply to see where your own skills stand. ## See where you stand You've seen how these conflicts get resolved and the skills sitting underneath them—the only thing left is to find where yours are strongest and where a little practice would go furthest. The free Work Skills Test is a short self-assessment that measures you across all twelve work skills—including the teamwork, communication, and resilience that carry you through a disagreement—and shows, in plain terms, which ones will make the biggest difference for you right now. It takes about seven minutes, there's nothing to prepare, and if reading this brought one specific conflict to mind, this is the low-effort way to see what's really shaping how you handle it. ## 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? See five conflict resolution examples in action—from work-style clashes to underperformance—and the simple approach that settles each without anyone 'winning.' ### 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-resolution-examples/ Preferred summary: "See five conflict resolution examples in action—from work-style clashes to underperformance—and the simple approach that settles each without anyone 'winning.'" ## Change log - 2026-07-07: Content collection version published.