The Mom Test

A customer-discovery technique that gets evidence instead of compliments by asking about the customer’s real past behavior, never about their hypothetical enthusiasm for your idea.

The name comes from a rule about who you can trust to give you a straight answer. Ask your mother whether your business idea is good and she’ll say yes, because she loves you and doesn’t want to discourage you. Rob Fitzpatrick’s insight, in his 2013 book The Mom Test, is that the problem isn’t your mother. It’s the question.

Ask anyone whether your idea is good and you’ll get a kind answer, because you’ve asked them to evaluate you rather than to report a fact. The fix is to ask questions so grounded in past behavior that even your mother couldn’t lie to you. They ask about things that already happened, not things you hope will happen.

Context

A founder has an idea, or the first version of one, and needs to know whether a real customer has the problem it solves. This is the idea-validation phase, before much has been built and before any metric exists to read. The only instrument available is conversation, and conversation is the one instrument that lies to you most readily, because the person across the table is trying to be nice.

Customer discovery sits at the front of every validation method. Steve Blank’s customer-development work made “get out of the building” the founding discipline of lean startups, and the build-measure-learn loop reads discovery evidence alongside the behavioral evidence an MVP produces. The Mom Test is the discipline that makes those conversations produce data instead of encouragement.

Problem

Talking to customers feels like the safe, humble thing to do, and it’s where validation most reliably goes wrong. The founder sits down across from someone, describes the idea, and asks the questions that feel natural: Would you use this? Do you think it’s a good idea? Would you pay for it?

The answers come back warm. People say yes. They say it’s interesting. They say they’d “definitely try it.” The founder leaves the room with a notebook full of encouragement and reads it as evidence of demand.

It’s nothing of the kind. Every one of those questions asks the customer to predict future behavior or render a verdict on the founder’s plan. People are bad at the first and too polite for the second. A “yes, I’d buy that” costs the speaker nothing and commits them to nothing. The founder has manufactured a false positive: a signal that looks like validation and isn’t, gathered with the best of intentions, expensive precisely because it’s believed. The harder a founder pushes to hear that the idea is good, the more reliably the conversation will tell them so.

Forces

• Politeness versus truth. The person across the table wants to be supportive, especially to a founder they like, and especially about a future they aren’t being asked to pay for. Their kindness is exactly the noise the method has to filter out.
• The founder’s hunger for validation. A founder needs to believe the idea is good to keep working on it, and that need shapes the questions toward the answers it wants. The instrument has to be strong enough to overrule the person holding it.
• Hypothetical versus actual. What someone says they’ll do in a future that hasn’t arrived is close to worthless; what they actually did last week is a fact. The two feel equally like data in the moment, and only one is.
• Talking versus selling. A discovery conversation that drifts into pitching stops collecting evidence and starts seeking approval. The moment the founder describes the idea, the customer’s answers turn into reactions to the founder instead of reports about themselves.

Solution

Ask only about the customer’s real past behavior and current life, never about your idea or their hypothetical future, and let them do most of the talking. Fitzpatrick distills the discipline into three rules:

1. Talk about their life, not your idea. Don’t mention what you’re building. Ask how they currently handle the problem, the last time it bit them, and what it cost. If they don’t know you have an idea, they can’t shade their answers to flatter it.
2. Ask about specifics in the past, not generics about the future. Replace “Would you buy a tool that did X?” with “Walk me through the last time you dealt with X. What did you do? What did it cost you in time or money?” A specific past event is a fact; a generic future intention is a wish.
3. Talk less, listen more. The founder’s job is to ask short questions and get out of the way. If you’re talking, you’re not learning, and you’re probably pitching.

The deeper move underneath the rules is to chase facts, commitment, and advancement rather than compliments. A compliment is “that sounds great.” Evidence is the customer telling you they already cobbled together a spreadsheet, a Zapier hack, and two contractors to solve this, and it still costs them six hours a week. Commitment means the customer gives up something they value: time, reputation, or money. Advancement means the relationship moves to a concrete next step: an introduction to the boss, a slot on the calendar, a pilot, a letter of intent, or a deposit.

