Every team has a default move when a disagreement gets tense. One person pushes harder. Another goes silent in the meeting and argues in DMs afterward. A third proposes splitting the difference before anyone has explained what they want. Those defaults have names. The five-style model of conflict management styles calls them competing, collaborating, compromising, avoiding, and accommodating.
The model is useful for one reason above all. Research on team conflict keeps finding that how a team handles disagreement predicts outcomes beyond what the disagreement is about. A 2013 meta-analysis of 45 studies and 3,218 teams found that conflict processes explained an additional 13% of the variance in team performance and team affective outcomes, after accounting for the type of conflict involved. Style is a lever you can pull.
Where the Five Styles Come From
The idea started with Robert Blake and Jane Mouton's Managerial Grid in 1964. They plotted managers on two axes, concern for production and concern for people, and named five ways of handling conflict: forcing, withdrawing, smoothing, compromising, and problem-solving.
In the 1970s, Kenneth Thomas and Ralph Kilmann reworked the axes into assertiveness (how hard you pursue your own concerns) and cooperativeness (how hard you work to satisfy the other person's concerns). Their version produced the labels most people use today and became the Thomas-Kilmann Conflict Mode Instrument, or TKI. Thomas described the five as conflict-handling modes: behaviors anyone can use, with each one suited to some situations.
A third instrument, M. Afzalur Rahim's ROCI-II from 1983, uses concern for self and concern for others and produced five reliable, independent scales. The names shift from model to model, but the ideas map cleanly:
- Competing = forcing (Blake and Mouton) = dominating (Rahim)
- Collaborating = problem-solving = integrating
- Compromising = compromising = compromising
- Avoiding = withdrawing = avoiding
- Accommodating = smoothing = obliging
The official TKI is published by The Myers-Briggs Company. Co-creator Ralph Kilmann's site sells the online version from $50 per person. QuestWorks is not affiliated with either. If you want a quick, free read on your own default before spending money, the QuestWorks conflict style quiz takes 15 questions and maps your answers to the same five styles.
Why Conflict Style Shows Up on the Calendar
Conflict eats time. A 2008 CPP study of 5,000 full-time employees in nine countries found that 85% of employees deal with conflict to some degree, and U.S. employees spent 2.8 hours per week on it, which the report valued at about $359 billion in paid hours. The all-country average in that study was 2.1 hours per week.
By 2022, The Myers-Briggs Company's follow-up found respondents spending 4.34 hours per week dealing with conflict, about double the 2008 all-country figure. More than a third said they deal with conflict often, very often, or all the time, up from 29% in 2008, and nearly 1 in 4 said their managers handle conflict poorly or very poorly. The full report names poor communication as the most common cause, with lack of role clarity, heavy workloads, and personality clashes also common. People who spent more time on conflict reported lower job satisfaction and felt less included.
Two caveats. Both studies come from the TKI's publisher, which has a commercial interest in conflict being expensive. And the $359 billion figure is an estimate of paid hours spent, which is a different thing from measured lost output. The direction of the trend is still hard to argue with. For a closer look at the cost side, see what workplace conflict costs and how to prevent it.
The 5 Conflict Management Styles, With Workplace Examples
1. Competing (assertive, uncooperative)
Competing means pursuing your own position at the other person's expense. Thomas called it power-oriented. It gets a bad reputation, and some of that reputation is earned, but it has a job to do.
Example: A production outage hits at 2 a.m. Three engineers are debating whether to roll back or patch forward. The on-call lead cuts the debate: "We roll back now. We can argue about the patch tomorrow." Nobody's concerns get fully heard, and that is fine, because the cost of a slow decision is higher than the cost of a bruised opinion.
When it helps: emergencies, safety and compliance calls, and decisions where one person owns the outcome and speed beats consensus.
When it backfires: when it becomes the default for ordinary disagreements. A manager who competes on every call becomes the bottleneck for every decision, and the team learns to wait for the verdict and stops thinking the problem through. Teammates who lose repeatedly stop raising objections, which means problems surface later and cost more.
2. Collaborating (assertive, cooperative)
Collaborating means digging into a disagreement until you find the underlying concerns on both sides and a solution that satisfies both fully. It is the only style that is high on both axes, which is why it gets treated as the gold standard.
Example: A product manager wants to ship a feature with a minimal onboarding flow. The design lead wants to hold the release for a fuller flow. They set their positions aside and ask what each is protecting. The PM is protecting a customer commitment date. The designer is protecting activation rates. They agree to ship on the date with a guided checklist that covers the two steps where new users drop off, and schedule the fuller flow for the next cycle.
When it helps: high-stakes decisions, complex problems with several valid perspectives, and situations where both parties need to own the outcome afterward. A study of 96 project groups found that task conflict was positively related to group performance when it was actively managed and negatively related when it was passively managed. Agreeable conflict management also predicted higher group satisfaction. That active, agreeable combination is close to what collaborating describes.
When it backfires: collaborating is slow. On trivial issues it wastes the team's time, and on urgent ones it delays action. It also fails when one side is only pretending to collaborate while holding a fixed position. Teams that try to collaborate on everything end up in long meetings about small things.
3. Compromising (intermediate on both axes)
Compromising looks for a quick, mutually acceptable middle that partly satisfies both sides. Everyone gives something up.
Example: Two squads share a platform team's sprint capacity, and both have a launch in the same month. After a short conversation, they split the capacity evenly and each squad cuts a stretch goal. Each squad gives something up, and both launches stay on schedule.
When it helps: when the parties have roughly equal power, when the goals are moderately important, when a temporary settlement is needed, and when time is short. It is often the fallback when collaboration stalls.
When it backfires: when it is used too early. Splitting the difference before anyone understands the problem can produce a solution nobody wants, such as half a feature. Frequent compromising can also train people to open with inflated positions so the middle lands where they wanted it.
4. Avoiding (unassertive, uncooperative)
Avoiding means sidestepping the conflict: postponing it, withdrawing from it, or letting it drop.
Example: Two writers on a docs team disagree about serial commas. The manager lets it go and lets each follow the style guide as written. Six months later, the same manager lets a disagreement about who owns release notes go unaddressed, and it surfaces every sprint as missed handoffs.
When it helps: when the issue is trivial, when emotions are running hot and a cooling-off period will help, when someone else is better placed to resolve it, or when you need more information first.
When it backfires: when the issue keeps coming back. Avoided conflicts can move into side channels and turn into relationship friction, which is costly. A meta-analysis of 116 studies covering 8,880 groups found stable negative links between relationship conflict and group outcomes, and the same for process conflict. Task conflict did not show a strong negative link to performance. Avoiding a task disagreement can let it harden into the relationship kind.
5. Accommodating (unassertive, cooperative)
Accommodating means putting the other person's concerns ahead of your own. You yield.
Example: A senior engineer disagrees with a new hire's proposed naming convention for a small internal service. It is a minor call, the new hire cares a lot, and the senior engineer wants to build trust early. She says, "Go with yours," and saves her pushback for the database schema review next week.
When it helps: when the issue means more to the other person than to you, when you find out you are wrong, when you want to build goodwill for later, and when preserving the relationship is the priority.
When it backfires: when it is the only move you have. People who always accommodate stop contributing their best ideas, and resentment builds. Managers who accommodate every request end up with overloaded teams and unclear priorities, which feeds the role-clarity and workload problems the 2022 study flagged as common conflict causes.
Task Conflict vs. Relationship Conflict: Why Style Choice Depends on Both
The style you pick should depend on what kind of conflict you are in. Karen Jehn's 1995 study of 105 work groups and management teams separated task conflict (disagreement about the work) from relationship conflict (personal friction). Relationship conflict was harmful. Task conflict could help on non-routine work.
Then a 2003 meta-analysis by De Dreu and Weingart complicated the picture. It found negative correlations for both task and relationship conflict with team performance and satisfaction, and the effect was stronger on complex tasks such as decision-making and projects. The 2012 de Wit, Greer and Jehn meta-analysis found task conflict was not reliably negative, while relationship and process conflict were.
The practical reading: task conflict helps only under certain conditions, such as when a team actively manages it and when relationship conflict stays low. That makes style choice central. Collaborating on a task disagreement can surface better ideas. Competing on the same disagreement can turn it into a relationship problem. For more on building teams where debate improves decisions, see collective efficacy and productive conflict.
Culture Changes What a Style Means
The two-axis model came out of U.S. management research, and it carries Western assumptions. A meta-analysis of 123 paired comparisons within 36 studies found that individualistic cultures choose forcing more than collectivistic cultures, which prefer withdrawing, compromising, and problem-solving. The same analysis found women endorse compromising more than men regardless of culture.
For distributed teams, this changes how you read behavior. A teammate who steps back from a heated thread may be protecting the group's harmony and giving a colleague room to save face, which is a considered choice in many settings. Before labeling someone an avoider, ask what the behavior is doing for them and for the group. Conflicts between functions add a second layer of culture on top of national culture, a pattern covered in how to resolve cross-functional team conflict.
Your Style Is a Default, and Defaults Can Change
Thomas framed the five styles as modes: behaviors anyone can use, whatever their personality. Everyone uses all five, and most people lean on one or two. A quiz or assessment tells you your default, which is useful information, and it is only the starting point.
There is also a measurement problem. The Managerial Grid, the TKI, and the ROCI-II all rely on self-report. People describe how they think they handle conflict, and the people across the table may see something different. A manager who rates herself as collaborative may be experienced by her team as competing with extra steps.
Practical ways to widen your range:
- Name the stakes before you pick a style. Ask how important the outcome is and how important the relationship is. High and high points toward collaborating. Low and low points toward avoiding or a quick compromise.
- Check the clock. If a decision is needed in the next hour, collaborating is probably off the table. Say so out loud so nobody reads speed as disrespect.
- Separate the task from the person. Keep the disagreement on the work. Relationship conflict is the type the research consistently links to worse outcomes.
- Ask for outside data. Ask a trusted peer which style you default to under pressure. Compare it with your self-assessment.
- Practice the conversation you usually dodge. If you default to avoiding, prepare for one hard conversation this week. The scripts for difficult conversations at work give you a starting structure.
How Conflict Style Shows Up Under Pressure
Self-report captures how people see their conflict style on a calm day. Pressure tells a different story. When a deadline is close and the plan is failing, people tend to fall back to their strongest default, and a team's collective pattern becomes visible: who takes over, who goes silent, who mediates, who gives up ground to keep things moving.
Most teams only see that pattern during an actual crisis, which is an expensive place to learn it. Some teams use structured practice instead: retrospectives on hard decisions, tabletop exercises, or team games with time pressure built in. QuestWorks is one option in that last group. On a weekly game day, the whole team plays a 25-minute quest at the same time on QuestWorks' own platform (it connects through Slack or Microsoft Teams), seated into groups of 3 to 6, and the pressure of the game surfaces how the group negotiates, decides, and recovers when things go wrong. Leaders get a weekly Team Intelligence Score with an 8-week trend, dimensions such as Decision Velocity and Role Clarity, and a short list of things to try that week. Participation is voluntary and never tied to performance reviews. The tradeoff: it takes a weekly time commitment, and it works best when the team opts in, so it suits leaders who want an ongoing read on team dynamics.
Whichever route you take, start by knowing your own default. That is the style you will reach for when the pressure is on.
Find out whether you compete, collaborate, compromise, avoid, or accommodate when work gets tense, and what that default costs your team.
Take the free conflict style quiz
