M05 Deck Outline: Objection Handling

Deck purpose: Develop the skill of decoding the objection beneath the stated objection, and responding with empathy before data. Participants leave with the Objection Decoder and the Tactical Empathy sequence.

01Title

M05: Objection Handling: Decoding the Objection Beneath the Objection

Module title and session framing
Core question: "What is the customer really saying when they say the thing they're saying?"

02Opening Scenario

The CTO Who Asked 12 Questions

CTO asks 12 increasingly detailed technical questions in the architecture review: none about the actual decision
The architect answers each question thoroughly; the CTO remains unconvinced
What was actually happening: the CTO had a failed migration two years ago and was not going to approve until someone named the fear out loud
The technical answers were right, but they were answering the wrong question

Every architect in the room has a version of this. Let one or two share before moving to the framework. The emotional resonance accelerates the learning.

03Concept

The 6 Objection Categories

Cost: "This is too expensive": root concern: budget exposure, CFO visibility, ROI uncertainty
Risk: "What if it fails?": root concern: personal accountability, prior failure, blast radius
Trust: "We've been burned before": root concern: vendor credibility, Microsoft-specific doubt
Technical Doubt: "We're not sure this can handle our scale": root concern: gaps in understanding, undisclosed requirements
Political: "We need to check with a few other people": root concern: missing stakeholder, competing priority, invisible veto
Inertia: "We're not ready for this yet": root concern: change fatigue, uncertainty about the team's ability to execute

6-box grid: one box per category, each with icon (optional), category name, and the "root concern" it is hiding.

04Framework

Framework 1: The Objection Decoder

Three steps: (1) Classify the stated objection into one of the 6 categories, (2) Identify the root concern, (3) Choose the right response type: empathy, data, or option
The first response to any objection is almost never data. It is acknowledgment
"It sounds like the concern here is less about the technology and more about what happens if this doesn't land." This unlocks the real conversation
The Decoder is in M05_Objection_Decoder_Sheet.pdf: use it before customer calls, not after

05Framework

Framework 2: Tactical Empathy (Voss Method)

Tactical Empathy: the deliberate effort to understand and articulate the perspective of the other party, even when you disagree with it
Sequence: Label → Pause → Mirror → Acknowledge → Address
Label: "It sounds like…" / "It seems like…": names the emotion without claiming to understand it
Mirror: Repeat the last 3 words of what was said as a question to create space for the customer to elaborate
Acknowledge: Confirm the concern is legitimate before addressing it: never minimize

5-step sequence flow: Label → Pause → Mirror → Acknowledge → Address. Each step: example phrase in quotation marks.

Practice the Label phrase specifically: "it sounds like" and "it seems like" feel awkward at first. The pause after the label is uncomfortable. Train participants to hold it.

06Framework

Framework 3: FUD Response Patterns

FUD = Fear, Uncertainty, Doubt: specific category of objection, often competitor-driven or prior-experience-driven
Five FUD types: Reliability ("Azure goes down"), Security ("cloud is not secure"), Lock-in ("we'll be trapped"), Product discontinuation ("Microsoft will kill this"), Competitor comparison ("AWS does this better")
FUD responses require: (1) not dismissing the concern, (2) distinguishing the perception from the fact, (3) offering a verifiable reference, not just a Microsoft assertion
The worst FUD response: "That's not true." The best FUD response: "That's a real concern: here's how customers in your situation have navigated it."

07Framework

Framework 4: The Objection Pre-Mortem

Before entering a high-stakes meeting: identify the 3 most likely objections and prepare for each
For each: classify (which of the 6 categories?), identify root concern, prepare first response (empathy phrase), prepare data or option as backup
The Pre-Mortem prevents the most common mistake: handling objections off the top of your head
"What are the three objections I am most hoping not to hear tomorrow?": prepare exactly those

08Exercise

Objection Hot Seat: Live Decoding

One participant plays a skeptical CTO (character brief from M05_Sample_Objections_Bank.pdf)
One participant responds in real time and must use the Tactical Empathy sequence before introducing any data
Observers note, which category is the objection? Did the responder label before defending? What was the root concern?
Debrief: what did the labeling unlock that data alone would not have?

09Exercise

The Pre-Mortem: For a Real Engagement

Each participant: identify a current or upcoming engagement with a likely objection
Complete the Pre-Mortem: 3 objections, classification, root concern, empathy phrase, data/option backup
Pair share: exchange Pre-Mortems and challenge each other's root concern diagnosis
"Is that really the root concern, or is that the stated version?" The peer challenge is the exercise

10Close

Application: Before the Next Objection

Run the Pre-Mortem before every customer meeting where an objection is likely
Practice the Label phrase: out loud, before the meeting until it sounds natural
After the next objection: identify which category it was; was your root concern diagnosis correct?
Use M05_Objection_Decoder_Sheet.pdf as a pre-call preparation tool, not a post-mortem

Module 05: Objection Handling & Tactical Empathy