How many customer interviews should I do per week?

One interview per week is the minimum for continuous discovery. Three per week is ideal for teams in active discovery mode. The [Continuous Discovery guide](/guides/continuous-discovery-habits) explains how to make this sustainable.

When should I use qualitative vs. quantitative research?

Use qualitative research (interviews, usability tests) when you need to understand why. Use quantitative research (A/B tests, surveys, analytics) when you need to measure what and how much. Most good research programs alternate between both.

How do I find users to interview?

Start with your existing user base. Use in-app prompts, email outreach, or customer success introductions. For prospect research, use social media groups and communities where your target users gather.

What is the biggest research mistake PMs make?

Asking users what they want instead of understanding their problems. Users are experts on their problems but poor designers of solutions. Use [JTBD interviews](/frameworks/jobs-to-be-done) to focus on problems and outcomes.

Top 10 User Research Methods for PMs (2026)

Quick Answer (TL;DR)

Customer interviews and usability testing are the two highest-value research methods for PMs. Interviews tell you what problems exist. Usability tests tell you whether your solution works. Every other method fills a specific gap between those two.

Why This List Matters

PMs who skip research build on assumptions. PMs who do too much research never ship. The skill is knowing which method to use when. This list covers 10 research methods ranked by the quality of product decisions they enable.

1. Customer Interviews

Best for: Understanding user problems, motivations, and unmet needs

The single most important research method for PMs. Weekly customer interviews surface problems you would never find in analytics. Use the Jobs to Be Done framework to structure your questions around outcomes, not features. Part of the Continuous Discovery Habits practice.

2. Usability Testing

Best for: Evaluating whether users can complete key tasks in your product

Watch 5 users attempt core workflows, and you will find 80% of usability issues. Test prototypes before building and live product after launching. Pairs well with the Double Diamond framework.

3. A/B Testing

Best for: Measuring the impact of specific changes on user behavior

When you have enough traffic, A/B tests give you causal evidence. They answer "does this change improve the metric?" Use the A/B Test Calculator to determine sample size and the A/B Testing guide for best practices.

4. Customer Journey Mapping

Best for: Visualizing the end-to-end experience and finding drop-off points

Journey maps reveal friction across the entire user lifecycle, not just within your product. Use the Journey Mapper to build yours and identify the highest-impact improvement opportunities.

5. Surveys

Best for: Quantifying sentiment and preferences at scale

Surveys complement qualitative research by putting numbers on what you have heard in interviews. Keep them short (under 7 questions). Use them to validate hypotheses, not to discover new problems. Track satisfaction with NPS or CSAT.

6. Jobs to Be Done Interviews

Best for: Uncovering the "why" behind switching behavior and product adoption

JTBD interviews focus on the moment a user decided to adopt (or abandon) a product. They reveal the push, pull, anxiety, and habit forces that drive decisions. Read the JTBD framework guide and use the JTBD Builder.

7. Card Sorting

Best for: Designing information architecture and navigation that matches user mental models

Have users organize features or content into groups. Open card sorts reveal how users think. Closed card sorts validate your proposed structure. Essential before redesigning navigation.

8. Analytics Deep Dives

Best for: Finding behavioral patterns and anomalies in usage data

Product analytics tools (Amplitude, Mixpanel, PostHog) reveal what users do. Look at funnel drop-offs, feature usage, and cohort behavior. Read about key metrics like Feature Adoption Rate, DAU/MAU, and Activation Rate.

9. Competitive Usability Reviews

Best for: Understanding how your experience compares to alternatives

Use competitor products as a user would. Note what works well and what is frustrating. This surfaces gaps and opportunities you can address. Use the Competitor Matrix to structure your findings.

10. Assumption Mapping

Best for: Identifying which assumptions to test first before committing to research

Before running any research, map your assumptions by risk and uncertainty. Test the riskiest ones first. Use the Assumption Mapper to prioritize what needs validation.

How We Ranked These

Methods are ranked by decision quality (how much they reduce the risk of building the wrong thing), effort-to-insight ratio (signal per hour invested), and universality (whether they work across product types). Interviews and usability tests rank highest because they produce the richest insights per session.