Key Moments

Eric Migicovsky - How to Talk to Users

Y CombinatorY Combinator
Science & Technology3 min read32 min video
Jul 25, 2019|459,971 views|8,868|142
Save to Pod
TL;DR

Founders must talk to users to get crucial feedback. Avoid pitching and hypotheticals; focus on specifics and listen.

Key Insights

1

Founders should directly engage with users throughout the company's lifecycle, not delegate this critical task.

2

User interviews should focus on past specifics, not future hypotheticals or pitching the product.

3

The 'Mom Test' highlights common interview errors: pitching ideas, asking hypothetical questions, and talking too much.

4

Key questions to ask include: 'What's the hardest part?', 'Tell me about the last time...', 'Why was this hard?', 'What have you done to solve this?', and 'What don't you love about current solutions?'.

5

During the idea, prototype, and iteration stages, user feedback is vital for refining the product and achieving product-market fit.

6

When identifying early customers, quantify the cost of the problem, its frequency, and the customer's budget for a solution.

THE FOUNDER'S DIRECT CONNECTION TO USERS

The most successful companies are built on founders maintaining a direct, consistent connection with their users across all stages of the business. This isn't a task to be outsourced to salespeople or product managers; it's a core responsibility for founders, including engineers and developers. Direct user interaction provides invaluable, unfiltered information essential for product development and strategic decision-making, forming a foundational pillar of Y Combinator's teachings alongside building the product itself.

AVOIDING COMMON USER INTERVIEW PITFALLS

The 'Mom Test' framework highlights three critical errors founders often make in user interviews. First, avoid pitching your idea or product; the goal is to extract information, not to sell. Second, steer clear of hypothetical questions like 'Would you use this if...?'; instead, focus on specific past experiences. Finally, refrain from dominating the conversation. Listen intently, take detailed notes, and allow the user to share their insights, gathering actionable data.

STRATEGIC QUESTIONS FOR EFFECTIVE INTERVIEWS

To gather rich, actionable data, ask specific questions that delve into user experiences. Start by asking about the hardest part of a task to identify pain points. Then, request details about the last time they encountered the problem to understand the context. Inquire why it was hard to uncover underlying motivations and marketing angles. Ask what they've already done to solve it to gauge problem significance and competitive landscape. Finally, ask what troubles them about current solutions to identify specific feature gaps.

NAVIGATING USER TALK ACROSS COMPANY STAGES

User interaction is crucial at three key early-stage phases. During the 'idea stage,' focus on finding early adopters by testing your interview strategy on yourself, then friends, and leveraging warm introductions or even direct outreach like visiting fire stations. At the 'prototype stage,' use user interviews to identify your ideal first customers by quantifying the problem's cost and frequency for them, and assessing their budget for a solution. Iterate towards product-market fit by consistently gathering user feedback on product value.

IDENTIFYING PRIME EARLY ADOPTERS

When testing prototypes, identifying the right first customers is paramount to avoid misdirected development. This involves asking quantifiable questions during interviews: How much does the problem cost them (in lost revenue or wasted expense)? How frequently do they encounter it (hourly, daily, weekly)? And what is their budget for a solution? The ideal early customer experiences the problem often, incurs significant costs from it, and possesses the budget and authority to implement a solution.

ITERATING TOWARDS PRODUCT-MARKET FIT WITH DATA

Beyond vague definitions, product-market fit can be quantitatively tracked. A key method involves asking users how they'd feel if they could no longer use your product, aiming for over 40% to report being 'very disappointed.' This metric indicates strong product value and integration into users' lives. Additionally, test feature desirability not by asking if users want them, but by including them in a paid upgrade flow to gauge commitment. Critically, learn to discard vague compliments and hypothetical fluff in favor of specific, actionable feedback.

User Interview Best Practices

Practical takeaways from this episode

Do This

Focus on extracting information, not pitching your idea.
Ask about specifics that have already occurred in the user's life.
Listen more than you talk; take detailed notes.
Ask about the hardest part of their current process.
Ask about the last time they encountered the problem.
Ask 'Why was this hard?' to understand pain points and inform marketing.
Ask 'What have you done to solve this problem?' to gauge problem severity and competition.
Ask 'What don't you love about the solutions you've tried?' to identify feature gaps.
At the prototype stage, quantitatively assess cost, frequency, and budget related to the problem.
For iterating towards product-market fit, use metrics like the 'how disappointed would you be' question (aim for >40% 'very disappointed').
Ask for user phone numbers during signup for direct contact.
Discard compliments and hypothetical statements; focus on specific, actionable data.

Avoid This

Don't pitch your product or sell the user during an interview.
Don't ask hypothetical questions like 'Would you use this feature?'
Don't talk too much; let the user share their experiences.
Don't rely on friends and family for unbiased feedback (the 'Mom Test').
Don't be afraid to show up in person to talk to users if cold outreach fails.
Don't design by committee; understand the 'why' behind feature requests.
Don't treat compliments or vague positive feedback as actionable data.
Don't get sidetracked by hypothetical future product discussions; return to past experiences.

Framework for Identifying Best First Customers

Data extracted from this episode

Customer SegmentCost of Problem (Revenue/Expense)Frequency of EncounterBudget for SolutionRank
French LaundryHigh potential revenue per saleLow frequencyLow budget (e.g., Sous Chef)Lower Rank
Google CafeLow revenue/savings (free food)High frequency (many Googlers)No direct budget (food is free)Mid-Low Rank
McDonald'sModerate revenue per sale (high volume)Very high frequency (many stores, many people)High budget (multi-billion dollar budget via Chief Food Officer)Highest Rank

Common Questions

Founders must maintain a direct connection with users to extract critical information at all stages of company development. Even CEOs and technical leads should participate, as outsourcing this vital communication can lead to misunderstandings and missed opportunities. The best companies are built on founders understanding their users firsthand.

Topics

Mentioned in this video

More from Y Combinator

View all 561 summaries

Found this useful? Build your knowledge library

Get AI-powered summaries of any YouTube video, podcast, or article in seconds. Save them to your personal pods and access them anytime.

Try Summify free