mom-test

name	mom-test
description	Plan, conduct, and review customer discovery conversations using The Mom Test (Rob Fitzpatrick). Use when preparing user or customer interviews, validating a product/feature/business idea through conversations, writing interview questions, judging whether feedback is real signal or bad data (compliments, fluff, ideas), or deciding whether a meeting produced real commitment vs polite rejection.

The Mom Test — customer conversation procedure

When to use

Any time you're validating an idea through conversations: drafting interview questions, prepping a discovery call, analyzing what someone said, or judging whether a meeting was a win. Core mechanism: people lie about opinions and the future, but rarely about specific things that already happened. Note the scope limit: conversations validate market risk (do they want it, will they pay, are there enough of them) — they cannot retire product risk (can you build/grow/retain it). Heavy product risk means building earlier with less certainty; live-product questions are often better answered by usage data.

The procedure

1. Prepare

1. Pick a focused, findable segment first. Slice ("Customer Slicing") until you have a who-where pair: who exactly, and where you can reach them. Slice by who wants it most and why (motivations), then by where they already gather or what workarounds they already do. Choose the first segment by: profitable, easy to reach, personally rewarding. If you can't say where to find them, keep slicing.
2. Write the list of 3 — with the whole team, the 3 most important things to learn from this type of person. Include at least one question that could destroy the idea; if none of your questions scare you, they're wrong. Prep prompts: "If this failed, why would it have happened?" and "What would have to be true for this to be a huge success?" Minimum viable prep: "What do we want to learn from these guys?" If you can't answer that, skip the conversation.
3. Desk-research first. Never spend conversation time on anything the internet can answer. 5 minutes of LinkedIn/company diligence before B2B meetings.
4. If asking for a meeting, frame it — Vision / Framing / Weakness / Pedestal / Ask ("Very Few Wizards Properly Ask"): the problem-space vision (not your idea), where you're at and that you have nothing to sell, your specific weakness they can fix, why they specifically can help, the ask. Never "can I interview you" / "can I pick your brain" / "can I get your opinion". Compressible to two sentences.
5. Keep it casual when possible. The first learning conversation doesn't need to be a meeting — 5 minutes tells you if a problem exists and matters. Video calls are fine (the 2013 "in person only" advice predates normalized remote work); the surviving principle is that formality kills candor. If it feels like they're doing you a favour, it's too formal.
6. Cap prep at about an hour. More is stalling.

2. Conduct

Follow the three rules — done right, they can't lie to you:

1. Talk about their life, not your idea. Don't pitch. Modern honest framing beats 2013 stealth: say you're exploring the space and have nothing to sell, then ask about their life. Delay mentioning the idea until you're asking for commitment — mentioning it too soon is the classic error, and once your ego is visible people protect your feelings (the Pathos Problem).
2. Ask about specifics in the past, not generics or the future. "Would you buy/pay X?" always returns an over-optimistic lie. Ask instead: How do you deal with this now? What did it cost you? When did it last happen — talk me through it. What else have you tried? Where does the money come from (B2B: whose budget, who can veto)?
3. Talk less, listen more. Don't interrupt to fix their understanding or answer objections. The more you're talking, the worse you're doing.

Also:

• Start broad; don't zoom prematurely. Open with "What are your big goals and problems right now?" Only drill into your topic once they raise it or you're certain it's must-solve. People will rank their "#1 problem with X" even when they don't care about X at all.
• Dig into any strong emotion — anger, embarrassment, excitement: "Tell me more. What makes it so awful? Why haven't you fixed this already?"
• If you slip into pitch mode, name it and recover: "Whoops — I slipped into pitch mode, sorry. Can we jump back to what you were saying?"
• Take verbatim notes (exact quotes in quotation marks), tagged by signal: emotions, pains, goals, obstacles, workarounds, feature requests, money/budget, names to get intros to, follow-ups. Transfer to shared, sortable, team-visible storage after — notes you won't look at are useless.
• End every conversation with: "Who else should I talk to?" and "Is there anything else I should have asked?"

3. Read the data

Three types of bad data, each with a recovery move:

Bad data	Looks like	Recovery
Compliments	"That's cool!", "I love it", "went really well"	Deflect — apologise for pitching, return to facts. Test: do you know why they liked it and what it costs them today? If not, you learned nothing.
Fluff	"I usually/always…", "I would/will…", "I might…"	Anchor — "When's the last time that happened? Talk me through it." Complainer vs customer: will they act now?
Ideas	Feature requests, "you should build…"	Dig — "Why do you want that? What would it let you do? How are you coping without it?" Understand, don't obey; the real build is usually different and simpler.

• Lukewarm ("meh") responses are gold: crystal-clear, reliable evidence this person doesn't care. Never "up your game" and pitch until they say something nice — that only manufactures false positives.
• Does the problem actually matter? Do they spend money or time on it today; is it in their top 3 goals/problems; have they actively searched for a solution; what did the last occurrence cost? If they haven't looked for a solution already, they won't look for (or buy) yours.
• Division of labour: they own the problem, you own the solution. Never let them design the product; never tell them what their problem is.

4. Push for commitment

Once you're showing the idea/product, every meeting succeeds or fails — there is no "went well". Success = a concrete commitment to advance. Failure = a compliment or a stall ("let me know when it launches").

• The currencies: time (scheduled next step with known goals, real trial use), reputation (intro to boss/team/decision-maker, public case study), cash (LOI, pre-order, deposit). A compliment costs nothing and is worth nothing. The more they give up, the more you can trust their kind words.
• Convert fuzzy promises to concrete ones: who exactly, when exactly, why not now? "It's not a real lead until you've given them a concrete chance to reject you." Rejection is data; not asking is the only real failure.
• If a trial is too cheap to try, raise its price (case study after 2 weeks' use, team-wide commitment, card on file).
• Beware zombie leads — friendly people who keep taking meetings but never commit. You caused it by not asking.
• Earlyvangelists (your first buyers): have the problem, know it, have budget, have already hacked a workaround. Chase deep emotion; keep the passionate close.

5. Review

1. After each batch, review notes with the team using exact quotes. One person hoarding the learning is a de-facto dictator ("the customer said so"). Founders/decision-makers can't outsource this — hired-out learning yields glossed-over lukewarm signals.
2. Update beliefs and pick the next 3 big questions. Also review the craft: which questions worked, what signals were missed.
3. Stop condition: keep going until you stop hearing new things — 3-5 conversations can suffice for a tight segment and simple question (a lower bound, not a target). More than 10 with scattered results = segment too fuzzy; slice tighter.
4. Then move: an hour of prep, a week or two of conversations, then build. "Go build your dang company already."

Rules and quick reference

Am I fooling myself? (going-through-the-motions signs) — talking more than them · getting complimented · told them the idea with no next step · no notes · notes not reviewed with team · unexpected answer changed nothing · no question scared me · can't name the big question this conversation serves.

Was the meeting real? — did they give up time, reputation, or money? If not, it failed, however friendly it felt.

Core rules of thumb:

• Opinions are worthless; anything involving the future is an over-optimistic lie.
• People will lie to you if they think it's what you want to hear.
• There's more reliable information in a "meh" than a "Wow!"
• Compliments are the fool's gold of customer learning.
• Ideas and feature requests should be understood, but not obeyed.
• Watching someone do a task shows where problems really are, not where they think they are.
• While people rarely say precisely what they'll pay, they'll show you what it's worth to them (current workaround cost = price anchor).
• If you aren't finding consistent problems and goals, your segment is too fuzzy.
• You should be terrified of at least one question in every conversation.
• If you don't know what you're trying to learn, skip the conversation.
• If you don't know what happens next after a product meeting, the meeting was pointless.
• Don't over-index on impressive people; talk to people representative of your customers.
• Talking to customers is a tool, not an obligation — half-assed box-ticking is worse than nothing. Sometimes just pick up the phone and hack through the knot.

2026 translations (the book is from 2013): video calls are fine — the point is informality and candor, not physical presence. Honest framing ("exploring the space, nothing to sell") replaces stealth. Use whatever note tooling the team will actually review (shared doc > index cards). Once you have a live product, analytics and experiments answer many questions better than conversations.

Source

Compiled from The Mom Test — Rob Fitzpatrick (2013). The skill is the procedure; the book carries the depth (worked examples, edge cases, the author's reasoning). If this stage is where your venture lives right now, buy and read it.