Experienced product teams value user research, as they should, but new entrants are often misled by famous quips that dismiss its importance.
User research is foundational to product management. The actual job is to understand your users deeply — their needs, behaviors, and pain points — so you can make informed decisions about what to build. Without this insight, you risk building features that nobody wants or solving problems that don’t exist.
The stakes are high. User needs are not static. Even within seemingly uniform demographics, individual demands vary widely. Use cases evolve, and new services disrupt existing models regularly. This makes the need for continuous user development more urgent than ever.
The myth of “faster horses” and why it misleads
Henry Ford supposedly said, “If I’d asked customers what they wanted, they would have said a faster horse.” Steve Jobs famously 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 quips have caused confusion about the value of user research.
Here is the uncomfortable reality: experienced product teams value user research deeply, but newcomers often misunderstand these statements as a dismissal of research altogether. The counterargument — “Well, Jobs didn’t do user research!” — is common but misguided.
What Jobs really meant was that observing user behavior is often more insightful than relying on what users say they want. People’s stated preferences are filtered through their beliefs and mental models, which may not reveal the real problem or the best solution.
The actual job is to look beyond surface answers and uncover the underlying needs and behaviors that drive user decisions.
Why user research is critical for PM decision-making
User research is the first phase in the lifecycle of any new feature or product. Before you define the product, implement it, launch, or evaluate success, you need to understand your users.
Consider this: even within a seemingly homogeneous group, users’ needs and demands vary significantly. For example, a fintech app’s users in Mumbai might have different transaction habits and pain points compared to those in Jaipur. These differences shape what features will be valuable.
Moreover, use cases evolve over time. A customer segment that was once satisfied with manual processes may now expect automated solutions. New services disrupt the market constantly, exposing previously unexplored pain points.
User research uncovers these nuances and informs your product decisions. Without it, you build on assumptions and risk failure.
The dimensions of user research methods
User research methods broadly fall into three dimensions:
- Attitudinal vs Behavioral
- Qualitative vs Quantitative
- Context of use
Attitudinal vs Behavioral
Attitudinal research captures what people say — their beliefs, desires, and self-perceptions. Behavioral research observes what people actually do — their actions and underlying motivations.
Why does this matter? Because what people say is often different from what they do. For instance, a user might say price is the most important factor, but their purchase behavior shows they prioritize convenience.
Attitudinal methods include surveys and interviews where users self-report their preferences. Behavioral methods include usage analytics, A/B testing, and contextual inquiry.
Take Henry Ford’s “faster horse” quote. If customers had asked for a faster horse, that reflects the attitudinal model — the mental model of transportation they knew. The behavioral insight is that they wanted to travel faster. Great PMs spot this subtlety and design solutions that address the real need, not just the stated preference.
Qualitative vs Quantitative
Qualitative research generates rich, descriptive insights — stories, motivations, and pain points. Quantitative research provides numerical data — usage patterns, conversion rates, and statistical trends.
Both are necessary. Qualitative methods help you understand the “why” and “how.” Quantitative methods help you measure the “how many” and “how often.”
Context of use
Research should consider the environment where users interact with your product. For example, a mobile app used in noisy, crowded Indian streets demands different design considerations than a desktop app used in offices.
How to do user research quickly and effectively
In startups and fast-moving teams, you won’t have time for exhaustive studies or large focus groups. You need to balance rigor with speed.
Here are tips from experience:
-
Avoid focus groups and online surveys as your primary tools. Focus groups often suffer from dominant participants skewing insights and obscure individual differences. Online surveys can miss subtlety and context.
-
Prioritize one-on-one, open-format interviews. These can be face-to-face or phone calls with a flexible script that encourages users to describe their needs in their own words. Ask questions like:
- “Describe your needs related to this problem.”
- “How else would you solve this?”
- “What do you like or dislike about current solutions?”
These interviews help you capture unexpected insights and identify patterns.
-
Conduct lean, goal-directed research for urgent questions. For example, if you suspect users struggle with a sign-up flow, reach out to a small group of relevant users for 15-minute sessions focused on that issue.
-
Take detailed notes and share them internally. Listening for patterns across interviews is key to identifying high-impact insights.
-
Compensate participants fairly and consider scheduling interviews early in the day for higher energy. For example, offering ₹1500 for a two-hour session is standard practice.
-
Use prototypes or wireframes as conversation aids. Early mockups help users articulate reactions and usability issues.
-
Debrief immediately after sessions with your team to consolidate learning.
-
Track time spent on different screens or features during usability tests to identify friction points.
Differentiating user development and buyer research
User development focuses on understanding the people who use your product — their behaviors, needs, and pain points.
Buyer research focuses on the purchasing decision-makers — often different from users — and their criteria, constraints, and motivations.
In B2B contexts, the buyer might be a procurement manager, while the user is a frontline employee. Your research approach must adapt accordingly.
Synthesizing research into actionable insights
The goal of user research is to inform product decisions. This requires synthesizing disparate inputs into clear patterns and prioritized problems.
Steps to synthesize:
- Aggregate notes and recordings from interviews and tests.
- Identify recurring themes and pain points.
- Map user journeys highlighting moments of friction or delight.
- Formulate problem statements based on evidence, not assumptions.
- Validate with stakeholders and cross-functional teams.
This synthesis becomes the foundation for product definition, prioritization, and roadmap planning.
The changing landscape of user needs and why research is more important than ever
User needs are dynamic. Consider the Indian market:
- Diverse languages, literacy levels, and digital access create varied user profiles.
- Rising smartphone penetration introduces new user segments unfamiliar with traditional UX patterns.
- Rapidly evolving regulations and payment methods alter transactional behaviors.
- The pandemic accelerated digital adoption, exposing new pain points and expectations.
User research must be ongoing, not a one-time activity. Regular engagement with users helps you stay ahead of these shifts and build products that remain relevant.
Common pitfalls in user research and how to avoid them
- Taking user statements at face value. Probe deeper to uncover the real motivations behind their words.
- Over-relying on attitudinal methods. Complement with behavioral observations and data.
- Ignoring context. A feature popular in one city or demographic might fail in another.
- Failing to share insights widely. User research is only valuable if it informs the team and shapes decisions.
- Skipping synthesis. Raw data without analysis leads to noise, not clarity.
By avoiding these traps, you increase the chances your product will hit the mark.
User research in Indian startups — practical considerations
Many Indian startups operate in fast-paced environments with resource constraints. Here is what I tell PMs:
- Prioritize research that delivers actionable insights within your sprint cycles.
- Leverage existing customer relationships for quick feedback loops.
- Use remote interviews and screen sharing to save time and cost.
- Be mindful of cultural nuances and language preferences in your questions.
- Balance qualitative insights with quantitative analytics from your product.
For example, Razorpay’s PMs conduct rapid interviews with merchant users to understand payment flow pain points, complementing this with transaction data analysis.
Where to go next
- Explore user research techniques in depth: User Research Methods
- Learn how to translate research into product vision: Product Vision and Strategy
- Understand the role of buyer research in B2B contexts: Buyer Research Fundamentals
- Practice synthesizing research insights: Research Synthesis and Prioritization
Test yourself: User research prioritization challenge
You are a PM at a Series A fintech startup in Bangalore building a digital lending product for small businesses. You have a list of ten user complaints collected from customer support, but only two weeks before the next sprint planning. The engineering team can implement only one major fix. You have access to five customers for interviews.
The call: How do you prioritize which user complaints to investigate further, and what research approach will you use to validate the problem before committing engineering resources?
Your reasoning: