The Mom Test

How to talk to customers and learn if your business is a good idea when everyone is lying to you

Rob Fitzpatrick

Business & Startups · 30,400 words · 9 chapters · added 2026-10-27

How to ask customers questions that even your mom can't lie about, so you learn whether your idea is any good.

customer interviewsvalidationproduct discoverystartups

Start reading →

Core Frameworks & Mental Models

1. The Mom Test (Ch 1)

Never ask anyone whether your business is a good idea. The question invites polite lies, and your mom lies the most because she loves you. Ask questions nobody can lie about:

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.

Use it as a filter on every question. If a question is about your idea, the future, or generic habits, rewrite it to ask about a specific recent event or current behaviour. “Would you buy X?” becomes “How do you handle X today, and what did it cost last time?” If they leave without knowing you have an idea, you did it right. Treat customer conversations as bad by default; fixing them is your job.

They own the problem, you own the solution. Don’t tell them what their problem is, and don’t let them tell you what to build. Gather facts about their problems, constraints, and goals, make your own leap to a solution, then confirm it with commitments.

Good questions: “Why do you bother?” · “What are the implications of that?” · “Talk me through the last time that happened.” · “What else have you tried?” · “How are you dealing with it now?” · “Where does the money come from?” (must-ask in B2B) · “Who else should I talk to?” (end every conversation with it) · “Is there anything else I should have asked?” Bad questions: “Do you think it’s a good idea?” · “Would you buy a product which did X?” · “How much would you pay for X?” · “Would you pay X for a product which did Y?” · “What would your dream product do?” is only okay with follow-ups on why.

Key rules of thumb: 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. People stop lying when you ask them for money.

2. Three types of bad data and how to fix each (Ch 2)

Bad data	Looks like	Fix
Compliments	“That’s cool. I love it.”	Deflect: ignore them and ask “How are you dealing with this at the moment?”
Fluff: generics, hypotheticals, and the future	“I usually…”, “I would…”, “I might…”, and the deadliest, “I would definitely buy that.”	Anchor: “When’s the last time that happened? Talk me through it.”
Ideas (feature requests, suggestions)	“Can it sync to Excel?”	Dig: “Why do you want that? What would that let you do? How are you coping without it?”

Dig into strong emotions the same way: “Tell me more about that.” “What makes it so awful?”

You also create bad data yourself, in three ways. Fishing for compliments means seeking approval deliberately. The Pathos Problem means exposing your ego, so they protect you. Being pitchy means holding them hostage until they say something nice. If you slip into pitch mode, apologize and return to what they were saying. Watch for these tells back at the office: “That meeting went really well,” “Everybody I’ve talked to loves the idea.” Compliments are the fool’s gold of customer learning. Ideas and feature requests should be understood, but not obeyed. The more you’re talking, the worse you’re doing.

3. Ask important questions (Ch 3)

• A question is important if its answer could change or disprove your business. You should be terrified of at least one of the questions you’re asking in every conversation. Find these questions by imagining failure (why did it happen?) and huge success (what had to be true?).
• Love bad news. A lukewarm “meh” is reliable data that they don’t care. Don’t pitch harder. Ask why, thank them, and leave. There’s more reliable information in a “meh” than a “Wow!”
• Look before you zoom. Avoid the premature zoom, which means asking about a specific problem before confirming that they care about the area. Start broad (“What are your big goals and focuses right now?”) and zoom in only once they raise the topic. To tell a painkiller from a vitamin, use the does-this-problem-matter questions: Do they spend money or make money on it? Is it in their top 3? Are they actively looking for a solution?
• Gaze upon the elephant. Check every failure point, and separate product risk (Can I build it? Can I grow it?) from customer/market risk (Do they want it? Will they pay me? Are there lots of them?). “If you could get me more gigs, I’d pay you” moves the risk onto your product and validates nothing.
• Prepare your list of 3 big questions for each type of person, decided calmly with your team and updated as you learn. You always need a list of your 3 big questions.

