Write a Customer Interview Script That Validates a Problem with Past-Behavior Questions

Get a 30-minute problem-discovery interview script with past-behavior questions, two follow-up probes each, banned-question rewrites and evidence signals.

You getOpening script, table and closing script with a referral ask

Prompt

Prompt
Act as a product researcher who runs problem-discovery interviews for early-stage products.

Write a 30-minute customer interview script that checks whether a problem is real, frequent and painful enough to solve. Before writing, ask me these in one message and wait for my answers:
1. What problem do you think exists, and for whom?
2. What do you believe people do about it today?
3. Who will you interview (role, company size or life situation)?
4. What decision will this round of interviews inform?

Rules:
- Every main question asks about past behavior ("Tell me about the last time..."). No hypotheticals ("Would you...", "If we built...") and no leading questions that name the problem or its pain before the interviewee does.
- Give 2 follow-up probes per question that dig for specifics: dates, time spent, money spent, tools used, who else was involved.
- Never mention a solution or pitch an idea.
- Mark which answers count as strong evidence and which are just polite interest.
- List 5 tempting questions to avoid, each with a past-behavior rewrite.

Output format:
1. Opening script (under 80 words)
2. Table: # | Main question | Probe 1 | Probe 2 | What we learn
3. Questions to avoid → rewrites
4. Closing script with a referral ask
5. Signals: strong evidence vs. false positives

End with one line naming the riskiest assumption these interviews cannot test.

Example output

At a glanceStructure of the 30-minute interview scriptProblem discovery for design agency owners facing late client payments
  1. Opening scriptSet context: real recent examples, not selling anything
  2. Interview questions6 past-behavior questions with two probes each
  3. Questions to avoid5 banned questions rewritten as past-behavior asks
  4. Closing scriptAsk what was missed and request introductions
  5. SignalsStrong evidence vs false positives, plus riskiest assumption

Example for: owners of 5-20 person design agencies who may struggle with late client payments; deciding whether to build an invoicing reminder tool.

1. Opening script

"Thanks for the time. I'm learning how small agencies handle the money side after a project ships. There are no right answers and I'm not selling anything. I'll ask about real recent examples, so specifics help most. Mind if I take notes?"

2. Interview questions
#Main questionProbe 1Probe 2What we learn
1Walk me through what happened after you sent your last invoice.What date was that, and when did it get paid?Who on your side was involved?Real payment timeline
2Tell me about the last time a client paid later than agreed.How many days late?What did you do first?Whether lateness happens unprompted
3How did you follow up on that payment?What tool or channel did you use?How long did follow-up take in total?Current workaround and its cost
4What did that late payment affect?Did you delay anything, like payroll or a hire?Did it come up with your partner or accountant?Severity
5Have you tried anything to fix this in the past year?What did it cost?Why did you stop or keep it?Willingness to spend
6How many invoices did you send last month?How many were paid on time?How do you track that?Frequency
3. Questions to avoid → rewrites
  • "Is chasing payments a big pain?" → "Tell me about the last payment you chased."
  • "Would you use an automatic reminder tool?" → "What have you used to send reminders?"
  • "How much would you pay to fix this?" → "What have you spent on this so far?"
  • "Don't you hate awkward money emails?" → "What did your last follow-up email say?"
  • "Do you usually get paid late?" → "How many of last month's invoices arrived late?"
4. Closing script

"That's really useful. Is there anything I should have asked? Who else runs an agency and deals with this, and would you introduce me?"

5. Signals

Strong evidence: they paid for a tool or bookkeeper to chase invoices; they name a date and amount; lateness changed a decision; they offer an intro unprompted.
False positives: "That sounds useful"; complaints with no example; "I'd definitely try it"; compliments on the idea.

Riskiest untested assumption: that owners, not their bookkeepers, would choose and pay for a new tool.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Banning hypotheticals and leading questions keeps answers tied to what people actually did, not polite guesses.
  • Two probes per question push for dates, money and tools, the details that separate real pain from mild annoyance.
  • The strong-vs-false-positive list helps you score interviews honestly instead of hearing what you hoped.

Use before building or scoping a feature, when you have a problem hypothesis and a list of people to talk to. Paste into ChatGPT, Claude or Gemini and answer its four questions about the problem and audience.

Common edits

  • Ask for a 15-minute version with only the four most important questions.
  • Add a column for note-taking cues or a tag scheme to synthesize across interviews.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Product Management