The Mom Test: Don't Ask If They'd Buy — Ask What They Did Last Time
Topic: The Mom Test·4 principles
Ask a prospect "would you buy this?" and almost everyone says "sure, looks great" — then not one of them pays. They're not lying to you; you asked the wrong question. Whether they'd buy is a guess. Where their money went last month is a fact.
Last time was about listening well. This time: even when you get the question out of your mouth, the answer can still be all lies. The most common way people building products, validating needs, or even pitching a partnership crash and burn: you excitedly show your solution, ask "what do you think?", the other person politely praises it, you think you've struck gold — and then collect zero dollars. The fix is called The Mom Test (Rob Fitzpatrick) — the name means: a question asked well enough that even your mom (the person guaranteed to say something nice so as not to crush you) can't fool you with it. The whole thing is one line: never let people evaluate your idea; get them talking about their own life and past instead. This one gives you three hard rules plus a test for what a "real signal" actually is. By the end you'll re-read all that feedback where "customers seemed really interested" — most of it is bad data.
PRINCIPLE 01
Talk about their life, not your idea
Move the topic off your pitch and onto their world
dodge polite liestheir life, not your plandrop the ego pressure
The principle in one line
The moment you present your idea and ask "is it good?", the other person flips into "don't crush this person / give some encouragement" mode, and hands you nothing but polite lies. Move the topic from "how's my idea?" to "how do you actually live with this — what did you do last time you hit it?" Talk about their world, and only then do you get the truth.
In their words
"You should never ask anyone whether your business is a good idea."— Rob Fitzpatrick, The Mom Test
Same person, two ways to ask, two kinds of data
Scene
Setup: You built an app that auto-tracks spending and generates a budget report at month-end. You want to know if anyone actually wants it, so you corner a friend (or target user) to chat.
✗ Pitch it and fish for a verdict (collect polite lies)
"I made an app that tracks your spending automatically and generates a budget report each month — what do you think? Would you use it?" — Them: "Oh, sounds handy, yeah, I'd definitely use something like that." Your heart soars, you go home and code for six months. After launch: zero paying users. Because that "I'd use it" was said to spare your feelings — not something they'll actually do.
✓ Only talk about their life and past (force out facts)
"How do you keep track of your money right now?" "Last month, was there a point where you checked and had no idea where the money went, or overspent?" "What did you do about it? Did you ever install an app for this, or pay for some tool?" — You never mentioned your solution, yet you learned: they did overspend last month, panicked a bit, downloaded a budgeting app, used it for three days, got tired of logging entries, and deleted it. "Downloaded it, then deleted it" — this one fact is worth more than a hundred "I'd use it"s: it tells you the need is real, but the "log it manually" solution is dead on arrival.
Why it works · mechanism & evidence
Why it works
Mechanism: social desirability bias + face-saving. When you present your own idea with a hopeful look, answering it adds a second task to their mind: "don't embarrass this person." So they're not reporting "what I'd really do" — they're picking an answer that keeps both of you comfortable. That's the source of the polite lie. Ask about their past, and you strip that "should I protect their feelings?" pressure out entirely: they have no stake in prettifying something that already happened.
Psychology · social desirability bias (fairly solid, methodological consensus): A robust finding in survey methodology — when asked about attitudes or intentions, people lean toward the "more socially approved / pleasing" answer rather than the true one (social desirability bias). See the review by Nederhof (1985) and the classic work of Edwards (1957). Decades of questionnaire research keep replicating this, not a one-off study.
Direct consequence · the say-do gap: Famous market-research faceplants (e.g. the classic New Coke taste tests that scored great yet flopped at launch) show it repeatedly: the preference people state and the behavior they pay for often don't match. This is industry-experience evidence; the direction is clear.
Foundational book: Rob Fitzpatrick, The Mom Test (2013) — turns "never let them evaluate your idea" into an operational questioning discipline. It's a practitioner methodology (not a controlled experiment), but it shares a root with the bias above.
Boundary: this isn't that people love to lie — it's that "being asked your opinion to your face" naturally invites nice answers. So the problem isn't the person, it's your phrasing. Switch to asking about the past and the specific, and the same person gives you the truth.
Check yourself before you open your mouth
Is this question about whether my idea is good, or how they live their life?
Am I "spoiling" the answer I want to hear inside the question, waiting for them to agree?
If they can only say "good" or "nice," it's a wasted question — can I swap it for "how did you do it last time…"?
Across the whole conversation, can I get the number of times I mention my own solution down to nearly zero?
Common mistakes
Can't resist pitching first. Two lines of small talk and you dump the solution — from that moment on, every bit of feedback is contaminated by your idea and becomes encouragement.
Treating compliments as validation. "Great idea!" "I totally support you!" — the words that make you giddy are exactly the ones to distrust (Principle 03 handles this).
Only talking to people who'll flatter you. Picking family and friends, whose motive to save your face is strongest, gets you the fakest data. Go find actual strangers who have the problem.
Key references
Rob Fitzpatrick, The Mom Test (2013) — origin of the "don't ask if your idea is good" discipline. Nederhof (1985) / Edwards (1957) — reviews and classic work on social desirability bias.
Key phrases
Say it like this
"How do you currently handle that?" — the best line for pulling the topic back to their status quo.
"Talk me through the last time that happened." — get them to replay one specific past instance.
Never ask "would you use it?" — ask "what do you do today?"
PRINCIPLE 02
Ask about the specific past, not opinions about the future
The past is fact; the future is a guess
past = factfuture = guessintention–behavior gap
The principle in one line
"Would you use it later?" "Would you pay for it?" — these all ask someone to predict themselves, and people predict their own future behavior badly, always optimistically. Ask instead: "When was the last time you hit this? What exactly did you do? How much money / time did it cost you?" Things that actually happened can't be invented.
In their words
"Opinions are worthless. … Anything involving the future is an over-optimistic lie."— Rob Fitzpatrick, The Mom Test
Intention ≠ behavior: there's a gap between them
Scene
Setup: still that budgeting app. You want to know: will anyone actually pay for this?
✗ Ask about future intent (collect an over-optimistic guess)
"If there were an app that handled all this for you automatically, would you pay $5 a month for it?" — Them: "Umm… yeah, probably, that price is fine." That "probably" is the self they imagine right now, not the self who's about to get charged at month-end. Take it as "payment validated" and you've mistaken a prediction for a fact.
✓ Ask about real past spending (get facts)
"Have you ever paid for anything to manage your money — an app subscription, a budgeting book, someone to help?" "When was the last time you spent time or money on it? How much? Are you still using it?" — If they say "I bought a subscription to XX, $98 a year, still using it," that's a real, cash-backed payment signal. If they hem and haw, "no… never spent money on it," then no matter how much they say they want it, your "$5-a-month" business deserves a big question mark.
Why it works · mechanism & evidence
Why it works
Mechanism: the intention–behavior gap. Between "I intend to do X" and "I actually do X" sits a gap: intentions are easily inflated by a moment's enthusiasm, wanting to please you, and rosy images of the future — but when it's time to pay a real cost (spend money, change a habit), behavior lags far behind intention. So "would you, in future?" measures their intention right now (inflated), not their behavior later. Ask about the past, and what you see directly is the behavior itself.
Psychology · intention predicts little behavior (hard evidence): Webb & Sheeran (2006, Psychological Bulletin) meta-analyzed 47 experiments — a large lift in intention (d≈0.66, medium-to-large) produced only a d≈0.36 (small-to-medium) change in actual behavior. Intention jumps a lot; behavior moves a little. This "intention ≠ behavior" result is a replicable meta-analytic finding. (cross-ref psychology: intention and behavior)
Mechanism add-on · we predict ourselves optimistically: people broadly overestimate "what I'll do in future" (optimism / planning-fallacy family), which systematically inflates future-intent answers. Direction is reliable; magnitude varies by situation.
Where the method lands: Fitzpatrick compresses it into one executable line — ask about specifics in the past, not opinions about the future; and dig for the concrete time, action, and cost of "the last time."
Honest note: Webb & Sheeran is a meta-analysis of health / behavior-change domains; extending "intention inflated, behavior lags" to purchase decisions is a reasonable mechanism transfer, not proof that anyone ran the same meta-analysis on sales. The direction is hard; don't treat it as "experiments proved asking about the past raises close rates."
Turn "future" questions into "past" questions
The same thing, asked two ways
· ✗ "Would you use it?" → ✓ "What do you use today to muddle through this?"
· ✗ "Would you pay for it?" → ✓ "Have you paid to solve it before? On what, how much?"
· ✗ "Would this feature be useful?" → ✓ "When did not having it last bite you?"
· ✗ "Would you use it often later?" → ✓ "How much time did this cost you last month?"
Rule of thumb: swap "would / willing / later" for "last time / how much exactly / how you do it now."
Common mistakes
Settling for "probably." Any future-tense answer with "probably / maybe / I'd likely" gets a mental "unverified" label — don't treat it as a conclusion.
Asking the past but stopping at generics. "I usually watch my spending" isn't the past — it's a generality. Nail it down to "the most recent specific time, what happened."
Leading with hypotheticals. "If there were a perfect tool you'd totally use it, right?" — you're feeding them the answer, and what comes back is still bad data.
Key references
Webb & Sheeran (2006), "Does changing behavioral intentions engender behavior change?" (Psychological Bulletin) — meta-analysis of the intention–behavior gap (d≈0.66 → 0.36). Rob Fitzpatrick, The Mom Test — "specifics in the past, not opinions about the future."
Key phrases
Say it like this
"When was the last time you ran into this?" — pin the topic to a concrete past.
"What did that cost you — in time or money?" — measure real pain by its cost.
Ask about the past, not the future.
PRINCIPLE 03
Spot the three kinds of bad data: compliments, fluff, hypotheticals
Don't bank praise — dig down to one specific past instance
Sitting on a pile of "positive feedback"? Don't celebrate yet — The Mom Test sorts bad data into three kinds: compliments ("great idea!"), fluff ("I usually…" / "I generally…," with no specific instance), and hypotheticals ("I would…" / "if it existed I'd…"). When you hear these, they're not evidence — they're a cue to immediately dig down to "what exactly happened one specific time."
In their words
"Compliments are the fool's gold of customer conversations."— Rob Fitzpatrick, The Mom Test
Three kinds of bad data · how to spot and crack them
Scene
Setup: mid-conversation, the customer says this — all three kinds of bad data in one breath.
✗ Take it as "validation succeeded"
Customer: "This idea's really nice (compliment), we've always cared a lot about data security (fluff), and if a tool like this ever existed we'd definitely consider getting one (hypothetical)." — You walk away pumped and report "customer is very interested, cares about security, willing to buy." Pure illusion: not one specific fact in those three sentences.
✓ Treat bad data as a cue and dig
"Thanks (accept the compliment, don't bank it). You said you've always cared about data security — when did you last actually invest in that? What did you buy, how much did it cost?" "In the past year, have you had an incident, or been dinged by an audit, over data security? Which time exactly, and how did you fix it after?" — If they can say "we paid out after a leak last year, then rolled out an XX system for a few hundred grand," the need is real. If they can't dig out anything specific and just repeat "we really care," that "caring" is mostly lip service.
Why it works · mechanism & evidence
Why it works
Mechanism: compliments are "cheap and intoxicating" for both sides, so they crowd out real information. For the speaker, a kind word costs almost nothing and earns goodwill; for the listener (you), being praised is a social reward — one hit and you tend to stop probing and cherry-pick signals that confirm your idea. Both sides collude, and the bad data lands neatly in your notebook. The only cure: don't bank compliments / fluff / hypotheticals as conclusions — dig every one down to "one specific time."
Neuroscience · "reputation / approval" runs on the same reward circuit as money (hard evidence): Izuma, Saito & Sadato (2008, Neuron) used fMRI to show that receiving a good social reputation (approval) activates the striatum (the reward circuitry around the nucleus accumbens) — heavily overlapping with the region that lights up for a monetary reward. That's why compliments are intoxicating, and why people are happy to give them: it's a cheap social reward. (cross-ref neuroscience: striatum / reward circuit; psychology: social reward)
Psychology · confirmation bias makes you believe only the nice parts: people have a systematic tendency to seek and over-trust information that supports their existing view (confirmation bias; review by Nickerson, 1998). Loving your own idea makes you especially prone to reading compliments as "validation" and dismissing cold water as "they just don't get it."
Where the method lands: Fitzpatrick's "bad data" trichotomy (compliments / fluff / hypotheticals) is a field-tested checklist — an experience framework, but each category maps onto the mechanisms above.
Honest note: Izuma et al. established the neural fact that "social approval activates the reward circuit"; using it to explain "why compliments are seductive" is a reasonable mechanism transfer. The "three kinds of bad data" itself is a practitioner framework, not a classification proven by any single controlled experiment.
Hear bad data? Dig like this
Cracking the three kinds
· Hear a compliment → "Thanks — but what I really want to understand: how did you handle it the last time you actually hit this?" (don't take the praise; turn to specifics)
· Hear fluff ("I usually…") → "Can you walk me through the most recent specific time? What actually happened?"
· Hear a hypothetical ("I would…") → "Forget later — how do you deal with it right now? Have you spent money / time on it?"
· Universal probe: "Be specific — when was the last time?" + "And then what?" Can't dig out specifics → the need is in doubt.
Common mistakes
Praise makes you float, then quit. The worst thing about a compliment isn't that it deceives you — it's that it makes you stop probing early. You think you've validated; you'd barely started.
Using bad data to report / decide. Writing "customer is very interested" into a business plan as grounds to build — this is how countless products die at the starting line.
Can't dig, so you comfort yourself. They give zero specific facts, yet you soothe yourself with "maybe they just don't remember." Usually, if you can't dig out specifics, the need isn't real.
Key references
Izuma, Saito & Sadato (2008), "Processing of Social and Monetary Rewards in the Human Striatum" (Neuron) — social approval and money share the striatal reward circuit. Nickerson (1998), "Confirmation Bias" (Review of General Psychology). Rob Fitzpatrick, The Mom Test — the bad-data trichotomy.
Key phrases
Say it like this
"Thanks — but tell me about the last time it actually happened." — deflect the compliment, turn to specifics.
"Can you give me a specific example?" — the smoothest line for cracking fluff.
Compliments are fool's gold. — shiny, but worthless.
PRINCIPLE 04
Only commitment that costs them is a real signal
Enthusiasm is noise; spending something they value is signal
time / reputation / moneyadvancerevealed preference
The principle in one line
Enthusiasm alone ("love it, let's keep in touch!") isn't signal, it's noise. A real signal is when they hand over something they value: time (a dedicated next meeting / a trial), reputation (an intro to their boss / colleague), money (a deposit / a letter of intent). Every contact should advance one notch toward a firmer next commitment; collect only compliments and no commitment, and you're standing still.
In their words
"A meeting either advances to a real commitment, or it's a failure."— Rob Fitzpatrick, The Mom Test (commitment & advancement)
Three "currencies they value": paying up is what's real
Scene
Setup: a warm, lively meeting, nearly over. The other side looks excited.
✗ Settle for enthusiasm (mistake a dead deal for a live one)
Them: "So interesting, what you've built is really great, let us chat internally, keep in touch!" You: "Sounds good, I'll wait to hear from you!" — You leave with the illusion "the customer is very interested." But they paid nothing: no time booked, no intro made, no money down. This kind of "very interested" is usually a polite goodbye, followed by read-but-no-reply.
✓ Ask for a commitment that costs them (verify it)
"Great. Then let's not stop at 'chat' — how about this: next Wednesday I bring a version tailored to your situation and spend 30 minutes with you and whoever owns the budget?" (asking for time + reputation: only agreeing to book it and pull in the decision-maker is real) If they cheerfully book it and even volunteer who to bring in — real signal. If they start tap-dancing, "bit busy lately, let me look on my own first" — this deal is politely declining you, and you find out early and cut your losses.
Why it works · mechanism & evidence
Why it works
Mechanism: revealed preference + commitment & consistency. (1) What a person truly values shows in where they put scarce resources (money, time, reputation), not in what they say — talk is free; handing over something valued exposes real priorities. (2) And once they've paid a little (booked a meeting, made an intro), the "be consistent with my actions" pressure makes them more likely to keep investing. So "ask for a small commitment" is both verification and advancement.
Economics · revealed preference (foundational theory): revealed preference, introduced by Samuelson (1938) — a person's true preferences are shown by their actual choices (where they spend resources), not by their verbal statements. It's a bedrock concept of modern microeconomics, and it fits perfectly here: watch behavior, don't just hear the talk.
Psychology · commitment and consistency (fairly solid): the "commitment and consistency" principle catalogued in Cialdini's Influence, and its source such as the Freedman & Fraser (1966) "foot-in-the-door" experiments — people who first agree to a small request agree to a bigger one at a notably higher rate. This supports "advance via a small commitment." (cross-ref psychology: commitment and consistency)
Where the method lands: Fitzpatrick redefines a meeting's success as "did I get a firmer commitment (an advance)?", not "was it a pleasant chat." A field framework.
Boundary: don't turn "ask for commitment" into hard closing. The commitment you request must match the current stage — early on, a small one like "time / intro" is plenty; demanding a signed order out of the gate scares off real customers. It's "verify + gently advance," not a pressure tool.
Close by asking for a real commitment
By cost, light to heavy
· Time: "Come do a 30-minute trial next Wednesday?" — only counts if it goes on the calendar.
· Reputation: "Could you introduce me to the person who owns this / your boss?" — staking their own credibility is a strong signal.
· Money: "Want to put down a small deposit to lock a slot?" — real cash is the hardest signal.
· At every close, ask yourself: "Did they take one step forward that cost them something?" If not, you're standing still.
Common mistakes
Mistaking enthusiasm for commitment. "I'm very interested" costs them nothing — don't write it into the pipeline as a closing signal.
Meetings with no close. A pleasant chat and everyone disperses, no next step requested — you restart from zero each time and the deal never advances.
Asking for a commitment that doesn't fit the stage. Pushing for a signed contract on the first meeting scares off real customers you could have nurtured. Advance in small steps; don't leap to the top.
Key references
Samuelson (1938) — revealed preference theory (watch behavior, not statements). Freedman & Fraser (1966) — foot-in-the-door (small commitment → big commitment). Rob Fitzpatrick, The Mom Test — judging a meeting by "commitment & advancement."
Key phrases
Say it like this
"What are the next steps?" — a must-ask close that forces out the real next move.
"Would you be open to introducing me to the person who owns this?" — ask for a "reputation" commitment.
Enthusiasm isn't commitment. — only paying a cost counts.
Your Day 8 Action
Pick something you're mulling over — a product idea, a service to sell, even a job-hunt or partnership direction. This week, find 3 real target people (not family or friends) and talk for 15 minutes each.
Don't describe your solution once the whole time — only ask about three things in the past: (1) When was the last time you hit X? (2) What exactly did you do about it? (3) How much money / time have you spent on it?
Afterward, sort their words into two piles line by line: compliment / fluff / hypothetical → cross it all out; things that actually happened / real spending → keep it. Count how many you kept. Finally, try asking one of them for a small commitment that costs something (book a next meeting, ask for an intro, or a small deposit) and see if they pay up.
Boundary: this is for validating real need, not for "proving I was right." If all three can't dig out a single specific fact and no one will pay any cost — that's not you asking badly, that's the need telling you "think again." Being able to hear that is what The Mom Test is really for.
Think It Through
1. If I never describe my solution, how do I actually sell? Asking without pitching feels like wasted talk.
Split discovery and pitching into two things and the tension disappears. The Mom Test governs the discovery stage — your job right now isn't to close, it's to figure out "is the need real, how do they cope today, does it hurt enough that they'll pay?" That information is itself your sharpest ammunition for later: when you do present, you can aim precisely at the pain and the spend they said out loud — far more persuasive than "I'm guessing you might need this." So you're not not-selling; you're diagnose first, prescribe second — a good doctor doesn't hand you pills the moment you walk in. As for "wasted talk": if 15 minutes of asking reveals the need is fake, that's the opposite of wasted — you just saved six months of building the wrong thing.
2. What if it's a brand-new category and the customer has never faced this problem or had any solution — how do I ask about the past?
A brand-new category is The Mom Test's hardest case, because there's no directly matching past behavior to ask about. Two moves: (1) Ask about the "workaround," not your product — however new the need, people always have some makeshift way to cope now (a spreadsheet, doing it by hand, just enduring it, or not doing it at all). Dig into how painful, how laborious, how error-prone that workaround is; if the pain is real, your opening is real; if you find people "endure it and it's fine," the need may be less urgent than you thought. (2) Upgrade "asking" into a "small real test" — for a brand-new category you can't ask your way to truth, so build a minimal usable thing and let someone actually spend money / time on it once, substituting revealed preference for verbal intent. Remember: the more "customers can't picture it," the less you trust their words about the future, and the more you rely on real behavior to verify.
3. Is The Mom Test only useful for startup research and B2B? Can I use it in everyday life?
You can, and its reach is huge, because the core is "don't trust statements, trust behavior; don't ask the future, ask the past" — which holds anywhere you need to judge someone's true intent. Interviews: instead of "are you good under pressure?" (everyone says yes), ask "tell me about the last time a project was falling apart and exactly what you did" — a specific past behavior. Partnerships: don't listen to "I'll give it everything," watch whether they'll pay a little cost first (do a small piece, invest some time). Judging if someone's reliable: look at what they've done, not what they've promised. Even your own decisions: to know whether you truly want to do something, don't ask "will I keep at it later" — look at "how much time did I actually spend on it this past month." Talk is cheap, behavior is honest — that never goes out of date.
4. If I only ask the past and only trust behavior, do I completely ignore the customer's vision and the new features they want?
Listen — but down-weight it, and be clear which kind of information it is. Fitzpatrick's move isn't "toss all future talk," it's labeling two classes differently: facts (what actually happened, what they actually paid) — high credibility, use for decisions; opinions / vision / wanted features — low credibility, use to understand direction and leads, but never as proof "they'll buy." When a customer says they want a feature, don't rush to build it — first probe "what specifically did not having it cost you last time?", using a past fact to test the weight of that wish. Vision tells you "where to look"; facts tell you "whether to act." Use both, but always let paid behavior outweigh cost-free statements.