Learn · fundamentals
What is user research?
User research is the systematic study of the people who use or might use a product, service, or experience. It investigates their behaviours, needs, motivations, and mental models to inform design and product decisions. Without it, teams build products for users they imagine rather than users who actually exist. The gap between those two things is where most product failures live.
Why user research exists
Every product decision rests on assumptions about what users want, how they think, and what they'll do. Some of those assumptions are correct. Many are not. User research is the systematic practice of checking those assumptions against reality before they're built into a product that's expensive to change.
The alternative to user research is not making fewer assumptions. It is making the same assumptions with less information. Teams without a research practice still make decisions about users. They just make them based on internal intuition, stakeholder opinion, and whatever the loudest customers said last week. That's not a neutral position. It's a high-risk one.
User research reduces that risk by creating direct contact between the people making product decisions and the people those decisions affect. Not through surveys that confirm existing hypotheses. Through conversations that surface what wasn't anticipated.
What user research covers
User research is not a single method. It is a discipline that encompasses multiple methods suited to different research questions at different stages of the product development cycle.
Generative research explores the problem space before solutions are defined. Who are the users? What are they trying to accomplish? Where does the current experience fail them? What workarounds have they developed? Generative research produces the raw material for product strategy and roadmap decisions. It answers "what should we build?" before anyone asks "how should we build it?"
Evaluative research tests specific designs, concepts, or hypotheses. Does this prototype make sense to users? Where does the flow break down? Does this messaging resonate? Evaluative research produces feedback on specific decisions before they're locked in. It answers "does this work?" before resources are committed.
Continuous research runs between major study cycles to maintain an ongoing understanding of users as the product and market evolve. What's changing in how users interact with the product? What are customers saying about a competitor that just launched? What signals are emerging that the analytics haven't surfaced yet? Continuous research keeps teams informed rather than periodically surprised. See the research interview scale problem for why volume matters here.
The methods user researchers use
Qualitative interviews are the foundational method of user research. A researcher, or an AI interviewer, conducts a structured conversation with a participant around a defined set of topics. The output is a transcript and structured analysis of what the participant said, thought, and experienced. Interviews are the method for understanding motivation, mental models, and the reasoning behind behaviour.
Usability testing observes participants attempting specific tasks in a product or prototype. It identifies where the interface creates friction, confusion, or failure. Usability testing is evaluative: it tests a specific design rather than exploring an open question.
Surveys and questionnaires collect responses from large numbers of participants to measure the distribution of opinions, behaviours, or experiences across a population. Surveys are quantitative by nature: they measure how many people think or behave a certain way, not why.
Diary studies ask participants to record observations, experiences, or behaviours over a period of time. They capture longitudinal experience, specifically how something changes over days or weeks, in a way that single-session interviews cannot.
Contextual inquiry observes participants in their natural environment, typically while they're working or using a product in context. It surfaces behaviours that participants don't articulate or even notice because they've become habitual.
Most applied user research uses qualitative interviews as the core method, supplemented by the others as the specific research question demands.
How user research fits into product development
User research is most valuable when it informs decisions that are still open, when there is still time to change direction based on what's found. Research that arrives after a decision has been committed to is archaeology, not strategy.
In practice, this means user research needs to run in parallel with product development, not as a discrete phase before it. The product teams moving fastest tend to have research feeding continuously into their work: generative research informing roadmap decisions, evaluative research informing design decisions, and continuous research informing prioritisation decisions.
The waterfall model of research, big study then months of building then another big study, produces research that's too infrequent to catch problems early and too delayed to change direction cheaply. Continuous research programmes, where studies run in parallel with development and produce findings at the sprint timescale, produce research that's actually used.
The difference between user research and market research
These disciplines are related but distinct, and confusing them produces decisions made with the wrong kind of evidence.
User research studies specific people's behaviour, motivation, and experience in relation to a product or service. It is conducted at the individual level, typically through qualitative interviews or usability testing. It answers questions about how specific people think and behave.
Market research studies populations and markets. It measures market size, competitive positioning, brand awareness, and purchase intent across a representative sample. It answers questions about how many people think or behave a certain way and how the market is structured.
A company launching a new product needs both: user research to understand how specific target users think and behave in relation to the problem the product solves, and market research to understand the size of the opportunity and competitive landscape. Neither substitutes for the other.
What makes user research rigorous
User research done poorly produces findings that confirm what the team already believed, miss the things that matter most, and generate no meaningful change in how decisions get made. User research done well changes what gets built and how.
The difference comes down to three practices.
Systematic design. Studies have clear research questions, appropriate methods, and interview structures designed to surface evidence rather than confirm hypotheses. The research question determines the method. The method determines the study design. How to design a qualitative research study walks through that sequence.
Appropriate recruitment. Participants have the specific experience the study is designed to understand. A study about why users abandon document upload requires participants who have attempted document upload, not users who broadly match the product's target persona.
Rigorous analysis. Findings trace back to the data. Claims about what users think or do are grounded in specific quotes and patterns across participants, not in the researcher's impressions or the stakeholder's preferred narrative.
What this looks like in practice
A product team at a B2B software company is deciding whether to invest in building a native mobile app. The internal assumption, held confidently by multiple senior stakeholders, is that customers are frustrated by the lack of mobile access and would pay more for a mobile app.
Before committing twelve months of engineering capacity to that bet, a researcher runs eight qualitative interviews with customers across different company sizes and roles.
The finding surprises everyone. Customers are not frustrated by the lack of a mobile app. They never thought to want one. The product requires too much context to use productively on a phone. What they want is a better notification system that tells them when something in the web app needs their attention, so they can address it quickly without sitting down at a computer.
That finding saves the team from building the wrong thing. It also gives them a better roadmap item than the one they started with. Eight interviews, three weeks, one changed roadmap decision. That is what user research is for.
Frequently asked questions
What is the difference between user research and UX research?
The terms are used interchangeably in most professional contexts. User research is the broader term covering all systematic study of users. UX research tends to refer specifically to research conducted to inform user experience and interface design decisions. In practice, a UX researcher and a user researcher typically do the same work. The distinction is more about job title convention than methodological difference.
How is user research different from customer feedback?
Customer feedback is unsolicited input from customers about their experience: support tickets, reviews, NPS comments, sales call notes. It is valuable but biased toward people with strong opinions (usually negative) and toward the topics customers choose to raise rather than the topics the team needs to understand. User research is solicited, structured, and designed to surface specific information. It reaches a representative range of users rather than the self-selected group who chose to provide feedback.
Do small teams need user research?
Yes, arguably more than large ones. Small teams have fewer data points and less margin for error. A wrong product decision at a small company can be existential. A wrong product decision at a large company gets absorbed. Small teams often cite lack of time as the reason to skip research. The cost of building the wrong thing is almost always greater than the cost of running a study to find out what the right thing is.
How often should user research be conducted?
Continuously, with the depth and focus calibrated to the decisions in flight. Most mature research functions run a combination of always-on continuous research (low volume, ongoing) and dedicated study-based research (higher volume, focused on specific questions). The goal is for research to inform decisions as they're being made, not after they've been committed to.
What is the ROI of user research?
The ROI is most visible in avoided costs: features that weren't built because research showed they wouldn't work, redesigns that weren't necessary because problems were caught in testing rather than after launch, churn that was prevented because the research identified the friction that was causing it. These costs are harder to attribute than revenue generated, but they are real and significant. Teams that try to measure research ROI through direct revenue attribution typically underestimate it substantially.
How is AI changing user research?
AI is changing the execution layer of qualitative research: AI interviewers can conduct structured interviews consistently at scale, without the scheduling constraints and moderator variance that have always limited how much qualitative research teams can do. The methodology, study design, analysis, and stakeholder communication remain human work. The interviews themselves, for structured research with defined topics and clear objectives, can be AI-conducted without meaningful loss of quality. Teams running UX research at scale use platforms like Fieldwork Interviews for this execution layer.
Related on Fieldwork
- What qualitative research is and when to use it
- How AI research interviews work and how they differ from surveys
- Run user research interviews at scale
Last updated: 2026-07-08