Experienced product teams value user research, as they should, but new entrants are misled by famous quotes that seem to dismiss it.
User development is the foundation of building products that truly solve real problems. Without it, you risk building features that nobody wants or using assumptions that do not hold in the market. The trap is thinking user research is optional or that customers can always tell you what to build.
This lesson clarifies why user research matters, how to do it efficiently, and how to interpret what users say versus what they actually do. You will learn how to avoid common confusions caused by famous quotes and how to tailor your research approach in fast-moving Indian startup environments.
The myth of "faster horses" and "users don't know what they want"
Two quotes often cause confusion about user research:
- Henry Ford supposedly said, “If I’d asked customers what they wanted, they would have said a faster horse.”
- Steve Jobs said, “It’s really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them.”
These statements are frequently used to argue that user research is useless or misleading. The reality is different.
Talvinder Singh explains:
“Experienced product teams value user research, as they should, but new entrants are misled by these statements.” The problem is misunderstanding what these quotes actually mean.
Ford’s quote is often taken literally, but the key behavioral insight is “fast.” Customers knew they wanted faster transport, but their mental model was limited to horses. Great product managers see beyond the literal request to the underlying need.
Jobs was emphasizing that users often cannot articulate innovative solutions because they only know existing paradigms. His point was that observing user behavior and experimenting with prototypes reveals true needs better than just asking users what they want.
The lesson: User research is not about asking users to design your product. It is about understanding their problems, behaviors, and pain points deeply — often beyond what they say explicitly.
Why user development is critical for product managers
User development is the first phase in the lifecycle of any new feature or product. It precedes product definition, implementation, launch, and evaluation.
India’s market diversity makes user research more important than ever. Even within seemingly homogeneous groups, needs and behaviors vary widely. Use cases evolve rapidly, and new services disrupt existing models constantly.
Pain points and unmet needs that were previously invisible are now visible and critical to identify.
Talvinder Singh emphasizes:
“User research is an overarching technique critical to product management decision making.”
Without it, you risk building products that fail to meet real customer needs or that miss emerging market shifts.
Attitudinal vs Behavioral research: what users say vs what users do
User research methods broadly fall into three dimensions:
- Attitudinal vs Behavioral
- Qualitative vs Quantitative
- Context of use
The key dimension to understand is attitudinal versus behavioral.
Attitudinal research captures what users say — their beliefs, preferences, and self-reported reasons for actions. Common methods include surveys and interviews.
The challenge: users often want to be perceived a certain way or may rationalize their choices inaccurately. For example, a user might say quality matters most, but price actually drives their decisions. This is a common bias in attitudinal methods.
Behavioral research focuses on what users actually do — their actions, habits, and real-world behaviors. It often reveals the true drivers behind decisions, beyond stated preferences.
Talvinder Singh explains:
“When Jobs said that users don’t know what they want, he really meant that to build great products, you need to observe their behavior and not rely on what they say.”
Great product managers know how to use both attitudinal and behavioral methods appropriately. Behavioral insights often reveal the core value users seek, even if users cannot articulate it.
Fast user research in startup contexts: balancing rigor and speed
Startups in India often operate at warp speed. Shipping products and features quickly is essential.
This creates tension: you cannot always do in-depth user research or large focus groups. You need to get insights fast enough to keep up with development cycles.
Talvinder Singh advises:
“Except on very simple consumer apps, I’ve shied away from focus groups and online surveys. Focus groups mostly fail because a few participants dominate, and differences between individuals are often more interesting than commonalities. Online surveys often suffer from biases inherent in fixed-choice answers.”
Instead, he recommends a mix of two approaches:
-
Extended one-on-one open-format interviews.
Face-to-face or phone conversations with a prepared list of questions to solicit detailed responses. This helps uncover unexpected insights and patterns. -
Narrow, goal-directed, lean-style research.
For urgent questions (e.g., signup flow issues), reach out to a small set of relevant users for focused interviews. Confirm they fit your audience and ask about their actual behavior and motivations.
Doing three in-depth interviews per week can quickly build deep understanding of your customer base.
Synthesizing and applying user research insights
Collecting research is only half the job. The other half is synthesizing findings into actionable insights that drive product decisions.
Look for patterns and contradictions across different users. Use both attitudinal and behavioral data to triangulate the real needs.
Avoid these pitfalls:
- Taking user statements at face value without observing behavior
- Over-generalizing from small or biased samples
- Ignoring context of use and evolving market conditions
Talvinder Singh reminds:
“Great product managers identify subtleties, like the difference between what users say and what they actually do. This is how you find the core user problem to solve.”
User research methods overview
User research methods vary depending on goals and contexts.
Some common attitudinal methods
- Surveys (quantitative)
- One-on-one interviews (qualitative)
- Card sorting (understanding mental models)
Some common behavioral methods
- User observation
- Usability testing with prototypes
- Analytics and usage data analysis
Combining methods
No single method suffices. Use multiple methods to validate and enrich insights.
For example, card sorting can reveal how users categorize information, guiding information architecture design.
User development vs buyer research
User development focuses on understanding actual users, their problems, and behaviors. Buyer research focuses on the decision-makers who purchase the product, which may be distinct from end users.
In B2B or enterprise contexts common in India, buyer research is crucial because buyers may have different priorities than users.
Balancing user and buyer insights is key to product success.
Example: Why ignoring user research costs you
Imagine a fintech startup in Bangalore building a new payments feature.
Without user research, the team assumes users want a sleek dashboard with advanced analytics.
But behavioral research reveals that most users are overwhelmed by data and prefer simple, quick payment flows.
Ignoring this leads to a product nobody adopts.
User research would have saved months of wasted effort.
Tips for doing user research faster
- Set clear research goals before you start
- Prioritize interviews with diverse users, including extreme cases
- Take detailed notes and share them immediately with the team
- Look for “golden insights” that challenge assumptions
- Use lightweight prototypes for early testing
- Avoid large focus groups unless absolutely necessary
Supporting media: Talvinder on user development
This video covers the core concepts of user development and practical tips for faster research.
Test yourself: User research prioritization
You are a PM at a Series A Indian healthtech startup building a telemedicine platform. The engineering lead wants to build a detailed patient dashboard. The sales lead wants a feature to integrate with local pharmacies. You have two weeks before the next sprint planning.
The call: How do you decide what user research to conduct in this time? What methods do you choose and why?
Your reasoning:
Where to go next
- Learn methods to conduct effective user interviews: User Research Methods
- Understand how to synthesize research into product insights: Problem Discovery and Validation
- Explore buyer research techniques for B2B contexts: Buyer Research and Stakeholder Management
- Master rapid experimentation and prototyping: Lean Startup and MVPs