Types of product research: a taxonomy and decision framework

Compare the main types of product research, from concept testing to usability studies, and see which method fits your budget and timeline.

White outline of Goldie, the SurveyMonkey mascot

Summary:

  • Product teams often struggle not from a lack of research, but from selecting the wrong type of study for their specific decision, leading to inefficient use of budgets and timelines.
  • Every research method is categorized by three core axes, allowing teams to map their research needs directly to the appropriate methodology.
  • Effective research programs focus on building a "decision calendar" rather than a fixed research schedule, ensuring that exploratory and evaluative studies are used in the correct sequence to validate concepts before committing capital.

Most product teams do not fail because they skipped research. They fail because they picked the wrong type of research for the decision in front of them. A five-minute poll cannot validate a $2 million launch, and a six-week ethnographic study will not save a pricing decision due in 48 hours.

This guide organizes the types of product research into a single decision framework: what each method is, when it belongs in your product's life cycle, and how to match it to your budget and timeline. Rather than walking through a single research process step by step, we group methods into a matrix you can scan in under a minute, then apply.

Product research is the umbrella term for the methods teams use to test ideas, concepts, features, and pricing with real customers before committing engineering, marketing, or capital budget to them. Every method sorts along three axes:

AxisCategory 1Category 2
Primary vs. secondaryPrimary research collects new data directly from your target customers.Secondary research analyzes data that already exists, such as industry reports, competitor reviews, or past studies.
Qualitative vs. quantitativeQualitative research explains why customers behave a certain way through open-ended conversation and observation.Quantitative research measures how many customers feel a certain way, at what statistical confidence.
Exploratory vs. evaluativeExploratory research is used early, when the question is still "what should we build?"Evaluative research is used later, when the question becomes "does this specific concept, price, or design work?"

No single method wins on every axis.

A concept test is primary, mostly quantitative, and evaluative. A focus group is primary, qualitative, and can serve either stage. Competitive analysis is secondary and largely exploratory.

The rest of this guide sorts eight common methods along these lines so you can pick the right one for the decision at hand, not just the one your team has used before.

For a step-by-step walkthrough, see our companion guide on performing product research, which covers the full research process and monadic survey design in depth.

Choosing the wrong type of product research is not an academic mistake. It is a budget mistake. Teams that default to whatever method they used last time routinely overspend on research that answers the wrong question or, worse, underinvest in research before a launch decision that carries real financial risk.

Three business outcomes depend directly on matching the method to the moment:

  • Capital efficiency. Evaluative, quantitative methods like concept testing exist specifically to stop a weak idea before it consumes development budget. Traditional agency concept studies can run tens of thousands of dollars and take weeks to field, which is often longer than the decision window a product team actually has.
  • Speed to decision. Exploratory qualitative methods surface the right questions early, so the quantitative study that follows is testing the right variables instead of guessing at them.
  • Stakeholder confidence. A decision backed by a statistically valid sample and a clear scorecard is easier to defend in a leadership review than a decision backed by five customer conversations, even when those conversations were directionally correct.

The teams that get the most value from product research are not the ones running the most studies. They are the ones matching study type to decision type, every time.

The eight methods below cover most of what teams mean when they ask about "types of product research." Instead of walking through each one narratively, use the table to place a method by category and typical use case, then read the notes below for nuance the table cannot capture.

MethodPrimary or secondaryQualitative or quantitativeBest-use case
Concept testingPrimaryQuantitativeDeciding which of several product or feature concepts to pursue before development
Price testingPrimaryQuantitativeSetting or validating a price point before launch or a price change
Usability testingPrimaryQualitative (with some quantitative metrics)Finding where users struggle inside a product, prototype, or flow
A/B testingPrimaryQuantitativeComparing two live variants of a page, flow, or feature by measured behavior
Competitive analysisSecondaryQualitative and quantitativeUnderstanding where competitors are strong or exposed before positioning a product
Diary studiesPrimaryQualitativeCapturing how customers use a product in their own context over days or weeks
SurveysPrimaryQuantitative (can include open-text qualitative data)Measuring attitudes, satisfaction, or preferences at scale across a target audience
Focus groupsPrimaryQualitativeExploring reactions, language, and unmet needs in a live group discussion

