What is product research?
Product research is the work of finding out what to build and whether what you built works. Interviews, observation, surveys, testing ideas before committing to them.
The term gets used for two other things it is not. Product research in e-commerce means finding items to sell. Research and development means building the technology. This page covers the product management sense.
What is an example of product research?
A product research example is a team that keeps hearing customers ask for "better reports," interviews eight of them about how they actually close the month, and finds the real problem is matching transactions in a spreadsheet outside the product.
The team behind an expense tool hears the same request in sales calls for a quarter. A product manager sets up eight interviews with finance managers and asks them to walk through their last month-end close, step by step. Six of the eight export everything to a spreadsheet to match card transactions against receipts. That's generative research, and it changes the question from "which reports do you want?" to "why does reconciliation happen outside our tool?"
Next the team builds a rough matching screen and asks five of the same finance managers to reconcile a sample month with it. Testing it that way is evaluative research. After release they keep an eye on in-product feedback and support conversations to see whether spreadsheet exports drop, which is the continuous part.
Smaller examples of product research:
- Interviewing customers who cancelled in the last 90 days about what they switched to
- A usability test on a clickable prototype before engineering starts
- A one-question in-app survey to size how many users hit a problem first heard in interviews
- Reading a quarter's worth of support tickets about one feature
- Checking the analytics funnel of a new onboarding flow to see which step people leave at
What is the difference between product research and market research?
Product research asks what to build for the people in a market, while market research asks whether there's a business in that market at all.
Market research studies a market: size, segments, competitors, willingness to pay. It answers whether there is a business here and is usually done for a decision about strategy or investment.
Product research studies the people who will use the thing: what they are trying to do, where they get stuck, whether your solution helps. It answers what to build next week.
They get commissioned by different people for different decisions, and the mistake is using one to answer the other's question. A market study will not tell you why onboarding fails.
What are the types of product research?
There are three types of product research: generative, evaluative and continuous.
- Generative. Open-ended, done before you have a solution. Interviews, observation, diary studies. Answers "what problem should we solve?"
- Evaluative. Done once you have something to show. Usability testing, concept tests, prototype reviews. Answers "does this work?"
- Continuous. Always running, through in-product feedback and support conversations. Answers "what changed?"
Teams over-invest in evaluative research because it has a clear output, and under-invest in generative research because it is uncomfortable to spend two weeks not knowing the answer.
What are the main product research methods?
The main product research methods are customer interviews, observation, surveys, usability testing, in-product feedback, and reviewing support and sales conversations.
Customer interviews. The highest-value method and the most commonly done badly. Ask what they did last time, not what they would do.
Observation. Watching someone work reveals workarounds they would never think to mention.
Surveys. Good for measuring how widespread something is once you know what to ask. Poor for discovering it.
Usability testing. Representative users try realistic tasks on a design or prototype while you watch where they get stuck.
In-product feedback. Continuous, unprompted, and the only method that reaches people who were never going to join a research call.
Support and sales conversations. Research that already happened and usually goes unread.
Nielsen Norman Group's map of research methods sorts them along two main axes: attitudinal against behavioural (what people say compared with what they do) and qualitative against quantitative. A research plan that only ever uses one corner of that map, say surveys, keeps confirming what the team already believed.
Why is research important before designing a product?
Research before design matters because it's the cheapest moment to find out you're solving the wrong problem. Five interviews can sink a weak idea in a week. Once the same idea is built and shipped, it has a team, a roadmap slot and a launch behind it, and the adoption numbers take months to become clear enough to argue with.
Product research for enterprise product teams
In a large product organisation the research usually exists somewhere. Dedicated researchers run studies, product managers run their own interviews, customer success hears problems on every call, and each group keeps notes in a different place.
The cost shows up in roadmap reviews. A theme from last quarter's interviews can't be checked against this quarter's tickets, so the most confident summary wins. Research holds up at this scale when each finding links to the transcripts, tickets and survey answers behind it, with a count, so another PM can reopen the evidence and reach the same conclusion.
How Usersnap supports product research
Usersnap brings the continuous half of product research into one workspace, together with the interviews and calls you already run, and keeps each item tied to its source.
- In-product collection: widgets and in-app surveys collect feedback while people work, including from users who would never join a research call.
- Interviews and support conversations: Channels imports transcripts of recorded Zoom calls and closed Intercom conversations as feedback items, so research that already happened stays findable. The AI user interview analysis template sets up a project for exactly this.
- Grouping: Sentiment Sensor tags topic and sentiment on every item, so an interview transcript and a support ticket about the same problem land under the same topic.
- Decisions: on the Opportunities Board you link feedback items and research notes to an opportunity and score it by value and effort.
- Your AI assistant: the MCP connector lets ChatGPT, Claude or Cursor query your live workspace with your own permissions, for example "summarise the top five topics across interviews and tickets in this project."
Sentiment Sensor is included on Professional plans and above, and available as an add-on on Starter and Growth. Channels is included from the Growth plan.
Product research FAQ
What is the difference between product research and product discovery?
Product discovery is the wider practice of deciding what is worth building. Research is the set of methods you use inside it.
What is product research also called?
In product management it overlaps with user research and UX research, and it's the main activity inside product discovery. E-commerce sellers use "product research" to mean finding products to sell, which is a different job.
How often should product teams do research?
Continuously, with a few deeper studies each year. Teresa Torres, author of Continuous Discovery Habits, recommends that the team building a product talks to customers every week, and in-product feedback fills the gaps between conversations.
Is product research qualitative or quantitative?
Both. Interviews and observation are qualitative and explain why something happens. Surveys, analytics and a count of how often a theme comes up add the numbers, which tell you how many people it affects.
Related terms
See how product teams keep interviews, tickets and in-app feedback in one place, each finding linked to its source.
.svg)
