Interest-Based Problem Framing: How to Turn Position Fights into Problem-Solving

The release-readiness meeting starts at 2:00 on a Thursday. The engineering lead opens with the defect count and says the build isn't safe to ship. The product manager opens with the customer commitment and says the date isn't moving. For the next forty minutes, two smart people restate their opening lines with increasing precision, and the meeting ends exactly where it began. I've sat in some version of that room for twenty years of product leadership – usually as the one holding the date.

Interest-based problem framing is the way out of that meeting. It means surfacing what each person actually needs – their interests – before arguing over what to do about it – their positions. A position is a preferred solution: "We ship on the 15th." An interest is what's underneath: "I can't walk back a promise to our biggest customer." Positions gridlock, because only one of them can win. Interests open possibilities, because once you understand what someone needs, there's usually more than one way to meet it.

What's the difference between a position and an interest?

A position is a solution someone has already picked, usually alone. An interest is the need, fear, or constraint that made the solution look right to them. "We should do X" is a position. "I need confidence this won't blow up in production" is an interest. The positions-vs-interests distinction comes out of the Harvard Negotiation Project's principled-negotiation work, and it sounds almost too simple to matter until you watch a room full of positions collide.

Deadline versus quality is the classic product-team version, and it belongs to a bigger family. In my map of the 15 types of conflict on product teams, the whole alignment-and-priority cluster – cross-functional fights, priority fights, "everything is P1" – yields to this one skill. Those fights look like arguments about facts. They're almost always collisions between two unexamined solutions.

Why do position fights stalemate?

Position fights stalemate because a position is binary. You adopt it or you reject it, and whoever moves first looks like they lost. The deadline standoff has this structure exactly: the date holds or slips, the defects block or don't, and every argument either side offers is really a restatement of a conclusion they reached before the meeting started.

There's a second mechanism, quieter and more expensive. A position fight runs on missing information. The product manager in my Thursday meeting knows something the engineering lead doesn't – what was promised to the customer, and by whom. The engineering lead knows something the product manager doesn't – which of those defects can eat data. Neither surfaces it, because the meeting's format is debate, and in a debate you don't hand ammunition to the other side. Problem framing reverses the format: seek more information before solutions get addressed at all.

Then there's the quietest failure mode. People watch a few of these standoffs, conclude that disagreement is a meat grinder, and stop raising concerns entirely. That silence carries its own compounding cost, and it's harder to see on a status report than any argument.

Five questions that shift a fight from positions to interests

The reframing move is a question, asked sincerely, before you counter. These are the five we print on a reference card for people who go through our training sessions:

1. "What would that solve for you?"
2. "What's driving that priority?"
3. "What risk are you most concerned about right now?"
4. "What problem does your plan solve?"
5. "What are we giving up with this option?"

All five are the same question wearing different clothes: why is that position important to you? Asking isn't conceding. It isn't even agreeing. It's collecting the information a real solution will need.

Run them against the Thursday meeting. "What's driving the date?" turns out to mean a renewal conversation with the company's largest customer in three weeks. "What risk are you most concerned about right now?" turns out to mean two defects out of the forty – the ones that touch billing data. Suddenly the problem isn't ship on the 15th versus don't. It's how do we walk into that renewal with billing intact? And that problem has answers the original fight didn't: fix the two billing defects and ship the rest behind a flag, stage a scoped build for the renewal account, move the demo instead of the date. Maybe none of those survives contact with reality. But now the table holds options instead of two positions and a scoreboard.

I keep that card in my desk drawer. I made it for workshop participants. I use it on myself more than I'd like to admit.

"Oh, that sounds like new information to me"

Adam, my collaborator on those training sessions, has a favorite phrase for the exact moment a fight starts to turn: "Oh, that sounds like new information to me."

It does more work than it appears to. Saying it out loud marks the disclosure – everyone in the room hears that something just changed. It signals that the speaker is willing to update their thinking, which gives the other side permission to update too, without losing face. And it rewards whoever surfaced the interest, which makes the next disclosure come faster. Position fights punish new information; whoever admits to learning something looks like they're losing ground. Adam's phrase flips the incentive. Learning something becomes the visible, respected move in the room.

Is interest-based problem framing trainable?

Yes – with an honest asterisk about what one session can and can't do. The concepts here (separating positions from interests, asking interest-surfacing questions, holding solutions until the problem is actually framed) are among the most reliably teachable skills in the conflict-training literature. A 2022 longitudinal study by William Baber in Negotiation Journal, drawing on ten years of survey data from business professionals who'd received negotiation training, found that more than 80 percent reported using the trained skills in their work – and 30 percent said the training affected their pay or promotion.

The asterisk is transfer. A 2024 study in BMC Nursing trained 64 head nurses in negotiation skills and watched both knowledge and behavior scores climb after training, then measurably decline during follow-up. That regression pattern repeats across the training-transfer research, and the forgetting-curve numbers behind it are blunt: roughly 70 percent of new knowledge is gone within 24 hours, and up to 90 percent within 30 days, without reinforcement. One line from that literature has stuck with me – training that ignores the stress response produces knowledge that "evaporates during actual negotiations."

So the gradient looks like this. A single day reliably changes what you understand. Weeks of practice change what you do when someone's pushing back hard. Plan for both.

How do you practice interest-based problem solving at work?

Start smaller than feels serious. The skill is a reflex, and reflexes get built in reps, in settings where a fumble costs little.

Pick one recurring meeting where positions tend to pile up and commit to asking one question from the card before you offer a counterargument. One meeting, one question. That's the whole first week.

Watch for the flinch. The moment someone dismisses your idea and you feel yourself heat up is the moment the skill matters most and is hardest to reach. You won't eliminate the reaction. Noticing it – "I'm feeling defensive right now" – opens a small window of choice, and the question fits through that window.

Write the plan down as an if-then. Vague intentions don't survive contact with a tense meeting; specific ones do. "If I notice myself digging in on a solution, I will ask what problem their plan solves." The implementation-intention research we build our sessions around shows that specific if-then plans roughly double transfer rates – from about 30 percent to about 67 – and that sharing the plan with someone raises follow-through from roughly 43 percent to 76. Tell a colleague what you're practicing. Ask them to check in two weeks later.

And if you want reps under genuine pressure without genuine consequences, rehearse where the stakes are fictional. That's the design logic behind running a tabletop RPG training session: the disagreements are real, the deadline pressure is real, and nobody's quarterly review is in the room.

The engineering lead and the product manager in that Thursday meeting were never really fighting about the 15th. The date was a position. Nobody had asked what it was protecting.