The Implication Question
5 min read · 4 principles · apply it by lunch
They named the problem in the first ten minutes. That’s the cheap half.
Take the live deal you most want to win: once the buyer had named their problem, how many more questions did you ask about what that problem leads to — and how many minutes was it before you started describing what you sell instead?
Neil Rackham, whose research you met on Day 39, sorted selling questions into four types in SPIN Selling (1988): situation, problem, implication, need-payoff. The third is the difficult one, and the distinction underneath it carries the book. Rackham separated implied needs from explicit needs. An implied need is a buyer describing a problem: the system’s slow, the handovers are messy, we lose a day a week to it. An explicit need is a buyer stating a want. In small sales, implied needs predict a purchase reasonably well; in large ones they predict almost nothing, because people mention problems they have no intention of paying to solve, all day, for free. What moves a large sale is the buyer converting their own problem into a want, and the implication question is the instrument that does it. It takes a problem they’ve already named and asks about consequences — what that lost day does to the delivery date, what the delivery date does to the renewal, what the renewal does to the number the person opposite you is measured on. Nothing is sold anywhere in that sequence. Day 40 asks whether a number the customer would defend exists at all; this morning is the chain of questions that gets one said out loud — until the problem is large enough in the buyer’s own accounting to displace whatever else the money was for.
The Implication Question is Day 241 of 365.
In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.
$29 a month · cancel any time · 7-day money-back guarantee