A few distinctions worth calling out:

  • Concept testing versus focus groups. Both test reactions to an idea, but concept testing isolates each concept with a single respondent, which removes the comparison bias that group settings introduce. A focus group is better suited to exploring why customers react a certain way; concept testing is better suited to proving how many will.
  • A/B testing versus usability testing. A/B testing measures which variant performs better once something is live. Usability testing observes a user attempting a task, live or in a prototype, and explains the friction that a behavioral metric alone would not surface.
  • Competitive analysis as a starting point, not an ending point. Because it relies on existing, secondary information, competitive analysis is fast and low cost, but it cannot tell you how your specific customers will react. Pair it with a primary method before committing budget.

Every research method should produce a decision, not just a data set. The measurement frameworks below apply across categories:

  • Statistical significance and sample size. For quantitative methods like concept testing, price testing, and surveys, confirm the sample size supports the confidence level you need before you act on the result.
  • Key driver analysis. Identify which attributes of a concept, price, or feature are actually driving preference, rather than just reporting overall scores.
  • Benchmarking against category norms. Industry benchmarks turn a raw score into a decision. A concept that scores well against its own category benchmark is a stronger bet than one judged only against internal expectations.
  • Task success rate and time on task. For usability testing, these two metrics tell you whether a design change actually reduced friction, not just whether users said they liked it.
  • Theme saturation. For qualitative methods like diary studies and focus groups, track when new sessions stop surfacing new themes. That point is a signal you have gathered enough to act.

A few practical shifts make research programs more useful over time, regardless of which method a given study uses:

  • Build a decision calendar, not a research calendar. Map upcoming product, pricing, and launch decisions first, then choose the method each decision requires, rather than scheduling research on a fixed cadence disconnected from real decisions.
  • Match budget and timeline to method, honestly. A stakeholder who needs an answer in two days should not be offered a six-week ethnographic study, and a launch decision worth millions should not rest on a five-person hallway test.
  • Combine exploratory and evaluative research in sequence. Use a qualitative method to identify which concepts, prices, or features are worth testing, then validate the shortlist with a quantitative method before committing resources.
  • Standardize your scorecards. When every concept test or price test reports against the same benchmarks and key drivers, stakeholders across the company can compare results across quarters, not just within a single study.
  • Revisit assumptions as the product stage changes. A method that worked for early-stage concept exploration will not automatically fit a late-stage pricing decision. Reassess the method each time the product moves to a new stage.

Use this hub to jump directly to the resource that matches the method you need.

  • What is the most common type of product research?
  • Which type of product research is best for an early-stage idea?
  • How is concept testing different from a general product feedback survey?
  • Do I need a large sample size for every type of product research?
  • Can I combine multiple types of product research in one project?
  • What is the difference between primary and secondary product research?

The type of product research you choose should follow the decision you are trying to make, not the other way around. Use the comparison matrix above to identify where your next decision falls, and start with a method built for that stage rather than defaulting to the one your team already knows.

If your team is deciding between several product concepts right now, concept testing is purpose-built to remove comparison bias and produce a statistically valid answer in hours rather than weeks. Explore tools and templates to find the method that matches your next product decision.

Two marketing employees, one reviewing a paper with brand strategy, and the other holding a printout of charts

SurveyMonkey can help you do your job better. Discover how to make a bigger impact with winning strategies, products, experiences, and more.

A man and woman looking at an article on their laptop, and writing information on sticky notes

Learn how the Gabor-Granger method works, how to build the survey, and how to calculate a demand curve with a full worked example.

Smiling man with glasses using a laptop

Run a price sensitivity analysis end to end: pick the right method, build the survey, read the results, and turn them into a pricing decision.

Woman reviewing information on her laptop

Follow this numbered checklist to conduct product research fast, with sample survey questions and concept testing tips for your team.