A few years ago, I thought user research was mostly about talking to users. If I could schedule a few interviews, ask questions, and gather feedback, I assumed I was doing research correctly. The more projects I worked on, the more I realized that user research isn’t just about collecting information.

It’s about collecting the right information. And that’s where many teams struggle. Sometimes the problem isn’t a lack of research. It’s choosing the wrong research method for the question you’re trying to answer. That distinction can completely change the quality of product decisions.

Why research methods matter:

One thing I’ve noticed in product teams is that user research often becomes a checkbox activity. A few interviews are conducted. Some feedback has been collected. A report is created. Then everyone moves on. The problem is that not every research question can be answered using the same method. 

🟠 •  If you’re trying to understand user behavior, interviews alone may not be enough.
🟠 •  If you’re testing usability, surveys won’t reveal much.
🟠 •  If you’re validating a concept, analytics data won’t tell the full story.

Different questions require different approaches. That’s why choosing the right method matters.

Start with the question, not the method:

A mistake I see frequently is selecting a research method before understanding the problem. Teams decide they want to run interviews.

🟢 • Or surveys.
🟢 • Or usability tests.

Then they try to fit their research goals around that decision. I’ve found it works better in reverse. Start with the question.

🟣 • What are you trying to learn?
🟣 • Are you trying to understand user behavior?
🟣 • Validate assumptions?
🟣 • Identify usability issues?
🟣 • Measure satisfaction?

Once the question becomes clear, choosing the right method becomes much easier.

Understanding user attitudes vs user behavior:

One of the most valuable lessons I’ve learned about research is that what users say and what users do are often different. Users might tell you they prefer a particular feature. But actual usage data may show something completely different. That’s why I like separating research into two categories.

Research that helps us understand what users think. And research that helps us understand what users do. Both are important. But they solve different problems. The strongest product decisions usually combine both perspectives.

Common research methods I use:

Depending on the project, I typically rely on a few research methods. User interviews help uncover motivations, expectations, and frustrations. Usability testing reveals interaction problems and friction points.

Surveys help gather feedback at scale. Analytics provide behavioral insights based on real usage. Each method serves a different purpose. The goal isn’t to use every method. The goal is to use the method that answers the most important question.

Research should reduce uncertainty:

For me, the purpose of user research has never been to collect more data. It’s reducing uncertainty. Every product decision carries risk. Research helps reduce that risk by providing evidence instead of assumptions.

The better the research approach, the better the decisions that follow. This is especially important in SaaS products where small design decisions can impact onboarding, retention, and long-term adoption.

How I choose a research method:

Whenever I’m planning research, I usually ask myself a few simple questions.

🔴 • What am I trying to learn?
🔴 • Do I need qualitative insights or quantitative data?
🔴 • Am I exploring a problem or validating a solution?
🔴 • Do I need attitudes, behaviors, or both?

These questions usually guide me toward the most appropriate method. The process isn’t complicated. But being intentional makes a significant difference.

Research is not about validation:

Another misconception I see often is treating research as a way to confirm existing ideas. Research should challenge assumptions, not protect them. If every research activity confirms what we already believe, we’re probably asking the wrong questions. Good research creates clarity. Great research changes perspectives. And sometimes the most valuable insight is discovering that our original assumptions were wrong.

Final thoughts:

The effectiveness of user research isn’t determined by how many interviews you conduct or how much data you collect. It’s determined by whether you’re learning the right things. Different research methods solve different problems.

Understanding that relationship helps teams make better decisions, reduce uncertainty, and create products that genuinely serve user needs. Because successful products aren’t built on assumptions. They’re built on understanding.