Clean the Lint Filterby Work Shouldn't Suck

Month 6 of 8

Not All Conflicts Are the Same

Decision types and knowing what kind of situation you are actually in.

The move

Name the level, name the type

The moment it is for

Your team has the same argument again, a solution did not hold, or a decision conversation gets strangely charged.

What it takes

One 90-minute session. A minute or two a day. Ten minutes a week.

Start here · about 5 minutes

Guess, then read

This month's lens comes from mediation's diagnostic tradition and negotiation research.

Two guesses before you read anything. Guessing first, even wrong, makes the reading stick. (It is also slightly annoying. Sorry.)

About the argument you keep having

Your team is arguing about office days again. Third time. The same people say the same things, a little louder, and someone proposes a survey. (There is already a survey.)

An argument that keeps coming back is usually happening at the wrong level, or the fix is aimed at the wrong kind of problem.

The level first.

Three levels, top to bottom

  1. 1PositionsWhat each side says it wants.“Use Vendor A.”
  2. 2InterestsWhy they want it.“I need the launch to be stable.”
  3. 3NeedsWhat they require underneath.“I want a say in my own work.”

Most workplace arguments stay at the top. They resolve at the bottom.

Then the kind. A technical problem has a known fix. An adaptive problem asks people to change what they value, believe, or do, and no new process will settle that. One question sorts them: if this were purely technical, would we have solved it by now?

And before any decision conversation, say which kind of decision it is. A fair amount of workplace betrayal is one person hearing “consult” when the other had already decided.

Four kinds of decision

  1. 1CommandOne person decides.
  2. 2ConsultOne person decides, after real input.
  3. 3ConsensusEveryone can live with it.
  4. 4VoteThe majority decides.

This month’s move comes before you respond: name the level, name the type.

Before the live session · one required piece

Introduction to Collaborating with the Enemy (Adam Kahane, Reos Partners)

A few pages. Why the usual idea of collaboration fails when people disagree deeply.

Next: Try it here

On your own · about 12 minutes

Try it here

Three short practice rounds load here. If you are logged in to Squarespace and see only this line, view the page logged out.

Next: Practice together

The live session · 90 minutes

Practice together

One session at the start of the month. Everyone tries the move once, with real people.

Run of show
0:00–0:10Check-in. Name a recurring conflict type on your team. Just name it, don’t analyze it yet.
0:10–0:30Core concept. The V model (positions, interests, underlying needs). Decision types and conflict categories. Adaptive vs. technical problems.
0:30–0:55Case analysis. Using three real situations from your team's past 90 days, identify the level of the conflict and what the appropriate response would have been.
0:55–1:15Power in the room. How does power and hierarchy shape conflict on your team? What goes unsaid because of it?
1:15–1:25Set the daily rep and meeting hook.
1:25–1:30Close.

Run the rep on conflicts in any domain. Replace the live session with a 45-minute solo session mapping one real conflict on the V Model worksheet and the Conflict Diagnosis Matrix.

Power in the room

The V model and the conflict-type diagnosis are useful tools. But they’re “neutral” tools, and neutral tools can obscure something important: not all conflicts are equally shared. Role, race, gender, seniority, disability, class, and organizational status shape who gets to define what the conflict is about, whose underlying needs get named, and whose do not. An adaptive problem looks different from the top of the hierarchy than from the bottom.

Before diagnosing a conflict this month, try these questions. They come from organizing and restorative traditions rather than management frameworks:

  • Who benefits from things staying the way they are?
  • Whose perspective is missing from how this conflict is being defined?
  • Who carries the most risk in naming this conflict honestly?
  • What would it look like to address this conflict in a way that strengthens the relationship rather than just resolving the issue?

These questions are diagnostic. Nobody is being accused. They work alongside the V model rather than replacing it, and they often reveal what the V model alone cannot.

What to have in the room

This month’s worksheet (PDF)
Handouts and frameworks
Session handoutTHE V MODEL (Harvard Negotiation Project / Understanding in Conflict)

A map of where conflict lives, from surface to depth:

  • Positions (top of the V, widest, most visible). What each party says they want. “I want to use Vendor A.” “I think we should expand the team.” This is where most conflict conversations happen. Also where they get stuck.
  • Interests (middle of the V). Why they want it. What outcome they are protecting. “I need stability.” “I need to feel heard in decisions.”
  • Underlying Needs (bottom of the V, where resolution lives). What they require underneath. Often about identity, belonging, fairness, or recognition.

