User Research Methods

User Research Methods

The most common and expensive mistake in product development is building for an assumed user. Teams imagine users like themselves — technical, patient, motivated to learn the product. Real users are none of these things. They are pressed for time, operating under stress, using your product as a side task while doing something else, and they will not read documentation.

User research is the discipline of replacing assumptions with evidence. It does not guarantee good design — but it systematically eliminates the class of failures caused by building the wrong thing.

The Two Modes of Research

Generative research is done before or during early design to understand user needs, contexts, mental models, and problems. It answers: What do users actually need? What are they trying to accomplish? What is their environment like? What frustrates them today?

Evaluative research is done with a design in hand to test whether it works. It answers: Can users accomplish tasks with this interface? Where do they get stuck? What did they misunderstand?

Both are required at different stages. Teams that skip generative research build elegant solutions to the wrong problems. Teams that skip evaluative research ship interfaces that look right but behave wrong.

Core Research Methods

Usability Testing — Participants attempt realistic tasks on the interface while a facilitator observes. The think-aloud protocol (participants verbalise what they're thinking) reveals mental models in real time. Rule of thumb: 5 participants reveal 85% of usability problems. Testing does not need to be elaborate — a prototype on a laptop with 5 users over an afternoon generates actionable findings.

Contextual Inquiry — Researchers observe and interview users in their actual work environment while they perform real tasks. Lab studies miss context: the workarounds users have developed, the distractions they operate under, the tools they combine with your product. Contextual inquiry captures these. The AEIOU framework structures observation: Activities, Environments, Interactions, Objects, Users.

Interviews — Structured conversations to explore user needs, workflows, and mental models. Effective interviews use open-ended questions ("Walk me through how you do X") rather than closed ones ("Do you like X?"). The critical failure mode: asking about hypotheticals ("Would you use this feature?") — users are poor predictors of their own future behaviour. Ask about actual past behaviour instead.

Surveys — Quantitative data at scale. Useful for measuring attitudes and satisfaction (System Usability Scale, Net Promoter Score), segmenting users, and triangulating qualitative findings. The weakness: surveys measure what users say, not what they do. Always complement with observational methods.

Diary Studies — Participants log their experiences, thoughts, and activities over an extended period (days to weeks), capturing longitudinal patterns and natural context that single sessions miss. Used for understanding workflows that unfold over time.

Card Sorting — Participants group concepts or features into categories that make sense to them — used to design information architecture. Open card sorts reveal user mental models; closed card sorts evaluate whether a proposed structure matches user expectations.

A/B Testing — Randomised experiments comparing design variants on real users at scale. Measures behaviour (not preference) with statistical significance. Powerful for optimisation; requires large traffic volumes to detect meaningful differences.

Synthesising Research into Action

Raw research data must be synthesised into design direction. Key synthesis tools:

Affinity Diagramming — Observations are written on individual notes and physically (or digitally) grouped into themes, revealing patterns that no single observation makes obvious.

Personas — Composite characters built from research, representing the range of users the design must serve. Effective personas include goals, frustrations, context, and a representative quote — they make the user visible in design discussions. The warning: personas built on demographic assumptions rather than research are useless or misleading.

Journey Maps — Visualisations of the user's experience across time as they accomplish a goal — including touchpoints, emotions, and pain points. Useful for identifying where the worst friction occurs and where design investment has the highest leverage.

"How Might We" Statements — Translating research findings into design challenges: "Users don't understand the pricing tiers" becomes "How might we make pricing differences immediately legible?" This reframes problems as opportunities and connects research to action.