Research is the bridge between an innovator’s dream and the real world.
User research is not a theoretical exercise. It is the foundation that separates wishful thinking from reality. Without research, your product decisions rest on assumptions that will almost certainly be wrong. The actual job is to find your users, understand their world, and test your hypotheses quickly and efficiently.
In practice, user research is a blend of art and discipline. You must know who to talk to, what questions to ask, and how to listen without bias. Then you must convert those conversations into insights that your team can act on — not vague feelings, but specific findings and recommendations.
Planning research with a customer development mindset
The core of user development is understanding your users’ habits, context, and pain points. Talvinder often emphasizes starting with these questions:
| Who are my users? | What are their habits? | Where do they access my product? |
|---|---|---|
| Are they individuals or businesses? Parents, friends, or siblings? | Are they creating content or merely sharing? | Mobile app, desktop, or web? Which platforms do they prefer? |
| When do they need your product? | Why do they need your product? | How do they currently access similar products? |
|---|---|---|
| Is it tied to a specific time of day or event? | Are existing solutions inadequate or missing? | Is it a one-time download or ongoing use? |
This matrix helps you segment your users and identify early adopters. It also surfaces assumptions you need to test — for example, that users primarily access your product via mobile, or that they have a specific unmet need.
Product discovery kickoff at a seed-stage startup in Bangalore
You (PM): “We need to define our customer segments clearly. Are we targeting parents, teachers, or kids directly? What platforms do they use?”
Founder: “I think parents mostly use WhatsApp, and kids use mobile apps, but we don’t have solid data.”
You (PM): “Let's validate that with 10 interviews this week before we finalize assumptions.”
This early alignment prevents months of building the wrong product.
The team is eager to build, but the user definition is still vague.
Conducting problem interviews that uncover real needs
A well-structured interview script is your roadmap to uncovering user truth. Talvinder recommends a format based on Ash Maurya’s Running Lean approach, which breaks the interview into these stages:
- Welcome (2 min): Set the stage. Explain the purpose without selling your product.
- Collect Demographics (2 min): Confirm the interviewee fits your target segment.
- Tell a Story (2 min): Help the user recall relevant experiences.
- Problem Ranking (4 min): Ask them to prioritize their problems.
- Explore Customer's Worldview (15 min): Understand current behaviors and workarounds.
- Wrapping Up (2 min): Get permission to follow up and ask for referrals.
- Document Results (5 min): Immediately record key findings and impressions.
The trap is asking yes/no questions or leading interviewees toward your solution. Instead, ask open-ended questions that reveal their actual behavior: “What do you usually do to solve this problem?” rather than “Would you use a product like this?”
Interviewing enough users, and the right ones
Talvinder advises interviewing 7 to 10 users per segment to start seeing patterns. The interviewees must fit your customer segments precisely — no friends or colleagues who don’t represent your users.
Record these sessions in whatever way possible: video, audio, or detailed notes. The priority is capturing raw data that you can analyze later.
- Define 2-3 customer segments using the questions in the planning matrix.
- Prepare your interview script based on the structure above.
- Recruit 7-10 interviewees per segment who fit your criteria.
- Conduct interviews, focusing on listening more than talking.
- Record responses and your impressions immediately after each session.
Converting interviews into actionable documentation
Raw interview data is useless without synthesis. Talvinder stresses the importance of mapping user flows and summarizing findings clearly.
One effective approach is to:
- Map the current user journey or workflow with flow diagrams, including screenshots or images where relevant.
- Create a findings matrix listing:
- The problem category
- Specific findings from interviews
- Recommendations for product or process changes
- Severity of the issue or business value
- Estimated effort to implement
Here is a sample findings matrix from a real product discovery:
| # | Category | Finding | Recommendation | Severity / Business Value | Effort to Implement |
|---|---|---|---|---|---|
| 1 | Customer Sanity Check | 80% of client issues relate to email authentication failures (SPF/DKIM missing) | AMs should educate new clients on adding SPF/DKIM records during onboarding. | High | None |
| 2 | Mail Logs | Email specialists struggle to analyze root causes due to paused mail log ingestion project | Restart mail log parsing project to speed up issue resolution. | High | Medium |
| 3 | New Tool - Email Validation | Frequent typos in email domains lower open rates | Implement a domain suggestion tool like mailcheck.js to reduce mistakes. | Medium | Medium |
Post-interview synthesis meeting with product and engineering teams
You (PM): “Most users struggle with email validation and often mistype domains. This causes deliverability issues.”
Engineering Lead: “We could integrate a domain suggestion feature to catch typos.”
Support Lead: “Educating clients on SPF/DKIM during onboarding would reduce tickets drastically.”
You (PM): “Great. Let’s prioritize these fixes in our next sprint.”
Turning research into prioritized actions that the team can execute
The research mindset: continuous learning over perfect data
Talvinder’s pattern recognition across thousands of PMs reveals this truth: perfect user research is a myth, but continuous learning is a must.
You cannot wait for large-scale surveys or perfect data. Instead:
- Build lean research into your development cycle.
- Use small, frequent studies like guerrilla usability tests or remote interviews.
- Leverage analytics and customer support feedback as ongoing sources of insight.
- Encourage your team to ask “why” and “how” about user behavior constantly.
Test yourself: Prioritizing research under time pressure
You are a PM at a Series A SaaS startup in Mumbai. The leadership wants you to validate three customer segments quickly: small businesses, mid-market enterprises, and freelancers. You have two weeks before the next board review.
The call: How do you plan your research to maximize insights within the time constraint? Which segments do you prioritize interviewing first, and why?
Your reasoning:
You are a PM at a Series A SaaS startup in Mumbai. The leadership wants you to validate three customer segments quickly: small businesses, mid-market enterprises, and freelancers. You have two weeks before the next board review.
Your task: How do you plan your research to maximize insights within the time constraint? Which segments do you prioritize interviewing first, and why?
your reasoning:
Where to go next
- Deepen your user research skills: User Research Methods
- Learn to synthesize user insights into strategy: Product Vision and Strategy
- Build empathy through structured discovery: Customer Discovery and Validation
- Prepare for user research interviews: Conducting Effective Interviews