The Mom Test

Core mental models

1. Everyone lies to you, politely. People you interview want the conversation to go well. Your mom says your app idea is great because she loves you; strangers say it’s great because it ends the meeting faster. The lie isn’t malicious — it’s social lubricant. The burden is on you to ask questions that even a polite person can’t answer with a comfortable falsehood. The Mom Test is named for the standard it sets: your questions should be so grounded in facts that even your mom couldn’t mislead you with them.

2. Talk about their life, not your idea. The moment you pitch, the data is contaminated. Every question afterward measures how nice the person is, not how real the problem is. The fix is structural: ask about what they did last week, what it cost them, what they tried, who else they complained to. Their past behavior is evidence; their opinion of your future product is not.

3. Compliments are worthless; commitments are gold. “That’s really cool” is a deflection, not a data point. What counts is anything that costs the person something: time (a scheduled follow-up with a clear agenda), reputation (an intro to their boss or budget owner), or money (a pre-order, a letter of intent, a deposit). Fitzpatrick calls these currency. If a meeting ends with kind words and nothing on the calendar, it didn’t go well — it went nowhere.

4. Bad news is good news. A lukewarm “meh” that arrives in week two saves you the year you would have spent discovering it in production. The goal of customer conversations is truth, not validation. Learning that a problem doesn’t matter, or that the customer has no budget, or that they’ve tried nothing to solve it (a tell that they don’t really care) is a successful outcome.

5. Some problems don’t matter. People will cheerfully confirm that something is annoying. The real questions are: Where does this rank against everything else on their plate? What does it cost them? What have they already tried? If they’ve never Googled for a solution, the problem isn’t burning enough to build a business on.

Key frameworks

The three rules of the Mom Test:

1. Talk about their life instead of your idea.
2. Ask about specifics in the past instead of generics or opinions about the future.
3. Talk less and listen more.

Question quality check. Bad: “Would you buy a product that did X?” (invites a hypothetical lie). Good: “What are you using now? What does it cost you? When did this last happen — walk me through it.” Future tense and hypotheticals are where lies live; past tense and specifics are where truth lives.

Deflect compliments, anchor fluff, dig beneath signals. When you get a compliment, ignore it and move on. When you get a generic claim (“I always…”, “I’d definitely…”), anchor it: “When did that last happen?” When you get an emotional signal (frustration, excitement), dig: “Tell me more about that.”

Commitment and advancement. Every meeting should end by pushing for a next step that costs the prospect something. If you don’t know what to ask for, you went into the meeting without a goal — Fitzpatrick’s “three big questions” prep: decide in advance the three things you most need to learn.

Keep it casual. Early-stage learning conversations don’t need a scheduled “interview.” A good conversation about someone’s workflow can happen at a conference, in a coffee line, or in a user’s existing support thread. Formality raises the stakes and invites performance.

When to reach for this book

• Before writing code for any new product or feature.
• When your user interviews keep producing enthusiastic feedback but no usage.
• When someone on the team says “everyone we talked to loved it” — this book is the antidote.
• When deciding whether a feature request is real or polite noise.

Memorable ideas

“You shouldn’t ask anyone whether your business is a good idea… It’s a bad question and everyone will lie to you at least a little.”

“Opinions are worthless… Anything involving the future is an over-optimistic lie.”

“If they haven’t looked for ways of solving it already, they’re not going to look for (or buy) yours.”

The book’s sharpest reframe: a failed conversation is one where you only collected compliments. By that standard, most “great meetings” founders report are failures.

How I’ve applied it

Building CrowdListen, my early conversations were classic anti-patterns: I demoed, people nodded, I logged “positive feedback.” Re-running those conversations Mom Test-style — “show me the last time you tried to figure out what your audience thought” — changed the product. The painful, specific stories were about aggregating scattered feedback, not about the dashboard I had been building. The other habit that stuck: ending every promising conversation by asking for something that costs the other person effort. The people who wouldn’t make an intro or schedule a follow-up were telling me something their compliments weren’t.