Early in my product career, I spent a lot of time looking at dashboards.

Usage was up.

Conversion had improved.

Retention was moving in the right direction.

On paper, everything looked fine.

Then we spoke to customers.

The story wasn’t quite as positive.

Customers were completing the workflow, but many found parts of it confusing. Some were creating workarounds. Others were using features differently from what we’d expected.

The data told us what was happening.

The conversations helped us understand why.

That’s the value of qualitative research.

What Is Qualitative Research?

Qualitative research is about understanding the experiences, motivations, frustrations, and behaviours behind customer actions.

Instead of asking only:

“How many users do this?”

we ask:

“Why are users doing this?”

Common methods include:

• Customer interviews
• Usability testing
• Focus groups
• Open-ended surveys
• Customer observation
• Diary studies
• Support conversations

The goal isn’t to produce a statistically representative number.

It’s to develop a deeper understanding of the people using your product.

Numbers Tell You Where to Look

One thing I’ve learned is that qualitative and quantitative research work best together.

Suppose your analytics show that 40% of users abandon a workflow at the same step.

That’s valuable.

But the number doesn’t tell you why.

Maybe the instructions are confusing.

Maybe users don’t have the information they need.

Maybe the workflow takes too long.

Or perhaps they’re questioning whether they need the feature at all.

Qualitative research helps investigate the reasons behind the pattern.

The data points you toward the problem.

The conversation helps you understand it.

Don’t Turn Interviews Into Feature Requests

A common mistake is treating customer interviews as a feature-request collection exercise.

You ask:

“What would you like us to build?”

The customer gives you a list.

You add it to the backlog.

Now you’ve done “research.”

But you’ve learned very little about the underlying problem.

I prefer questions such as:

“Can you walk me through how you do this today?”

“What happens when this goes wrong?”

“What is the hardest part of this process?”

“How are you solving this today?”

These questions reveal behaviour and context rather than hypothetical solutions.

Watch What People Do

One lesson I’ve learned is that observation can be more revealing than conversation.

During an interview, a customer might tell you:

“This workflow is easy.”

Then you watch them use it.

They hesitate.

Go back to the previous screen.

Search for help.

Try something else.

That’s a valuable signal.

People aren’t always able to articulate every friction point they experience.

Watching them work can reveal things they don’t think are worth mentioning.

Look for Patterns

One interview is a story.

Several interviews can reveal a pattern.

If three customers independently describe the same frustration, pay attention.

If ten customers use a feature differently than expected, investigate.

But don’t treat every comment as a universal truth.

Qualitative research isn’t about counting opinions until you reach a magic number.

It’s about identifying recurring themes and understanding the context behind them.

Avoid Confirmation Bias

This is where Product Managers need to be especially careful.

It’s easy to hear a customer say something that confirms what you already believe.

“Exactly. That’s why we should build this feature.”

But good research should sometimes challenge your assumptions.

If you’re convinced customers want a feature, actively look for evidence that might prove you wrong.

If customers describe a different problem, don’t force their feedback into your existing framework.

The goal of research isn’t to validate your idea.

It’s to improve your understanding.

Connect Research to Decisions

Research becomes much more valuable when it changes something.

Maybe you change the roadmap.

Maybe you simplify a workflow.

Maybe you decide not to build a feature.

Maybe you discover a new customer segment.

Maybe you change your positioning.

The output of research shouldn’t simply be a document sitting in a folder.

It should influence what the team does next.

Final Thought

I’ve come to see qualitative research as one of the most important tools for Product Managers because it brings the customer’s experience into the room.

Analytics can tell you that users are dropping off.

Qualitative research can help you understand what that moment feels like.

Both perspectives matter.

The best product decisions happen when we combine behavioural evidence with human context.

Because behind every metric is a person trying to accomplish something.

And sometimes, the fastest way to understand the number is simply to ask the person behind it.