For each significant objection you've encountered (or expect), decode it before preparing a response.
From Chris Voss's Never Split the Difference: effective objection handling follows a specific sequence. Skipping steps produces defensiveness.
| Step | Technique | What it sounds like | Your version (for your most important current objection) |
|---|---|---|---|
| 1 | Label: name the emotion behind the objection | "It sounds like you're concerned about…" | |
| 2 | Pause: let the label land. Don't fill the silence. | [silence, 3–5 seconds] | N/A: just pause |
| 3 | Mirror: repeat the last 2–3 words as a question | "…control the cost variable?" [rising intonation] | |
| 4 | Acknowledge: validate without agreeing | "That's a completely reasonable concern given [context]." | |
| 5 | Address: respond to the root concern, not the surface objection | "Here's how we handle that specifically…" |
Before a high-stakes meeting, list every objection you might face. For each, write the response you would give if you were at your best, not the defensive first instinct.
| Anticipated objection | Root concern | Best-version response |
|---|---|---|
| "Cloud costs more." | ||
| "We've tried this before and it didn't work." | ||
| "We're not ready for this level of change." | ||
| "Our data can't leave [geography/system]." | ||
| "We need to do more analysis first." | ||
| [Your specific objection] |
| Behavior | Did I do this? (Yes / Partially / No) |
|---|---|
| I paused before responding to give myself time to decode the objection | |
| I labeled the emotion behind the objection before addressing the content | |
| I responded to the root concern, not just the stated objection | |
| I did not become defensive when challenged | |
| I used evidence or a reference customer when addressing a trust-category objection | |
| I acknowledged when I did not have a complete answer rather than deflecting |