mom-test

어떤 스킬인가요?

Validates business ideas through customer conversations using Rob Fitzpatrick's Mom Test framework. Use when planning user interviews, getting product feedback, validating ideas, designing discovery questions, or extracting honest signal from biased customer responses. Covers good vs bad questions, deflecting compliments, anchoring fluff, pressing for commitment, and customer slicing.

설치 방법

프로젝트 폴더에서 아래 명령어를 실행하고, 설치할 에이전트를 선택하세요.

설치 명령을 직접 실행해야 적용됩니다. 지원 에이전트와 필요한 권한·라이선스는 제작자의 안내를 확인하세요.

스킬 원문 파일

# Mom Test - Case Studies and Concepts

## Earlyvangelists (First Customers)

**Attribution note:** "Earlyvangelist" is **Steve Blank's** term, coined in *The Four Steps to the Epiphany*. Fitzpatrick uses the concept in The Mom Test but did not coin the word. The criteria below align with Blank's earlyvangelist profile.

Your first customers are "crazy" - they want your solution so badly they'll try it first.

### Signs You Found One

1. **Have the problem AND know they have it** - Not in denial, not unaware
2. **Have budget to solve it** - Money exists, just needs direction
3. **Already cobbled together their own makeshift solution** - Spreadsheets, manual processes, hacks
4. **Get emotional about what you're doing** - Visible frustration with status quo
5. **Will commit before it makes rational sense** - Buy on promise, not proof
6. **Will fight for you against their boss** - Champion you internally

### Key Insight

When someone isn't emotional about what you're doing, they're unlikely to be your first customer. Lukewarm interest = not an earlyvangelist, even if they say nice things.

## The Compliment Trap (Common Pattern)

Founder shares idea → friend says "that's amazing!" → founder feels validated → builds for 6 months → no one buys.

**What happened:** Friend was being polite. The compliment was data about the friendship, not the idea.

**Fix:** Deflect immediately to current behavior. "Thanks! How are you handling this today?"

## The Feature Request Trap

User says: "If only it had X feature, I'd buy it."

**Naive interpretation:** Build X, get the sale.

**Mom Test interpretation:** Why do they want X? What underlying problem? Are they actually committed enough to buy, or just brainstorming?

**Field example pattern:**
- Build X. User says "great, but actually I also need Y."
- Build Y. User says "great, but..."
- Lesson: They were never going to buy. Feature requests without commitment are noise.

## The Casual Conversation Pattern

A founder in a coffee shop overhears a stranger complain about a problem in the founder's space. The founder asks "oh how do you handle that today?" and gets 10 minutes of pure, unfiltered detail.

**Why it works:**
- Stranger has no reason to lie
- No "meeting" frame = no pitch expectation
- Question is about their life, not a product

This is the format you're trying to recreate even with scheduled interviews. Strip the meeting feel.

## The Visionary Customer Trap

Even paying customers can derail you:

**Pattern:** Big customer with strong opinions wants you to build their specific use case. They're willing to pay a lot. You agree.

**Result:** 6 months later you've built a custom system that doesn't generalize. The "$200K contract" actually cost you $400K in opportunity cost and steered you off your real market.

**Filter:** Ask "would 10 other companies want exactly this?" If no, this is custom work, not product work.

## The Price Anchor Conversation

```
Founder: How are you handling [problem] now?
Customer: We use [competitor] for $500/month.
Founder: Does that work for you?
Customer: Sort of. We end up doing X manually.
Founder: How much time does that take?
Customer: Maybe 5 hours a week?
[Founder now knows: budget ≥ $500/mo, real pain = manual work, value = recovered hours]
```

Compare to the bad version:

```
Founder: How much would you pay for our solution?
Customer: I dunno, $50?
[Founder now has a useless number that has nothing to do with reality]
```

## Pattern: When "Yes" Means "No"

Founder asks: "Would you use this if I built it?"
Customer says: "Yes, definitely."

Three months later, product launches. Customer doesn't sign up.

