Great products aren't built in a vacuum. They are the result of deep, continuous engagement with the user.
1The Bias Trap
As PMs, we often fall in love with our own ideas. User research is the antidote. It forces us to confront the 'uncomfortable truth' that our assumptions might be wrong.
2Generative vs Evaluative
Generative research happens early (Discovery). Evaluative research happens late (Delivery). If you skip Generative, you'll end up perfecting a solution for a problem that doesn't exist.
3Continuous Discovery
Research isn't a one-time project. Modern PMs practice 'Continuous Discovery'—talking to at least 2-3 users every single week to keep their finger on the pulse.
4Step-by-Step Breakdown
User Research is the process of understanding user behaviors, needs, and motivations through various techniques. It's the only way to avoid building things nobody wants.
There are two main types: Generative (finding the problem) and Evaluative (testing the solution). You need both to build a successful product.
Qualitative (Why?) vs. Quantitative (How many?). Interviews and observations tell you the story; surveys and analytics give you the scale.
Which type of research is most useful for 'identifying a new market opportunity' or 'understanding a customer's daily routine'?
- →Evaluative Research
- →Generative Research
- →Usability Testing
- →A/B Testing
A Product Manager wants to know *why* users are dropping off at the checkout page. Which method should they prioritize?
- →A survey with 1,000 respondents
- →Qualitative user interviews or session recordings
- →Checking the server logs for errors
- →Asking the sales team for their opinion
Level Up 🚀
Advanced cheat sheets, SEO tricks, and interview prep for this topic.
Browser Support
Fully supported.
Fully supported.
Fully supported.
Fully supported.
Accessibility (A11y)
1Research Panels Should Include Assistive-Tech Users
If your interview and usability panels never include users who rely on screen readers, switch access, or voice control, your research will systematically miss real accessibility barriers until they show up as support tickets or complaints.
// Wrong
Recruiting screener: excludes anyone requiring 'special accommodations'.
// Right
Recruiting screener: explicitly asks about assistive technology use and includes a target quota for it.SEO Implications
- 1
Method-Comparison Queries Have High Intent
Searches like 'qualitative vs quantitative user research' or 'generative vs evaluative research' are common and often precede a real research project. Clearly labeling and contrasting these method pairs in the page text helps it match those queries directly.
Best Practices
Match the Method to the Question, Not the Habit
If you're asking 'why are users dropping off,' a survey with 1,000 responses won't tell you - you need qualitative interviews. Pick the method based on whether you need the 'why' or the 'how many.'
Run Research Continuously, Not Just Before Big Launches
Talking to 2-3 users every week keeps assumptions in check in real time, instead of discovering a wrong assumption only after a quarter of work has shipped.
Frequent Bugs
A PM runs only evaluative research (testing a solution) and skips generative research (understanding the problem), so the team builds a polished solution to a problem users don't actually have.
Before any solution design starts, run generative interviews or observation sessions to confirm the problem is real and prioritized by the user, not just assumed by the team.
Real-World Examples
Catching a Wrong Assumption Early
The team assumes users want a faster checkout, but generative interviews reveal they actually distrust the payment page's design, not its speed.
Assumption: 'Checkout needs to be faster.'
Interview finding: 'It's not slow, it just looks sketchy - no security badges, unfamiliar logo.'
Revised bet: redesign trust signals, not performance.