Negotiation Scripts & Role-play Library

Purpose

This library helps teams negotiate trade-offs and secure alignment over resources, timelines, and scope without burning relationships. Use the 3-step prep template before conversations, try short scripts as starting language, and run compact role-play exercises to build confidence.

What's included

• Three-step stakeholder negotiation prep template (BATNA, interests, concessions)
• Short, adaptable scripts for resource requests, timeline trade-offs, and scope negotiations
• Three concise role-play scenarios with objectives, roles, timing, and debrief questions
• Facilitator tips, do/don't checklist, and sample phrases to preserve long-term relationships

How to use this collection

1. Fill the prep template before the meeting (5–10 minutes).
2. Pick and adapt a short script to open the conversation (30–60 seconds).
3. Run a role-play with a peer to practice the ask and concessions (10–20 minutes).
4. Immediately capture commitments and next steps; if useful, record the role-play debrief notes for later improvement.

Three-step Stakeholder Prep Template

Use this quick template to clarify your position.

1. Best realistic outcome (your aim)

   One-sentence statement of the commitment you want (e.g., "An additional two FTE for Q3 to deliver feature X").

2. BATNA & constraints

   What you'll do if you don't get the ask (BATNA), and non-negotiable constraints (deadlines, safety, compliance).

3. Interests, evidence & concessions

   List your core interests (why the ask matters), one or two concrete pieces of evidence (metrics, customer stories), and one concession you can offer (shift scope, phased delivery, shared risk).

Quick Scripts (adapt to tone and context)

Resource request (additional capacity)

Opening: "I'd like to discuss a short-term resource request to keep Program X on track."

Evidence: "Over the last two sprints, velocity dropped 18% due to two long-running support tickets and onboarding work."

Ask: "Can we allocate two dedicated engineers for Q3 to deliver the agreed scope? In return, we can reduce scope for Y and commit to weekly progress updates."

Close: "If that isn't possible, what's the minimum support you can offer that will reduce our risk of a missed delivery?"

Timeline trade-off

Opening: "We need to align on timeline trade-offs so we don't compromise quality."

Frame options: "Option A: keep current scope, move release two weeks. Option B: keep date, reduce scope by these two items."

Ask: "Which option aligns better with your priorities? If we choose B, here's the recommended scope reduction and the impact on users."

Scope negotiation (feature prioritization)

Opening: "I want to ensure we preserve the features that deliver the most customer value while keeping delivery realistic."

Proposal: "Let's agree on a core set for the milestone and park the lower-value items. I can re-scope those as a follow-on backlog if you're comfortable."

Role-play Scenarios (compact)

Run these in pairs with a 10–15 minute cycle: 5–7 minute role-play, 5–8 minute debrief.

1. Scenario: Emergency resource reallocation

   Roles: Project Lead (asker), Engineering Manager (responder).

   Objective for asker: Secure two sprints of dedicated support. Success criteria: Manager proposes at least one viable support option or a clear alternative timeline.

2. Scenario: Timeline vs. quality

   Roles: Delivery Lead (asks to delay), Product Sponsor (pushes for date).

   Objective: Find a compromise that preserves a critical quality requirement. Success criteria: Agreement on a concrete mitigation (partial release, extended validation window, or adjusted acceptance criteria).

3. Scenario: Scope pushback from a stakeholder

   Roles: Feature Owner (asks for added capability), Program Manager (must limit scope).

   Objective: Negotiate a phased approach. Success criteria: Stakeholder accepts phased delivery with a defined promise for the next phase.

Debrief Questions (use after each role-play)

• What worked in the asker's opening? What could be clearer?
• Which evidence or interest statement felt most persuasive?
• Were concessions framed to protect the relationship? Which concession was most effective?
• Did either side escalate quickly? How might they have reduced tension?
• What is one small change to try in the next run?

Facilitator Tips

• Keep role-plays short and focused—clarity beats theatricality.
• Rotate roles so people practice both asking and responding.
• Timebox each debrief and capture one concrete action to test in a real meeting.
• Encourage simple, evidence-based language and explicit trade-offs rather than vague appeals.

Do / Don't Quick Guide

Do: Lead with shared outcomes, use evidence, offer realistic concessions, ask clarifying questions, confirm next steps.

Don't: Threaten, make absolute ultimatums, hide constraints, or make one-off promises you can't keep.

Sample Relationship-preserving Phrases

• "I know you're balancing many priorities—how can we make this easier for your team?"
• "If we can't get full support, what's the smallest commitment that still reduces our risk?"
• "What would make this acceptable to you?"
• "We can try a phased approach and re-evaluate after the first milestone."

Next steps

Adapt these scripts to your organization's language, run brief role-plays in team huddles, capture one learning per run, and iterate. This collection is designed to be copied and tailored for your team—preserve the intent (protect relationships while negotiating real trade-offs) and make it yours.