Framework

The Thomas-Kilmann (TKI) Model

Five conflict styles, two dials — how hard you push, how much room you give — chosen on purpose, not by default.

The Thomas-Kilmann (TKI) Model Find this on the mind-map

Introduction

Back in the 1970s, two researchers named Kenneth Thomas and Ralph Kilmann went looking for a better answer to a question every manager has asked: why do some people handle conflict so differently from others? They borrowed an idea from Robert Blake and Jane Mouton, who had spent the 1960s mapping leadership styles onto two simple axes with something called the Leadership Grid. Thomas and Kilmann pointed that same two-axis approach at conflict instead of leadership style.

What they built is now called the Thomas-Kilmann Conflict Mode Instrument, or TKI for short — a way to read any response to conflict along two dials, and use where it lands to name your default style.

How It Works

You can read any conflict response along two dimensions:

  • Assertiveness — how hard you push for your own needs or goals
  • Cooperativeness — how much room you make for the other person's needs or goals

Plot where a response lands on those two dials, and you get one of five conflict styles.

Style Assertiveness Cooperativeness The stance When it works Watch out
Competing High Low I win, you lose Crises, non-negotiable issues, enforcing a boundary or a standard Reads as aggressive, damages relationships, silences people
Collaborating High High We both win Both sides' concerns genuinely matter, trust needs building, there's time Slow, stalls momentum, frustrates people who just want a decision
Compromising Moderate Moderate Split the difference Time is short, the issue is moderately important, you need to break a standstill Weaker outcomes, breeds a mediocre middle-ground culture
Avoiding Low Low I'd rather not deal with it The issue is minor, emotions are running too hot, you need more information Tension festers, signals that conflict is unsafe, wears down trust
Accommodating Low High You win, I yield The relationship matters more than the outcome, the other person knows more, you're building goodwill You get treated like a doormat, resentment builds

Here's the core claim: no style wins every time. Competing isn't always bad, and collaborating isn't always good. The style is neutral — the situation is what decides whether it works.

So how do you pick? Run it through a simple decision tree built on two questions: how important is the issue, and how important is the relationship or the other person's needs.

  • High issue, low relationship: Competing
  • High issue, high relationship: Collaborating
  • Moderate issue, moderate relationship: Compromising
  • Low issue, low relationship: Avoiding
  • Low issue, high relationship: Accommodating

Treat the tree as guidance, not a rule. The goal is matching the style to the moment, not finding a perfect answer.

Why It Matters for Leaders

Most leaders avoid conflict simply because nobody ever taught them how to manage it. You get trained on prioritizing, delegating, motivating — and then left to figure out the tension between people entirely on your own.

Without a framework, you fall back on whatever feels safe. That usually means avoiding, waiting, or overreacting. The conflict doesn't resolve — it festers, and eventually you're refereeing a problem that's already spread to the rest of the team.

You have one or two default styles, and your default is also your blind spot. Always accommodate and you get walked over while quietly building resentment. Always compete and you stop hearing bad news, because people learn that pushing back costs them.

The model changes the question from "how do I make this go away" to "what does this moment actually need." Picture this: two people on your team keep clashing. Telling them to work it out is avoidance, and picking a side just creates a loser — so the fit is collaborating. Get both of them in a room, surface what each one actually needs, and guide them toward a solution they both own.

Or this: a performance review turns defensive. Competing harder makes it hostile, and softening the message leaves the real problem unaddressed — so the fit is a blend of compromising and collaborating. Hold the standard, invite the constraints, and build the plan together.

Or this: you're in a roadmap disagreement with a senior stakeholder. Going along just to keep the peace costs you credibility — so the fit is competing with data when the issue really matters, and collaborating when there's room to explore.

Used well, this framework doesn't remove conflict from your job. It makes your response deliberate, and that's what turns conflict from something you dread into something you manage.

Your chat with Kyoshi about the The Thomas-Kilmann (TKI) Model framework

What to do next

Test your knowledge of The Thomas-Kilmann (TKI) Model

Take the quiz →

Practice The Thomas-Kilmann (TKI) Model

Apply The Thomas-Kilmann (TKI) Model to a real situation

Skills related to The Thomas-Kilmann (TKI) Model

Frameworks related to The Thomas-Kilmann (TKI) Model

CLEAR Model

CLEAR Model

A five-stage coaching structure — Contract, Listen, Explore, Action, Review — that centers real listening and reflection before rushing to a plan.

Dunning-Kruger Effect

Dunning-Kruger Effect

Knowing little makes you feel unstoppable; knowing more makes you hesitate — the loudest voice is rarely the most reliable one.

FUEL Model

FUEL Model

A four-stage coaching model — Frame, Understand, Explore, Lay out a plan — built for managers, ending in an actual plan.

Goldilocks Principle

Goldilocks Principle

Support runs on a dial between micromanagement and abdication — enough direction for clarity, enough space for ownership, always moving.

