20 Apr · 15 min read
Here at UPDIVISION, a big part of our software development process is product discovery. It’s the stage where we and the product owner try to understand what the app is supposed to do, who the users are, and how we can help them achieve their goals.
There’s a big mistake beginner entrepreneurs tend to make - and it often leads to the downfall of their business. They should never ask anyone if their business is a good idea. Why? It invites people, especially those close to you, to lie. They will try to spare your feelings and tell you it’s a good idea, you should go for it, and they will try your product when it’s out.
After having such experiences, Rob Fitzpatrick, a developer turned entrepreneur, wrote a book called, “The Mom Test: How to Talk to Customers and Learn If Your Business is a Good Idea when Everyone is Lying to You”.
In his book, Fitzpatrick talks about the dangers of being praised too much on your business idea: if you’re misled from the beginning, your business might end up being a costly failure. But the key to avoiding that is having better conversations with potential customers - so you know from the start that your idea is worth pursuing.
So today, we'll be doing a review of his book and going through his best tips on how to get proper feedback on your business ideas.
Table of contents
Chapter 1. The Mom Test
Chapter 2. Avoiding Bad Data
Chapter 3. Asking Important Questions
Chapter 4. Keeping it casual
Chapter 5. Commitment and advancement
Chapter 6. Finding conversations
Chapter 7. Choosing your customers
Chapter 8. Running the process
In this chapter, Fitzpatrick goes into detail about what the mom test really is: a way to ask someone about your business idea in such a way that they don’t lie to you. It comes down to asking the proper questions.
Here are the main talking points within The Mom Test:
1. Talk about their life instead of your idea - if you simply ask them, “I’m making an app that helps people make online payments faster, would you try it?”, they’d be inclined to lie to you. Instead, ask them how they make payments online, what kind of role they play in their life, and what they find challenging about it.
2. Ask about specifics in the past instead of generics or opinions about the future - ask them about the last time they tried whatever your app is trying to do, how they’ve fixed any issues, or they had any issues at all. The author, in fact, insists multiple times throughout the book that it is also useful to find out you’re fixing an unexisting problem.
3. Talk less and listen more - one of the pitfalls of talking to someone about a business idea is falling into “pitch mode”. But you’re not trying to promote your business: let the potential customer talk about their life, so you can see how your business idea can fit in - or if it does at all.
The author also talks about specific questions you should, and shouldn’t ask. So here are the good ones, and why:
✅ "What would your dream product do?" - A good question if you have a good follow-up. After you ask this, make sure to also ask why.
✅ “Why do you bother?" - This question can help you understand why a specific problem is a problem. It helps determine what the user’s true goal is.
✅ "What are the implications of that?" - This way, you can find out if the problem you’re trying to solve is big enough of a deal to require a solution.
✅ "Talk me through the last time that happened." - Get into detail about the potential customer’s day to day life, or even watch them complete the task in question.
✅ "What else have you tried?" - With this question, you can find out if the issue is big enough of a deal for the customer to be willing to pay for solutions.
✅ "How are you dealing with it now?" - Similarly, here you can find out how much money and effort they’re putting into fixing the issue.
✅ "Where does the money come from?" - This question is suitable in a B2B medium, because you can find out who the biggest stakeholder is.
✅ "Who else should I talk to?" - By asking this, your potential customer might introduce you to other people having the same issues.
✅ "Is there anything else I should have asked?" - If there are any useful details that the customer didn’t get the chance to talk about, this is their chance.
Here are some examples of bad questions:
❌ "Do you think it's a good idea?" - Unless you’re talking to an expert, there’s no use in asking for opinions. They won’t determine whether it’s worth the effort or not.
❌ "Would you buy a product which did X?" - It’s better to ask them if they’ve tried a solution, and if they’re paying for it. Or if they didn’t find a solution at all.
❌ "How much would you pay for X?" - Ask them how much they’re paying for their current solution instead.
Bad data, says Fitzpatrick, is information that misleads you - and which doesn’t pass The Mom Test. He puts it into 3 categories:
You might think that a meeting that ends with “That’s cool, I like it” was successful. But unless you’re talking to an industry expert who has built something similar, this opinion doesn’t prove anything - it’s just that, an opinion. The key, says Fitzpatrick, is not mentioning your idea right off the bat, and deflecting compliments.
Specifically, once the people you’re talking to say “That’s cool”, ask them why, get to specifics. Ask them how much money it would save them, how it would fit into their life, or if it’s better than other solutions they’ve tried..
Fitzpatrick divides his idea of fluff into 3 categories:
These kinds of comments aren’t actually useful when testing out a business idea, as they’re not reliable commitments. When a potential customer says “I would definitely buy that”, the author says, they’re being wildly optimistic. Sure, they might buy it. But it doesn’t guarantee that they will.
A good way to avoid fluff is by asking good follow-up questions: instead of asking someone if they would use an app that fixes their problem, ask them if they’ve tried a solution at all, and how that went. This way, you might even find out that there’s no need for your app. Plus, finding out about their past behavior is a better reference for what they might do in the future (compared to those “I would try it” comments).
Potential customers tend to come up with lots of feature requests, but founders shouldn’t include everything in their business. But how do you know if a feature is truly important or not? Keep asking why, says Fitzpatrick. Dig, dig, dig, until you find out if a problem is so important that people will rush to your product to fix it.
The pitfall of feature-packing is not knowing, beforehand, that most of those features won't be used. This is why you need to find the motivation behind a feature request: maybe all existing solutions lack that important feature, or whatever solution they’re trying requires too much money and effort.
Fitzpatrick talks about The Pathos Problem, where a business owner exposes their ego and invites people to give them compliments - instead of useful information. Questions like “I’m thinking of starting a business... so, do you think it will work?” or “I can take it — be honest and tell me what you really think!” don’t bring you useful business insights. Just compliments people will give you so they don’t hurt your feelings.
The author also talks about letting the customer talk: if you do all the talking, how can you get useful information out of a conversation with them? Listen to what they’re saying, and don’t interrupt.
Fitzpatrick says that an important question is one that can disprove your business idea. Like we’ve already mentioned, it’s just as useful to know if your idea is useless. This way, you’ll save time and money and won’t build a product no one will use. The trick is to allow yourself to ask these questions, and to fully listen.
Another issue in how founders structure their questions is zooming in too fast: if you’re talking about a specific activity and your business idea relies on it, but your potential customer doesn’t do that enough, don’t push. The example the author gives here is an app that helps you stay fit: if the customer you’re talking to doesn’t work out and doesn’t even care about it, ask them why. Don’t push with more specific fitness questions. Stop at the first “no”, and head into the “why”.
Another example Fitzpatrick gives is a blog marketing tool: when talking to potential customers, start by asking what their biggest blog problems are. Then, if they say that blog marketing is an issue, ask them why, and dig deeper. But if they don’t mention it, talk to more people, or take it as a sign that the problem isn’t important enough.
A big part of asking the right questions is preparing the 3 most important ones, before you talk to people. Pick these with your team, and when you find a potential customer to talk to, you already know what to ask.
It takes a while to set up meetings. And it’s even harder to convince someone to take the time and effort to do it - especially when meeting face to face. This book was written before the pandemic, so this part is slightly out of date. But this chapter highlights a bigger issue.
What makes people not want to talk to you is making it too formal. So Fitzpatrick says: keep it casual. Have a regular chat, just you and the potential customer, and ask your most important questions.
Learning from customers doesn’t mean you have to be wearing a suit and drinking boardroom coffee, he says. Taking away the pressure of an interview lets people open up, and give you actually useful information. Don’t talk about your idea, talk about the problem you’re trying to fix and how the customer is facing it.
When talking to potential customers or investors, there are 2 majors things that prove they’re truly interested in your business idea:
With those in mind, it’s not easy to say that a meeting “went well”. A successful meeting isn’t one that leaves you with “good vibes” and compliments - it’s one that leads to some sort of commitment.
These commitments are based on 3 major elements: time, reputation risk, and cash. Here are some of the author’s examples:
In other words, the more they’re giving up for you, the more believable their compliments will be. They might even combine all 3 elements and have a paid trial that involves their entire team.
Next up, Fitzpatrick talks about some big statements said at the end of a meeting and which ones prove that it truly went well:
❌ "That's so cool. I love it!" - It’s a compliment that brings no useful data.
❌ "Looks great. Let me know when it launches." - This is a common stalling tactic, and they likely won’t care about the launch. It’s better to ask for a commitment anchored in the present.
🤔 "There are a couple people I can introduce you to when you're ready." - This might be out of politeness, so to test their willingness to commit, ask for more details.
✅ "What are the next steps?" - This shows interest and the willingness to commit to your idea.
❌ "I would definitely buy that." - As we’ve mentioned before, anything involving “would” is unreliable. A concrete promise or pre-order is more significant.
🤔 "When can we start the trial?" - If your trial involves more effort (a fairly high cost, takes time and resources to use), their validation means more.
✅ "Can I buy the prototype?" - They’re willing to commit by spending money, which is a great sign.
✅ "When can you come back to talk to the rest of the team?" - In a B2B environment, this is a very good sign. If they don’t say this, you might have reached a dead end.
How do you fix bad meetings, then? Fitzpatrick says it’s all about asking for more details: when faced with rejection, ask why. When left with fluff, dig deeper.
You know your product and your audience. Now, where do you actually find those people? Fitzpatrick says to pay attention to what people around you talk about, find good excuses to talk about key topics for your business, and immerse yourself in where they are. If you create a landing page with a sign up for updates function, email everyone back and say hello - it could start useful conversations.
Alternatively, try to get them to you. If you’re building a product aimed at HR professionals, have an event called “HR professionals happy hour”, says Fitzpatrick. You can also hold talks about the issue you’re solving, which can help you meet people you can talk to. Or do industry blogging, which can also attract members of your audience.
The author gives a couple of tips on how to find people to talk to:
If you frame your meeting poorly, you’re setting yourself up for failure. Don’t make it formal, don’t ask for opinions, and don’t say “thank you for agreeing to this interview”. Instead, Fitzpatrick proposes this framing structure: Vision / Framing / Weakness / Pedestal / Ask.
Here’s how that works:
1. Tell them what problem you’re trying to solve and what your vision is for it - don’t talk about your business idea yet.
2. Tell them what stage you’re at, so you frame expectations
3. Show them what your weakness is - talk about any specific issues you’re having while building the product
4. Tell them how important their help would be, with concrete examples
5. Ask for help
It’s never good to start too broad, nor too specific, in terms of audience. Asking the right questions but not getting useful answers is a sign you’ve gone too broad: this is where customer slicing comes in. This is a process where you take an audience segment, and dig deeper, to subsets of it.
Here are some questions you can ask your main segment, to find subsets:
After that, you should ask them what this subset is doing to fix the issue, and where you can find them. When you have to choose who to start talking to, Fitzpatrick says to choose who is more:
2. Easy to reach
3. Rewarding to build a business around
If your product has multiple stakeholders (take, for instance, apps for kids - which you have to “sell” to both the kids, and the parents) or relies on a certain partner, don’t leave them out of the conversation. Talking to the right people will help you get the right data for your business.
It’s a terrible idea, as the team leader, to withhold useful information from the rest of your team. Everything you learn should be shared with them right away - and they should be as involved as you are.
Before talking to customers, you should:
While talking to customers, you should:
After talking to customers, you should:
Overall, we found this book to be a very interesting read, that we can apply in our own work, in the product discovery process. It brought some valuable insights about how to evaluate a business idea, the right questions to ask, and how to find people to talk to.
If you’re here looking to go further with your own business idea and you need some technical assistance, contact us and let’s see what we can do together.