**Why:** "Yes" was the polite answer. The real test is past behavior, not future promises.

**Better question:** "When was the last time you ran into this problem? What did you do? How much did it cost you?"

If the answer is "I haven't really had this problem," all the future-tense yeses in the world are noise.

## The B2B Buying Committee Pattern

In B2B you're often selling to multiple roles:

| Role | Cares About | Question for Them |
|------|-------------|-------------------|
| **User** | Daily friction | Walk me through your workflow |
| **Economic buyer** | ROI, budget impact | How is success measured? |
| **Technical evaluator** | Integration, security | What would block this from being adopted? |
| **Champion** | Career impact | Who else needs to approve this? |

Talking to only one role gives you a partial truth. Each conversation can pass the Mom Test individually but you'll still miss why deals stall if you skip the other roles.

# Mom Test - Templates and Worked Examples

## Note-Taking Symbols

| Symbol | Meaning |
|--------|---------|
| :) | Excited |
| :( | Angry |
| :\| | Embarrassed |
| ⚡ | Pain or problem |
| 🥅 | Goal or job-to-be-done |
| ☐ | Obstacle |
| ⤴ | Workaround |
| ^ | Background/context |
| ☑ | Feature request / purchasing criteria |
| $ | Money / budget / purchasing process |
| @ | Mentioned specific person or company |
| ★ | Follow-up task |

Use these in real-time during conversations. Faster than writing words; preserves emotional valence.

## Worked Conversation: Good vs Bad

### BAD Version (typical founder)

```
Founder: Hi, I'm building a tool that helps marketing teams automate their reporting. Would that be useful to you?
Customer: Oh yeah, that sounds great!
Founder: How much would you pay for that?
Customer: I dunno, maybe $200/month?
Founder: Would you use it if I built it?
Customer: Definitely!
Founder: Awesome, I'll send you a link when it's ready.
[6 months later: customer ignores the launch email]
```

What went wrong: every question was a Mom Test violation. Hypothetical, opinion, future-tense, no commitment.

### GOOD Version (Mom Test applied)

```
Founder: Hey, I noticed you're a marketing director. What's your week look like?
Customer: Honestly insane. Tuesdays I lose 4 hours just pulling reports.
Founder: 4 hours? Walk me through what that looks like.
Customer: I export from Google Analytics, then HubSpot, then Salesforce, mash them together in a spreadsheet, format for the board...
Founder: What happens if you don't get it done?
Customer: My CMO yells at me. Last quarter I missed it and almost got fired.
Founder: How are you handling it now?
Customer: I have a contractor who does it but he's expensive and slow.
Founder: How much do you pay him?
Customer: $1500 a month for like 8 hours.
Founder: Who else on your team has this problem?
Customer: My counterpart at [other company] is dealing with the same thing. Want me to introduce you?
Founder: That'd be amazing. Also - if I had something working in 2 weeks, would you be willing to try it for the next quarterly report?
Customer: Yeah honestly send it over, I'll pay for early access.
```

What went right: past behavior, real costs, current solution, intro committed, time + money commitment offered. This is signal.

## Email Templates

### Cold Outreach for Interview (VFWPA)

```
Subject: 20-min chat about [their domain]?

Hey [Name],

I'm working on making [problem] easier for [target segment]. (VISION)

We're not selling anything yet - just trying to understand 
if we're solving a real problem. (FRAMING)

I'm stuck on [specific thing you don't understand]. (WEAKNESS)

You've been doing [their relevant experience] longer than 
just about anyone I could talk to. (PEDESTAL)

Got 20 minutes in the next two weeks for a casual chat? (ASK)

[Your name]
```

### Follow-up After Conversation

```
Subject: Thanks - and a small ask

Hey [Name],

Thanks for the chat yesterday. The thing you said about 
[specific painful detail] is going to change how we 
think about this.

Two quick things:
1. Would it be okay if I came back to you in 4 weeks 
   to show you what we built?
2. You mentioned [colleague's name] also runs into this - 
   would you be open to making an intro?

Either way, super grateful for the time.

[Your name]
```

### Commitment-Forcing Close

```
Subject: Real version of [thing]?

Hey [Name],

We have a working version of [the thing we discussed]. 
Three options for what's next:

1. I send you a link, you try it on a real report, 
   and we talk about what works.
2. I do the first report for you so you can see it, 
   and your team uses it for the next one.
3. You skip it - no hard feelings, would just love to 
   know which option to pull off the table.

Let me know which one.

[Your name]
```

The third option matters: it makes "no" easy and reveals lack of commitment without the polite-yes trap.

## Common Re-Anchoring Phrases

When the conversation drifts into hypothetical territory, redirect:

| They Say | You Say |
|----------|---------|
| "I would always..." | "When was the last time? Walk me through it." |
| "Most people probably..." | "Tell me about you specifically." |
| "It would be cool if..." | "What's the worst part of how you do it now?" |
| "Sounds like a great idea." | "Thanks - how are you handling this today?" |
| "I'd definitely buy it." | "Could I send you an invoice today for early access?" |
| "Add feature X." | "Why? What would that let you do?" |

## Conversation Quality Self-Audit

After each conversation, score yourself:

- [ ] Did I learn something I didn't already know?
- [ ] Did I get specific past behavior, not generalizations?
- [ ] Did I get a real commitment (time/reputation/money)?
- [ ] Did I keep my mouth mostly shut?
- [ ] Was I terrified of any answer I might hear?
- [ ] Did I avoid pitching?

5+ checks = good conversation. <3 = redo it.

## The "Earliest Possible Pitch Refusal" Test

Push the offer earlier than feels comfortable:
- Not "I'm thinking about building..."
- Instead: "Would you put down $500 today to be the first user?"

Their reaction is data. A flinch, a wandering excuse, or a "let me check with my team" all = no. A "yes, where do I send it?" = real lead.

This feels rude. It's not. It saves both of you from a 6-month dance ending in nothing.

## From Notes to Team Beliefs

Raw interview notes don't become product direction on their own. This protocol converts them into shared, tracked beliefs.

**Step 1 - Write up within 24 hours.**
Each interviewer writes up their notes within 24 hours of the conversation. Include direct quotes, emotional signals (use the symbols from the note-taking table), and one sentence on what you personally believe changed or was confirmed.

**Step 2 - Weekly team review.**
The team reviews all write-ups from the past week together. Each person calls out surprises, contradictions, or patterns. No decisions yet - just shared understanding.

**Step 3 - Track belief changes on a shared doc.**
Maintain a living belief tracker. Before each batch of interviews, record what the team currently believes. After the batch, record what (if anything) changed and why. This makes drift visible and prevents the team from unconsciously moving the goalposts.

**Step 4 - Only update product direction on convergence.**
A single interview, no matter how compelling, is not signal. Only update roadmap or positioning when multiple interviews, from different people with no reason to coordinate, point at the same problem or behavior. One data point is an anecdote. Three is a pattern.

**Belief Tracker Template**

| Belief | Evidence For | Evidence Against |
|--------|-------------|-----------------|
| [State the belief clearly] | [Quotes, behaviors, patterns that support it] | [Quotes, behaviors, patterns that contradict it] |

# Mom Test - Detailed Frameworks

## The VFWPA Email Framework (Cold Conversation Requests)

For warm intro emails / cold outreach to potential interviewees:

| Letter | Element | Purpose |
|--------|---------|---------|
| **V**ision | Your big-picture goal | Why they should care |
| **F**raming | Honest where you are | Sets expectations, removes pitch fear |
| **W**eakness | What you don't know | Gives them a way to help |
| **P**edestal | Why they specifically | Flatters genuinely, signals research |
| **A**sk | Concrete request | Makes saying yes easy |

### Template

```
Hey [Name],

I'm trying to [solve problem / achieve vision]. (VISION)

We're just starting out and don't have anything to sell, but want 
to make sure we're building something that actually helps. (FRAMING)

I'm having a hard time understanding [specific gap]. (WEAKNESS)

You've been [doing relevant thing] and could really help me 
cut through the fog. (PEDESTAL)

Do you have time in the next couple weeks to meet up for a chat? (ASK)
```

## Where to Find People

| Source | How |
|--------|-----|
| Industry events | Conferences, meetups, trade shows |
| Self-organized meetups | Unfair advantage - you control the room |
| Universities | Professors have industry contacts |
| LinkedIn cold outreach | Even works for executives |
| Landing pages | Email everyone who signs up |
| Cash in favors | Everyone who said "let me know how I can help" |

## Question Depth Hierarchy

### Surface (avoid)
- "Do you like X?"
- "Would X be useful?"

### Workflow (good)
- "Walk me through how you do this today"
- "What happens after that?"
- "Where does this break down?"

### Motivation (better)
- "Why do you bother?"
- "What are the implications if you don't solve this?"
- "What's the cost of doing nothing?"

### Commitment (best)
- "Who else should I show this to?"
- "Can I get back on your calendar after I build this?"
- "Would you put down a deposit?"

## Conversation Frame: The Casual Default

### Why Formality Kills Conversations
- Meetings cost 4+ hours with overhead
- Sets expectation you'll pitch, inviting biased feedback
- Feels like an interview, not a conversation

### Better Approach
- Strip the formality - reduce "meeting" to "chat"
- Pop your most important question immediately
- 5-10 minute casual conversations yield as much as formal meetings
- Goal: they don't even realize they've "had a meeting"

## The Three Levels of Filtering

When you hear customer signal, filter through three lenses:

| Layer | Question | Why |
|-------|----------|-----|
| **Behavior** | What have they actually done? | Past beats hypothetical |
| **Money** | Where does budget come from? | Reveals real priority |
| **Process** | Who else is involved? | Tests buying complexity |

## Minimum Useful Threshold

The book's general guidance is: keep going until you stop hearing new things.

Practical signals you have enough:
- Hearing the same problems repeatedly
- Can predict the next interview's answers
- Distinct segments emerging clearly
- B2B with buying committees: talk to economic buyer, user, AND technical evaluator (these are typically different people)

If 10+ conversations and still confused → segment is too broad. Slice tighter, don't keep interviewing.

## Three Big Questions Framework

Before each round of conversations, decide with your team:

1. What's the most important thing we need to learn?
2. What would change our plans if we learned it?
3. How will we know we've learned it?

After each round:
1. What did we learn?
2. How does this change what we'll do?
3. What are the next 3 big questions?

This forces continual focus and prevents "interviewing for interviewing's sake."

# Mom Test - Integration with Other Skills

## Sequencing with Other Skills

```
mom-test → 100m-offers → money-models → 100m-leads
   ↓             ↓              ↓              ↓
 discovery   packaging    monetization      traffic
```

| Stage | Use | Why |
|-------|-----|-----|
| Pre-validation | mom-test | Find a problem worth solving |
| Validated, no offer | 100m-offers | Package the solution |
| Validated, has offer, growth is cash-constrained | **money-models** | Sequence offers so each customer funds acquiring the next |
| Validated, has offer | 100m-leads | Drive traffic |

If your business has products but no paid customers, you're almost always missing offer work (step 2).

## Skill Combinations

### mom-test + 100m-offers

Mom Test extracts the customer's actual language about their dream outcome. Use those exact words when designing the offer's value proposition.

| Mom Test Output | 100m-offers Input |
|-----------------|-------------------|
| "I lost 4 hours a week to manual reporting" | Time delay lever (reduce) |
| "I almost got fired last quarter" | Dream outcome (specific stakes) |
| "I pay a contractor $1500/mo for this" | Price anchor + total value math |
| 15 obstacles named in conversations | Step 2 obstacle list (no need to invent) |

### mom-test + spin-selling

Spin Selling structures questions for in-person enterprise sales calls. Mom Test structures questions for early-stage idea validation. They share DNA (past-behavior, problem-implication-need-payoff) but operate at different stages.

| Question Type | Mom Test | SPIN |
|---------------|----------|------|
| Background | "Walk me through your week" | Situation |
| Pain | "What's the cost of doing nothing?" | Problem + Implication |
| Solution fit | "Have you tried solving this?" | Need-Payoff |
| Commitment | "Would you put money on this?" | Closing/Advancing |

Use Mom Test for discovery interviews. Switch to SPIN once you have a product to sell into a defined buying process.

### mom-test + obviously-awesome

Mom Test reveals which segment is "the one." Obviously Awesome positions for that segment. Sequence: interview → identify segment with most pain + most willingness to pay → position around that segment's worldview.

### mom-test + crossing-the-chasm

Crossing the Chasm distinguishes early-adopter behavior from mainstream behavior. Mom Test interviews can mislead if you only talk to early adopters - their needs differ. Use Mom Test on both groups separately, label which is which, don't average them.

## Conflicts and Tensions

### Conflict 1: "Don't tell them what their problem is" vs domain expertise

**Mom Test rule:** They own the problem. Don't put words in their mouths.

**Reality:** In some industries (medical, technical, regulatory), customers genuinely don't have the vocabulary or framework to articulate their problem. A radiologist can describe symptoms but may not articulate "we need a workflow tool that auto-prioritizes urgent scans."

**Resolution:** Lead with open questions. If they describe a workflow that obviously has a problem, name it carefully ("It sounds like X is slowing you down - is that right?") rather than imposing it ("You need an X tool, right?").

### Conflict 2: Mom Test caution vs Lean Startup speed

**Mom Test:** Be careful, don't pitch, take weeks.
**Lean Startup:** Build-measure-learn loops fast.

**Resolution:** They're not opposed. Mom Test interviews complement build-measure-learn. Use Mom Test for the discovery loop ("What problem matters?"), Lean Startup for the validation loop ("Does my solution work?").

Don't use Mom Test endlessly to avoid building. Don't use Lean Startup to skip listening.

### Conflict 3: "Talk less" vs sales/closing skills

**Mom Test:** The more you're talking, the worse you're doing.
**Sales:** Persuasion requires articulating value.

**Resolution:** Different stages. In discovery (Mom Test), shut up. In sales (after you have a product and validated market), articulate. Don't conflate them. A "discovery call" that's secretly a pitch fails at both.

### Conflict 4: Hypothesis-driven vs ethnographic

**Hypothesis-driven:** Form a specific belief, design questions to test it.
**Ethnographic:** Observe without preconceptions.

**Resolution:** Mom Test leans ethnographic but accepts hypotheses. The trick is: have hypotheses, don't lead the witness. "I think founders struggle with X" → "Walk me through your week" (open observation), then check if X comes up unprompted.

If you have to lead them to your hypothesis, the hypothesis is probably wrong.

## When to Stop Using Mom Test

You're past the discovery phase when:

- Multiple people describe the same problem in similar words
- You can predict the next interview's answers
- People are paying you (deposits, LOIs, real money)
- You can name a single, specific, findable customer segment
- You have at least one earlyvangelist actively pushing for the product

At that point, switch from interviews to building, and use sales conversations (SPIN, etc.) instead of discovery conversations.

## Anti-Pattern: "I've done 50 interviews and still don't know what to build"

This is a customer slicing problem, not a question quality problem. Going to interview 51 won't help.

**Fix:** Stop interviewing. Look at your notes. Find the segment whose pain was most visceral, most expensive, most concrete. Re-interview only that segment. Almost always, you've been mixing 3+ segments and averaging into mush.

---
name: mom-test
description: Validates business ideas through customer conversations using Rob Fitzpatrick's Mom Test framework. Use when planning user interviews, getting product feedback, validating ideas, designing discovery questions, or extracting honest signal from biased customer responses. Covers good vs bad questions, deflecting compliments, anchoring fluff, pressing for commitment, and customer slicing.
---

> **Note:** This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.


# The Mom Test

> "How to talk to customers and learn if your business is a good idea when everyone is lying to you" - Rob Fitzpatrick

## The 3 Core Rules

1. **Talk about their life, not your idea**
2. **Ask about specifics in the past, not generics or opinions about the future**
3. **Talk less, listen more**

## Decision Tree

```
Need customer feedback?
├─ Pre-product, no idea what to build → Mom Test (this skill)
├─ Have validated market, packaging product → 100m-offers
├─ Have offer, need traffic → 100m-leads
└─ Selling enterprise → spin-selling
```

```
In a customer conversation?
├─ They're complimenting you → DEFLECT to current behavior
├─ They're speaking in generics ("usually", "always") → ANCHOR to last specific instance
├─ They're requesting features → DIG to underlying motivation
└─ They're committing nothing → PRESS for time/reputation/money
```

## Bad Questions (Never Ask)

| Question | Why It Fails |
|----------|--------------|
| "Do you think it's a good idea?" | Only the market can tell. Opinions are worthless. |
| "Would you buy a product which did X?" | Everyone says yes. Hypotheticals are lies. |
| "How much would you pay for X?" | Numbers feel rigorous but are still lies. |
| "Do you ever..." / "Would you ever..." | Invites fluff and future-tense promises. |

## Good Questions (Use These)

| Question | What It Reveals |
|----------|-----------------|
| "Why do you bother?" | Real motivation behind perceived problem |
| "What are the implications?" | Must-solve vs nice-to-have |
| "Talk me through the last time that happened." | Concrete past behavior |
| "What else have you tried?" | Whether they care enough to search |
| "How are you dealing with it now?" | Current solution + price anchor |
| "Where does the money come from?" | Budget and purchasing process |
| "Who else should I talk to?" | Tests if they care enough to make intros |
| "Is there anything else I should have asked?" | Catches missed points |

## Three Types of Bad Data + Responses

| Bad Data | Example | Response |
|----------|---------|----------|
| **Compliments** | "That's really cool, I love it." | "Thanks - but how are you dealing with this stuff at the moment?" |
| **Fluff** | "I usually..." / "I would definitely buy that." | "When's the last time that happened? Walk me through it." |
| **Ideas/Features** | "Can you add X feature?" | "Why do you want that? What would it let you do? How are you coping without it?" |

## Commitment Currencies

Real interest = giving up something valuable. Compliments cost nothing.

| Currency | Examples |
|----------|----------|
| **Time** | Clear next meeting, using trial for real, sitting down for feedback |
| **Reputation** | Intro to peers, intro to boss, public testimonial |
| **Money** | Letter of intent, pre-order, deposit |

### Good Meeting Endings
- "What are the next steps?"
- "When can we start the trial?"
- "Can I buy the prototype?"
- "When can you come back to talk to the rest of the team?"

### Polite Rejections (Bad Endings)
- "That's so cool, I love it!"
- "Let me know when it launches."
- "I would definitely buy that."

## Critical Principle

**They own the problem. You own the solution.**

You aren't allowed to tell them what their problem is. They aren't allowed to tell you what to build.

## The Filter Test

If they haven't even Googled for a solution, they don't actually care enough to pay for yours.

## Customer Slicing

### Signs Your Segment Is Too Broad
- 10+ conversations, results all over the map
- Everything "sort of works" but nothing breaks through
- Cannot prove yourself right or wrong
- Every feature is someone's favorite
- Massive price variance ($10 vs $10,000)

### The Slicing Process
1. Within this group, who would want it MOST?
2. Why do they want it? What's their specific problem?
3. What are they already doing to solve it?
4. Where can we find them?

**Good segment test:** A segment is useful only if you know WHERE to find them.

## Conversation Length Guide

| Duration | Goal |
|----------|------|
| 5 min | Does problem exist? Is it important? |
| 10-15 min | Workflow details, what they've tried |
| 1+ hour | Industry deep-dives with experts |

## Keep It Casual

- Strip the formality - reduce "meeting" to "chat"
- Pop your most important question immediately
- Goal: they don't even realize they've "had a meeting"
- 5-10 minute casual conversations yield as much as formal meetings

## Process Checklist

### Before
- [ ] Choose focused, findable segment
- [ ] Decide 3 big learning goals with team
- [ ] Decide ideal next steps and commitments
- [ ] Do basic desk research first

### During
- [ ] Frame the conversation
- [ ] Keep it casual
- [ ] Ask questions that pass The Mom Test
- [ ] Deflect compliments, anchor fluff, dig beneath signals
- [ ] Take good notes
- [ ] Press for commitment and next steps

### After
- [ ] Review notes and key quotes with team
- [ ] Update beliefs and plans
- [ ] Decide next 3 big questions

## Signs You're Doing It Wrong

- You're talking more than they are
- They're complimenting you or your idea
- You don't have notes
- You got an unexpected answer and didn't change anything
- You weren't scared of any question you asked
- You don't know what happens next
- Meeting "went well" but no concrete commitments

## Quick Rules

Rules not already captured in the tables and checklists above:

1. Customer conversations are bad by default. Your job to fix them.
2. People know problems but not solutions. Don't ask what to build.
3. You should be terrified of at least one question you're asking (terrified of the answer, not the asking).
4. There's more reliable information in a "meh" than a "Wow!"
5. It's not a real lead until you've given them a concrete chance to reject you.

## Timeline

Spend a week, maybe two. Get your bearings, then give them something to commit to. Don't spend months theorizing.

## Context: Founders vs. Product Teams

This framework is written for founders validating whether a new idea is worth pursuing at all. If you're a product manager at an established company, your situation is different: you already know customers want the product. Your interviews are doing problem discovery (what's broken?) or feature discovery (which direction next?) with existing users - not testing whether a market exists. The "press for commitment" and customer-slicing sections are largely irrelevant. The core questioning mechanics (past behavior, avoid hypotheticals, anchor fluff) still apply directly.

