Reflacto

ENDE
All reflection methods

Interest-Based Negotiation

Cross-team conflicts usually happen because teams optimize for their own success metrics. This framework reframes the problem as "how do we both win?" instead of "who gets their way?"

  • Cross-team conflicts
  • Competing priorities
  • "How do we both win?"

What is interest-based negotiation?

Interest-based negotiation follows the four principles of the Harvard negotiation method. Instead of bargaining over fixed demands, it separates people from the problem, surfaces each side's interests, and uses shared criteria to explore workable options.

  1. Separate people from the problem

    Address the substantive conflict without treating the people or teams involved as the problem.

  2. Focus on interests, not positions

    Ask which needs, goals, and constraints sit behind each side's stated demands.

  3. Create options for mutual gain

    Generate several possible solutions before judging which ones could serve important interests on both sides.

  4. Agree objective criteria

    Evaluate the options against data, standards, or testable conditions that both sides accept.

Interest-based negotiation in a concrete example

An illustrative conflict between a product team and a platform team over the timing of a new release:

  1. Separate people and problem

    The teams stop calling each other blockers and name the actual tension: a promised launch date versus an unresolved reliability risk.

  2. Clarify interests

    The product team needs to honour a customer commitment; the platform team needs to avoid unstable operations and added pressure on the on-call team.

  3. Create options

    They consider a staged rollout using a feature flag, close monitoring, and a small initial user group.

  4. Agree criteria

    They set thresholds for error rate and response time, plus a clear rollback condition, before expanding the rollout.

The example shows one possible agreement that does not require either side to abandon its core interests. Whether it is workable is tested against the agreed measures.

When this method helps

Use when teams are blocking each other, have competing priorities, or when you need a solution that both teams will actually implement (not just agree to).

Limits and when to pause

Not every conflict has a mutual-gain solution. Protect non-negotiable boundaries, test objective criteria and understand your alternative if no agreement is reached.

Where Reflacto uses this method

Choose the situation you want to reflect on:

Key benefits

  • Can interrupt an "us vs them" dynamic that undermines cross-team collaboration
  • Identifies the real constraints each team faces (not just what they're asking for)
  • Supports solutions that account for both teams' success criteria
  • Can strengthen relationships and make future cross-team work easier

Questions Reflacto asks

Reflacto turns the method into these concrete reflection questions:

  1. 1Which teams are involved in this conflict?
  2. 2What are the main priorities and constraints for each team?
  3. 3Where do their goals align or conflict?
  4. 4How can you frame this as a shared problem to solve?
  5. 5What compromise or mutual benefit is possible?

Common questions about interest-based negotiation

What is a BATNA and why does it matter?

Your BATNA is your best alternative to a negotiated agreement — what you'd do if no deal happens. It sets the line below which walking away beats agreeing. Without knowing it, you negotiate blind and accept terms that leave you worse off than doing nothing. Work it out before the conversation starts, not during.

Is this the same as Getting to Yes?

It's the same core idea, developed by Roger Fisher and William Ury at the Harvard Negotiation Project: separate people from the problem, focus on interests rather than positions, generate options for mutual gain, and use objective criteria. What Reflacto does is turn that into a preparation sequence for a specific workplace conflict rather than a general negotiation theory.

What's the difference between this and a compromise?

A compromise splits a fixed amount — both sides get half and both are half satisfied. Interest-based negotiation first looks for interests that are weighted differently: what matters a lot to one side and costs the other side little? When two teams need genuinely different things, there's a trade available instead of a split.

Does it work when one side has far more power?

Only partly, and it's worth being direct about that. The method doesn't manufacture leverage — whoever has the weaker alternative still has the weaker hand. What it does give you is clarity on what you actually need versus what you were merely asking for, which stops you conceding the wrong things.

Origin and Reflacto's adaptation

Principled negotiation was set out by Roger Fisher and William Ury in Getting to Yes (1981); Bruce Patton, credited as editor of the original edition, is listed as co-author in current printings. All three were members of the Harvard Negotiation Project.

Also known as: principled negotiation, the Harvard negotiation method

What Reflacto changed

Getting to Yes addresses negotiation generally. Reflacto applies its four elements specifically to conflict between two teams inside the same organization, asking about each team’s priorities, where their goals align or conflict, and what mutual-benefit compromise is possible.

Primary sources and further reading

Editorially reviewed by Daniel Schmeiß

Last substantive review: August 23, 2026

Related reflection methods

Compare another method that approaches a similar situation from a different angle.

Compare all methods