17:31
How To Talk To Users | Startup School
Y Combinator
Overview
This video explains the critical importance of founders talking directly to their users and customers throughout a company's lifecycle. It details how to find potential users, conduct effective interviews by focusing on problems rather than solutions, and avoid common pitfalls like asking leading questions. The speaker emphasizes learning from user feedback to build a Minimum Viable Product (MVP) and stresses the value of continuous user engagement, even after the product is launched. The core message is that deep user understanding, not just product ideas, drives startup success.
How was this?
Save this permanently with flashcards, quizzes, and AI chat
Chapters
- Founders must engage with users throughout the company's life, not just at the idea stage.
- Users are the ultimate stakeholders who pay for the product and provide honest feedback.
- Learning directly from users keeps founders grounded and ensures product-market fit.
- Examples like Airbnb's early days show how direct customer interaction led to product evolution.
Understanding user needs directly prevents founders from building products nobody wants, saving time and resources by focusing on genuine problems.
Brian Chesky of Airbnb lived in 50 different Airbnb apartments to gain firsthand insights from hosts, demonstrating a deep commitment to understanding user experience.
- Start by reaching out to your existing network, but don't rely solely on them as they might be less critical.
- Leverage professional networks like LinkedIn, online communities (forums, Slack, Discord), and industry events to find users outside your immediate circle.
- When contacting strangers, be clear, concise, and respectful of their time, requesting a brief call.
- For a mock startup focused on carbon emissions, the founder identified potential users as CEOs, CFOs, and individuals with 'carbon,' 'climate,' or 'sustainability' titles.
Identifying and reaching the right people is the first step to gathering unbiased, actionable feedback that can shape your product strategy.
Outreach messages on LinkedIn were crafted differently for former colleagues (mentioning shared history) versus unknown individuals (focusing on the project's relevance).
- Prioritize video calls or in-person interviews over text-based communication for richer insights.
- Build rapport with interviewees to encourage open and honest sharing.
- Crucially, avoid introducing your product idea early; focus on listening and understanding the user's problem.
- Use open-ended follow-up questions like 'Tell me more about that' or 'Why is that important?' to probe deeper.
- Observe user behavior, not just their stated opinions, by asking them to demonstrate their current processes.
Asking the right questions and actively listening allows you to uncover the true pain points and motivations behind user behavior, which is essential for problem-solving.
An interview with 'Amy' about carbon emissions revealed that while her company cared, they struggled with dense PDF reports and lacked clear action steps, highlighting a problem with information usability, not just data collection.
- Focus on understanding the user's current process ('How do you do X today?'), challenges ('What's the hardest part?'), and motivations ('Why is it important?').
- Ask about existing solutions to understand the competitive landscape and user workarounds.
- Avoid asking direct questions about your potential product ('Will you use our product?') or soliciting feature ideas ('What features would make it better?').
- Steer clear of yes/no questions and avoid asking two questions at once.
- The biggest danger is focusing on features instead of deeply understanding the core problem.
Knowing what to ask and what to avoid ensures you gather genuine insights into user problems, rather than biased opinions or premature feature requests.
Instead of asking 'Would you like a feature to track emissions?', ask 'Tell me about how your company currently tracks carbon emissions and what challenges you face.'
- Organize interview notes to identify recurring problems and synthesize key learnings.
- Formulate a hypothesis for a solution based on the identified problems.
- Develop a Minimum Viable Product (MVP) quickly, focusing on solving the core validated problem.
- Validate the problem's value by checking if people pay for existing solutions or if current workarounds (like Excel) are cumbersome.
- Consider the ease of selling to your target audience when defining your MVP and go-to-market strategy.
Translating user feedback into a testable MVP allows you to validate your solution efficiently and iterate based on real-world usage.
If users struggle with dense carbon emission reports, an MVP might be a simplified dashboard that translates complex data into actionable insights, rather than a full-fledged reporting tool.
- Test your MVP, even if it's just a design prototype, with real users.
- Observe users interacting with the prototype without guiding them excessively; let them explore naturally.
- Encourage users to 'think aloud' during testing to capture their immediate thoughts and interpretations.
- Maintain ongoing communication with early users, perhaps through dedicated Slack or WhatsApp groups.
- Show users your progress and react to their feedback to build trust and demonstrate responsiveness.
Continuous testing and feedback loops with users ensure your product evolves in a direction that truly meets their needs and builds loyalty.
Showing an early Airbnb app prototype to people waiting in the office and observing how they attempt to make a booking, without telling them how.
Key takeaways
- Direct user interaction is non-negotiable for startup success.
- Focus interviews on understanding problems, not pitching solutions.
- Listen more than you talk during user conversations.
- Observe user behavior to uncover unmet needs.
- Users often have problems but poor solutions; your job is to find the problem.
- Build an MVP based on validated user problems, not assumptions.
- Continuous user engagement fosters trust and product improvement.
- Honest feedback, even if critical, is invaluable for growth.
Key terms
FounderUserCustomerMinimum Viable Product (MVP)FeedbackRapportOpen-ended questionsHypothesisPrototypeProduct-market fit
Test your understanding
- Why is it crucial for founders to talk to users throughout the entire lifecycle of a company?
- What are the key differences between asking users about problems versus asking them for product features?
- How can a founder effectively find and approach potential users who are outside of their immediate network?
- What are the most important principles to follow when conducting a user interview to ensure you gather valuable insights?
- How can user feedback be translated into a practical Minimum Viable Product (MVP)?