mom-test

---
name: mom-test
description: Use when preparing customer interviews or validating an idea. Applies the Mom Test rules: discuss their life not your idea, ask about specifics in the past, talk less.
category: Business Knowledge
version: 1.0.0
tools: []
---

# The Mom Test Framework

Have customer conversations that won't lead you astray. Everyone is lying to you -- not maliciously, but because you're asking the wrong questions. The Mom Test gives rules for asking questions so good that even your mom can't lie to you.

## Core Principle

Good customer conversations are about their life, not your idea. The moment you mention what you're building, people switch from truth to polite performance. Talk about their problems and existing behavior, ask about specifics in the past (not hypotheticals about the future), and above all talk less, listen more.

## Scoring

**Goal: 7/7.** One point per passing row in the Quick Diagnostic. **6-7** = focused on their life and past behavior, concrete facts captured, a real commitment (time/reputation/money) secured, they talked 80%+ of the time, and beliefs got updated. **4-5** = some past-behavior facts but leaking into hypotheticals, compliments accepted as signal, or ending without an ask. **<=3** = a pitch in disguise: leading questions, opinions and fluff, a polite zombie lead, no learning. Always state the score out of 7, the failing rows, and the fix.

## 1. The Mom Test Rules
Three rules that make it impossible for even loved ones to give false validation: (1) talk about their life, not your idea -- never mention your solution until the end, if at all; (2) ask about specifics in the past, not generics or future hypotheticals; (3) talk less, listen more -- aim for them to speak 80% of the time. A question fails the Mom Test if the answer is always "yes" regardless of whether the business will succeed. Good questions could potentially destroy your currently imagined business. Copy patterns: "Tell me about the last time you...", "What else have you tried?", "Why does that bother you?"

## 2. Good vs Bad Questions
Most interview questions are broken because they ask people to predict the future or confirm your assumptions. Bad: "Do you think it's a good idea?" (always gets a yes); "Would you buy a product that does X?" (hypothetical, anchored to please you). Good: "How are you dealing with this problem today?"; "What have you tried before and why did you stop?"; "Where does the money come from for solutions like this?" The scariest questions -- ones with the power to change what you're building -- produce the most useful data.

## 3. Avoiding Compliments and Opinions
Three types of bad data feel like progress but mislead: **compliments** ("That's a great idea!"), **fluff** (hypotheticals, "I usually," "I would never" without a specific instance), and **ideas** (feature requests disconnected from real problems). Compliments are the fool's gold of customer development -- deflect immediately and return to concrete facts. Dig into the motivation behind every feature request. If you walk away feeling great but with no concrete facts or commitments, the conversation was bad. Copy: "Thanks -- but what does your current process look like?"; "Why do you want that? Can you show me the last time you needed it?"

## 4. Commitment and Advancement
The currency of a conversation is commitment, not compliments. End every conversation with a clear advance or a clear rejection -- the worst outcome is a "zombie lead" who is polite but never commits. Three commitment currencies: **time** (meeting, trial), **reputation** (intro, testimonial), **money** (deposit, pre-order, letter of intent). Know your ask before the meeting. A "no" is more valuable than a "maybe" -- if they won't give you their time, they definitely won't give you their money. Copy: "Who else should I talk to about this?"; "Would you be willing to try a prototype next week?"

## 5. Finding Conversations
The best conversations happen casually -- warm intros, industry events, online communities, coffee. Formal "customer interview" framing triggers performance mode; "I'm trying to learn about the industry" produces honest data. Warm intros are the best source; go where customers already gather and participate genuinely first. Use a five-part structure for meeting asks: vision / framing / weakness / pedestal / ask. Ethical boundary: never disguise a sales call as a learning conversation.

## 6. Processing and Learning
Conversations are only useful if processed: distill notes into beliefs, update them regularly, share with your team. Take notes during or immediately after -- never rely on memory. Separate facts (what they said and did) from interpretations (what you think it means). Share raw notes with the team, not filtered summaries, to prevent any one person's bias dominating. Update your three key beliefs after each batch: the problem, the customer segment, the solution. Stop talking and start building when conversations start repeating. Rule of thumb: a problem named by 7 of 10 people is real signal; 1 of 10 might not be.

## Product Applications by Section

| Context | Application | Example |
|---------|-------------|---------|
| Idea validation | Ask about the problem, never the solution | "Tell me about the last time you tried to [problem]" not "Would you use an app that does X?" |
| Pricing research | Anchor to existing spending | "What are you currently paying to solve this?" not "Would you pay $X?" |
| B2B prospecting | Warm intros through advisors | "Our advisor [Name] suggested I ask how you handle [problem]" |
| Pivot decisions | Track evidence against core beliefs | 8 of 10 conversations reveal a different problem than expected -- pivot |

## Common Mistakes

| Mistake | Why It Fails | Fix |
|---------|-------------|-----|
| Pitching your idea instead of asking about their life | Triggers politeness; produces compliments, not facts | Don't mention your idea until the very end, if at all |
| Asking "would you buy this?" | Hypothetical yeses cost nothing | Ask what they've already done: "How much are you spending on this now?" |
| Accepting compliments as validation | "Great idea!" carries zero information about behavior | Deflect immediately: "Thanks -- but what are you doing about this today?" |
| Talking too much | You learn while listening, not talking | They should talk 80%+ of the time |
| No clear ask at the end | Produces zombie leads that go nowhere | Know your advance before the meeting: trial, intro, pre-order |
| Running formal "interview" sessions | Triggers performance mode and filtered answers | Keep it casual: coffee, hallway conversations, Slack DMs |
| Not processing notes as a team | Individual bias filters data into confirmation | Share raw notes weekly; update shared beliefs together |

## Copy Patterns Reference

"Tell me about the last time you..." (past specifics) | "What have you tried before, and why did you stop?" (reveals real alternatives) | "Where does the budget for this come from?" (reveals real spending power) | "Who else should I talk to?" (advances the relationship) | "What's the hardest part about [doing this]?" (surfaces the real problem) | "Walk me through what happened the last time this came up" (forces concreteness over opinion).

## Quick Diagnostic

Did the conversation focus on their life and past behavior, not your idea? Did you extract concrete facts rather than opinions? Did you avoid accepting compliments as validation? Did they talk at least 80% of the time? Did the conversation end with a real commitment (time/reputation/money)? Did you separate facts from interpretation when processing notes? Did your beliefs actually change based on what you heard?