The Mom Test: How to talk to customers & learn if your business is a good idea when everyone is lying to you

21 highlighters806 highlights12 notes4.7 / 5

+11

Read on Kindle Listen on Audible

About This Book

The Mom Test is a practical guide to getting honest customer feedback without being misled by politeness, compliments, or hypothetical enthusiasm. Its core idea is simple: people will often lie when they think you want encouragement, so the way to learn the truth is to stop pitching your idea and start asking about their real life.

The book revolves around three memorable rules:

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

From the highlighted passages, the book’s main argument is that early customer conversations are useful only when they produce concrete facts: what people currently do, what it costs them, what they’ve already tried, how often the problem happens, and what the real implications are. Questions like “What happened last time?”, “How are you dealing with it now?”, “What else have you tried?”, and “Why do you bother?” reveal whether a problem is painful enough to matter.

A major theme is separating real demand from noise. Readers repeatedly highlighted the rule that if someone hasn’t already tried to solve the problem, they probably won’t buy a new solution. Likewise, opinions, compliments, and feature requests are weak signals unless backed by behavior, budget, or urgency. Customers own the problem; founders own the solution.

The book also expands beyond interview technique into execution. It advises founders to define a focused, findable customer segment, prepare their three biggest learning questions, keep conversations casual, and end with commitment or advancement rather than vague positivity. Time, reputation, and cash are treated as meaningful currencies.

Overall, the structure moves from asking better questions, to avoiding bad data, to validating seriousness through commitments, and finally to finding the right people to learn from in the first place.

Key Takeaways

1.Opinions are weak evidence; real learning comes from specific past behavior, existing workarounds, and actual constraints.
2.If customers have not already tried to solve a problem, it is usually a sign the problem is not important enough to buy a solution for.
3.The best interview questions explore workflow, goals, costs, consequences, and motivations rather than asking what product to build.
4.Customers should define their problems, while you as the founder remain responsible for proposing and testing the solution.
5.A good sign of seriousness is commitment in time, reputation, or cash, not a flattering reaction to your concept.
6.Broad customer segments create noisy feedback; sharper who-where segmentation makes learning faster and more reliable.
7.Casual, focused conversations often work better than formal interviews because they reduce politeness, pitching, and scripted answers.

Top Highlights

Rule of thumb: If they haven't looked for ways of solving it already, they're not going to look for (or buy) yours.

Highlighted by 9 people

The questions to ask are about your customers’ lives: their problems, cares, constraints, and goals. You humbly and honestly gather as much information about them as you can and then take your own visionary leap to a solution. Once you’ve taken the leap, you confirm that it’s correct (and refine it) through Commitment & Advancement, which we’ll look at in Chapter 5.

Highlighted by 9 people · 1 left notes

Rule of thumb: People know what their problems are, but they don’t know how to solve those problems.

Highlighted by 8 people

"What are the implications of that?" Good question. This distinguishes between I-will-pay-to-solve-that problems and thats-kind-of-annoying-but-I-can-deal-with-it “problems”. Some problems have big, costly implications. Others exist but don’t actually matter. It behooves you to find out which is which. It also gives you a good pricing signal. I once had someone keep describing the workflow we were fixing with emotionally loaded terms like “DISASTER”, accompanied by much yelling and arm waving. But when I asked him what the implications were, he sort of shrugged and said “Oh, we just ended up throwing a bunch of interns at the problem—it’s actually working pretty well.” Rule of thumb: Some problems don’t actually matter.

Highlighted by 8 people

Good question. Usually, by the end of the meeting, people understand what you’re trying to do. Since you don’t know the industry, they’ll often be sitting there quietly while you completely miss the most important point. Asking this question gives them a chance to politely “fix” your line of questioning. And they will! This question is a bit of a crutch: you’…

Highlighted by 8 people

It boils down to this: you aren’t allowed to tell them what their problem is, and in return, they aren’t allowed to tell you what to build. They own the problem, you own the solution.

Highlighted by 8 people

If you just avoid mentioning your idea, you automatically start asking better questions. Doing this is the easiest (and biggest) improvement you can make to your customer conversations. Here are 3 simple rules to help you. They are collectively called (drumroll) The Mom Test:

Highlighted by 7 people

Let’s fix it: Ask how they currently solve X and how much it costs them to do so. And how much time it takes. Ask them to talk you through what happened the last time X came up. If they haven’t solved the problem, ask why not. Have they tried searching for solutions and found them wanting? Or do they not even care enough to have Googled for it?

Highlighted by 7 people

With the exception of industry experts who have built very similar businesses, opinions are worthless. You want facts and commitments, not compliments.

Highlighted by 7 people

The measure of usefulness of an early customer conversation is whether it gives us concrete facts about our customers’ lives and world views. These facts, in turn, help us improve our business.

Highlighted by 7 people

AI Review

4.7/ 5

Glasp's AI analysis of 19 reader highlights suggests a strong consensus that this is a highly actionable startup classic. The most-saved passages emphasize memorable rules, practical questions, and a sharp framework for separating real demand from empty encouragement.

Pros

+Memorable framework for better customer conversations
+Strong emphasis on facts over opinions and compliments
+Highly actionable question prompts readers can use immediately
+Clear test for problem severity, urgency, and willingness to pay
+Useful distinction between customer problems and founder solutions
+Practical guidance on commitment, advancement, and segmentation

Cons

−Can feel repetitive because the same core rules are reinforced often
−Conversation tactics are stronger than deep product strategy
−Some advice is most directly applicable to early-stage startups and B2B contexts

Glasp AI analysis based on highlights from 19 readers.

Who Should Read This

This book is best for founders, product managers, startup teams, indie hackers, and B2B sales-led builders who need to validate demand before building too much. It is especially useful if you keep hearing positive feedback but still feel uncertain about whether customers will actually pay.

It also fits people entering a new market, refining a customer segment, or struggling to turn interviews into actionable evidence. No deep prior startup knowledge is required, but readers working on early-stage products will get the most immediate value.

Frequently Asked Questions

What is the book about?

It is about how to talk to customers in a way that reveals whether their problems are real, costly, and urgent. Instead of asking if your idea is good, it teaches you to learn from concrete facts about what people already do, pay, and struggle with.

Who is it for?

It is for founders, startup teams, product builders, consultants, and anyone testing a new business idea. It is especially relevant for early-stage teams trying to avoid building based on false-positive feedback.

What are the key lessons?

Ask about past behavior rather than future intentions, avoid pitching too early, and treat compliments as weak data. Look for evidence in current workarounds, budget, urgency, and concrete commitments of time, reputation, or money.

Why is it called The Mom Test?

Because even your mom cannot easily lie to you if you never ask for approval of your idea. By talking about her life instead of your startup, you get more reliable information.

How does the book define a good customer conversation?

A good conversation produces facts, leads to commitment, or creates advancement to a next step. If you leave with only praise or vague enthusiasm, the book suggests you learned very little.

What does the book say about feature requests?

Do not treat requests as a to-do list. Instead, dig into why the person wants that feature, what it would let them do, and how they are coping without it now.

Is it worth reading?

Based on the highlighted passages, readers found it unusually practical and quotable. If you need a short book that improves customer interviews quickly, the signal here is very strong.

How to Apply What You Read

1.Rewrite your customer interview script so every question focuses on past behavior, current tools, costs, and recent examples.
2.Prepare your three biggest learning questions before each batch of conversations, including one that could disprove your current idea.
3.End every conversation by asking who else you should talk to and what the concrete next step should be.
4.Track signals separately: facts, compliments, feature requests, commitments, and advancement.
5.Review notes with your team after interviews and update your beliefs, segment definition, and next questions.

Discussion Questions

Q1.Which kinds of customer praise are easiest to mistake for validation in your own work?
Q2.How can you tell the difference between an annoying problem and a problem people will pay to solve?
Q3.What are the risks of letting customers tell you what to build instead of focusing on their underlying problems?
Q4.In your market, what would count as a meaningful commitment: time, reputation, cash, or something else?
Q5.How narrow does a customer segment need to be before feedback becomes useful rather than contradictory?
Q6.When have you asked future-focused questions and received answers that sounded useful but probably were not?
Q7.What changes would your team need to make to turn customer conversations into a repeatable learning process?