4. Keep it casual (Ch 4)

Learning about problems works better as a quick chat than as a formal meeting. Keep Steve Blank’s separation of problem, solution, and sales conversations, but make the problem conversation a chat. The Meeting Anti-Pattern is putting every customer conversation opportunity into a calendar block. Instead, ask your key question on the spot, such as “How did you end up getting this gig?” Typical lengths: about 5 min to learn whether a problem matters, 10–15 min for workflow, 1 hour or more for industry detail, and about 30 min for a sales meeting with a product. If it feels like they’re doing you a favour by talking to you, it’s probably too formal. Give as little information as possible about your idea while still nudging the discussion in a useful direction.

5. Commitment and advancement (Ch 5)

Once you show the idea, compliments come back, so cut through them by asking for something. Commitment: they give up something they value (time, reputation, or money). Advancement: they move to the next step of your real-world funnel. Meetings either succeed or fail, and there’s no such thing as one that “went well”. Rejection is good data; not asking is the real failure.

Currencies: time (a next meeting with goals, wireframe feedback, a real trial); reputation risk (an intro to peers, the boss, or a decision maker; a testimonial or case study); cash (a letter of intent, a pre-order, a deposit). The more they’re giving up, the more seriously you can take what they’re saying.

Meeting endings: “Can I buy the prototype?” is great. “What are the next steps?” and “When can you come back to talk to the rest of the team?” are good. “When can we start the trial?” is maybe good, so check what the trial costs them. “Let me know when it launches,” “I’ll intro you when you’re ready,” and “I would definitely buy that” are bad, so convert them into a concrete commitment today. Zombie leads keep meeting and saying nice things but never buy. It’s not a real lead until you’ve given them a concrete chance to reject you. Look for earlyvangelists: people who have the problem, know they have it, have the budget, and have already cobbled together their own solution.

6. Find and frame conversations (Ch 6)

Start with cold outreach only to get warm intros; the goal of cold conversations is to stop having them. Better options: bring customers to you (organise meetups, teach, blog), seize chance encounters, and ask everyone for intros (“7 degrees of bacon”), including advisors, professors, and investors. When a meeting is unavoidable, frame it with VFWPA, “Very Few Wizards Properly Ask”: Vision (the problem you’re solving, not your idea) / Framing (your stage, nothing to sell) / Weakness (where you’re stuck) / Pedestal (why they in particular can help) / Ask. Then take control of the meeting. Use the advisory flip: go in looking for advisors, not customers. Prefer meeting in person. Keep having conversations until you stop hearing new stuff. If you’ve had more than 10 conversations and answers are still all over the map, your segment is too vague.

7. Choose your customers (Ch 7)

Startups don’t starve, they drown in options. A vague segment means you’re having one conversation each with 20 different customer types. Use Customer Slicing: repeatedly ask “Within this group, which type of person would want it most, and why?” until you reach a who-where pair, meaning you know where to find them. Pick your starting slice by how profitable or big it is, how easy it is to reach, and how rewarding it is personally. Watch for missed segments and stakeholders (parents of kids, partners, buyers inside the company). If you aren’t finding consistent problems and goals, you don’t have a specific enough customer segment.

8. Run the process (Ch 8)

Avoid the learning bottleneck, where one person holds all customer knowledge and wins every argument with “the customer said so.”

• Before: choose a focused, findable segment. Set your big 3 questions with the team. Decide which commitments to push for. Write down your best guesses about what they care about (up to an hour). Do desk research first.
• During: frame the conversation, keep it casual, and pass The Mom Test. Deflect, anchor, and dig. Take notes. Press for commitment when relevant.
• After: review notes and exact quotes with the team. Update your beliefs. Choose the next 3 questions.

