The Mom Test Review: How to Ask Without Being Lied To

Last week, while reviewing feedback for our team’s Claude Sonnet 4.6 automation bot, I realized that 90% of user responses were just polite, hollow praise. We had built a feature no one needed, simply because we asked the wrong questions from the start.

🧠 The Lie Named “Feedback”

Your mom loves you, so she’ll lie to protect your feelings. That’s the premise of this book. The problem is, it’s not just your mom—almost everyone does it.

When you pitch an idea to someone and ask, “Do you think this is cool?”, social etiquette forces them to nod. They don’t want to be the villain who crushes your dreams.

I used to think that building an MVP, letting users try it, and asking “What do you think?” was enough. But after spending three months completely rebuilding a dashboard feature, it turned out that asking that question only yielded meaningless nods of approval. The truth is, if you ask the wrong questions, you get garbage data.

🚫 The Real Downsides of The Mom Test

Many people treat this book as the Product Management bible. But from an engineer’s perspective, I find it has some frustrating gaps.

Overlooking the Remote Work Context

Rob Fitzpatrick wrote this book based on spontaneous conversations in coffee shops or at conferences. In 2026, we work through screens. Interviewing a user via Google Meet or Zoom has a completely different psychological dynamic. Applying the “casual run-in” tactics described in the book feels forced and unrealistic in today’s B2B environment.

The Post-Interview Void

You asked the right questions. You got the truth. Now what? The book stops right as you’ve gathered a pile of qualitative data. It doesn’t teach you how to translate those rambling stories into Jira tickets or feature specs. Much like when you read about system architecture thinking: don’t fall into the trap of over-designing on paper, collecting data without a processing system is useless.

✅ What Saves the Book: Three Core Rules

Despite its flaws, the first half of the book is worth its weight in gold. It completely changed how I communicate with customers.

Talk about the past, not the future

Never ask, “Would you be willing to pay for this feature?” The future is a cheap lie. Instead, ask, “When was the last time you encountered this problem? How much time and money did you spend trying to solve it?”

Listen instead of pitching

As tech people, we love to show off our stack. But users don’t care if you’re using tool calling: miracle or gimmick behind the backend. They only care if their problem gets solved. The Mom Test teaches you to bite your tongue while a user talks about their pain points, instead of jumping in and shouting, “My app can do that!”

⚖️ Distinguishing Garbage Questions vs. Quality Questions

Criteria	Naive Question (Wrong)	Mom Test Question (Right)	Note
The Idea	what do you think of this app idea?	How are you currently solving problem X?	Evaluate actual behavior, not opinions.
Pricing	Would you pay $10 for this feature?	How much are you currently paying for your existing tools?	Money already spent is real. Promised money is just air.
Features	Do you need a PDF export function?	Walk me through the steps the last time you had to create a report.	Understand the workflow instead of asking for feature requests.

🛠️ How I Apply The Mom Test as a Dev

If you’re a software engineer forced to talk to users, follow these 3 steps:

1. Prepare 3 core questions: Write down 3 things you actually want to know about their behavior. Keep the conversation centered on these points.
2. Take notes verbatim: Don’t paraphrase. If a user says they are “extremely frustrated by that loading button,” type that exact phrase. Their language is the copy you’ll use for the landing page later.
3. Ask about failures: “What other ways have you tried to solve this that didn’t work?” This is a goldmine for finding out where your competitors are failing.

❓ FAQ

I’m a dev, why should I read a PM book?

Because you’re the one writing the code. Coding the wrong feature wastes hundreds of hours. Understanding the problem correctly sometimes requires stepping out of your comfort zone, much like facing the tough philosophies in The Courage to Be Disliked: A Senior’s Bedside Book?. Understanding the user helps you write less “trash code.”

Can I apply it immediately after reading?

Yes. The rules are very intuitive. However, the first few times you apply them, you’ll feel an “itch” because of the habit of wanting to protect your idea. Be patient.

Is this book outdated in the AI era?

Quite the opposite. When models like GPT-5.2 can generate an entire web app in 10 minutes, the barrier is no longer programming ability. The barrier is knowing what you should actually build.

🎯 Conclusion

The Mom Test isn’t a perfect book. It repeats its points and leaves the data processing part hanging. I give it 3.5 stars because of the letdown in the second half. However, it provides a necessary bitter pill to shatter the delusions of product builders. If you’re about to write the first line of code for a side project, stop and read the first 100 pages of this book first. You’ll save yourself several months of your life.