Name: The Mom Test
Author: Rob Fitzpatrick

Key Ideas

1. The Mom Test: Why Opinions Lie and Facts Don't

The book's namesake concept is devastatingly simple: if you ask your mom whether your new business idea is good, she will say yes — because she loves you, not because the idea is good. This isn't just about moms; it's about every human being you talk to. When you ask people "Do you think this is a good idea?" you are asking for their opinion, and opinions are cheap, unreliable, and heavily biased by social desirability. People want to be encouraging, avoid conflict, and appear smart — none of which leads to honest feedback about your business.

The core insight is that you should never ask anyone whether your idea is good. Instead, talk about their life, their problems, and their past behavior. Facts about how people actually behave are infinitely more valuable than their predictions about how they might behave. If someone says "I would definitely buy that," it means almost nothing. If they can show you how they've already spent money or time solving a related problem, that's gold.

Practical application: Before any customer conversation, replace every opinion-seeking question with a fact-seeking one. Instead of "Would you use this?" ask "When was the last time you dealt with [problem]?" Instead of "Do you think this would work?" ask "How are you currently solving [problem]?" The shift from hypotheticals to concrete past behavior is the single most important change you can make.

2. The Three Rules of The Mom Test

Fitzpatrick distills the philosophy into three concrete rules that should govern every customer conversation. Rule one: Talk about their life instead of your idea. The moment you mention your solution, the conversation shifts from facts to opinions. People will evaluate your idea rather than sharing their actual experiences. Rule two: Ask about specifics in the past instead of generics or opinions about the future. "How do you currently handle X?" beats "Would you handle X differently?" every time. Rule three: Talk less and listen more. Your job is to gather information, not to pitch.

These rules work because they short-circuit the natural human tendency to be polite and encouraging. When you ask someone about their own life and experiences, they become a reliable narrator. They're not guessing about the future or trying to protect your feelings — they're simply recounting what happened. This data is the foundation of every good business decision.

Practical application: Write out your interview questions and run them through the Mom Test filter. For each question, ask yourself: "Could someone give a flattering but useless answer to this?" If yes, rewrite it. The three rules should be printed and taped to your notebook before every customer conversation.

3. The Danger of Pitching Too Early

One of the most common mistakes founders make is treating customer conversations as pitch sessions. When you pitch, you activate a completely different dynamic: the listener shifts into evaluation mode, which triggers social desirability bias. They start thinking about whether they should encourage you, whether they want to seem interested, or whether they want to end the conversation politely. None of this produces useful data.

Fitzpatrick argues that you should almost never pitch during learning conversations. The purpose of these conversations is to understand the customer's world — their problems, their current solutions, their workflow, and their constraints. Pitching contaminates the data. Even a brief mention of your idea can color every subsequent answer. The customer starts answering through the lens of your solution rather than describing their actual experience.

Practical application: Separate your conversations into two distinct types: learning conversations and pitching conversations. In learning conversations, your idea doesn't exist. You are a researcher, not a founder. Only after you've gathered enough evidence to confirm the problem and understand the market should you switch to pitching mode — and even then, the pitch should be tailored to what you've learned.

4. Finding the Right People to Talk To

Not all conversations are created equal. Talking to the wrong people — people who don't actually have the problem you're investigating — is worse than talking to no one at all, because it gives you false confidence. Fitzpatrick emphasizes the importance of finding "the right people" — those who are experiencing the problem right now, have tried to solve it, and have the budget or authority to do something about it.

The book provides practical strategies for finding these people: going where they already congregate (conferences, online communities, industry events), asking for introductions through your network, and using cold outreach that demonstrates genuine curiosity rather than a sales agenda. The key is to make the conversation about them, not about you. If your outreach email reads like a pitch, you'll attract people who want to be pitched to — not people who want to share their problems.

Practical application: Create a profile of your ideal conversation partner: what they do, where they hang out, what they care about. Then go to those places with genuine curiosity. Your outreach should be about learning from their expertise, not about getting them to look at your product. "I'm researching how teams handle X and your experience at [company] seems really relevant" works far better than "I'd love to show you my new product."

