User Research
The complete user research hub for product managers. Research methods, free tools, framework guides, and best practices for understanding your users and validating product decisions.
What is User Research?
User research is the practice of studying real users to understand their behaviors, needs, and pain points. For product managers, research is the difference between building what you think users want and building what they actually need. Good research reduces the risk of shipping features nobody uses.
There are two broad categories: qualitative research (interviews, usability tests, contextual inquiry) reveals the "why" behind user behavior, while quantitative research (surveys, analytics, A/B tests) measures the "what" at scale. The best product teams combine both. Read our complete user research guide for a structured approach, or explore the Discovery Guide for the broader product discovery process.
User research is not a phase. It is a continuous practice. Teams that build research into their weekly cadence consistently outperform teams that only research before big bets. Our continuous discovery habits guide shows how to make research a habit, not a project.
Key Research Concepts
Qualitative Research
In-depth methods for understanding user motivations and context
Quantitative Research
Data-driven methods for measuring behavior at scale
Usability Testing
Watching real users interact with your product to find friction
User Persona
Fictional archetype representing a key user segment
Jobs to Be Done (JTBD)
Framework focused on the job users hire your product to do
Contextual Inquiry
Observing users in their natural environment
Card Sorting
Method for designing information architecture based on user mental models
Product Discovery
The practice of deciding what to build through research and experimentation
Survey
Structured questionnaire for collecting user feedback at scale
Free Research Tools
User Persona Builder
Create detailed user personas with goals, frustrations, and behaviors
JTBD Builder
Craft Jobs to Be Done statements with structured templates
Assumption Mapper
Map and prioritize assumptions by risk and evidence level
NPS Calculator
Calculate Net Promoter Score from survey data
Product-Market Fit Calculator
Measure PMF using the Sean Ellis survey method
Stakeholder Map
Map stakeholders by influence and interest for research planning
Research Guides and Frameworks
Get the Research Toolkit
Interview scripts, analysis templates, and persona worksheets. Delivered weekly.
Instant PDF download. One email per week after that.
Want full SaaS idea playbooks with market research?
Explore Ideas Pro →Research Approach Comparisons
Job-based vs demographic-based approaches to user modeling
Design Thinking vs Design SprintOngoing mindset vs time-boxed sprint format
Opportunity Solution Trees vs Assumption MappingTwo approaches to structuring discovery output
Design Thinking vs Lean StartupHuman-centered design vs build-measure-learn
Further Reading
Frequently Asked Questions
What is user research in product management?
User research is the systematic study of target users to understand their needs, behaviors, and motivations. Product managers use research to validate assumptions, discover unmet needs, and make evidence-based decisions about what to build. It includes both qualitative methods (interviews, usability tests) and quantitative methods (surveys, analytics).
What are the most common user research methods?
The most common methods are user interviews (1:1 conversations), usability testing (watching users interact with your product), surveys (scaled feedback collection), contextual inquiry (observing users in their environment), card sorting (information architecture), and A/B testing (behavioral experiments).
How many users do I need to interview?
For qualitative research, 5-8 interviews typically reveal 80% of usability issues. For discovery interviews, 12-15 conversations usually reach thematic saturation. For surveys, sample size depends on your confidence level and margin of error, but 100+ responses is a common minimum for statistical reliability.
What is the difference between user research and product discovery?
User research is a set of methods for understanding users. Product discovery is a broader practice that uses research alongside prototyping, experimentation, and data analysis to decide what to build. Research is a core input to discovery, but discovery also includes solution ideation and validation.
How do I convince stakeholders to invest in user research?
Show the cost of building the wrong thing. Reference past features that failed because they were not validated. Start small with lightweight methods (5 interviews take days, not months). Share concrete findings that change a decision. When research prevents one bad bet, it pays for itself many times over.
What is Jobs to Be Done (JTBD)?
Jobs to Be Done is a research framework that focuses on the job customers are trying to accomplish rather than their demographic profile. Instead of asking "who is our user?", JTBD asks "what progress is the user trying to make?" This shift often reveals non-obvious competitors and unmet needs.