negotiation
This negotiation skill applies tactical empathy and calibrated questioning techniques from FBI hostage negotiator Chris Voss to help users prepare for and execute high-stakes conversations. Use it when facing salary negotiations, contract disputes, vendor talks, pricing disagreements, or difficult conversations where understanding emotional drivers and building rapport matters more than logic alone. The framework covers accusation audits, Black Swan discovery, and the "That's Right" technique to uncover hidden information and reach mutually beneficial outcomes.
git clone --depth 1 https://github.com/wondelai/skills /tmp/negotiation && cp -r /tmp/negotiation/negotiation ~/.claude/skills/negotiationSKILL.md
# Negotiation
Tactical empathy-based negotiation framework from FBI hostage negotiator Chris Voss. Understand the emotional drivers behind decisions and use proven techniques to build rapport, uncover hidden information, and reach better outcomes.
## Core Principle
**People want to be understood and feel safe.** The most effective path to "yes" runs through empathy, active listening, and emotional intelligence -- not logic, arguments, or compromise. Treat every negotiation as a discovery process: your assumptions are hypotheses to test, and the other side's needs (respect, security, autonomy) matter more than their stated positions. Never split the difference -- no deal is better than a bad deal.
## Scoring
**Goal: 10/10.** Score 1 point per satisfied Quick Diagnostic row (6 rows), plus up to 4 points for execution quality: emotions labeled out loud (+1), "That's right" earned not "You're right" (+1), no "Why?" / no splitting the difference / no chasing "yes" (+1), at least one Black Swan surfaced (+1). Bands: **9-10** = audit delivered, calibrated questions and BATNA prepared, "That's right" achieved, Black Swans hunted; **5-6** = some prep but arguing the position or chasing "yes"; **<=3** = no audit, no BATNA, splitting the difference. Always state the current score and the specific gaps to reach 10/10.
## Framework
### 1. Tactical Empathy
**Core concept:** Consciously imagine yourself in the counterpart's situation, then vocalize their perspective to create trust and openness.
**Why it works:** When people feel understood, brain chemistry shifts toward trust and cooperation, short-circuiting defensive reactions. Empathy is not agreement -- you can understand their position while advocating your own.
**Key insights:**
- Before responding, ask: "What is their world like right now?"
- Articulate their situation, pressures, and fears before stating your position
- Empathy must be genuine, not performed -- people detect fakeness instantly
- Unconditional positive regard: respect them as a person regardless of disagreement
- Emotions are contagious -- stay calm and positive; slow pace enables clear thinking
**Product applications:**
| Context | Application | Example |
|---------|-------------|---------|
| **Customer support** | Acknowledge frustration before solving | "I understand this outage is affecting your team's deadline" |
| **Sales calls** | Voice the prospect's pressures | "It sounds like you're under pressure to show results this quarter" |
| **Pricing conversations** | Acknowledge budget constraints upfront | "I know adding another tool to the stack feels risky right now" |
**Copy patterns:**
- "I understand you're dealing with..."
- "It seems like this is creating pressure for your team..."
- "Before we talk about next steps, I want to make sure I understand where you're coming from..."
See [references/techniques.md](references/techniques.md) for the full 21-technique reference -- each section below points to the part you need at the moment you need it. Open it now for The Power of Apology and Pause, which has no section here.
### 2. Mirroring
**Core concept:** Repeat the last 1-3 critical words your counterpart said, with a curious, upward-inflecting tone, then go silent.
**Why it works:** Mirroring signals deep listening, creating familiarity and rapport. It prompts elaboration without direct questions, revealing more than the counterpart intended to share.
**Key insights:**
- Repeat the key or emotion-laden words back as a gentle question
- Wait silently (4+ seconds) for them to expand
- Works in person, on the phone, and in written communication
- The simplest technique, but often the most effective for information gathering
**Product applications:**
| Context | Application | Example |
|---------|-------------|---------|
| **Discovery calls** | Mirror key concerns to get elaboration | Client: "The timeline is tight." You: "The timeline is tight?" |
| **User interviews** | Encourage deeper explanation of pain | User: "It's just frustrating." You: "Frustrating?" |
| **Objection handling** | Reflect to find the root cause | "Doesn't fit your budget?" |
**Copy patterns:**
- "[Key phrase they used]?" (with question mark)
- "You mentioned [their exact words]..."
- "When you say [mirror], what does that look like?"
### 3. Labeling
**Core concept:** Identify and verbalize the counterpart's emotions or perspective using neutral phrases: "It seems like...", "It sounds like...", "It looks like..."
**Why it works:** Naming emotions validates them -- labeling negative emotions diffuses their power, labeling positive emotions reinforces them. The tentative phrasing gives room to correct you, which deepens the conversation either way.
**Key insights:**
- Always use third-person phrasing ("It seems like..."), never "I think you..."
- After labeling, be silent -- let them respond
- A wrong label still pays: their correction is valuable information
- Watch for emotional shifts that signal you've hit the mark
**Product applications:**
| Context | Application | Example |
|---------|-------------|---------|
| **Customer complaints** | Name the frustration before solving | "It sounds like you feel let down by our response time" |
| **Sales objections** | Label the underlying concern | "It seems like there's a concern about implementation risk" |
| **Churn prevention** | Identify the real reason for leaving | "It sounds like something changed since you first signed up" |
**Copy patterns:**
- "It seems like..."
- "It sounds like you're feeling..."
- "If I'm reading this right, it feels like..."
### 4. Calibrated Questions
**Core concept:** Open-ended "How...?" and "What...?" questions that shape the conversation while giving the counterpart the illusion of control.
**Why it works:** Calibrated questions engage the counterpart's problem-solving mind, making them feel in charge while you steer. They force the other side to consider your position without you stating itBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.
Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "referral program", "nobody is sharing it", or "make this spread". Also trigger when designing shareable features, crafting social campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.
Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.
Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "conversion funnel", "increase signups", or "people add to cart but dont buy". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.