Problem and impact discovery

Discovery works when the prospect can describe the problem, connect it to a business effect, and decide it deserves attention. Move from situation to problem to impact, checking for agreement as you go. If a prospect gets excited about a feature, ask what work or outcome sits behind that interest. The reaction can reveal an underlying problem.¹ The discovery outcome is a prospect who admits a problem and wants to learn more about solving it.²

Run the map

1

Situation

2

Problem

3

Agreement

4

Impact

5

Fit

1. Situation
2. Problem
3. Agreement
4. Impact
5. Fit

Use one path through the conversation. Each stage earns the next question, so keep the prospect's wording in view as you go. The discovery process maps the progression from situation to problem to impact.³

Stage	What you are trying to learn	Example question
Situation	How the work happens today and what the prospect is trying to achieve	"How does this work today?"
Problem	What is breaking, missing, or getting in the way	"About your current system, what would that be?".4
Agreement	Whether the issue exists in real work and can be addressed	"Can you give me an example?".5
Impact	What the issue changes for the business and whether it deserves attention now	"Why does that matter to you?".6 "Why is it worth addressing now?".7
Fit	Whether the agreed problem is something you can help solve and worth exploring further	"Would it be useful to look at how this could be addressed?"

Start with the situation

Start with how the prospect works today. Give them room to recognise a problem before you try to name it for them.

Some prospects are still exploring whether a problem exists, so begin with the current situation and let the issue emerge.⁸ Prepare by understanding the current situation and the business impact you expect to investigate.⁹ That preparation gives you a direction without forcing your diagnosis onto the call.

Ask about the process, the handoffs, the work that gets delayed, and the result the prospect is trying to produce. Listen for the point where a description becomes friction. When the prospect mentions a technical challenge, begin digging into it.¹⁰

Move on when the prospect has described a problem in their own words. A general description of the workflow is useful until it points to something that fails, costs effort, or prevents an outcome.

Turn the situation into an agreed problem

Make the problem testable. State what you think is happening, then let the prospect correct or confirm it.

Problem agreement means the prospect agrees that they have a problem you can solve.¹¹ You can state the assumption plainly: "Here's what I'm assuming your problems are".¹² Then ask whether that reflects their situation and what you have missed.

If the prospect confirms the issue, ask for the event behind the label. Have them describe what happened, who dealt with it, and what the current approach failed to handle. When a current solution or proposed capability enters the conversation, ask why the current solution was adopted. That can reveal the original problems and motivations behind it.¹³ If they lead with a solution, work back to the problem behind it.¹⁴

Do not treat a vague nod as agreement. Ask the prospect to validate that the assumed problem is genuinely present before you build the rest of the call around it.¹⁵ Move forward when the problem is specific enough for the prospect to recognise and for you to test against what you can solve.

Turn the problem into a story

A label such as "slow," "manual," or "hard to manage" gives you a direction. A story shows when the issue appeared, how it shows up, and what keeps it in place.

Once the prospect agrees there is a problem, ask when they realised it needed attention: "When was the moment that you realized that this was a problem?".¹⁶ Stay with the answer until you hear an incident, a change, or a consequence that made the problem visible.

Then find out what has prevented the prospect from solving it. After establishing the problem, the seller diagnoses what is stopping the prospect from making it go away.¹⁷ Ask what they tried, what blocked that attempt, and what happens when the issue remains in the current process.

Keep going after the first explanation. A prospect can name a symptom before describing the problem that carries the business weight. Ask for a more concrete account instead of steering the prospect toward your product.

Translate the problem into impact

Impact connects work that goes wrong with the business effect of leaving it that way. Stay close to the prospect's language and ask them to make the connection.

The problem map runs through operational and executive problems to business impact.¹⁸ After identifying the problem, turn it into a substantial business impact.¹⁹ Ask what the issue affects across the business, who feels the consequence, and what outcome becomes harder to reach.

Probe for importance after you understand the effect. The seller should understand how important the issue is to the prospect.²⁰ Ask what they are measured on or focused on, then listen for where the problem touches that work. Discovery should establish whether the problem is worth fixing and identify the other initiatives the prospect is dealing with.²¹

The prospect does not need to give you a perfect calculation. You need a business consequence they recognise, a reason it matters, and enough priority to justify continuing. If the impact stays abstract, return to the example and ask what changed because of the problem.

Test fit before you advance

An agreed problem still needs to fit what you can help with. Use this point to check the boundary of your offer and the prospect's willingness to explore a solution.

In outbound, determine whether the prospect's agreed framing of the problem is something you can help solve.²² Ask what a useful outcome would look like and whether they want to examine ways to reach it. If their answer changes the problem, update your wording and test agreement again.

Write the actual problem statement from the discovery call using a business-case framework.²³ Keep the wording close to what the prospect said. That statement gives you a reference for later conversations and prevents the impact from becoming a seller-created story.

What not to do

These mistakes shorten discovery by moving you past the part where the prospect gives the problem meaning.

• Do not turn an assumption into a confirmed problem without validating it with the prospect.¹⁵
• Do not stop at the initial pain after the prospect identifies a problem. Continue discovery.²⁴
• Do not move into impact before you understand the problem in enough depth.²⁵
• Do not walk through a full proposal before the buyer has confirmed the problem and vendor-of-choice status.²⁶