Hawthorne Effect

Hawthorne Effect

People change how they behave when they know they're watched — your attention is an intervention that changes what you see.

Maslow's Hierarchy of Needs

Maslow's Hierarchy of Needs

Abraham Maslow's five-level model of motivation, applied to leadership as a stack — mastery, trust, belonging, up through recognition and vision.

McKinsey 9-Box Model

McKinsey 9-Box Model

A 3x3 grid that plots each person on performance against potential, giving nine distinct calls instead of one blurry verdict.

Multipliers and Diminishers

Multipliers and Diminishers

Liz Wiseman's split between leaders who bring out best thinking in people around them, and those who shut it down.

Situational Leadership

Situational Leadership

There's no right way to lead — only the right way for this person right now: direct, coach, support, or delegate.

T-GROW

T-GROW

A five-stage coaching structure — Topic, Goal, Reality, Options, Way Forward — that names what's actually worth discussing before it moves you from where you are to where you want to be.

The 6 Human Needs

The 6 Human Needs

Every behavior at work is really an unmet need in disguise — six needs, popularized by Tony Robbins, worth checking first.

The Architecture of High-Performing Teams

The Architecture of High-Performing Teams

Six elements, built like a temple — culture as the base, four pillars, vision as the roof — name the missing piece.

The Bannister Effect

The Bannister Effect

One person breaking a barrier makes it stop being fixed for everyone else — break the unspoken belief in public first.

The Five Dysfunctions of a Team

The Five Dysfunctions of a Team

Lencioni's pyramid of five team-killing behaviors — a lack of trust at the base drags everything above it down.

The Four Leadership Support Roles

The Four Leadership Support Roles

A 2x2 separating four modes for helping someone — coaching, mentoring, counseling, consulting — plus a test for picking the right one.

The Inner Drive

The Inner Drive

A leadership take on Daniel Pink's *Drive* that turns three conditions for motivation — autonomy, mastery, purpose — into habits for 1:1s.

The Pygmalion Effect

The Pygmalion Effect

What you expect from someone leaks into how you treat them, which shapes what they become — for better or worse.

Tuckman's Stages of Team Development

Tuckman's Stages of Team Development

Every team moves through five predictable stages — forming, storming, norming, performing, adjourning — each demanding a different move from you.

Books related to The Thomas-Kilmann (TKI) Model

Coaching for Performance

Coaching for Performance

Sir John Whitmore's foundational case for coaching-style management over command-and-control, built on a single idea: performance is limited less by skill than by interference, and a manager's job is to remove the interference, not supply the answer.

Elevate

Elevate

Robert Glazer's case, from his book "Elevate: Push Beyond Your Limits and Unlock Success in Yourself and Others," that performance isn't a willpower problem. It's a capacity problem across four specific domains, built like a muscle, not willed into existence overnight.

First, Break All The Rules

First, Break All The Rules

A large-scale look at what the best managers actually do differently, and the uncomfortable finding that most of it runs against conventional management wisdom, starting with the idea that you shouldn't try to fix people's weaknesses.

Multipliers

Multipliers

Liz Wiseman's case that the biggest lever on a team's output isn't headcount or talent density, it's whether the leader in the room makes people smarter or slowly makes them smaller.

Team Topologies

Team Topologies

Skelton and Pais's case that most team structures are drawn to fit an org chart, not the actual flow of work, and a small set of team shapes and interaction rules for fixing that, built around a resource every leader habitually overspends: people's cognitive load.

The Coaching Habit

The Coaching Habit

Michael Bungay Stanier's pitch that most managers have an "advice monster" problem, and a short list of deceptively simple questions designed to starve it, a little at a time, in conversations that already happen every day.

The First-Time Manager

The First-Time Manager

The unglamorous, practical handbook for the specific week your job title changed and nothing else came with instructions. Less a framework, more a set of answers to the questions new managers are usually too embarrassed to ask out loud.

The Five Dysfunctions of a Team

The Five Dysfunctions of a Team

Patrick Lencioni's pyramid of the five behaviors that sink teams without much notice, stacked so that each one is actually caused by the dysfunction beneath it, which means fixing results or accountability first almost never works.

The Making of a Manager

The Making of a Manager

Julie Zhuo's field notes from becoming a manager in her twenties with no idea what the job actually was. A clear-eyed answer to the question most new managers are too embarrassed to ask out loud: what am I actually supposed to be doing all day?

The Manager's Path

The Manager's Path

Camille Fournier's map of the actual career ladder from doing the work to leading an organization of leaders, written for engineering managers, but mostly a clear-eyed account of how the job itself changes at every rung, which almost nobody explains to you before you climb it.

Turn the Ship Around!

Turn the Ship Around!

A submarine captain's account of giving up the one thing every leader is taught to protect, being the person who gives the orders, and turning the worst-performing submarine in the fleet into one of the best by making every sailor think like a captain instead.