Module 3: Conflict Resolution & Negotiation

The most important negotiation book ever written is Getting to Yes by Roger Fisher and William Ury. Its core principle applies to every PM conversation: separate positions from interests. A position is what someone says they want. An interest is why they want it. When two positions conflict, there is often a solution that satisfies both underlying interests.

How to uncover interests in practice:

• Ask “why” but gently. Not “Why do you want that?” (feels combative) but “Help me understand what outcome you are trying to achieve” (feels collaborative).
• Ask “what happens if we do not do this?” The answer reveals the real stakes. If the answer is “We lose a $2M contract,” you are dealing with a high-stakes interest. If the answer is “It would be nice to have,” you are dealing with a preference, not a need.
• Listen for emotional language. When someone says “I promised the board” or “My team has been waiting for this for a year,” you are hearing about personal credibility and team morale, which are interests that might be satisfied in ways other than the specific feature they requested.
• Map multiple stakeholders' interests on the same issue. Often you will find that 80% of the interests align and the conflict is only about the remaining 20%. Focus your negotiation on that 20%.

Scope negotiation is not about saying no. It is about making the cost of yes visible. Most stakeholders are reasonable people who will make good trade-off decisions if you give them the right information. The problem is that PMs often present scope as binary (yes or no) rather than as a spectrum with trade-offs.

Phrases that work in scope negotiations:

• “Absolutely, we can do that. Here is what it would cost in time/resources/trade-offs.”
• “Great idea. Help me understand: is this more important than [existing commitment X]? Because we would need to swap them.”
• “We can build the 80% version in 2 weeks or the full version in 6 weeks. Which serves your needs better right now?”
• “I want to make sure we deliver this well. Can we scope it to [smaller version] for this release and expand it in the next cycle?”

The worst thing you can do is accept scope without acknowledging the impact. Saying “Sure, we will fit it in” when you know it jeopardizes the timeline is not being helpful. It is setting up a bigger, more painful conversation later. Be honest about trade-offs immediately. It is uncomfortable for 5 minutes but saves weeks of pain.

Every PM encounters the stakeholder with unrealistic expectations. They want the full-featured product, on an impossible timeline, with no additional budget. Before you get frustrated, understand something: this person is usually under pressure themselves. Their boss made a commitment. The board set an aggressive target. They are not being unreasonable for fun; they are scared of failing.

The four-step approach to unrealistic expectations:

The HiPPO is the senior leader whose opinion overrides everyone else's, not because they are right, but because they are powerful. A VP who walks into a sprint review and says “Why are not we doing X instead?” can derail weeks of planning in 30 seconds. Managing the HiPPO is one of the most delicate and important skills a PM develops.

First, understand the HiPPO's perspective. They are usually not trying to be disruptive. They have context you might not have (a customer conversation, a board directive, a competitive threat). Their input might actually be valuable. The problem is not the input itself but the way it arrives: unscheduled, without context, overriding a planned process.

One more thing: pick your battles. Not every HiPPO opinion is worth fighting. If the CTO wants the button to be blue instead of green and it does not affect the sprint goal, let it go. Save your credibility for the moments that actually matter, like when they want to add three weeks of scope two days before the release.

Many PMs treat escalation as an admission of failure. It is not. Escalation is a project management tool. Used correctly, it gets decisions made faster, unblocks teams, and prevents small problems from becoming large ones. The failure is not escalating; the failure is escalating too late, too aggressively, or without a recommendation.

Notice what this script does: it gives the decision-maker everything they need in 30 seconds, includes a recommendation so they can just say “approved,” and sets a clear deadline. It does not assign blame, does not dramatize the conflict, and does not make either team look bad.

Not all conflict is overt. Some of the most damaging stakeholder behavior is passive-aggressive: agreeing in meetings but not following through, CC'ing executives on minor issues to create political pressure, providing feedback so late that it forces rework, or being perpetually “too busy” for reviews that their team needs to move forward.

How to handle passive-aggressive patterns:

• Document agreements in writing, immediately. After every meeting with a passive-aggressive stakeholder, send a follow-up email: “Confirming what we agreed: [list]. If I have misunderstood anything, please let me know by [date]. Otherwise, we will proceed on this basis.” This removes the “I never agreed to that” escape route.
• Set explicit deadlines for feedback. Instead of “Please review when you can,” say “I need your feedback by Thursday at noon. If I do not hear from you, I will proceed with the current approach.” This creates a clear accountability mechanism without being confrontational.
• Address patterns, not incidents.One missed deadline is a mistake. Three missed deadlines is a pattern. When you see a pattern, address it privately: “I have noticed that the last three review cycles have been delayed. Is there something about the process that is not working for you? I want to find a way to make this easier.” This approach gives them an opportunity to raise legitimate concerns without feeling attacked.
• Create visibility without blame.If a stakeholder is consistently blocking progress, make it visible in your status updates: “Blocked: Awaiting design review from [team]. Submitted 3/1, current SLA is 48 hours, now at day 8.” The data speaks for itself. You are not accusing anyone; you are reporting facts.

If passive-aggressive behavior persists despite your efforts, it is an escalation trigger. Frame it as a process problem: “Our review process is creating consistent delays. I need help establishing SLAs that the team can commit to.”

Here is a counterintuitive truth: the strongest stakeholder relationships are often forged through conflict, not despite it. When you navigate a difficult negotiation fairly, deliver bad news honestly, and follow through on commitments even when it is hard, you build a reputation that pays dividends for years.

When to push back vs. when to absorb:

The ability to distinguish between these two situations is judgment, and it is built through experience. Early in your career, err toward pushing back because it is easier to relax a boundary than to establish one. As you gain experience, you will develop an intuition for when flexibility serves the project and when it undermines it.

Ultimately, conflict resolution is not about winning. It is about building the conditions where everyone can do their best work. The PM who navigates conflict well does not just deliver the current project. They create an environment where the next project starts with trust already in place, and that is the compound interest of good stakeholder management.