Most conflicts resolve when the conversation reaches underlying needs. Most stay stuck at positions.

Session handoutADAPTIVE vs. TECHNICAL PROBLEMS (Heifetz, Grashow & Linsky)

Technical problem: a known solution exists. Expertise and process can solve it.

Adaptive problem: the solution requires people to change values, beliefs, or behaviors.

TECHNICAL: “Our reporting process is broken.” Fix the process.

ADAPTIVE: “We disagree about whose priorities get protected.” Involves power and identity.

The most expensive mistake is applying a technical solution to an adaptive problem. Signs you have an adaptive problem: the same issue returns after you solved it, the fix does not hold, people agree in the meeting and revert, the conflict seems irrational.

Diagnostic question: if this were purely technical, would we have solved it by now?

Session handoutDECISION TYPES

Before any decision conversation, name the type:

  • COMMAND: One person decides. Others execute.
  • CONSULT: One person decides, but input is genuinely sought first.
  • CONSENSUS: The group decides together. Everyone must be able to live with it.
  • VOTE: The majority decides. Fast. Best for lower-stakes choices.
  • NO DECISION: Not making a decision is itself a decision.

Many conflicts happen because the type is never named:

  • Person A thinks they are being consulted; Person B has already decided. Betrayal.
  • The team thinks it is consensus; the leader thinks it is consult. Resentment.

Practice: name the decision type before the conversation starts.

Three practice scenarios

Scenario 1
A recurring conflict about a process, resource, or priority. Map it on the V: each side’s positions, interests, underlying needs. What changes about how you would approach the conversation if you focused on underlying needs?

Scenario 2
Apply the adaptive/technical diagnostic to that same conflict. Is it technical, or are people being asked to change how they see their role or value? What changes if you treat it as adaptive?

Scenario 3
Your team is about to discuss a decision. Before it starts: what type is this, command, consult, consensus, vote, or no decision? What happens to the conversation if the type is not named?

Next: Keep it going

All month · a minute or two a day

Keep it going

Decide now when you will use it

People who decide the when in advance follow through more often than people who only intend to. Pick the moment in your week where the cue is most likely to show up.

…I will name the level and the type before I respond. Other whens: a decision meeting gets oddly charged. A fix we agreed on has stopped holding. Someone says “we’ve been over this.”

Saved in this browser only.

The daily rep

Once a day, when a disagreement shows up, name the level and the type before you respond.

The cue: Your team has the same argument again, a solution did not hold, or a decision conversation gets strangely charged.

One line on the practice log each day you run it. A missed day is information.

Monthly Practice Log (PDF)

Attach it to a meeting you already hold

Before a significant decision or disagreement, name the level out loud: are we disagreeing about positions, interests, or underlying needs? Then check whether you are treating it as technical when it might be adaptive.

Each week: one prompt, then two from memory

Think of a recurring conflict. Map it on the V: is the conversation at the position level, interest level, or underlying need level? What would change if you went one level deeper?

Is there a conflict that keeps coming back? Is it possible it is an adaptive problem you have been addressing with technical solutions?

Two from memory. Answer first, then check.

The three levels, top to bottom.

Positions. Interests. Underlying needs.

From Month 5: the three restorative questions.

What happened? What was the impact? What would make it right?

How does power show up in conflict on your team? Who tends to be heard? Who tends to go quiet?

Two from memory. Answer first, then check.

The question that separates technical from adaptive.

“If this were purely technical, would we have solved it by now?”

From Month 3: what do you ask when someone answers “sort of”?

“What am I missing?”

What assumptions have you been carrying about someone’s position or motivation that you have never tested by going deeper on the V?

Two from memory. Answer first, then check.

The kinds of decision.

Command. Consult. Consensus. Vote. And no decision, which is also a decision.

From Month 4: the question before any BIFF reply.

Do I need to respond at all?

More to try between sessions, and the team artifact
  • The next time a conflict arises, pause and diagnose it: what type is this, and what level is it at on the V?
  • In your next team decision, make the decision type explicit before discussing: is this a decision someone owns? An input process? A consensus situation? Name it before you begin.

Team artifact this month: a conflict diagnosis matrix. When a conflict arises, map it before responding. Post it in the room where you have hard conversations.

  • Technical problem? Adaptive problem? Relational issue?
  • Positions:
  • Interests:
  • Underlying needs:
  • Decision type for this situation: Command, Consult, Consensus, or Vote
