Discovery question design

Discovery questions should get the prospect to describe a situation in their own terms and give you a clear way to test whether change matters. Build the conversation path around a bounded prompt, the current workflow, the problem in the prospect's answer, and detail only where you need it. An unconstrained opening can make you lose control,¹ so begin with a closed question and then open the conversation.²

Before the call

Build the path around what you need to learn from the conversation. Prepare questions that can uncover whether there is a need or problem you can solve,³ using information the prospect has already given you.⁴ Start with a broad prompt, then narrow in small steps.⁵ Wide questions can reveal problems, goals, the desired transformation, and its value, while narrow questions produce narrow answers.⁶ Let the prospect's answers determine which question comes next.

Write a few prompts for each part of the path, but leave room to follow the language the prospect uses. The question list keeps you oriented. It should not decide the order once the prospect gives you a useful answer.

Run the question path

Use the stages below in order. Move to the next stage when the answer gives you enough detail to continue.

Set the frame

Give the call a clear entry point. The opening answer should tell you why the prospect agreed to speak.

Ask why they took the call before moving into priorities or similar topics.⁷ Try: What made this conversation worth taking today? Listen for the event, concern, or change that brought them in. When they give you a reason, use their wording to open the next question.

A permission-based broad prompt can ask the prospect to describe the team, its challenges, and the overall company situation from their perspective.⁸ You could ask: "So, I could tell you a million things about #samsales Consulting, but I'd love to hear from your perspective first: what the team is like, challenges you're having, and just the overall landscape of what things look like at COMPANY, if that's okay?" Once they accept the frame and begin describing their situation, move to the current workflow.

Map current work

Get the prospect to explain how the work runs today before you try to diagnose it. This gives later questions something specific to attach to.

Ask, "How does your workflow work today?".⁹ Keep the prompt open, then follow the answer from the broad process into the part that deserves attention. When a step is unclear, ask how they normally complete or capture it. That question can expose a root cause.¹⁰

Listen for the prospect's own description of the process. Ask what happens before or after the step they mention, and keep narrowing until you can describe the current workflow without filling gaps from your own assumptions. When you understand the process well enough to locate the problem inside it, trace the problem.

Trace the problem

Make the problem concrete by separating the event from the explanation. A problem label alone will not tell you what caused it or how long it has been present.

Ask what is happening, why it is happening, and how long it has been happening.¹¹ Useful prompts include: What is happening in that process? What do you think is causing it? How long has it been this way?

Ask how the prospect discovered the issue. That question can lead them to tell a story about what happened to them.¹² Follow the event in the story with a question about what changed, what they expected, or where the process broke down.

When an answer leaves a gap, use a more refined and deeper question to work toward the root cause.¹³ Continue when you can explain the problem in the prospect's terms and they agree that your explanation fits.

Test the weight

Once the problem is clear, find out whether it carries enough weight to change. Ask for detail before asking the prospect to judge the situation.

Use prompts that ask the prospect to elaborate, explain duration, describe attempted fixes, quantify cost, and consider the result of inaction over the next twelve months.¹⁴

• Ask: "Tell me more about that".¹⁴
• Ask: "How long has that been the case?".¹⁴
• Ask: "What have you tried to fix it?".¹⁴
• Ask: "What does that cost you in time, revenue, or stress?".¹⁴
• Ask: "What happens if you do nothing about it for the next twelve months?".¹⁴

Do not run through every prompt automatically. Follow the answer that carries the most detail, and stop when the prospect has made the cost or consequence clear enough to evaluate.

Test change and alternatives

A problem matters to the call only when the prospect can act on it. Use this stage to learn whether the required change is possible and what else may shape the decision.

Ask how the buyer would respond to the implementation requirements. Their answer can reveal willingness to change.¹⁵ Try: What would have to change in your process for this to work? Listen for a concrete response about effort, ownership, or resistance.

Ask about vendor support before asking how happy the customer is with the vendor. That order is more likely to guide you toward the right issue.¹⁶ Ask: Where does the current support fall short? Follow the answer into the effect on daily work.

If alternatives matter, ask what else the prospect has considered and what each option proposed. Questions about competitive differences can reveal the competitors, their proposals, and what the customer prefers or dislikes.¹⁷ Continue when you know what the change would require and what the prospect would compare it against.

Check understanding

Finish each explanation by checking what the prospect is carrying forward. The answer can expose confusion or interest while there is still time to address it.

Replace the generic question, "Do you have any questions?" with a specific question that helps you tell whether the buyer is following.¹⁸ Try: Which part of this would you want to examine more closely? Questions that encourage the prospect to open up give you more to work with than a simple check for understanding.¹⁹

Use the prospect's answer to choose the next question. Finish when they can connect what you discussed to their own process, problem, or decision.

What not to do

Keep these mistakes out of the question path. Each one makes the call easier to script and harder to learn from.

• Do not ask for information you could have learned before the call.²⁰
• Do not ask whether the prospect has budget.²¹
• Do not use scripted questions that fail to match the conversation. Unnatural or overly rehearsed questions cause buyers to tune out.²²
• Avoid firing through questions about what keeps the prospect awake, the consequences of leaving it unresolved, and who else cares as a rapid sequence. That can make the interaction feel like an interrogation.²³