The bad questions are painfully recognizable, and the replacements can improve tomorrow’s interview. Fitzpatrick shows exactly how founders train people to lie politely.
Is The Mom Test worth reading?
The best two-hour correction for founders who mistake compliments for evidence. Its rules make customer conversations dramatically less self-serving, but a clean interview is still qualitative discovery, not proof of market size, willingness to pay, retention, or a viable business.
Why it works, and where it does not
Fitzpatrick’s central rule is to ask about the person’s life rather than your idea. Replace “Would you use this?” with questions about the last time the problem occurred, what they did, what it cost, who was involved, what they have already tried, and why the current workaround remains in place. Avoid compliments, opinions about hypothetical futures, and feature brainstorming because they are cheap for the interviewee and emotionally seductive for the founder. Enter each conversation with three important things you need to learn, listen for concrete facts and contradictions, and take notes without turning the meeting into a pitch. Interest becomes stronger evidence when the person gives something scarce: time, reputation, an introduction, access to data, a pilot step, or money. If every conversation ends in “let us know when it launches,” the process has produced friendliness, not advancement.
The brisk rules can make clean interviewing look like the whole discovery job. Good conversations still do not prove market size, retention, willingness to pay, or product quality.
This is a short, plainspoken startup manual with occasional profanity and examples of failed sales or customer conversations. There is no graphic content.
The Mom Test fixes the social failure at the center of many founder interviews: people are kind, hypothetical questions are easy, and the interviewer desperately wants confirmation. Asking for a recent episode, the actual workaround, the sequence of actions, and the consequences is far more informative than asking whether an invented solution sounds useful. That logic aligns with cognitive interviewing, which probes comprehension, recall, judgment, and response to understand what an answer means and where error enters. It also aligns with a broad warning from behavioral research: self-reports and observed behavior can diverge, especially when an answer is desirable, hard to recall, or weakly observable. The book sometimes slides from “better conversational evidence” toward “reliable validation.” Those are not the same. CDC guidance is explicit that purposive qualitative interviews are useful for identifying problems and understanding response processes, not estimating prevalence or establishing causes. A founder who interviews eight friendly peers has learned about eight selected accounts, not measured a market. Past behavior is usually better evidence than a future promise, but it can still be misremembered, rationalized, or irrelevant to a new product. A strong workaround proves that a problem can matter; it may also prove that the workaround is good enough. Commitment is directional evidence, not a universal ladder: an introduction can reflect generosity, a pilot can be politically cheap, and a letter of intent may cost almost nothing. Money raises the stakes, yet even stated willingness to pay systematically differs from actual purchasing; meta-analytic research finds meaningful hypothetical bias and no single elicitation method that eliminates it across contexts. Customer discovery should therefore generate and refine hypotheses, language, segments, constraints, and test designs. It should not become a ritual that declares product-market fit. Follow interviews with behavior: observation, a concierge workflow, a real data handoff, a paid pilot, a preorder with honest terms, repeated use, renewal, or another commitment whose cost matches the claim you need to test. Finally, interview the people who said no, stopped using the workaround, chose a competitor, lack purchasing authority, or face access barriers. A method designed to defeat leading questions can still produce founder theater if recruitment, note coding, and contrary cases are ignored.
Choose The Innovator’s Dilemma if your problem is not interview technique but an established organization that cannot fund a small, uncertain market.
Show all 8 sourcesHide additional sources
Try the useful part in real life.
Name the three assumptions that could most change the decision: who experiences the problem, what triggers it, how it is handled now, what the current cost is, who controls budget, or why previous attempts failed. Every question must serve one of those uncertainties.
Ask the person to reconstruct the most recent real episode from trigger to outcome. Capture actors, tools, handoffs, delays, workarounds, cost, and consequence. Ask what happened next. Do not introduce your solution until the current system is concrete enough to diagram.
Use two columns after each call: what the person said or did, and what you infer. Tag evidence by segment and learning goal. After five conversations, look for contradictions and disconfirming cases before counting repeated phrases as a theme.
For each promising claim, write the cheapest observable test that would be harder to fake: watch the workflow, request real data, ask for an introduction to the buyer, run a manual service, put a price on a pilot, or measure repeat use. Define in advance what result changes your plan.
- What did this person actually do the last time the problem occurred, and what evidence besides memory supports the account?
- Did I recruit someone with the problem, the user, the buyer, the approver, or merely someone willing to talk to me?
- Which answer would I have interpreted differently if I disliked the idea?
- What contrary case, noncustomer, lost user, or failed workaround have I deliberately sought?
- What behavior or costly commitment must happen next before I call this assumption validated?
Did this review help you decide?
Your answer is saved and helps us decide what to revise next.