Praise is free, so it’s worthless; commitment costs something, so it counts. The test of a good discovery conversation isn’t how enthusiastic the customer was. It’s how much you learned about a problem they already spend real time or money on, and what they were willing to give up to see it solved.

The technique pairs with a demand theory. Jobs to Be Done tells the interviewer which past behavior to dig into: the progress the customer was trying to make and what they “hired” to make it. Discovery without that lens collects anecdotes; with it, the founder knows which story to chase.

How It Plays Out

A founder building a scheduling tool for hair salons sits down with a salon owner. The instinct is to open the laptop and demo. Instead, following the method, she never mentions the product. She asks how appointments get booked today. The owner walks her through a paper book at the front desk, a part-time receptionist who also answers the phone, double-bookings every few weeks when the phone and the walk-in collide, and one memorable Saturday last month when a no-show cost three hundred dollars in an empty chair.

The founder learns the problem is real, frequent, and quantified, without asking a single question about her idea. Then she asks for a next step: will the owner let her sit at the desk for a morning to watch the booking flow? The owner says yes and hands over two other salon owners’ numbers. That’s evidence, commitment, and advancement, not a compliment, and it beats any number of “sounds useful” verdicts.

The failure runs the other way and is far more common. A founder pitches the idea, gets told it sounds great by a dozen people, and reads the warmth as a green light. He builds for six months, launches, and discovers that none of the dozen who loved the idea will actually pay, because they never had the problem badly enough to act on it. They were being kind. The conversations had measured the founder’s likability, not the market’s demand. This is how weak discovery feeds the False Positive Trap: the early signal that justifies building and raising turns out to have been manufactured by the questions themselves.

Consequences

Running discovery this way changes what a founder learns and how far they can trust it, at the cost of some comfort.

Benefits. The method is the cheapest defense a founder has against building the wrong thing, because it surfaces the absence of a real problem before any code or capital is committed. It produces evidence a founder can act on and defend to an investor. “The salon owners we talked to lose a chair to no-shows most Saturdays, and three of them pay for two separate tools to manage it” is a fundable observation in a way that “everyone we talked to loved it” never is. Done well, the method also generates the first commitments and advances (intros, pilots, pre-orders) that become the earliest real traction. Investors read discovery discipline as a tell: a founder who reports specific customer behavior rather than enthusiasm signals a team that tests rather than assumes, which is the habit that survives a hard market.

Liabilities. The method is harder than it sounds. Its main failure mode is the founder cheating without noticing: sliding back into pitching, hearing commitment where there was only courtesy, or asking the past-behavior questions and then overweighting the one answer that confirmed the plan. It’s also a qualitative instrument, and qualitative evidence has limits: a handful of vivid conversations can mislead as easily as inform if the people interviewed aren’t representative of the market the company actually needs. Discovery tells you whether a problem is real; it doesn’t tell you whether enough people have it to build a company on, which is why it complements behavioral testing rather than replacing it. And as AI tooling makes it trivial to synthesize personas and market maps, the temptation grows to skip the awkward human conversations entirely. AI can size a market and map competitors; it cannot tell you that a real person already spends six hours a week and real money working around the problem you want to solve. That fact only comes from asking them, correctly.

Related Articles

Sources

• Rob Fitzpatrick, The Mom Test: How to Talk to Customers and Learn If Your Business Is a Good Idea When Everyone Is Lying to You (2013) — the book that named the technique and supplied the three rules and the compliments-versus-commitment distinction.
• Steve Blank, The Four Steps to the Epiphany (2005) — the customer-development foundation that made “get out of the building” the founding discipline of validation, the practice the Mom Test sharpens into a question technique.
• Clayton Christensen and co-authors, Competing Against Luck (2016) — the Jobs to Be Done framing that tells the interviewer which past behavior to chase: the progress the customer was trying to make.