Conflict styles: the Thomas-Kilmann model and when each mode actually works

60-Second Summary

Thomas-Kilmann maps conflict behavior on two axes: assertiveness (concern for own outcomes) and cooperativeness (concern for others’ outcomes). Five modes emerge: competing, collaborating, compromising, avoiding, accommodating.
No mode is universally best. The instrument explicitly says effectiveness depends on the situation — and Kilmann’s own writing flags that mid-career professionals over-rely on compromising as a safe default.
Avoidance and accommodation are appropriate in well-defined situations (low-stakes issues, preserving harmony for a more important issue, when you’re wrong). Treated as character flaws by most modern training — wrongly.
Collaborating is the most resource-intensive mode. Using it on low-stakes issues wastes the relationship’s capacity for the high-stakes ones.
The TKI instrument is licensed (Kilmann Diagnostics). Free knock-offs exist but are poorly normed; for serious team work, use the licensed version.

Conflict is a permanent feature of teamwork, not a sign of dysfunction. The Thomas-Kilmann Conflict Mode Instrument (TKI), developed by Kenneth Thomas and Ralph Kilmann in 1974, is the most widely used framework for naming and developing conflict behavior — and one of the most distorted in second-hand training.

The two underlying axes

Assertiveness — the extent to which you try to satisfy your own concerns.
Cooperativeness — the extent to which you try to satisfy the other person’s concerns.

Crossing these two axes yields five modes. The TKI position is that everyone uses all five, but typically has 1–2 default modes overused and 1–2 underused.

The five modes

Mode	Assertiveness	Cooperativeness	Stance
Competing	High	Low	Win at the other’s expense
Collaborating	High	High	Find a solution that fully satisfies both
Compromising	Mid	Mid	Each side gives up something
Avoiding	Low	Low	Postpone or sidestep
Accommodating	Low	High	Yield to the other

When each mode is actually right

Situational use

1
Competing
When quick decisive action is vital (emergencies); on important issues where unpopular actions need implementing (cost cutting, enforcing rules); when you know you’re right and the issue is critical.
2
Collaborating
When the concerns of both parties are too important to be compromised; when you need a creative integrative solution; when you need buy-in by incorporating others’ concerns; when you need to repair a relationship damaged by past conflict. Resource-intensive — use selectively.
3
Compromising
When goals are moderately important but not worth the disruption of stronger modes; when two opponents with equal power are committed to mutually exclusive goals; for temporary settlements to complex issues; when under time pressure.
4
Avoiding
When an issue is trivial; when you have no chance of winning; when potential damage outweighs benefits of resolution; when others can resolve it better; when more information is needed; to let people cool down.
5
Accommodating
When you realize you’re wrong (let a better position be heard); when issues are more important to others (a goodwill deposit); to build social credits for later issues that matter more to you; when preserving harmony is especially important; to allow subordinates to develop by learning from mistakes.

Avoiding and accommodating are taught as bad in most management training. The research and the instrument disagree. Both are appropriate — and skilled — responses in the right context.

Common pattern failures

Compromising as a default — produces mediocre outcomes on high-stakes issues that warranted collaboration, and over-invests on low-stakes ones that warranted accommodating.
Competing as a default — produces compliance but exhausts relational capital. Often misread by the competer as ‘direct’ and ‘decisive.’
Collaborating as a default — well-intentioned, but turns every disagreement into a 90-minute meeting. Burns the team’s collaboration budget on low-stakes issues.
Avoiding as a default — sometimes the right answer; chronically used, it produces unresolved residue that contaminates later issues.
Accommodating as a default — produces resentment and identity erosion. Often correlates with burnout in service roles.

Using TKI in a team

Have each team member take the official TKI (≈$15–25 per assessment, licensed).
Map the team distribution. Discuss which modes are overused as defaults vs underused.
Pair the modes with recent team conflicts: what mode was used? what mode would the situation have warranted?
Build a shared vocabulary: ‘This is a collaborating issue — let’s book the time.’ ‘This is an accommodating issue — I’ll defer to you.’
Revisit at 6 months. The pattern shifts most when used as a working language, not a one-time workshop.

References

Thomas, K. W., & Kilmann, R. H. (1974). Thomas-Kilmann Conflict Mode Instrument — Kilmann Diagnostics
Thomas, K. W. (1992). Conflict and conflict management: Reflections and update — Journal of Organizational Behavior

Written by Pawan Joshi.Sources cited inline.

First published 15 Jun 2026See site changelog →