You will be able to tell a surface complaint from the root problem that would make a buyer act.
A buyer sits down and tells you what is wrong within the first five minutes. "Our staff keep making mistakes." "The kids' savings are all over the place." "Month end is a nightmare." It feels like a gift. You have a product that fixes exactly that, so you start explaining how.
Then the meeting ends with "let me think about it," and you never hear back. The buyer was telling the truth about the mistakes. They just were not going to pay to fix them, because the mistakes were not the real problem. They were a symptom of it.
This lesson is about telling the two apart, and about the questions that take you from one to the other.
A symptom is the part of a problem the buyer notices first: the visible annoyance, the thing that goes wrong. A root problem is the cause underneath, and its consequence, the thing that actually costs the buyer money, time or reputation.
Buyers mention symptoms first because symptoms are what they see every day. That does not make them wrong, and you should not dismiss them. But a symptom on its own rarely moves anyone to spend money. Joel, the cafe owner from module 1, has put up with staff miscounting the till for over a year. He grumbles about it, he has had a word with the staff, and he has not done anything else.
Buyers act on root problems. They tolerate symptoms for years.
To get from a symptom to a root problem, ask about two directions in turn: what causes it, and what happens as a result. Keep going until you reach something that costs money, time or reputation.
This is the layering habit from lesson 2.1, Open, layered and follow-up questions, aimed at a particular target. Here is how Priya, the bookkeeper from module 1, works through Joel's complaint.
Joel: "My staff keep making mistakes with the cash count."
Priya: "What do you think causes the mistakes?"
Joel: "The two cafes close up differently. The new one never got a proper closing checklist."
Priya: "And when the count is wrong, what happens?"
Joel: "I end up with a gap between the till and the sales report most weeks. Small amounts, usually."
Priya: "What does that gap lead to?"
Joel: "Honestly, I can't tell if it's mistakes or if someone's taking money. And my accountant said if the records stay like this, she can't sign off the year without a lot more work, which she'll charge me for."
Four questions in, the problem has changed shape. The symptom was staff miscounting. The root problem is that Joel cannot trust his own numbers, cannot tell error from theft, and faces a bigger accountancy bill. That is something he will pay to fix.
Notice that Priya did not suggest any of it. Each step came from Joel. If she had said "so you might have a theft problem," he would likely have bristled. When he reaches it himself, he owns it.
One effect of tracing problems down often surprises sellers. The root problem is often owned by a different person than the surface complaint.
In Hafiz's meeting with Rachel, from module 3, the surface complaint was overtime errors on payslips. That belongs to the payroll clerk, who fixes them, and to Rachel, who hears the complaints. As Hafiz traced it down, the root turned out to be driver retention: experienced drivers losing trust and, in at least one case, leaving. Retention belongs to the director, who worries about delivery capacity and the cost of hiring.
This matters for two reasons. First, the person who owns the root problem usually has more authority to spend money on it. Second, if you only ever talk to the person with the symptom, your proposal will be judged by someone who has not felt the real cost. Lesson 5.4, Map who decides and how, picks up this thread. For now, when you find a root problem, ask, "Who else feels this?" and write down the name.
You have reached a root problem when the answer is something the buyer would spend money or time to get rid of. A practical test: could you write the problem in one sentence that includes a cost? "Joel can't tell mistakes from theft, and his year-end accountancy will cost more" passes. "Joel's staff make mistakes" does not.
Some symptoms have more than one root. The cash count problem might also trace to staff turnover at the second cafe, which has its own costs. When that happens, note both and ask the buyer which one matters more to them. Do not choose for them.
And sometimes you trace a symptom down and find nothing much underneath. The mistakes are small, rare and cheap to fix. That is useful too. Sales foundations lesson 1.3, Why no decision beats every competitor, explains why a buyer who loses little from a problem usually chooses to do nothing about it.
Most sellers hear the same three or four surface complaints over and over. Payroll is slow. The money is messy. Staff make mistakes. The kids' education fund is behind. Because they repeat, you can prepare the questions that trace each one down, the same way you prepared follow-ups for your question bank in lesson 2.4, Build your discovery question bank.
For each complaint, you want a cause question, a result question, and at least one more layer that reaches money, time or reputation.
Think about the complaints you hear most often in the first five minutes of your meetings, and write down three of them before you start the activity below.
Take three surface complaints you often hear and write the questions that would trace each one down to a root problem.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).