# Objection Source Causal Map

This reference supplements the `objection-source-diagnoser` skill. It provides the full behavior→response chain with research evidence, the annotated Dallas word-processor dialogue, and the Japanese-recruit case study.

---

## The FAB→Customer Response Chain

Derived from Linda Marsh's correlation studies (cited in SPIN Selling, Chapter 6), which analyzed statistically significant links between seller FAB behaviors and customer response patterns across thousands of sales calls.

| Seller Behavior | Most Probable Customer Response | Why |
|---|---|---|
| **Feature** (describing product characteristics without linking to value) | Price concern ("It's expensive," "Is it worth the cost?") | Features increase price sensitivity. For low-cost products this is advantageous — the customer expects a high price, then the low price is pleasant. For expensive products, Feature-heavy selling amplifies cost scrutiny before value has been established. |
| **Advantage** (showing how product can help, without a prior Explicit Need) | Objection — value doubt ("We don't need that," "Not worth the trouble," "We're fine with what we have") | The customer evaluates the Advantage against an undeveloped problem. In large sales, the solution cost typically exceeds the perceived urgency of an undeveloped problem. The customer raises a "not worth it" objection because the seller has not invested sufficient time in building the problem's importance through Implication Questions. |
| **Benefit** (showing how product meets a customer-expressed Explicit Need) | Support / approval ("Yes, that's exactly what we need," "That would solve our problem") | Benefits, by definition, meet something the customer already wants. Approval follows naturally. |
| **Premature solution presentation** (mentioning product capabilities in the first third of the call, before need development) | Early-call objection — budget lock, "not in the market," deflection | The customer has not been led to feel the problem's importance, so any solution appears unnecessary. Early resistance is generated by missequencing, not by the product. |

---

## Research Backing

### Linda Marsh Correlation Studies
Rackham's colleague Linda Marsh carried out correlation studies mapping statistically significant links between each FAB behavior type and customer responses. Key findings:
- Features → price concerns (significant positive correlation)
- Advantages → objections (most probable customer response to Advantages is an objection)
- Benefits → support/approval (significant positive correlation)

### The 55% Objection Reduction Experiment
In a division of a high-tech corporation, Huthwaite identified 8 salespeople who each received unusually high numbers of objections per selling hour. Behavior analysis showed all 8 were high in Advantage use. An objection-prevention training program was designed that:
- Did not mention the word "objection" or any objection-handling technique
- Taught SPIN questioning to develop Explicit Needs
- Taught offering Benefits only after Explicit Needs were expressed

Post-training measurement: average objections per selling hour fell by 55%.

Conclusion: More than half of objections in a typical sales team are seller-caused and preventable through sequencing change. The remaining objections represent true product/competitor gaps.

### Japanese-Recruit Price Objection Case
A major U.S.-based multinational corporation faced competition from lower-cost Japanese machines and attempted to recruit top salespeople from the Japanese competitor. These recruits had strong track records selling Feature-rich, lower-priced machines.

Outcome: The recruits received 30% MORE price objections than the existing sales force selling the identical product to the same customers.

Root cause: The recruits' selling style was trained on Feature-rich machines where Features worked in their favor (lower price + Feature list = positive purchase). Transferred to a premium-priced product, the same Feature-heavy style amplified price sensitivity without having built value through need development. The Features primed customers to scrutinize cost just when they needed to feel the value.

Remedy: Retrain in SPIN questioning and Benefits-first selling. Result: sales increased, price objections fell.

Key lesson: Price objections are not caused by price. They are caused by Feature overuse before value development.

---

## The Dallas Word-Processor Dialogue (Annotated)

Recorded September 1981. Seller attempting to sell word processors to a Dallas office manager. Edited for length; behavior labels added.

```
SELLER: [Problem Question] Does all this retyping waste time?
BUYER: [Implied Need] Yeah, some. But there's not so much of it here, not like in Fort Worth.

SELLER: [Advantage — jumps to solution before building need importance]
  "Here's where our word processors would be a real big help because they'd eliminate
   that retyping for you."
BUYER: [Objection — value doubt]
  "Look, we retype stuff, sure. But you won't get me paying for fancy $15,000 machines
   just to cut down on some retyping."

SELLER: [Advantage — tries to counter with another capability claim]
  "I understand you, but the labor costs of retyping can climb out of sight. A big plus
   of word processors is that they save you money by making your people more efficient."
BUYER: [Objection — value doubt + capability resistance]
  "We're very efficient right now — and if I wanted to do better on efficiency I can
   think of 16 ways without new word processors."

[Pattern continues: each Advantage → each objection]
```

**What went wrong:** The seller heard an Implied Need ("some retyping") and immediately presented an Advantage ("would be a real big help"). The customer had not developed the problem — had not articulated how much it cost, what consequences it had, or what the business impact was. The Advantage was evaluated against an undeveloped problem and found not worth $15,000.

**The prevention path (shown in Chapter 6):** On the final exchange in the dialogue, Rackham shows an alternative sequence. The seller uses Implication Questions to develop the error-rate problem into: proofreading time (2 hours/day), bottlenecking the team, preventing training, risk of sending errors to clients, retyping costs. Only after the customer says "When you put it that way, those mistakes are really hurting us" does the seller present the capability — now as a Benefit meeting an expressed Explicit Need. No objection arises.

---

## Two Signs You Are Getting Preventable Objections

From Rackham's summary guidance (Chapter 6):

1. **Objections early in the call.** Customers rarely object to questions. If objections are arising in the first half of a call, the seller is presenting solutions too soon — before questions have developed the need's importance. Cure: no solution mentions until thorough need development.

2. **Objections about value.** "It's too expensive," "not worth the trouble," "happy with our existing system" — these are value objections indicating needs have not been developed strongly enough. Cure: more Implication and Need-payoff Questions, not better objection-handling scripts. Specifically, cut Feature use and replace with Problem, Implication, and Need-payoff Questions.

---

## Objection Types Reference

| Objection Type | Language Pattern | Most Probable FAB Source |
|---|---|---|
| Price concern | "Too expensive," "Can't justify the cost," "Budget is tight," "Is there a cheaper version?" | Feature overuse |
| Value doubt | "Not worth the trouble," "Don't see enough value," "Happy with what we have," "Marginal improvement" | Advantage before Explicit Need |
| Capability doubt | "My people won't use it," "Wouldn't work in our environment," "Too complex" | Advantage on an undeveloped need (fit hasn't been established) |
| Early-call resistance | "Not in the market right now," "Budget is locked," "Send me something to review" | Premature solution presentation (opening benefit/Advantage statement) |
| True objection | "Our current vendor has a contract," "You don't have [feature] that we specifically need" | Genuine product/competitor gap — cannot be prevented, requires acknowledgment |