User Research
User research is the systematic study of the people who use, or might use, a product: their behaviors, needs, motivations, and the context they work in. Teams use methods such as interviews, observation, usability tests, surveys, and analytics to replace assumptions with evidence. Often called UX research, it underpins product discovery and design decisions.
How User Research Works
User research covers many methods. Nielsen Norman Group classifies them along three dimensions that help teams choose the right one:
- Attitudinal vs. behavioral. Attitudinal methods capture what people say, through interviews or surveys. Behavioral methods capture what people do, through field observation, usability testing, or analytics. The two often disagree, which is why strong research uses both.
- Qualitative vs. quantitative. Qualitative methods, such as customer interviews, observe people directly and are best at answering "why" and "how to fix it." Quantitative methods, such as surveys and analytics, collect data at scale and answer "how many" and "how much."
- Context of use. Whether participants use the product naturally, follow a scripted task, use a limited version of it, or do not use it at all during the study.
Research also changes with the stage of the work:
- Generative research uses field studies and interviews to uncover needs and opportunities before a solution exists.
- Formative research uses methods like usability testing and card sorting to improve a design in progress.
- Summative research uses A/B tests, benchmarks, and analytics to measure how a released product performs.
Raw findings are then synthesized, often through thematic analysis, into insights that shape artifacts such as personas, journey maps, problem statements, and requirements.
Why User Research Matters
Teams that skip research build on assumptions, and the mistakes surface late, when changes are expensive. Research lowers that risk by checking whether a problem is real, whether people understand a design, and whether a released feature actually changes behavior.
It also settles debates. When stakeholders disagree, evidence about what users actually do carries more weight than opinion. Because methods vary widely in cost, even small teams can do useful research: a handful of interviews or a short usability session can reveal major issues.
In many organizations research is a shared responsibility. A dedicated researcher may plan studies and protect quality, while product managers, designers, and engineers join sessions so findings reach the people making decisions. Evidence is most useful when it survives into delivery; for one approach, see how to turn UX research into functional requirements without losing evidence.
User Research Example
A team building a project management tool sees in its analytics that many new teams never create a second project. That is the "what." To learn the "why," they interview eight recent sign-ups and watch five of them set up a project in a usability session.
The sessions show that people expect to import their existing tasks from a spreadsheet and give up when they cannot find the option. The team adds a visible import step, then checks analytics again to see whether second-project creation rises. One question used three methods: analytics to spot the pattern, interviews and usability testing to explain it, and analytics again to measure the fix.
User Research vs. Market Research
Market research studies markets: their size, segments, buying behavior, and competitors. User research studies how people experience problems and products, often down to individual tasks. Product teams use both, but a TAM, SAM, SOM estimate will not tell you why users abandon onboarding.