User research
YOO-zer REE-surch
The practice of studying users through interviews, observation, and data analysis to understand their needs and behaviors.
User research is learning about your users by talking to them, watching them, and analyzing their behavior. It answers questions that analytics cannot: Why do users drop off at step 3? What are they trying to accomplish? What frustrates them about the current experience?
Research methods include user interviews (one-on-one conversations), usability testing (watching users attempt tasks), surveys (quantitative data from many users), and contextual inquiry (observing users in their natural environment).
The biggest mistake teams make is skipping research because they 'already know' what users want. Every PM has stories about features they were certain users needed, only to discover through research that users wanted something completely different.
Examples
A team runs usability tests on a new feature.
Five users attempt to complete a task using the new interface. Four struggle with the same step. The designer watches their screen recordings and sees the exact confusion point. They redesign that step before launch.
A PM conducts customer interviews before building.
The PM interviews 10 customers about their deployment workflow. A pattern emerges: 8 of 10 mention that rollbacks are their biggest pain point. The PM had planned to build a dashboard feature. They pivot to building better rollback tooling based on the research.
A company surveys users to prioritize features.
A survey of 500 users asks them to rank 10 potential features. The top 3 ranked features are all related to team collaboration. The PM reprioritizes the roadmap to address collaboration first.
In practice
Read more on the blog
Frequently asked questions
How many users do you need for user research?
For usability testing, 5 users typically reveal 85% of usability issues. For customer interviews, 10-15 reveal common patterns. For surveys, 100+ responses give statistically meaningful quantitative data. Quality of participants matters more than quantity.
When should you do user research?
Before building (to validate the problem and approach), during building (to test prototypes and designs), and after shipping (to measure adoption and identify improvements). Continuous research, not just pre-launch research, keeps the team connected to users.
Related terms
Observing real users as they attempt tasks in your product to identify confusion, friction, and areas for improvement.
Tools and practices for tracking how users interact with a product to inform decisions about features, onboarding, and growth.
A document that defines what a product or feature should do, who it serves, and how success will be measured.
A system for continuously collecting, analyzing, and acting on user feedback to improve the product.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.