Two people per meeting works best: one talks and one takes notes. Use the signal symbols: :) excited, :( angry, :| embarrassed, ☇ pain, ⨅ goal, ☐ obstacle, ⤴ workaround, ^ context, ☑ feature request or purchasing criteria, ＄ money, ♀ person or company, ☆ follow-up. Founders can’t outsource this learning. Keep it fast: an hour of prep, a week or two of conversations, then give them something to commit to. The big prep question is “What do we want to learn from these guys?”

Signs you’re going through the motions: you talk more than they do; they compliment you; you pitched without next steps; you have no notes, or didn’t review them with the team; an unexpected answer changed nothing; no question scared you; you aren’t sure what you’re trying to learn.

9. Hack it (Ch 9)

A good meeting produces facts, commitment, or advancement. Process helps, but don’t get stuck in it. If one phone call would answer the question, make the call (the Gordian Knot).

---

Chapter Index

#	Title	Key Frameworks
ch01	The Mom Test (+ Introduction)	The Mom Test’s 3 rules, good/bad question drill, they own the problem / you own the solution
ch02	Avoiding bad data	Compliments/fluff/ideas, deflect/anchor/dig, Pathos Problem, cutting off pitches
ch03	Asking important questions	Scary questions, love bad news, premature zoom, product vs market risk, list of 3
ch04	Keeping it casual	Casual chats, Meeting Anti-Pattern, conversation length by stage
ch05	Commitment and advancement	Meetings succeed or fail, currencies, good/bad meeting drill, earlyvangelists
ch06	Finding conversations	Cold vs warm, bringing them to you, VFWPA, advisory flip, how many meetings
ch07	Choosing your customers	Segmentation, Customer Slicing, who-where pairs, talking to the wrong people
ch08	Running the process	Learning bottleneck, prep/review, signal symbols, the full process checklist
ch09	Conclusion and cheatsheet	Hack it, results of a good meeting, the author’s summary lists

Topic Index

• 7 degrees of bacon → ch06
• Advancement → ch05, ch09
• Advisors / advisory flip → ch06
• Anchoring fluff → ch02
• Approval-seeking / fishing for compliments → ch02
• B2B buying process / budget owner → ch01, ch05, ch07
• Cold calls and cold outreach → ch06
• Commitment / currencies (time, reputation, cash) → ch05
• Complainer vs customer → ch02
• Compliments, deflecting → ch02, ch05
• Conversation length → ch04
• Customer Development (Steve Blank), relation to → ch01, ch04
• Customer Slicing / segmentation → ch07
• Digging (feature requests, emotions) → ch02
• Earlyvangelists → ch05
• Elephant / failure points → ch01, ch03
• Feature requests → ch01, ch02
• Formality, symptoms of → ch04
• Good question / bad question → ch01
• Good meeting / bad meeting → ch05
• Hack it (Gordian Knot) → ch09
• Important / scary questions → ch03
• Keeping it casual / Meeting Anti-Pattern → ch04
• Landing pages → ch06
• Learning bottleneck → ch08
• List of 3 → ch03, ch08
• Love bad news / lukewarm responses → ch03
• Meetups, teaching, blogging → ch06
• Note-taking / signal symbols → ch08
• Painkiller vs vitamin → ch03
• Pathos Problem → ch02
• Phone vs in person → ch06
• Pitch mode, recovering from → ch02
• Premature zoom → ch03
• Prepping and reviewing → ch08
• Price anchor / pricing signals → ch01
• Product risk vs customer/market risk → ch03
• Talking to the wrong people → ch07
• The Mom Test (3 rules) → ch01, ch09
• Trials, raising their cost → ch05
• VFWPA meeting framing → ch06, ch09
• Warm intros → ch06
• Who should attend → ch08
• Who-where pair → ch07
• Zombie leads → ch05

Scope & Limits

This skill covers the book’s content only: synthesized summaries, not the book text. It does not cover the wider Customer Development process (see Steve Blank’s The Four Steps to the Epiphany and The Startup Owner’s Manual) or pricing, marketing, and sales methods beyond what the book discusses. For topics beyond this book, check related skills or ask the agent directly.