5. Commitment and Advancement: Moving Beyond Nice Conversations

A friendly conversation that ends with "That sounds great, keep me posted!" is a failure, not a success. Fitzpatrick introduces the concept of "commitment and advancement" — the idea that every conversation should move the relationship forward in a concrete, measurable way. If someone isn't willing to commit some form of resources (time, money, reputation, or effort), they're not actually interested in your solution, regardless of what they say.

The forms of commitment range from soft (giving you an introduction, letting you observe their workflow) to hard (signing a letter of intent, making a pre-order, committing to a pilot). The key insight is that commitment is a much better signal than enthusiasm. Someone who says "I love it!" but won't give you 15 minutes of their time next week is telling you everything you need to know. Someone who says "I'm not sure, but let me introduce you to my team" is showing real interest.

Practical application: Before every conversation, define what "advancement" looks like. What would be a concrete next step that requires the other person to invest something? After the conversation, evaluate whether you achieved that advancement. If you consistently leave conversations with compliments but no commitments, you have a problem with either your idea or your conversation technique.

6. The Problem Interview: Proving the Problem Exists

Before you can validate a solution, you must validate the problem. Fitzpatrick outlines a structured approach to problem interviews that systematically tests whether the problem you think exists actually exists, whether it matters to people, and whether it matters enough for them to pay for a solution. The problem interview follows a specific flow: start with broad questions about the person's life and work, narrow down to the specific area where you suspect the problem lives, then dig deep into how they currently handle it.

The critical test is whether the problem is important enough. Many problems exist in theory but don't cause enough pain for anyone to change their behavior or spend money. Fitzpatrick suggests looking for three signals: the person is already trying to solve the problem (even with bad solutions), the problem costs them significant time or money, and they have the authority and budget to do something about it. If all three signals are present, you may have a real business opportunity.

Practical application: Structure your problem interviews in three phases: (1) Broad context — "Tell me about how you handle [area]," (2) Specific problem — "What's the hardest part about [specific process]?," (3) Validation — "When was the last time this happened? How much time/money did it cost?" If people can't recall a specific instance or quantify the cost, the problem probably isn't painful enough.

7. Avoiding the "Idea Smashing" Trap

While The Mom Test is primarily about getting honest feedback, Fitzpatrick also warns against the opposite extreme: being so committed to your idea that you dismiss all negative feedback. He calls this "idea smashing" — the tendency to explain away every piece of contradictory evidence. If every person you talk to says they wouldn't use your product, and your response is "they just don't understand it yet," you're idea smashing.

The antidote is to set clear criteria for success and failure before you start talking to customers. What would make you abandon the idea? What specific evidence would convince you that the problem isn't real or the market isn't there? If you can't answer these questions, you're not doing research — you're doing confirmation bias. The whole point of customer conversations is to discover the truth, not to confirm what you already believe.

Practical application: Before your first customer conversation, write down your three riskiest assumptions and what evidence would falsify them. After each conversation, honestly assess whether the data supports or contradicts your assumptions. If the evidence is consistently negative, have the courage to pivot or kill the idea. A failed idea discovered early is infinitely cheaper than one discovered after months of development.

Frameworks and Models

The Mom Test Rules

A three-rule framework for conducting effective customer conversations that yield reliable data instead of flattering opinions:

Rule 1 — Talk about their life, not your idea: Never introduce your solution during a learning conversation. Keep the focus entirely on the other person's experiences, problems, and current behaviors.
Rule 2 — Ask about specifics in the past, not generics or opinions about the future: Replace "Would you...?" with "When did you last...?" Past behavior is the best predictor of future behavior.
Rule 3 — Talk less, listen more: Your role is to gather information, not to persuade. The more you talk, the less you learn.

The Commitment Spectrum

A framework for evaluating how genuinely interested someone is based on what they're willing to invest, ranging from cheap talk to hard commitments:

Level	Signal	Reliability
Compliments	"That sounds great!"	Very low — costs nothing
Soft commitment	Introduction, meeting, observation	Moderate — costs time/reputation
Hard commitment	Pre-order, pilot, letter of intent	High — costs money or resources

The key principle: never mistake compliments for validation. Only commitment signals real interest.

The Problem Interview Flow

A structured approach to validating that a problem exists before building a solution:

Step 1 — Broad context: Ask about the person's life and work in the relevant area. Understand their world before zooming in.
Step 2 — Specific problem: Narrow down to the particular problem you're investigating. "What's the hardest part about...?"
Step 3 — Depth and validation: Dig into specifics. When did it last happen? How much did it cost? What have they tried?
Step 4 — Importance check: Is this problem important enough to spend money on? Look for existing solutions, quantifiable costs, and decision-making authority.

Pre-Mortem Assumption Testing

A framework for avoiding confirmation bias by defining falsification criteria before conducting research:

Step 1 — List your three riskiest assumptions about the problem, the customer, and the market.
Step 2 — Define what would falsify each assumption. What specific evidence would prove you wrong?
Step 3 — Conduct conversations seeking disconfirming evidence, not just confirming evidence.
Step 4 — Evaluate honestly. If the data contradicts your assumptions, pivot or kill the idea.

Key Quotes

"The Mom Test: Talk about their life instead of your idea. Ask about specifics in the past instead of generics or opinions about the future. Talk less and listen more." — Rob Fitzpatrick

"You aren't allowed to tell them what their problem is, and in return, they aren't allowed to tell you what you should build. They own the problem; you own the solution." — Rob Fitzpatrick

"If you've mentioned your idea, everyone will tell you it's great. They have to. It's the only polite option." — Rob Fitzpatrick

"A conversation which ends with 'That sounds great, keep me posted!' is a failure, not a success." — Rob Fitzpatrick

"The best way to hear what someone really thinks is to ask about their past behavior instead of their future intentions." — Rob Fitzpatrick

Connections with Other Books

the-lean-startup: Both books emphasize the importance of validated learning over assumptions. Where The Lean Startup provides the macro framework of Build-Measure-Learn, The Mom Test provides the micro-level technique for the "Learn" phase — how to actually talk to customers and get reliable data.
thinking-fast-and-slow: Kahneman's research on cognitive biases underpins why The Mom Test works. People's "System 1" responses to direct questions about ideas are unreliable due to social desirability bias and optimism bias. Asking about past behavior engages "System 2" and produces more accurate data.
the-innovators-dilemma: Christensen's concept of "jobs to be done" aligns with Fitzpatrick's emphasis on understanding the customer's actual problem rather than pitching a solution. Both argue that customers hire products to do specific jobs, and you can only discover those jobs through careful inquiry.
zero-to-one: Thiel's emphasis on building something genuinely new requires deep customer understanding, which The Mom Test provides the methodology for. While Thiel focuses on the strategic question of what to build, Fitzpatrick focuses on the tactical question of how to validate that you're building the right thing.
crossing-the-chasm: Moore's framework for technology adoption depends on understanding early adopters' specific problems and contexts. The Mom Test's interview techniques are essential for the customer discovery phase that precedes crossing the chasm.

When to Use This Knowledge

When a founder or entrepreneur is preparing for customer discovery interviews and wants to avoid common mistakes that lead to false positives
When someone is about to launch a new product or feature and needs to validate the problem before investing in development
When a team is debating whether to pivot based on customer feedback and needs a framework for evaluating the quality of that feedback
When someone asks how to conduct effective user research or customer interviews that produce actionable insights
When a startup is struggling with the "everyone says they love it but nobody buys it" problem
When someone needs to distinguish between genuine customer interest and polite encouragement
When a product manager wants to validate assumptions about user needs before committing engineering resources
When someone is designing a customer development process and needs a structured approach to learning conversations

