The first 3 interviews are free · Start free or see the prices

Problem Validation Interview: Questions to Test a Startup Idea

Use this guide when you have a specific problem in mind and want to know if it is worth solving. It checks the last time the problem happened, its cost, current spend on it and where it ranks.

Length
25 min
Questions
14
People
12 to 20
Sections
5
Run this study

What this guide finds out

  • If the problem happens to the target group, and how recently and how often.
  • The cost of the problem in time, money or risk, in the words of the people who have it.
  • What people already try or pay for to solve it, and why that falls short.
  • Where the problem ranks among the other problems of the target group.

When to use it

  • You have a startup idea and a specific problem in mind, but no evidence that the problem matters.
  • You must choose between two or three problems to work on.
  • Investors or partners ask for proof of demand before any product exists.

Who to talk to

People in the target group who should have the problem, including some who you expect do not have it. Talk to 12 to 20 people. Each interview takes about 25 minutes.

The discussion guide

Each question has a probe note. The note tells the moderator, a person or an AI, what to do with the answer.

01

Context

3 min

Learn the role and responsibilities of the participant, without mention of the problem.

  1. Tell me about your work and what you are responsible for.

    ProbeAsk what a normal week looks like. Do not mention the problem yet.

  2. What are the hardest parts of [the area of work] for you right now?

    ProbeRecord each problem they name, in their order. Note if your problem appears without a prompt.

02

The last occurrence

7 min

Find out if the problem happens, and rebuild the last time it did.

  1. When was the last time you had to deal with [the situation where the problem appears]?

    ProbeDescribe the situation, not the problem. If they cannot remember a time, record that the problem is rare for them.

  2. Walk me through that time from start to end.

    ProbeAsk what came before and after each action. Do not suggest where the difficulty was.

  3. Which part of that was the most difficult or annoying?

    ProbeIf they name your problem, ask why it was difficult. If they name a different part, follow their answer.

  4. How often does this happen?

    ProbeAsk for the number of times in the last month. Accept "I do not know", and ask about the last two times instead.

03

Cost

5 min

Measure what the problem costs, in the words of the participant.

  1. What did that last time cost you, in time, money or anything else?

    ProbeAsk for an estimate in hours or money. Ask how they got that number.

  2. What happens if you do not deal with it?

    ProbeAsk about the worst case they have seen. Record if the cost is a risk or a daily loss.

04

Current solutions

6 min

Learn what people already do and pay to solve the problem.

  1. What do you do about it today?

    ProbeAsk for the tools, people and spreadsheets they use. If they do nothing, ask why it is not worth the effort.

  2. Have you looked for a better way? What did you find?

    ProbeAsk what they searched for and what they tried. Ask why they stopped using it, if they stopped.

  3. Do you pay for anything to help with this today? How much?

    ProbeInclude staff time, contractors and software. Ask who approved the spend.

05

Priority and close

4 min

Learn where the problem ranks and if the participant will give a small commitment.

  1. Of the problems you named today, which one would you solve first if you could?

    ProbeRead back their list. Ask why that one is first. Record where your problem ranks.

  2. Can I contact you again if we work on this, for example to test an early version?

    ProbeRecord yes or no. A yes with an email is a small commitment. Do not describe the idea, even if they ask.

  3. Who else do you know who has this problem?

    ProbeAsk if they would introduce you. Thank them and end the interview.

Example finding

ExampleProblem real but not a priority

Most clinic owners had the scheduling problem every week. But they ranked it below hiring and did not pay to solve it.

“Yes, the double bookings are annoying. We fix them with a phone call. Finding a second nurse is what keeps me up at night.”
In a User Evaluation study report, each claim links to the clip where a participant says it.

Mistakes to avoid

  • Do not pitch the idea. Once people hear it, they are polite and the evidence about the problem is lost.
  • Do not ask "Would you use a product that solves this?". Almost everyone says yes. Ask what they do and pay today.
  • Do not count compliments as evidence. Count recent occurrences, real costs and current spend.
  • Do not talk only to friends and people who already like the idea. Recruit strangers from the target group.

Analyze the answers

Analysis templateOpportunity Solution Tree Template: From Interviews to ExperimentsUse this template to connect a product outcome to what you heard in interviews. Each node type has a rule for what belongs in it, so opportunities do not turn into solutions in disguise.

Questions

A problem validation interview checks if a specific problem is real, frequent and costly for a target group. It happens before you build a product, and it does not describe the idea.

Customer discovery explores a broad area to find problems. Problem validation tests one problem that you already have in mind. Many founders do discovery first, then validation.

Start with 12 to 20. Stop when new interviews do not change your view of the problem. If results differ by group, add interviews for each group.

Look for recent occurrences, a cost people can describe, current spend or workarounds, and a high rank among their problems. Requests to see the product are weaker evidence.

Let the AI moderator ask these questions

The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.

Run this study