T08: Negotiate | Domain 1 | PMP Study Guide

📖 Lý thuyết / Theory

🇺🇸 English

Principled Negotiation (Fisher & Ury — "Getting to Yes") is the PMI-preferred negotiation framework. It focuses on interests, not positions, and seeks mutual gain.

4 principles of principled negotiation:

Separate people from the problem: Attack the issue, not the person
Focus on interests, not positions: Ask "Why?" not just "What?"
Invent options for mutual gain: Brainstorm before committing
Use objective criteria: Market rates, standards, precedents

BATNA (Best Alternative to a Negotiated Agreement) — know your walk-away point before negotiating.

Reference: Harvard PON — Principled Negotiation

🇻🇳 Tiếng Việt

Đàm phán theo nguyên tắc (Fisher & Ury — "Getting to Yes") là framework đàm phán PMI ưu tiên. Tập trung vào lợi ích, không phải lập trường, và tìm kiếm lợi ích chung.

4 nguyên tắc của đàm phán theo nguyên tắc:

Tách người ra khỏi vấn đề: Tấn công vấn đề, không phải người
Tập trung vào lợi ích, không phải lập trường: Hỏi "Tại sao?" không chỉ "Cái gì?"
Tạo ra các lựa chọn cho lợi ích chung: Brainstorm trước khi cam kết
Sử dụng tiêu chí khách quan: Giá thị trường, tiêu chuẩn, tiền lệ

BATNA — Biết điểm bỏ cuộc của bạn trước khi đàm phán.

🔧 Negotiation Preparation Template

Negotiation Prep Sheet

NEGOTIATION: API SLA with Bank Partner A DATE: 2026-06-01 PARTICIPANTS: PM, CTO vs Partner Tech Lead, Account Manager ── OUR INTERESTS (not positions) ─────────────────── • API uptime ≥99.5% to ensure our platform reliability • Response time ≤500ms for good user experience • Clear error codes for debugging • Sandbox environment for testing before production ── THEIR LIKELY INTERESTS ─────────────────────────── • Limit liability in SLA • Realistic maintenance windows • Not be called at 2am for every outage • Commercial relationship continuation ── OUR TARGET ─────────────────────────────────────── Best case: 99.9% uptime, 200ms, dedicated support line Acceptable: 99.5% uptime, 500ms, email support BATNA: Use fallback to alternative partner or build resilience ourselves ── OBJECTIVE CRITERIA ─────────────────────────────── • Industry standard banking API SLA: 99.5-99.9% • Comparable partner agreements we have with others • Our contractual obligations to end users

💼 Thực chiến / Scenario

🏢

FinTech Company X — Negotiating API SLA with Bank Partner

Tình huống: Trước khi go-live Project Alpha với Bank Partner A, cần negotiate SLA agreement. Partner muốn 99% uptime SLA (8.7 hours downtime/month). PM/CTO muốn 99.9% (52 phút/tháng) vì platform lending cần high availability.

Principled negotiation approach:

Tách người ra khỏi vấn đề: "Chúng ta đều muốn partnership thành công. Vấn đề là SLA levels — hãy tìm solution thoả mãn cả hai."

Focus on interests: Hỏi partner: "Tại sao 99% là giới hạn?" → Họ lo về maintenance windows và on-call costs. Không phải họ không muốn reliable service — họ sợ commitment quá cao.

Options for mutual gain: Propose tiered SLA: 99.9% for business hours, 99% for off-peak. Agree on maintenance windows (Sundays 2-6am). Auto-notification when downtime planned. Penalty structure đơn giản.

Kết quả: Agreement đạt được: 99.5% overall, 99.9% business hours. Cả hai sides có win. Đây là principled negotiation trong action.

✏️ Practice Questions

Question 1

During contract negotiation with a vendor, both parties are stuck on price. The vendor won't go below $100K, and your budget is $80K. According to principled negotiation, what should you do FIRST?

A. Walk away from the negotiation
B. Explore each party's interests to understand why these positions exist, and look for creative options
C. Split the difference and agree on $90K
D. Bring in a mediator to resolve the deadlock

✅ Answer: B — Principled negotiation says: focus on interests, not positions. Explore WHY the vendor needs $100K (cash flow? cost structure?) and WHY $80K is your limit (budget cap? other constraints?). Creative options might emerge: phased payments, reduced scope for $80K, performance-based bonuses, etc. Splitting the difference (C) is compromise not principled negotiation. Walking away (A) should come after options are exhausted.

Question 2

During a negotiation with a vendor, the vendor refuses to budge on price but offers better support terms. According to principled negotiation, what should the PM consider?

