You will be able to describe the four SPIN question types from Neil Rackham's research and write an example of each.
Hafiz has a first meeting with Rachel, the operations manager of a logistics firm in Tuas. He opens well, then asks: how many staff do you have, how many are on shifts, what payroll system do you use, how often do you pay, who processes it, how long have you used the current setup. Rachel answers every question patiently. After fifteen minutes she glances at the clock, and Hafiz has learned nothing he could not have found on the company website or guessed from the industry.
Neil Rackham's research into selling describes this pattern closely. His book, SPIN Selling, sorts discovery questions into four types and shows which ones help in larger sales and which ones wear the buyer out. This lesson takes you through the four types as he describes them, with an example of each from Hafiz's meeting.
Rackham led a research programme that observed real sales calls and compared what successful sellers did with what less successful ones did. It focused on large sales: bigger purchases, several meetings, more than one person deciding. His conclusion was that the questions that work in a quick, one-meeting sale are a poor guide to what works in a large one, and that the types of question a seller asks matter more than their charm or their closing lines.
From that work he named four types of question, and the initials give the method its name: situation, problem, implication and need-payoff. The order is the order they usually appear in a good conversation, though real meetings move back and forth.
A situation question gathers facts about the buyer's current circumstances. "How many people are on your payroll?" "What system do you use for leave?" "How often do you run payroll?"
You need some of these. You cannot discuss a problem without knowing the basic setup. But Rackham found that less successful sellers ask far too many, and buyers find them tedious, because the questions help the seller and give the buyer nothing back. That is what happened to Hafiz in the first fifteen minutes.
The fix is to ask only the situation questions you could not have answered yourself. Headcount, industry, number of sites and recent news are often public or easy to guess, and your preparation from lesson 1.2, Prepare a hypothesis, not a pitch, should cover them. Save the meeting for facts only the buyer knows, such as how the process actually runs day to day.
A problem question asks about difficulties, dissatisfaction or things that are not working. "Which part of payroll causes the most trouble?" "How often do overtime calculations need correcting?" "What do staff complain about?"
Problem questions are where discovery starts to earn its keep, because they show you where the buyer might need help. In Hafiz's meeting, a single problem question changes the tone. "Which part of the monthly payroll gives you the most trouble?" Rachel answers at once: overtime for the drivers and warehouse staff, which is calculated by hand from timesheets and goes wrong most months.
Rackham's point is that finding a problem is not the same as finding one the buyer will pay to solve. Rachel has tolerated the overtime trouble for two years. Something has to make it feel bigger than it does right now.
An implication question asks about the consequences of a problem: what it leads to, what else it affects, what it costs. "When an overtime figure is wrong, what happens next?" "How does that affect the drivers?" "What does fixing it take each month, and whose time is that?"
These are the questions that make a problem feel larger, because they let the buyer trace its effects out loud. Rachel had thought of overtime errors as an admin annoyance. Under Hafiz's implication questions she describes the corrections that take her payroll clerk most of two days, drivers who check every payslip because they no longer trust them, and one experienced driver who left last quarter and mentioned pay errors as part of the reason.
Rackham found implication questions were the ones most closely linked to success in large sales, and also the ones sellers find hardest to ask. They need you to stay on a problem and go down into it, which is the layering habit from lesson 2.1, Open, layered and follow-up questions. Implication questions are layered questions aimed at consequences.
A need-payoff question asks the buyer to describe the value of solving the problem, in their own words. "If overtime was calculated correctly from the timesheets, what would that change for you?" "How would it help if your clerk had those two days back?"
The point is who does the explaining. When you describe the benefits, the buyer weighs them with suspicion. When the buyer describes them, they are persuading themselves, and they will often repeat the same words to their boss. Rachel says, "Honestly, if the drivers stopped arguing about their pay, I'd get my Mondays back, and we might keep people longer." Hafiz could never have made that case as well.
Hafiz's second attempt at the meeting runs very differently. He asks two situation questions he could not have researched, then a problem question, then four or five implication questions on the overtime problem alone, and finally a need-payoff question. The meeting takes the same forty minutes, and at the end Rachel is the one asking what happens next.
Situation questions should be few. Problem questions open the door. Implication questions do the heavy lifting. Need-payoff questions let the buyer name the value.
Think of your most common buyer, the person you meet most often, and keep them in mind as you start the activity below.
Write two questions of each SPIN type for your main buyer persona, and mark the situation questions you could answer through research instead.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).