20 Customer Discovery Questions That Validate Demand

Customer discovery questions should uncover recent behavior, consequences, current alternatives, and the real buying process. They should not ask people to predict whether they would use an imaginary product.

Use these questions as a flexible interview guide, not a script to complete mechanically. Follow surprising details and ask for examples.

Before the interview

Define who qualifies for the conversation: role, organization, workflow, relevant trigger, and how recently the problem occurred. Recruit beyond friends and enthusiastic early followers.

Ask permission to take notes. Record the participant’s words separately from your interpretation, and avoid collecting sensitive information you do not need.

Problem and context

1. Walk me through the last time this happened

Anchor the conversation in a real event. Ask when it happened and what triggered it.

2. What were you trying to accomplish?

This reveals the desired outcome rather than the feature the participant thinks you want to hear about.

3. What made the situation difficult?

Probe for delay, errors, coordination, uncertainty, cost, risk, or emotional friction.

4. How often has this happened recently?

Ask for examples from a defined period. Avoid accepting “all the time” without clarification.

5. What happens when you leave it unresolved?

Consequences help distinguish an irritating problem from a priority.

Current behavior and alternatives

6. What did you do first?

Reconstruct the actual sequence, including people, tools, documents, and handoffs.

7. What do you use today?

Include direct products, spreadsheets, internal processes, outside services, and doing nothing.

8. What works well enough about the current approach?

This question exposes switching barriers. A competitor does not need to be perfect to remain the rational choice.

9. Where does the current approach fail?

Ask for a recent example and its consequence instead of collecting a wish list.

10. What have you already tried to improve?

Past effort is stronger evidence than a stated intention to act later.

Cost, urgency, and ownership

11. How much time or money did the last occurrence consume?

Accept a range and ask how it was estimated. Do not pressure participants into false precision.

12. Which deadline or event makes this urgent?

Look for operational triggers such as reporting cycles, customer commitments, renewals, audits, or hiring.

13. Who feels the impact most directly?

The user, beneficiary, manager, and buyer may be different people.

14. Who owns the outcome?

This identifies the person accountable for solving the problem, even if they do not use the eventual product.

Buying and switching process

15. When did you last pay for something related to this problem?

Ask what initiated the purchase, which alternatives were considered, and why one was chosen.

16. Who can approve budget or block adoption?

Probe for procurement, security, legal, integration, or operational approval where relevant.

17. What would have to be true for you to change the current process?

This surfaces minimum outcomes, proof requirements, and switching costs without pitching your solution.

18. What would make a new approach unacceptable?

Constraints and no-go criteria are often more useful than feature requests.

Evidence and next steps

19. Can you show me a redacted example of the workflow?

Ask only for information the participant is authorized to share. A document, screen, template, or process map can reveal details that memory omits.

20. Who else sees this problem differently?

Request introductions to users, buyers, skeptics, and people who chose another solution—not only likely supporters.

Questions to avoid

Avoid prompts that reveal the desired answer:

• “Do you think this is a good idea?”
• “Would you use an AI tool that saves time?”
• “Would you pay $20 for this?”
• “Which features should we build?”
• “Don’t you find the current process frustrating?”

Replace predictions with history. Ask what the person did, used, paid, delayed, escalated, or changed.

A practical note-taking format

For each interview, capture:

How to synthesize interviews

Do not count only how many people mentioned a theme. Compare participants by qualification and evidence strength.

1. Group recent events by trigger and workflow.
2. Separate stated opinions from observed past behavior.
3. Identify current alternatives and why they remain acceptable.
4. Map consequences and buying ownership.
5. Highlight contradictions and segment differences.
6. Decide which assumption needs the next behavioral test.

The U.S. Small Business Administration lists interviews, surveys, questionnaires, and focus groups as direct-research methods, while noting that direct research provides audience-specific context and existing sources answer broader quantitative questions. See its market research guidance.

Interviews establish context; they do not establish total market size or guarantee purchase. Move next to a prototype, concierge test, workflow artifact, introduction, or paid pilot. See how to validate without building and the complete market validation process.