Effective user research isn’t about running a specific test; it’s about asking the right question. Before you choose a method, you must define your objective. Are you trying to understand a problem or test a solution? Are you exploring a new opportunity or refining an existing feature? The answer determines your entire approach.

Every research study falls into one of two broad categories: generative or evaluative. Think of them as two different modes of inquiry. Generative research is about exploration and discovery. It helps you understand a user's world, their motivations, and their unmet needs. You use it when you don't know what the problem is yet. It generates insights and ideas.

Evaluative research, on the other hand, is about assessment. You have a proposed solution—a prototype, a wireframe, a live feature—and you need to know if it works. It helps you identify usability issues and measure how well a design performs against specific goals.

Another critical distinction is between what people say and what they do. This is the difference between attitudinal and behavioral data. Attitudinal data reflects users' stated beliefs, opinions, and feelings—what they think about your product. You gather this from surveys, interviews, and focus groups.

Behavioral data is about what users actually do. It’s derived from observing their actions: where they click, how long they stay on a page, whether they complete a task. This data comes from usability tests, analytics, and A/B tests.

Users often have poor recall or want to appear helpful, leading them to say things that don't match their actions. Someone might say they value privacy features above all else (attitudinal), but their clickstream data shows they always accept all cookies without reading the policy (behavioral). A robust research plan often includes a mix of both data types to get a complete picture.

A common challenge in UX is organizing information intuitively. How do you structure a website's navigation or an app's menu? Two powerful methods help you base your Information Architecture (IA) on user mental models, not your own assumptions: card sorting and tree testing.

Card sorting is a generative method. You give participants a list of topics (on cards, physical or digital) and ask them to group them in a way that makes sense. An "open" card sort lets them name the groups themselves, while a "closed" sort provides predefined categories. This reveals how users naturally cluster information.

Tree testing is the evaluative counterpart. You present users with a text-only version of your site structure—the "tree"—and ask them to find specific information. For example, "Where would you go to update your payment information?" If users consistently go down the wrong path, you know your structure is confusing. You use card sorting to design the IA and tree testing to validate it.

Some behaviors and habits don't reveal themselves in a one-hour session. To understand long-term patterns, you can use a diary studys. In this longitudinal method, participants log their experiences, thoughts, and actions related to a product or activity over several days or weeks. This provides rich, contextual data about how a product fits into the fabric of their daily lives.

After conducting interviews or diary studies, you'll have a mountain of qualitative data: transcripts, quotes, observations, and photos. The goal is to turn this raw information into actionable insights. The most common technique for this synthesis is affinity mapping.

Affinity mapping is a bottom-up process. You start by writing every individual observation or quote onto a separate sticky note. Then, you and your team begin grouping related notes together without any preconceived categories. As you cluster the notes, themes will naturally emerge from the data. You name these clusters, and those names become your key insights.

This process helps you move from individual data points to overarching patterns in user behavior and needs. It ensures your conclusions are grounded in the data you collected, not just the loudest voice in the room.

Let's put this all together. Here's a quick reference for when to use which method.

Time to test your knowledge of these research methodologies.

By moving from simply asking users what they want to systematically observing what they need, you elevate your practice from basic design to evidence-based problem-solving.