What does The Mom Test teach about user interviews?

Rob Fitzpatrick’s The Mom Test is the rare business book that is actually a method — short enough to read in an evening, specific enough to use the next morning. Here is the whole apparatus.

The premise: everyone lies, politely

The book’s title is the standard it sets: your interview questions should be designed so that even your mother — the person most motivated to make you feel good — couldn’t answer them with comforting falsehoods. The insight is that bad interview data isn’t caused by dishonest people; it’s caused by questions that make politeness and truth diverge. “Do you like my idea?” forces a kind person to lie. “What did you do the last time you hit this problem?” doesn’t.

The three rules

1. Talk about their life, not your idea. The interview is about their workflow, their costs, their attempts to fix things. The moment you pitch, every subsequent answer measures niceness, not need.
2. Ask about specifics in the past, not generics or the future. “Would you ever…?”, “Do you usually…?”, “Would you pay for…?” all invite hypothetical selves who are more organized, more diligent, and freer with money than any real human. The corrective: “When did this last happen? Walk me through it. What did it cost? What did you try?”
3. Talk less, listen more. You cannot learn while you are talking. Every minute you spend explaining is a minute of data you didn’t collect.

The taxonomy of bad data

Three contaminants show up in every interview, and each has a standard response:

• Compliments (“This is so cool!”) — worthless. Deflect and redirect: don’t write them down, don’t repeat them to your team, get back to their life.
• Fluff — generic claims (“I always…”), future promises (“I would definitely…”), hypotheticals (“I might…”). Anchor fluff to reality: “When did that last actually happen?”
• Ideas (“You should add…!”) — flattering, dangerous, and not your roadmap. Dig for the motivation underneath: “Why do you want that? What would it let you do? How are you coping without it?” The request is rarely the requirement.

There’s a fourth contaminant the book is blunt about: you. Founders fish for validation, pitch when nervous, and talk formally when they should be casual. The data is only as good as your discipline.

Signals that actually mean something

• They’ve already tried to solve it. Googled, built a spreadsheet, paid for a workaround. This is the strongest single signal in the method — people with burning problems leave evidence. Its absence is disqualifying: “If they haven’t looked for ways of solving it already, they’re not going to look for yours.”
• Specificity and emotion. Real frustration over a specific recent incident beats agreeable generalities about “pain points.”
• Commitment. The interview’s exit measurement. A meeting “went well” only if it ended with the other person giving up something of value: scheduled time with an agenda, an introduction to someone with budget, or money (pre-order, LOI, deposit). “Sounds great, keep me posted” is a rejection delivered politely.

Practical mechanics

• Prep three big questions. Before any conversation, decide with your team the three things you most need to learn. Terrifying questions — the ones that could kill the idea — go first, not last.
• Keep it casual. Early learning conversations don’t need a lab and a consent form; the best ones feel like normal conversation about their work. Formality invites performance.
• Take notes in their words, not your interpretations. “Spends ~3 hrs/week reconciling exports by hand” is data; “loves the idea” is not.
• Review with the team. An interview that isn’t shared and acted on is a coffee chat.

The one-line summary

Stop asking people to predict their future behavior or judge your idea; start collecting documented evidence of their past behavior and present commitments. Everything in the book is a technique for making that swap stick under social pressure — and the discipline transfers far beyond startups, to any situation where people would rather be kind to you than accurate.