What Is UX Research? Methods, Tools, and When to Use Each

UX research is the practice of studying the people who use (or will use) your product so that design decisions rest on evidence rather than opinion. It covers everything from interviewing a handful of customers to running a usability test or analysing what thousands of users actually click. The point is the same throughout: replace “we think users want this” with “here is what users do and why”.

The confusing part for most teams is not what UX research is, but which method to reach for. There are a dozen common ones, and they answer genuinely different questions. Pick the wrong one and you get a confident answer to a question you were not asking. This guide lays out the main methods, the two dimensions that tell them apart, and how to choose the right one for the decision in front of you.

The two dimensions that organise every method

The clearest way to think about user research methods comes from the Nielsen Norman Group, which plots them along two axes.

The first is attitudinal versus behavioural: what people say versus what people do. Surveys and interviews are attitudinal, capturing beliefs, preferences and expectations. Usability testing and analytics are behavioural, capturing actual actions. The oldest truth in the field is that the two rarely match, so knowing which you need matters.

The second is generative versus evaluative. Generative (or discovery) research happens early, before you have a solution, to uncover needs, problems and opportunities. Evaluative research happens once you have something to test, a concept, a prototype or a live product, and measures how well it works. Plot a method on both axes and you can see exactly what it is good for.

Qualitative vs quantitative

Cutting across those axes is the qual/quant split, which decides your sample size and the kind of answer you get.

Qualitative research explains the “why”: motivations, mental models and the reasoning behind behaviour. It uses small samples, often five to fifteen people, and produces rich, interpretive insight rather than statistics. Quantitative research measures the “how many” and “how often”, validating whether a pattern is widespread and tracking change over time with statistical confidence.

The strongest programmes use both in sequence: qualitative work generates a hypothesis, quantitative work tests how common it really is. Our guide to CRO research methods goes deeper on combining the two when the goal is conversion.

The core methods and when to use each

User interviews are open-ended conversations, structured, semi-structured or unstructured, that surface experiences, needs and frustrations in the user’s own words. Use them early, when you are still defining the problem.

Contextual inquiry observes people using a product in their real environment, which catches the workarounds and context that interviews alone miss. Use it when behaviour depends heavily on setting.

Usability testing watches people attempt real tasks with a prototype or live product, moderated (you guide and probe) or unmoderated (they complete tasks alone). Use it to find where a design trips people up, ideally before launch and on a recurring basis after.

Surveys gather attitudinal data at scale, good for measuring satisfaction or prioritising known issues across a large group. Use them when you need breadth, not depth.

Card sorting and tree testing reveal how users expect information to be organised, which is invaluable for navigation and information architecture. Card sorting needs a reasonable number of participants to be reliable: roughly fifteen for a qualitative read and more for a quantitative one.

Analytics review mines the behavioural data you already hold to see what users actually do at scale, and is often the cheapest place to start because the data is sitting there.

Diary studies track behaviour and feelings over days or weeks, suited to habits, onboarding journeys and anything that unfolds over time.

A simple rule: define the decision first, then pick the method. If you do not yet know the problem, lean generative and qualitative. If you have a design to validate, lean evaluative. If you need to know how widespread something is, go quantitative.

The tools

Most teams run modern UX research through a small stack: a testing platform for moderated or unmoderated usability sessions and surveys (Maze, Lyssna, UserTesting and similar), a participant recruitment service to find the right people, a repository to store and tag findings (Dovetail is common), and your existing product analytics for the behavioural layer. You do not need all of it to start. A video call, a prototype and a notes document will run a perfectly valid first study.

How research fits into design and SEO

Research is not a one-off phase; it threads through the whole product cycle, generative work to find the problem, evaluative work to refine the solution, and ongoing measurement once it ships. It also feeds neighbouring disciplines. A clearer understanding of user intent improves both the experience and how a page performs in search, which we cover in our conversion rate optimisation guide and our walkthrough of running a user experience audit.

The teams that get value from UX research are not the ones with the biggest budgets. They are the ones who ask a sharp question, choose the method that actually answers it, and act on what they find.

Frequently asked questions

What is UX research in simple terms? UX research is studying the people who use your product to understand their needs, behaviours and frustrations, so design decisions are based on evidence rather than guesses. It ranges from interviews and usability tests to surveys and analytics.

What is the difference between qualitative and quantitative UX research? Qualitative research explains why people behave as they do, using small samples and producing rich, interpretive insight. Quantitative research measures how many and how often, using larger samples to validate patterns with statistical confidence. Strong teams use both together.

Which UX research method should I use first? Start by defining the decision you need to make. If you do not yet understand the problem, begin with generative, qualitative methods like interviews or contextual inquiry. If you have a design to validate, use evaluative methods like usability testing.

How many participants do I need for UX research? It depends on the method. Qualitative usability testing surfaces most major issues with around five users, while card sorting and quantitative studies need more, often fifteen or many more, to be reliable. Surveys and analytics work best at larger scale.

What is the difference between attitudinal and behavioural research? Attitudinal research captures what people say, through surveys and interviews, while behavioural research captures what people do, through usability testing and analytics. The two often disagree, so choose the one that matches the question you are answering.