Questions for a mid-month check-in

Optional. Forty-five minutes, in pairs or small groups.

  • What happened when you tried to identify the level of a conflict on the V? Where did the conversation naturally want to stay?
  • Can you identify a conflict you have been treating as technical when it might be adaptive? What would the adaptive version of addressing it look like?
  • How does power show up in this team’s conflicts? Who gets to define what the conflict is about?
  • In Emergent Strategy, adrienne maree brown proposes that the quality of our relationships determines the quality of our outcomes. Do you believe that? What evidence do you see for it here?

Three checks before you move on

  • Did I identify at least one conflict at a level deeper than positions this month?
  • Did I name the decision type before at least one significant team discussion?
  • Can I distinguish between a technical problem and an adaptive one?
Next: Go deeper

Optional · for the weeks you have appetite

Go deeper

None of this is required. The rep is the practice. The media is the seasoning.

If you pick three

The rest of the list (4 more)
  1. LISTEN Emergence Magazine Podcast: Practical Reverence, with Robin Wall Kimmerer Botanist and Citizen Potawatomi Nation member Robin Wall Kimmerer on the serviceberry as a living model for a gift economy. Pairs directly with the Serviceberry essay from Month 5. Free transcript.
  2. ARTICLE Collaborating with the Enemy: Interview with Adam Kahane (Journal of Wild Culture) Long-form interview with Kahane on his work in Colombia, Mexico, and South Africa: what collaboration across deep difference looks like in practice.
  3. Book Collaborating with the Enemy (Adam Kahane)
  4. Book Good Arguments (Bo Seo) Two-time world debate champion Bo Seo on disagreement as a craft: how to find the real point of clash, argue it cleanly, and keep the relationship intact. A strong companion to this month's diagnosis work.
Where this month’s ideas come from
From the fieldINTERESTS VS. POSITIONS (HARVARD NEGOTIATION PROJECT)
Roger Fisher and William Ury’s foundational insight from Getting to Yes: people argue about positions, but what they need to negotiate are interests, the underlying reasons behind those positions. Focus on positions and you get stuck. Focus on interests and you often discover more room to move than you thought. The V model maps the same terrain.
From the fieldADAPTIVE LEADERSHIP (HEIFETZ, LINSKY, GRASHOW)
The distinction between technical problems and adaptive problems, developed by Ronald Heifetz with Marty Linsky and Alexander Grashow, is one of the most useful conflict diagnostics available. Technical problems have known solutions. Adaptive problems require people to change values, beliefs, or behaviors. Most organizational conflict that feels stuck is stuck because people are applying technical solutions to adaptive problems. You cannot process-design your way out of a values conflict.
From the fieldEMERGENT STRATEGY (ADRIENNE MAREE BROWN)
Drawing on science fiction, biomimicry, and Black radical traditions, brown’s work offers a frame many Western management approaches lack: how we move matters as much as where we go, and the quality of our relationships determines the quality of our outcomes. Small patterns replicate at scale. If the pattern in your meetings is that some voices shape the agenda and others respond to it, that pattern will replicate into your decisions and your community relationships.
From the fieldNEMAWASHI (JAPANESE CONSENSUS PRACTICE)
Nemawashi, literally “preparing the roots,” is the Japanese practice of building a decision through quiet one-on-one groundwork before the meeting where it is formalized. It pairs with this month's diagnosis work. Once you know what type of decision you are in, nemawashi moves the real conversation to before the room, person by person, so the meeting confirms agreement instead of manufacturing it. Toyota pairs it with the 5 Whys you met in Month 2.

For whoever runs the session

Running the session?

Facilitator guide

Draw the V on a whiteboard and use it visually throughout. For the case analysis, use situations from the past 90 days that at least two people experienced. Ask: what level were we at? What level should we have been at? The power conversation requires careful setup. You are asking people to name patterns, not individuals. Keep that distinction clear. If time runs short, protect the power conversation. It is the part teams most need and most often skip.

Watch for people who want to resolve the case studies rather than diagnose them (“we are practicing diagnosis, not resolution”), the power conversation stalling out of fear (“this is exactly what the lint filter is for”), and people who say all their conflicts are technical (“if it were fully technical, would you have solved it by now?”).

Month 6 is often where teams realize that some of their recurring conflicts are adaptive problems they have been treating as technical ones for years. That realization is uncomfortable and important. Give it room.