The Problem: Your Mom Will Lie To You (Politely)
Rob Fitzpatrick's insight is brutal and true: people lie to founders because they're kind. In India, this is amplified by cultural politeness. A user won't tell you your product is useless. They'll say 'haan, bilkul interesting idea.' Then they'll never use it.
You ask: 'Would you use this app for expense tracking?'
They answer: 'Yes, definitely.'
You build for three months.
They disappear.
You've been lied to. But not maliciously. They wanted to be nice.
The Mom Test Framework: Three Rules
Rule 1: Talk About Their Life, Not Your Idea
Bad: 'Do you struggle with managing your remote team?'
Good: 'How do you currently manage your remote team?'
Bad question presumes a problem. Good question observes reality. You're not leading the witness. You're asking them to describe their actual life.
When you pitch first, users rationalize backward. They convince themselves the problem exists because you just mentioned it. In India's startup ecosystem, this is especially common—founders pitch, investors say yes out of politeness, and everyone wastes time.
Rule 2: Ask About Specific Past Behavior
Bad: 'Do you get frustrated with payment delays?'
Good: 'Tell me about the last time you couldn't pay someone. What did you do?'
Future intentions are noise. Past behavior is signal. Fitzpatrick calls this the 'commitment and consistency heuristic'—people reveal truth through what they've actually done, not what they say they'll do.
A Bangalore SaaS founder asked 50 HR managers: 'Would you pay for automated leave tracking?' Forty-five said yes. When he asked, 'Tell me about the last time your leave process broke,' only three had a story. The other 42 had never actually faced the problem.
Rule 3: Listen for Specific Objections
Bad feedback: 'It's a good idea. I'd definitely use it.'
Good feedback: 'We tried something similar last year, but our team rejected it because they wanted to see comments.'
Specificity is honesty. Vagueness is a polite brush-off. When someone says 'interesting,' they've mentally moved on. When someone says 'we'd need integration with Slack,' you've found a real constraint.
Track the pattern: if three users independently mention the same objection, it's real. If you hear it once, it might be a one-off preference.
The Framework in Action: Two Examples
Example 1: The B2B Trap
Your idea: a tool for Indian small business owners to manage invoices.
Wrong approach:
- 'Do you struggle with invoicing?'
- 'Would you pay ₹500/month for this?'
- 'How many small business owners do you know?'
Right approach:
- 'Walk me through the last time you sent an invoice. What happened?'
- 'How long did it take? What annoyed you?'
- 'What did you do about it?'
- 'Have you tried any tools?'
- 'Why did you stop using it?'
The fourth and fifth questions are where truth lives. People discard products for real reasons. Understanding those reasons tells you what actually matters.
Example 2: The Feature Creep Killer
Your users say: 'Add multi-user access, advanced reporting, and API integrations.'
You could build all three. Or ask:
- 'Tell me about the last time you needed multi-user access.'
- 'What did you do instead?'
- 'How much time did it waste?'
One user might have needed it once in six months. Another might have built a workaround. A third might have switched tools. Same feature request, three different truths.
The Non-Obvious Insight: Compliments Are Warnings
Scott Belsky's "The Messy Middle" emphasizes listening to what gets ignored, not what gets praised. A Y Combinator partner put it sharply: 'If everyone loves your idea, you're probably talking to the wrong people or asking the wrong questions.'
When 20 potential users say 'great idea,' you've failed at validation. You've gotten politeness, not data. Good validation feels uncomfortable—it's specific pushback, not enthusiasm.
Indian founders especially need to internalize this. Positive feedback is the default. Your job is to find the skeptics and understand why they're skeptical.
How to Implement This Week
1. Identify 5-10 actual users of the problem (not hypothetical users).
2. Ask them to describe a specific moment last week when the problem occurred.
3. Write down their exact words. Don't paraphrase.
4. Look for patterns in what they did, not what they said they'd do.
5. Track objections by specificity. Vague praise gets zero points.
Actionable Takeaway
Before your next user interview, write down the three worst questions you could ask. Then delete them. Replace each with a question about past behavior. Record the call. Listen for moments where they describe actual friction, not hypothetical interest. That friction is your product roadmap.
The Mom Test isn't about tricking users. It's about respecting their time enough to ask real questions. Build what solves actual problems, not what sounds nice in a pitch.