# The Mom Test ## Key Ideas ### 1. The Mom Test: Why Opinions Lie and Facts Don't The book's namesake concept is devastatingly simple: if you ask your mom whether your new business idea is good, she will say yes — because she loves you, not because the idea is good. This isn't just about moms; it's about every human being you talk to. When you ask people "Do you think this is a good idea?" you are asking for their opinion, and opinions are cheap, unreliable, and heavily biased by social desirability. People want to be encouraging, avoid conflict, and appear smart — none of which leads to honest feedback about your business. The core insight is that you should never ask anyone whether your idea is good. Instead, talk about their life, their problems, and their past behavior. Facts about how people actually behave are infinitely more valuable than their predictions about how they might behave. If someone says "I would definitely buy that," it means almost nothing. If they can show you how they've already spent money or time solving a related problem, that's gold. **Practical application:** Before any customer conversation, replace every opinion-seeking question with a fact-seeking one. Instead of "Would you use this?" ask "When was the last time you dealt with [problem]?" Instead of "Do you think this would work?" ask "How are you currently solving [problem]?" The shift from hypotheticals to concrete past behavior is the single most important change you can make. ### 2. The Three Rules of The Mom Test Fitzpatrick distills the philosophy into three concrete rules that should govern every customer conversation. Rule one: Talk about their life instead of your idea. The moment you mention your solution, the conversation shifts from facts to opinions. People will evaluate your idea rather than sharing their actual experiences. Rule two: Ask about specifics in the past instead of generics or opinions about the future. "How do you currently handle X?" beats "Would you handle X differently?" every time. Rule three: Talk less and listen more. Your job is to gather information, not to pitch. These rules work because they short-circuit the natural human tendency to be polite and encouraging. When you ask someone about their own life and experiences, they become a reliable narrator. They're not guessing about the future or trying to protect your feelings — they're simply recounting what happened. This data is the foundation of every good business decision. **Practical application:** Write out your interview questions and run them through the Mom Test filter. For each question, ask yourself: "Could someone give a flattering but useless answer to this?" If yes, rewrite it. The three rules should be printed and taped to your notebook before every customer conversation. ### 3. The Danger of Pitching Too Early One of the most common mistakes founders make is treating customer conversations as pitch sessions. When you pitch, you activate a completely different dynamic: the listener shifts into evaluation mode, which triggers social desirability bias. They start thinking about whether they should encourage you, whether they want to seem interested, or whether they want to end the conversation politely. None of this produces useful data. Fitzpatrick argues that you should almost never pitch during learning conversations. The purpose of these conversations is to understand the customer's world — their problems, their current solutions, their workflow, and their constraints. Pitching contaminates the data. Even a brief mention of your idea can color every subsequent answer. The customer starts answering through the lens of your solution rather than describing their actual experience. **Practical application:** Separate your conversations into two distinct types: learning conversations and pitching conversations. In learning conversations, your idea doesn't exist. You are a researcher, not a founder. Only after you've gathered enough evidence to confirm the problem and understand the market should you switch to pitching mode — and even then, the pitch should be tailored to what you've learned. ### 4. Finding the Right People to Talk To Not all conversations are created equal. Talking to the wrong people — people who don't actually have the problem you're investigating — is worse than talking to no one at all, because it gives you false confidence. Fitzpatrick emphasizes the importance of finding "the right people" — those who are experiencing the problem right now, have tried to solve it, and have the budget or authority to do something about it. The book provides practical strategies for finding these people: going where they already congregate (conferences, online communities, industry events), asking for introductions through your network, and using cold outreach that demonstrates genuine curiosity rather than a sales agenda. The key is to make the conversation about them, not about you. If your outreach email reads like a pitch, you'll attract people who want to be pitched to — not people who want to share their problems. **Practical application:** Create a profile of your ideal conversation partner: what they do, where they hang out, what they care about. Then go to those places with genuine curiosity. Your outreach should be about learning from their expertise, not about getting them to look at your product. "I'm researching how teams handle X and your experience at [company] seems really relevant" works far better than "I'd love to show you my new product." ### 5. Commitment and Advancement: Moving Beyond Nice Conversations A friendly conversation that ends with "That sounds great, keep me posted!" is a failure, not a success. Fitzpatrick introduces the concept of "commitment and advancement" — the idea that every conversation should move the relationship forward in a concrete, measurable way. If someone isn't willing to commit some form of resources (time, money, reputation, or effort), they're not actually interested in your solution, regardless of what they say. The forms of commitment range from soft (giving you an introduction, letting you observe their workflow) to hard (signing a letter of intent, making a pre-order, committing to a pilot). The key insight is that commitment is a much better signal than enthusiasm. Someone who says "I love it!" but won't give you 15 minutes of their time next week is telling you everything you need to know. Someone who says "I'm not sure, but let me introduce you to my team" is showing real interest. **Practical application:** Before every conversation, define what "advancement" looks like. What would be a concrete next step that requires the other person to invest something? After the conversation, evaluate whether you achieved that advancement. If you consistently leave conversations with compliments but no commitments, you have a problem with either your idea or your conversation technique. ### 6. The Problem Interview: Proving the Problem Exists Before you can validate a solution, you must validate the problem. Fitzpatrick outlines a structured approach to problem interviews that systematically tests whether the problem you think exists actually exists, whether it matters to people, and whether it matters enough for them to pay for a solution. The problem interview follows a specific flow: start with broad questions about the person's life and work, narrow down to the specific area where you suspect the problem lives, then dig deep into how they currently handle it. The critical test is whether the problem is important enough. Many problems exist in theory but don't cause enough pain for anyone to change their behavior or spend money. Fitzpatrick suggests looking for three signals: the person is already trying to solve the problem (even with bad solutions), the problem costs them significant time or money, and they have the authority and budget to do something about it. If all three signals are present, you may have a real business opportunity. **Practical application:** Structure your problem interviews in three phases: (1) Broad context — "Tell me about how you handle [area]," (2) Specific problem — "What's the hardest part about [specific process]?," (3) Validation — "When was the last time this happened? How much time/money did it cost?" If people can't recall a specific instance or quantify the cost, the problem probably isn't painful enough. ### 7. Avoiding the "Idea Smashing" Trap While The Mom Test is primarily about getting honest feedback, Fitzpatrick also warns against the opposite extreme: being so committed to your idea that you dismiss all negative feedback. He calls this "idea smashing" — the tendency to explain away every piece of contradictory evidence. If every person you talk to says they wouldn't use your product, and your response is "they just don't understand it yet," you're idea smashing. The antidote is to set clear criteria for success and failure before you start talking to customers. What would make you abandon the idea? What specific evidence would convince you that the problem isn't real or the market isn't there? If you can't answer these questions, you're not doing research — you're doing confirmation bias. The whole point of customer conversations is to discover the truth, not to confirm what you already believe. **Practical application:** Before your first customer conversation, write down your three riskiest assumptions and what evidence would falsify them. After each conversation, honestly assess whether the data supports or contradicts your assumptions. If the evidence is consistently negative, have the courage to pivot or kill the idea. A failed idea discovered early is infinitely cheaper than one discovered after months of development. ## Frameworks and Models ### The Mom Test Rules A three-rule framework for conducting effective customer conversations that yield reliable data instead of flattering opinions: - **Rule 1 — Talk about their life, not your idea:** Never introduce your solution during a learning conversation. Keep the focus entirely on the other person's experiences, problems, and current behaviors. - **Rule 2 — Ask about specifics in the past, not generics or opinions about the future:** Replace "Would you...?" with "When did you last...?" Past behavior is the best predictor of future behavior. - **Rule 3 — Talk less, listen more:** Your role is to gather information, not to persuade. The more you talk, the less you learn. ### The Commitment Spectrum A framework for evaluating how genuinely interested someone is based on what they're willing to invest, ranging from cheap talk to hard commitments: | Level | Signal | Reliability | |-------|--------|-------------| | Compliments | "That sounds great!" | Very low — costs nothing | | Soft commitment | Introduction, meeting, observation | Moderate — costs time/reputation | | Hard commitment | Pre-order, pilot, letter of intent | High — costs money or resources | The key principle: never mistake compliments for validation. Only commitment signals real interest. ### The Problem Interview Flow A structured approach to validating that a problem exists before building a solution: - **Step 1 — Broad context:** Ask about the person's life and work in the relevant area. Understand their world before zooming in. - **Step 2 — Specific problem:** Narrow down to the particular problem you're investigating. "What's the hardest part about...?" - **Step 3 — Depth and validation:** Dig into specifics. When did it last happen? How much did it cost? What have they tried? - **Step 4 — Importance check:** Is this problem important enough to spend money on? Look for existing solutions, quantifiable costs, and decision-making authority. ### Pre-Mortem Assumption Testing A framework for avoiding confirmation bias by defining falsification criteria before conducting research: - **Step 1 — List your three riskiest assumptions** about the problem, the customer, and the market. - **Step 2 — Define what would falsify each assumption.** What specific evidence would prove you wrong? - **Step 3 — Conduct conversations seeking disconfirming evidence,** not just confirming evidence. - **Step 4 — Evaluate honestly.** If the data contradicts your assumptions, pivot or kill the idea. ## Key Quotes > "The Mom Test: Talk about their life instead of your idea. Ask about specifics in the past instead of generics or opinions about the future. Talk less and listen more." — Rob Fitzpatrick > "You aren't allowed to tell them what their problem is, and in return, they aren't allowed to tell you what you should build. They own the problem; you own the solution." — Rob Fitzpatrick > "If you've mentioned your idea, everyone will tell you it's great. They have to. It's the only polite option." — Rob Fitzpatrick > "A conversation which ends with 'That sounds great, keep me posted!' is a failure, not a success." — Rob Fitzpatrick > "The best way to hear what someone really thinks is to ask about their past behavior instead of their future intentions." — Rob Fitzpatrick ## Connections with Other Books - [[the-lean-startup]]: Both books emphasize the importance of validated learning over assumptions. Where The Lean Startup provides the macro framework of Build-Measure-Learn, The Mom Test provides the micro-level technique for the "Learn" phase — how to actually talk to customers and get reliable data. - [[thinking-fast-and-slow]]: Kahneman's research on cognitive biases underpins why The Mom Test works. People's "System 1" responses to direct questions about ideas are unreliable due to social desirability bias and optimism bias. Asking about past behavior engages "System 2" and produces more accurate data. - [[the-innovators-dilemma]]: Christensen's concept of "jobs to be done" aligns with Fitzpatrick's emphasis on understanding the customer's actual problem rather than pitching a solution. Both argue that customers hire products to do specific jobs, and you can only discover those jobs through careful inquiry. - [[zero-to-one]]: Thiel's emphasis on building something genuinely new requires deep customer understanding, which The Mom Test provides the methodology for. While Thiel focuses on the strategic question of what to build, Fitzpatrick focuses on the tactical question of how to validate that you're building the right thing. - [[crossing-the-chasm]]: Moore's framework for technology adoption depends on understanding early adopters' specific problems and contexts. The Mom Test's interview techniques are essential for the customer discovery phase that precedes crossing the chasm. ## When to Use This Knowledge - When a founder or entrepreneur is preparing for customer discovery interviews and wants to avoid common mistakes that lead to false positives - When someone is about to launch a new product or feature and needs to validate the problem before investing in development - When a team is debating whether to pivot based on customer feedback and needs a framework for evaluating the quality of that feedback - When someone asks how to conduct effective user research or customer interviews that produce actionable insights - When a startup is struggling with the "everyone says they love it but nobody buys it" problem - When someone needs to distinguish between genuine customer interest and polite encouragement - When a product manager wants to validate assumptions about user needs before committing engineering resources - When someone is designing a customer development process and needs a structured approach to learning conversations