Before building anything—a new app, a website, or even a physical product—you face a big question: Will people actually use this? Answering that question is the job of User Experience (UX) research. Think of it as detective work. Instead of solving a crime, you're uncovering people's needs, frustrations, and motivations.

Without research, teams are just guessing. They might build a feature they think is brilliant, only to find out nobody wants it. Research is the bridge between a business's goals and a user's real-world needs. It dramatically reduces the risk of building the wrong thing.

Research methods generally fall into two broad categories. The first is qualitative research, which focuses on understanding the why behind people's actions. It's about stories, feelings, and motivations. You get this kind of insight by talking to people directly, like in one-on-one interviews, or by observing them as they go about their tasks.

The second category is quantitative research, which deals with numbers and measurable data. It answers questions like how many users clicked a button or how much time they spent on a page. This kind of data often comes from surveys, website analytics, or A/B tests where you compare two versions of a design to see which performs better.

Another important distinction is what you're measuring: what people do versus what they say. This is the difference between behavioral and attitudinal data.

Attitudinal data is what people report about themselves—their thoughts, beliefs, and feelings. It's asking someone to describe their typical diet.

Often, there's a gap between attitude and behavior. Someone might say they want to eat healthier (attitude), but you observe them eating fast food three times a week (behavior). Both types of data are valuable. Attitudinal data tells you about users' goals and perceptions, while behavioral data shows you what they actually do when faced with a choice. A good research plan often combines both.

Research isn't just a single step at the beginning of a project. It happens throughout the entire design cycle, and the type of research changes based on your goal.

Generative research (or exploratory research) happens at the very beginning. Its purpose is to uncover opportunities and understand user problems you might not even know exist. You're generating ideas. This is where you conduct interviews and field studies to build a deep understanding of your users' world.

Evaluative research happens once you have a concept or a prototype. Its purpose is to evaluate how well your design solves the problem you identified. Does it work? Is it easy to use? This is where you conduct usability tests or send out surveys to get feedback on a specific design.

By understanding these core foundations—qualitative vs. quantitative, behavioral vs. attitudinal, and generative vs. evaluative—you can see how research guides a team from a vague idea to a successful, user-friendly product.