UX glossary
User Research
User research is the systematic study of the people who use a product: their goals, their behavior and their context. It gives you a foundation for design decisions based on evidence instead of guesswork.
Imagine a city library planning to redesign its app. The team is convinced people want more features, such as reading recommendations and a community area. Before building anything, it talks to a few people who use the app and watches them use it. The result is a surprise: most of them want just one thing, a quick way to see when their books are due.
Explained simply
User research means studying the people you’re designing a product for. You find out what they want to achieve, how they go about it today, where they get stuck and in what context they use the product. The goal is to base decisions on evidence rather than gut feeling or the loudest opinion in the meeting.
Think of a good doctor: you don’t get a prescription until someone has asked questions, listened and examined you. User research is that check-up for digital products. It can happen before design starts, during development or after launch, when you want to see how the product holds up in everyday use.
Which methods exist
The Nielsen Norman Group maps research methods along several dimensions, two of which are especially useful. The first separates what people say (attitudinal methods, such as interviews or surveys) from what they do (behavioral methods, such as observation, usability testing or A/B testing). The two often differ, which is why observing real behavior is so valuable.
The second dimension separates qualitative from quantitative methods. Qualitative methods answer “why” questions and work with just a few participants. Quantitative methods like surveys or analytics answer “how many” questions and need larger samples. The right method always depends on your question, not on personal preference.
An example
Back to the library app. Before: the team plans three new sections and a chat feature, based on a hunch. After: five conversations and a look at the usage data make it clear that the home screen mainly needs to show due dates and a renewal option. The team builds that first, tests it with a prototype and saves months of work on features hardly anyone would have missed.
Common misconceptions
User research isn’t a one-off big project. Small, regular studies already go a long way. And it can’t be replaced by assumptions about your audience, not even by AI-generated answers. You can read why in Synthetic Users: Can AI Replace Real User Research?. For a look at the day-to-day work behind it, see What Does a UX Researcher Do?.
In practice
- Start with a clear question. Write down what you want to learn. The question decides whether you need interviews, tests or numbers.
- Combine what people say with what they do. Add observation or usage data to your interviews. That’s how you spot where statements and behavior drift apart.
- Share findings in a way the team will use. Short summaries, quotes and video clips are more convincing than a long report nobody reads.
Related terms
Usability Testing, Persona, A/B Testing, Journey Map