Don’t Avoid Conflict; Aim It

Teams that dodge conflict move slow and build quiet resentment. High performers do the opposite: they channel heat at the work, not the people. Don’t avoid conflict; aim it at a clear decision with shared criteria and simple rules.

Why aimed conflict wins

• Speed: Debate has a destination and a deadline.

• Quality: Diverse views collide with evidence.

• Ownership: People commit to decisions they pressure-tested.

• Trust: Safe dissent → stronger commitment.

Aim it with TARGET

• Topic: Name the decision and the deadline. Reversible or not?

• Aim: Define success criteria and constraints (budget, risk, brand).

• Rules: Heat ideas, not people; steelman first; evidence over opinion; time-box; disagree-and-commit.

• Ground truth: Bring data and the customer signal.

• Explore: Generate at least three options and explicit trade-offs.

• Take the call: Who decides, by when; document choice, why, risks, dissent.

Rules that keep it safe

• Attack ideas, protect relationships.

• Steelman before you rebut: “Here’s your strongest point as I get it…”

• One conversation at a time; equal turns.

• No side deals; decisions live in writing.

Phrases that aim heat

• “What decision are we making, by when?”

• “What would change your mind? Here’s mine.”

• “What trade-off are we making on purpose?”

• “This feels personal—back to criteria.”

• “Time-box 10 more minutes, then decide or test.”

When to adjust the heat

• Turn up: Smell groupthink, stakes high, facts conflict—use red-team/rotate first speaker.

• Turn down: It’s personal, re-litigating—pause, restate criteria, switch to writing/gather data.

Buy data, not drama

• Turn claims into hypotheses.

• Define a minimum test (audience, time, budget, metric).

• Time-box and pre-commit to the readout.

• Use results to update the call.

A 30-minute conflict workout

• Pre-read (5): Context, data, draft options.

• Frame (3): Decision, criteria, constraints, roles.

• Debate (15): Steelman, evidence, trade-offs.

• Decide (5): Decider chooses, states why and next steps.

• Commit + log (2): Owners state first action; publish decision.

If it goes sideways

• Name the rupture; reset the decision and criteria.

• Narrow scope/time; clarify roles.

• Change channel (write, async) to cool off.

• Debrief triggers and update rules.

Signals it’s working

• Faster decision latency.

• Lower reversal-for-missed-info rate.

• Broader contribution spread.

• Higher follow-through on first actions.

Closing thought: Don’t snuff out the fire—point it at the decision, bind it to criteria, and ship.