Customer discovery: talking to users
Why this matters
You can't solve a problem effectively unless you truly understand the people who have it. Talking to potential users helps you confirm if the problem is real, how severe it is, and what they really need, preventing you from building something nobody wants.
7-day study plan
- Read
Before you build anything, you must know who you are building for. In entrepreneurship, a 'User' is not just a general category like 'students' or 'Indians.' A user is a specific person who experiences the specific pain you want to solve. If you try to solve a problem for everyone, you end up solving it for no one. Defining your user means narrowing down their age, their daily habits, and the specific context in which they face a problem. Imagine you want to start a healthy snack brand. Instead of saying your user is 'anyone who is hungry,' define them more specifically. Your user might be 'a college student in Delhi who has back-to-back classes from 9 AM to 4 PM and often skips lunch, leading them to buy oily samosas from the canteen even though they want to stay fit.' This level of detail helps you understand their constraints, like budget and time. To define your user, follow these three steps: First, identify the core problem. Second, visualize the person who suffers most from this problem. Third, write a short description that includes their name (imaginary), their goal, and what stops them from achieving it. This persona will guide every conversation you have during the customer discovery phase. It keeps you focused on real human needs rather than abstract ideas.
DoDefine who your potential 'user' is for a problem you identified last week. Describe them in 3 sentences.
Check yourself- Can I describe my user's daily routine related to the problem?
- Is my user definition specific enough to exclude people who don't have this problem?
- Do I know the primary goal my user is trying to achieve?
Revision notes
- Customer discovery is about listening, not selling your idea.
- Talk to potential users to understand their 'pain points' deeply.
- Ask open-ended questions (e.g., 'Tell me about...', 'How do you currently...?').
- Avoid leading questions that suggest a solution; let them speak freely.
- Listen for emotions and real-life examples, not just opinions.
- Look for patterns across multiple conversations.
- The goal is to validate the problem, not your solution.
- Users might not know what they want, but they know what bothers them.
Global case studies
Revolutionizing school transport for safety
Safe Bus founders identified a major pain point for Indian parents: anxiety about their children's safety and whereabouts during school commutes. Through extensive discussions with parents and school administrators, they understood the deep need for real-time tracking and communication, leading them to develop a robust IoT-based solution.
Takeaway: Deep empathy and direct engagement with users (parents and schools) are crucial to build trust and tailor solutions to critical safety concerns.
The early days of Airbnb
When Airbnb was struggling, its founders manually went to their users' (hosts') homes in New York City. They talked to them, took professional photos of their listings, and personally understood their challenges and needs. This direct customer interaction revealed critical insights that helped them refine their product and attract more users.
Takeaway: Directly engaging with and observing users in their environment can uncover deep insights essential for product improvement and growth.
Try this week
Identify a problem you care about (e.g., students forgetting their water bottles). Find three students (or teachers/parents) who might face this problem. Ask them questions like: 'Tell me about a time you forgot your water bottle. How did it make you feel? What did you do?' Don't offer solutions yet, just listen!
Chapter test
One combined MCQ test for all 10 lessons in this chapter. 1 mark per question, no negative marking. Score 60% or more to unlock your certificate.
Chapter test