User interview script (Mom Test)
A discovery interview is about their week, not your idea. Every question here asks about something the person has already done: the last time the problem came up, how they handled it, what they paid. Kind people will guess generously about the future. They rarely make up last Tuesday.
Best for: Product teams and researchers doing problem discovery before anything gets built.
Use this template freeWalk me through the last time you ran into this problem.
A live preview of this template. Click through it. Nothing gets sent.
The questions
- 1Walk me through the last time you ran into this problem.Long textA specific past episode beats a general opinion.
- 2How did you handle it? What tools or steps did you use?Long text
- 3What was the most frustrating part of that?Long text
- 4How often does this come up for you?Single selectDaily / Weekly / Monthly / Rarely. How often it happens shows how much it hurts.
- 5What have you tried to fix it, and why didn't it stick?Long text
- 6If you've paid for anything to help with this, what was it?Short textMoney already spent is the strongest sign the problem is real.
- 7Who else on your team deals with this?Short text
Sample replies, counted
These replies are made up to show the method.
Asked: Walk me through the last time you ran into this problem.
Last Tuesday. A client was 40 days late, so I dug through my sent folder for the original invoice and forwarded it again.
Chased it by emaili keep a google sheet of every invoice and colour the late ones red. checked it sunday night
Kept a spreadsheetOur bookkeeper usually handles it. I just ping her on Slack when someone hasn't paid.
Handed it to someoneI wrote a polite reminder, deleted it, wrote a firmer one, then sent the polite one anyway. Took half an hour.
Chased it by emailHonestly I let a $300 one go last month. Not worth the awkwardness.
Gave up on itSpreadsheet, plus calendar reminders on the 1st and the 15th.
Kept a spreadsheetCalled them. Email had stopped working.
Other
| Label | Replies |
|---|---|
| Chased it by email | 2 |
| Kept a spreadsheet | 2 |
| Handed it to someone | 1 |
| Gave up on it | 1 |
| Other | 1 |
Four of seven already chase late payments with email or a spreadsheet, so those are what you're up against. The person who wrote three drafts shows where the pain sits: the awkward message, not the tracking.
How to run it well
- Don't describe your idea before these questions. Once they know it, every answer bends toward being nice.
- Chase specifics. Ask 'tell me about the last time', not 'do you usually'.
- Don't rush to fill a pause or cut in. Give people room to finish the thought.
- Listen for strong feelings and homemade workarounds. Those mark problems worth solving.
When not to use this: If you haven't worked out who to talk to yet, interviews with the wrong people waste everyone's hour. Start with a customer interview screener.
FAQ
Why ask about the past instead of the future?
Can I run a Mom Test script as a form instead of a live call?
Where the method comes from
Related templates
- Product-market fit surveyThe Sean Ellis 40% test, plus the questions that find your best segment.
- NPS surveyThe 0-10 question plus the open follow-up that explains the score.
- Customer satisfaction (CSAT) surveyRate one real interaction, not a vague overall feeling.
- Onboarding feedback surveyFind the exact step where new people stall before they see value.