The Mom Test: How to Get Brutally Honest Feedback Without Asking a Single Leading Question
Type: media · article
Stage: Stage 4: Prototype Proof
Difficulty: intermediate
If you ask your mother whether your business idea is good, she will say yes — because she loves you. Most potential users behave exactly like your mother. The Mom Test is a set of rules for asking questions they cannot lie to you about: talk about their life not your idea, ask about the past not the future, look for commitment not enthusiasm.
Overview
Every founder has done this interview. You sit down with a potential user. You explain the idea. They nod. They say "that's really interesting." They ask how it works. You leave convinced you've validated something. You have not validated anything. Rob Fitzpatrick named this problem in The Mom Test. The premise: if you ask your mother whether your business idea is good, she will say yes — because she loves you. Most potential users behave exactly like your mother. They want to be encouraging. They don't want to hurt your feelings. And so they tell you what you want to hear, not what you need to know. The Mom Test is a set of rules for asking questions your mother — or any polite stranger — cannot lie to you about.
The core rules
**Talk about their life, not your idea.** The moment you describe your solution, the conversation shifts. The user is no longer talking about their real behavior — they're reacting to your proposal. Keep the solution out of the conversation entirely until you have learned everything you can about the problem.
**Ask about the past, not the future.** "Would you use this?" is a useless question. People cannot accurately predict their future behavior, especially when they want to be helpful. "When did this last happen? What did you do?" is a useful question. Past behavior is evidence. Future intent is noise.
**Look for commitment, not enthusiasm.** Enthusiasm is cheap. "That's so cool" costs nothing to say. Commitment has a price. The user who asks when they can try it, who introduces you to their team, who offers to be a beta user — that is signal. The user who says "definitely, keep me posted" is not validating your idea. They are ending the conversation politely.
The questions that reveal truth
Use these to get past politeness and into real behavior:
— "Walk me through how you handle [X] today."
— "What's the most frustrating part of that process?"
— "When did this last happen? What did you do?"
— "Have you tried to fix this? What happened?"
— "What would you lose if this never got solved?"
Do not ask: "Would you pay for this?" Do not ask: "What features would you want?" Do not describe your prototype and ask for opinions. Your job is to listen and record the exact words people use to describe their pain.
What to do with the data
After each conversation, write down the exact phrases the person used — not your interpretation of what they meant. Look for language that repeats across interviews. If three different users describe the same frustration using the same metaphor, that language belongs in your positioning.
Count strong signals separately from weak ones. Strong signals: they've spent money on a workaround, built something themselves, or described a specific recent incident with measurable cost. Weak signals: they expressed general interest but couldn't recall a specific instance of the problem.
If you reach ten conversations and have fewer than five strong signals, either the problem isn't painful enough or you're talking to the wrong people.