## When This Doesn't Apply

- **Formal B2B/Enterprise:** Some contexts require formal protocols
- **Regulated industries:** Healthcare, finance may need different approaches
- **Truly novel innovations:** Customers can't imagine what they want until they see it
- **Cultural contexts:** Japan, Germany, formal corporate cultures expect different protocols
- **Domain experts:** Expert opinions about THEIR domain carry weight (the rule is about opinions on YOUR IDEA)

## Red Flags (Customers to Avoid)

Even enthusiastic, paying customers can derail you:
- Needs so specific they'll pull you off-course
- Demand custom work that doesn't generalize
- "Visionaries" who want something completely different from your vision
- Will only commit if you build their pet feature first

## Supporting Files

- **[frameworks.md](frameworks.md)** - VFWPA email template, ACA framework, deeper question hierarchy, finding-conversations playbook
- **[cases.md](cases.md)** - Earlyvangelist concept (Steve Blank's term, used by Fitzpatrick), case-style examples
- **[examples.md](examples.md)** - Note-taking symbols, full email scripts, conversation walk-throughs
- **[integration.md](integration.md)** - How Mom Test feeds 100m-offers, 100m-leads, spin-selling, obviously-awesome; conflicts with hypothesis-testing approaches

## The Nuance

- "Talk less" means don't pitch your solution, not don't talk at all. Strategic questions and redirections are talking.
- "Be terrified of a question" means terrified of the ANSWER (it might invalidate your idea), not asking aggressive questions.
- "Press for commitment" doesn't mean be pushy. Know when to back off. Burning a contact is worse than no commitment.
- "They can't tell you what to build" doesn't mean ignore domain experts. Sophisticated users may know implementation better than you - understand the WHY.