Problem and impact discovery moves from what the prospect says is wrong to what the issue changes in the business. Start with the current state, follow a signal of trouble, trace how it arose and what blocks a fix, then test the consequence and the reason to act. The call needs different depth for different prospects. Deep discovery focused on pain fits prospects who know the seller and their problem.1 Outbound or longer-tail prospects may need a taste of the solution before that kind of discovery works.2 Set the call's depth to the prospect's awareness.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Current state | What normal looks like and where the gap sits | What does this look like today? |
| Problem | How the prospect describes the issue | "Tell me about the problem."3 |
| Origin | How the issue appeared and developed | How did this start? |
| Impact | What the issue changes for the business | "Oh, that's interesting. Can you share more about how that impacts your business?"4 |
| Importance | Whether the issue deserves action | Have you thought about what the impact might be?5 |
Prepare
Bring a starting hypothesis into the conversation, then let the prospect correct it. Your notes should help you tell a passing complaint from an issue with business weight.
Come prepared with the business impact and the current situation.6 Write down what you believe is happening, who may feel it, and what business result could move. Treat each point as something to test so the prospect's words can replace your assumptions.
Establish the current state
Start by learning what normal looks like for the prospect. That gives you a baseline for judging the problem's size and reach.
Ask about the business, team, and current situation to establish a baseline for what normal looks like and where the gap sits.7 Let the prospect describe the process in their own language. Ask what happens today, who handles it, and where the work starts to break down.
When a prospect mentions a technical challenge, begin digging into it.8 A problem can also appear as a passing comment, so follow it while it is still connected to the prospect's experience. If the prospect has not recognized a problem, a sequence of questions can help them realize it.9
Move on when you can describe the current state clearly enough to name the problem without borrowing your own product language. If the prospect cannot confirm the description, keep calibrating the current state.
Diagnose the problem
Once the issue has a name, learn how it arose and what keeps it in place. This separates the visible symptom from the conditions around it.
Ask about the past, including when the prospect identified the issue.10 Then ask what prevents them from solving it. After establishing the problem, cover what is stopping the prospect from making it go away.11
Use a humbling disclaimer while you dig deeper into the issue.12 A simple phrase such as "I may be missing some context" gives the prospect room to correct your read. Then ask what they have tried, what they use today, and where those efforts fall short.
Discussing existing solutions helps you understand how the prospect already handles the problem and its dimensions before you present an offering.13 Listen for workarounds, ownership gaps, repeated manual effort, and attempts that solved part of the issue. Move on when the prospect can explain both the problem and why it remains unresolved.
Map the business impact
Translate the issue into consequences the prospect can see and defend. Stay with the impact until the problem has meaning beyond the task where it first appeared.
Move from the technical problem to the business impact.14 Map who or what is involved, including relevant processes, transactions, customer groups, equipment, teams, or populations.15 Ask, "What is the operational, financial, or customer consequence?"16
Let the prospect describe the consequence in their own terms before you attach a value to it. When verified information supports a calculation, include the customer, output, or financial consequence.17 Ask the prospect to calculate the cost of inaction aloud, because doing so can change the urgency they attach to the problem.18
Listen for effects that spread beyond the person who raised the issue. A problem may affect delivery, customers, output, or financial results without appearing in the original complaint. Move on when the prospect can connect the issue to a consequence and explain what continuing with the current state would mean.
Confirm importance and fit
Impact gives the problem weight. This stage tests whether the prospect will prioritize it and whether the issue sits inside the help you can provide.
Find out how important the issue is to the prospect.19 Confirm that the problem is worth solving.20 Test your read by summarizing it and asking the prospect to confirm or correct you.21
Take the prospect's wider priorities into account before judging the opportunity. When the prospect is deep in significant current-state pain, stay there until you understand it before positioning a solution.22 Ask whether the issue belongs among the problems they can act on now and whether solving it would change the outcome they care about.
If the prospect cannot give the problem importance, keep exploring the context or qualify it out. If they can explain the problem, its impact, and its priority, you have earned the right to discuss how you might help.
What not to do
These mistakes break the path from problem to impact and make the call feel like a product presentation.
- Do not pitch as soon as a prospect mentions a pain point. Explore who the problem impacts, what it costs, and what they have tried to do about it first.23
- Do not interrupt the prospect's explanation to compare your product with the current solution.24
- With a prospect who does not know or trust you, leading with impact questions skips the problem questions this approach calls for.25
- Do not steer discovery toward problems you cannot help with and address.26