A. Walk away since price is fixed
B. Explore whether the support terms represent value equivalent to the price gap (focus on interests, not positions)
C. Accept the higher price since the vendor is being firm
D. Bring in legal to enforce the original price

✅ Answer: B — Fisher & Ury: focus on interests (value) not positions (price). The vendor's "better support terms" may represent real value — e.g., reduced operational cost, faster issue resolution, or risk reduction — that closes the gap between the $price positions. A PM applying principled negotiation looks beyond the stated position to the underlying interest and evaluates the total value of the package.

Question 3

A PM is negotiating resource allocation with a functional manager. The functional manager insists they cannot release their developer for more than 2 days per week. The PM needs 4 days. What is the BEST first step?

A. Escalate to the sponsor to force the manager to comply
B. Identify the functional manager's underlying interests (why only 2 days?) and explore options that satisfy both
C. Accept 2 days and adjust the project schedule
D. Find an external contractor immediately

✅ Answer: B — Understand interests first before escalating or accepting. The functional manager's "2 days" is a position — their interest may be: protecting a key resource for another critical deliverable, concern about context-switching, or BAU commitments. By exploring the "why," the PM may uncover options: staggered allocation, role split, time-boxing the high-need weeks, or solving the functional manager's other constraint. Escalating immediately (A) damages the relationship and may not be needed.

🤖 AI Tools for PMs

🤖

How AI Augments This Process

AI helps PMs prepare negotiation strategies, analyze BATNA positions, draft proposals, and simulate counterpart responses before entering high-stakes conversations.

Sample Claude Prompts

Negotiation preparation — BATNA analysis I'm preparing to negotiate [what — contract / resources / timeline / budget / scope]. My position: [what I want] My BATNA (Best Alternative To Negotiated Agreement): [what I do if negotiation fails] Their likely position: [what the other party wants] Their likely BATNA: [what they do if this fails — my estimate] Zone of Possible Agreement: [where I think overlap exists] Constraints I can't move on: [hard limits] Help me: 1. Map the negotiation zone (ZOPA analysis) 2. Identify 3 tradeable variables (things I can give to get what I need most) 3. Develop my opening position and first concession plan 4. Anticipate their top 3 objections and prepare responses 5. Define my walk-away point and how I'll communicate it without burning the relationship

Vendor/contractor negotiation I'm negotiating a contract with [vendor / contractor type]. Deliverable: [what they'll deliver] My budget: [range — don't reveal exact number to them] Their quoted price: [their opening offer] Market rate (if known): [benchmark] Timeline flexibility: [fixed / flexible] Quality requirements: [non-negotiables] Relationship: [new vendor / existing partner] Draft a negotiation strategy including: 1. Counter-offer with justification (market data, scope adjustments) 2. 3 creative value exchanges (not just price reduction) 3. Contract terms I should push for (payment milestone, IP, SLA) 4. Red flags to watch for in their response 5. Script for the opening 2 minutes of the negotiation call

Internal resource negotiation I need to negotiate for [team members / budget / timeline extension] with [functional manager / sponsor / PMO]. What I need: [specific resource request] Business justification: [why the project needs this] Their likely concerns: [budget / other priorities / precedent] What I can offer in return: [flexibility, reporting, phasing] My leverage: [project priority, sponsor support, risk of not having it] Help me build a persuasion case with: 1. Data-driven justification (ROI or risk cost of not approving) 2. Options I can present (full ask / scaled ask / alternative) 3. Pre-wiring strategy (who to talk to before the formal ask) 4. The one-page proposal I'd send ahead of the meeting

Jira / Confluence Template

Confluence — Negotiation Preparation Brief

── CONFLUENCE: NEGOTIATION PREP BRIEF ─────────────────── Negotiation: [Topic / deal] Date: [YYYY-MM-DD] Counterpart: [Name / org] | Relationship: [new / ongoing] PM Lead: [Name] ── POSITION MAPPING ────────────────────────────────────── My ideal outcome: [best case] My walk-away point: [minimum acceptable] My BATNA: [what I do if no deal] Their likely ask: [estimate their position] Their likely BATNA: [estimate their alternative] ZOPA estimate: [where deal is possible] ── TRADEABLE VARIABLES ─────────────────────────────────── High value to me / Low cost to give: [list] High value to them / Low cost to me: [list — offer these] Hard limits (non-negotiable): [list] ── OUTCOME ─────────────────────────────────────────────── Agreed terms: [summary] | Next steps: [owner + date]

Negotiate Project Agreements