Conflict Resolution

Conflict on a balanced team is not a failure -- it's a signal that people care about different things. When a PM, designer, and engineer disagree about the right approach, the disagreement itself is evidence that all three perspectives are active. The goal is not to eliminate conflict but to resolve it quickly, explicitly, and without lasting damage to trust.

Conflict signals

Catch these early. The longer a conflict goes unnamed, the harder it is to resolve.

Signal	What it looks like
Relitigating decisions	A decision made last week keeps coming up for rediscussion
Working around someone	People avoid pairing with a specific person or skip meetings they attend
Passive agreement	Everyone says "sounds good" but nobody acts on it
Architecture wars	Two engineers build competing approaches without aligning
Scope creep by addition	A stakeholder keeps adding requirements after stories are committed
The same retro topic three weeks running	Something keeps surfacing but never gets resolved
Back-channel conversations	Decisions are being made in DMs instead of team forums

If you see two or more of these signals at the same time, you have a conflict that needs structured resolution, not just better facilitation.

The resolution ladder

Not every disagreement needs a formal process. Escalate only as far as needed.

Level 1: Direct conversation (15-30 min) The two people talk it through. Use this at the first sign of disagreement when stakes are low and ownership is clear.

Level 2: Facilitated session (45-60 min) A neutral facilitator structures the discussion. Use this when the conversation has stalled, emotions are rising, or more than two people are involved.

Level 3: Mediated decision (30-45 min) A decision-maker hears both sides and makes the call. Use this when facilitated sessions haven't resolved it, stakes are high, or a deadline forces a decision.

Level 4: Escalation Bring it to a manager, sponsor, or engagement lead. Use this when the conflict involves a power dynamic, safety issue, or a pattern the team can't self-correct. (A product leadership coach can serve this role for teams without an obvious neutral escalation path.)

Most team conflicts should resolve at Level 1 or 2. If you're regularly reaching Level 3, your team may have a structural issue worth investigating.

Psychological safety requirements

Conflict resolution only works when people feel safe enough to say what they actually think. Before running any resolution process, check these conditions:

• People can disagree without fear of retaliation or social punishment
• The facilitator or decision-maker is genuinely neutral -- not an interested party
• The outcome is not predetermined -- if the answer is already decided, don't pretend it's collaborative
• The conversation happens in a private setting, not in front of an audience

If any condition is missing, fix that first. A conflict resolution session without psychological safety just teaches people to stay quiet.

The resolution process

This is the core process for a facilitated session (Level 2). Adapt it for other levels.

1. Frame the conflict (5 min)

The facilitator states what the disagreement is about (in neutral terms), what outcome the session is aiming for, and the ground rules: listen to understand, not to rebut.

Say this: "We're here because we have different views on [topic]. The goal is to understand each other's reasoning and find a path forward."

Not this: "We're here because there's a problem between you two."

2. Hear both sides (15 min)

Each party shares their perspective uninterrupted. The facilitator takes notes on:

• Position -- what they want to happen
• Interest -- why they want it (the underlying need)
• Evidence -- what data or experience supports their view

3. Identify common ground (10 min)

The facilitator reflects back where the parties agree (there is almost always overlap), where the interests differ, and what assumptions each side is making.

Say this: "It sounds like you both want [shared goal]. The disagreement is about [specific dimension]. Is that right?"

4. Generate options (15 min)

Brainstorm possible resolutions:

• Full commitment to one approach
• Time-boxed experiment -- try approach A for two weeks, measure, then decide
• Compromise or hybrid
• Deferring the decision until more information is available

Avoid splitting the difference on everything. That usually means nobody is satisfied and nothing is learned.

5. Decide and document (10 min)

Choose an option. Document:

• Decision -- what was agreed
• Rationale -- why this option was chosen
• Actions -- who does what by when
• Review trigger -- when to revisit (a date, milestone, or condition)

If the team cannot reach agreement, escalate to Level 3.

After resolution

• Follow up in the next retro. Ask whether the resolution is working. If not, reopen -- don't let it fester.
• Don't relitigate. Once a decision is made with clear rationale, treat it as settled unless new evidence emerges or the review trigger fires.
• Normalize it. Teams that resolve conflict well don't hide it. Share what you learned so the team builds a pattern for handling disagreements.

Common pitfalls

Pitfall	What to do instead
Avoiding the conversation	Name it early -- Level 1 is a 15-minute conversation, not a formal process
Making it personal	Focus on specific behaviors and their impact, not character
Consensus at all costs	Sometimes the right answer is "we disagree, and the decision-maker is making the call"
Relitigating resolved conflicts	Document decisions with rationale and a review trigger. Point back to the record
Skipping to escalation	Start at Level 1. Escalation is a last resort, not a shortcut
Ignoring power dynamics	The facilitator must actively create space for junior voices. Round-robin sharing helps

Try this today

Think of one disagreement on your team that's been simmering. Write down the specific behavior or decision you disagree with -- not the person, not a character judgment. Frame it as "I observed [X], and the impact is [Y]." That sentence is all you need to start a Level 1 conversation.