negotiation is a constant, not an event

PMs negotiate far more often than the word "negotiation" suggests: trading off scope with a stakeholder, securing a resource commitment from a functional manager, agreeing vendor terms, adjusting a deadline or budget, resolving a disagreement inside the team. It's closely related to influencing without authority, but negotiation specifically deals with situations where two sides want different, seemingly incompatible things.

positions vs. interests

The central insight from principled negotiation (from the Harvard Negotiation Project's Getting to Yes) is the difference between a position — what someone is demanding — and an interest — what they actually need underneath that demand. Negotiating over positions tends to produce a standoff, because positions are often drawn as opposites ("I need it by Friday" vs. "we can't deliver until next month"). Digging into the interests behind each position — why Friday, why not sooner — often reveals a solution neither side saw while arguing about the position itself.

batna: your best alternative

BATNA — Best Alternative To a Negotiated Agreement — is what you'd do if this negotiation fails entirely. Knowing it clearly before a negotiation starts does two things: it strengthens your position (a strong BATNA means you're not desperate for this deal), and it tells you exactly when to walk away versus when even a mediocre deal beats no deal at all. This applies directly to vendor negotiations, but just as much to internal asks — negotiating for more headcount or more time.

the four elements of principled negotiation

  • Separate people from the problem — keep personal friction out of the substance of the disagreement (the same task-vs-relationship-conflict distinction covered in leadership & team dynamics).
  • Focus on interests, not positions — ask "why" behind a stated demand before accepting it as fixed.
  • Generate options for mutual gain — brainstorm possibilities before either side commits to a single answer.
  • Use objective criteria — when interests genuinely conflict, decide using an agreed external standard (market rate, industry benchmark, a rule set in advance) rather than whoever pushes hardest.

persuasion in the moment

Beyond the negotiation structure itself, a few tactical things matter: anchoring — whoever states a number first tends to shape the range the rest of the conversation happens in, which is worth being deliberate about in scope or budget discussions. A well-reasoned written proposal often lands better than the same argument made verbally, because it can be reviewed calmly rather than reacted to in the moment. And timing matters — asking for something in the middle of an unrelated crisis rarely gets a fair hearing, however reasonable the ask.

a short example

Two teams both need the same specialized QA engineer for overlapping two-week stretches. Arguing over the position — "we asked first" vs. "we need them first" — goes nowhere. Digging into interests reveals the other team has a hard external compliance deadline, while this team's own deadline is soft and could slip a few days. The PM agrees to give priority now, in exchange for guaranteed priority the next time a similar conflict comes up — and both sides adopt an objective standing rule going forward: whichever project has the harder external deadline gets priority, so the next conflict doesn't need to be relitigated from scratch.

practical notes

Going into a negotiation without a clear BATNA is negotiating from weakness, even when it doesn't feel that way in the moment.
Positional bargaining tends to escalate every future disagreement into another fight, because nothing about the underlying interests ever actually got resolved — just the immediate demand. Identifying real interests, even when it takes longer up front, tends to actually settle things.

related topics

reference