Symptom, Impact, Root Cause: The Three Layers of 'Pain' Most Reps Never Get Past Layer One
'What's the pain?' is the wrong question. Here's what actually separates reps who surface root cause from reps who stop at the symptom.
Ask a rep what pain they found on a call and you'll usually get one sentence back: "their reporting takes too long." That goes in the CRM, the call moves to budget, and everyone calls it discovery. It isn't discovery. It's the first of three layers, and it's the layer that changes nothing — because "reporting takes too long" isn't a reason anyone signs a purchase order.
Pain is three layers, not one
Symptom is what the buyer notices day to day — the thing that's annoying enough to mention. Business impact is what the symptom actually costs, in money, time or risk, once you follow it downstream. Root cause is why the problem exists in the first place, and why nobody's fixed it yet. Most discovery calls stop at layer one and call it a day.
Here's the same problem run through all three layers:
- Symptom: "Our month-end close reports take four days to pull together across three systems."
- Business impact: "That means we miss the freight-booking window for the following month, so we pay for expedited shipping — roughly £18,000 a quarter, based on the last three quarters."
- Root cause: "Finance, ops and the warehouse each run their own system. Nobody owns a shared data layer. The last attempt to fix this died in an IT backlog eight months ago, because it wasn't formally anyone's job to push it through."
Only one of those three sentences justifies a budget conversation. Only one of them tells you whether this is actually fixable, or whether you're about to become the second attempt that dies in the same backlog.
The three layers, side by side
| Layer | Sounds like | What it actually tells you | Why reps stop here anyway |
|---|---|---|---|
| Symptom | "Reports take too long" | A fact. No money attached, no urgency, easy to move past | Arrives inside the first two minutes and feels like "pain found" — it ends the awkward silence |
| Business impact | "Costs us roughly £18k a quarter" | A number that justifies a business case and a timeline | Needs a follow-up question and a bit of buyer-side maths reps are often reluctant to force |
| Root cause | "Nobody owns the fix, last attempt died in an IT backlog" | Whether this is genuinely solvable, and what you're actually competing against | Needs a third question after two "yes, and"s already landed — feels like pushing your luck |
Two reps, same buyer, different call
Rep A: "What's the biggest challenge with your current process?" Buyer: "Honestly, the reporting takes forever." Rep A: "Got it — makes sense. So on budget..." Discovery, closed, in ninety seconds. Nothing here justifies a deal.
Rep B asks the same opening question, gets the same answer, and doesn't move on: "When that happens, what does it actually cost you — time, money, or something breaking downstream?" Buyer: "We end up missing the freight window most months, so we're paying rush rates." Rep B: "Why has that been allowed to keep happening — what's got in the way of fixing it before now?" Buyer: "We tried, about eight months back. Died in the IT queue — nobody owned it enough to keep pushing." Rep B now knows the number, the mechanism, and exactly which internal failure mode they have to design around so they don't become attempt number two.
The questions that move you down a layer
- Symptom → impact: "When that happens, what does it actually cost you — time, money, or something breaking downstream?"
- Impact → root cause: "Why is that still happening — what's got in the way of fixing it before now?"
- Root cause, confirmed: "If nothing changes, is this an every-quarter problem, or is it getting worse?"
Each one takes maybe fifteen seconds to ask. The only cost is tolerating a beat of silence while the buyer actually does the arithmetic, instead of rescuing them from it by moving to your next scripted question.
Why this is a competency, not a knack
This is exactly the kind of thing that separates reps who plateau from reps who get handed the harder accounts. A rep who reliably stops at symptom is, structurally, an order-taker who occasionally gets lucky with timing — competent, but not building a case anyone with budget authority has to take seriously. A rep who reliably reaches root cause is doing something closer to consulting: they can create urgency in an account that didn't think it had any, because they can show precisely what's broken and why it's stayed broken. That's the actual line between an IC handling inbound and someone trusted with a complex, multi-stakeholder deal — check where you sit against the full arc on the Sales Career Level Matrix (IC1 → Principal/Enterprise).
Practice this before you need it live
The follow-up phrasing above isn't hard to say. It's hard to remember to say, live, under the mild social pressure of a buyer who's already given you an answer and clearly considers the topic closed. Drill the phrasing with the Discovery Questioning Skill-Builder Cheat Sheet until the second and third questions are reflexive, and use the Qualification IQ Self-Assessment Quiz to find out, honestly, which layer you actually stop at by habit rather than which layer you think you reach.
Most qualification failures aren't a framework problem. They're a nerve problem — a rep who won't ask the third question because the buyer already answered the first one, and it felt like enough.