The systematic study of target users and their requirements, in order to add realistic context and insights to design processes. User research encompasses qualitative methods (interviews, observation) and quantitative methods (surveys, analytics) to build understanding of user behavior, needs, and motivations.
Common contexts
- Running generative interviews at the start of a product discovery phase to understand unmet user needs
- Combining analytics data with user interviews to explain a conversion drop that quantitative data alone couldn't diagnose
- Presenting a research synthesis to a skeptical leadership team to reframe a feature request around actual user goals
Use when
Conduct user research whenever a design decision rests on an assumption about user behavior, mental models, or context that your team hasn't validated — which covers most decisions at the start of a new product or feature. The question isn't whether to do research but which method fits the question.
Avoid when
Don't run research when the question can be answered faster and just as reliably with existing data — analytics, support tickets, and past research are often overlooked. Commissioning a new study to answer a question that was answered last quarter is a waste of participant time and team budget.
The biggest risk in user research isn't asking the wrong questions — it's finding the right answers and then watching them sit in a report that no one reads, which means research impact is half craft and half organizational navigation.
Real-world examples
- Spotify's user research revealed that listeners used the app in 5 distinct emotional contexts (focus, commute, workout, social, relaxation), leading to the contextual playlist recommendation system that became their biggest engagement driver.
- Monzo's early user research with financially anxious users discovered that real-time spending notifications reduced financial anxiety rather than increasing it — an insight that reversed an initial product decision to delay notifications.
- GOV.UK's user research with 80+ non-digital-native participants directly produced their plain-language writing standards, as researchers observed that government jargon created comprehension barriers for 40% of the UK adult population.