UR

User Interviews

A practical research method for understanding how people think, behave, and make decisions in a real context.

How to use user interviews to uncover real behaviour, decision-making, and pain points instead of relying on opinion or assumption.

26 March 20265 min read

Quick take

If you need to understand why something is happening, not just what is happening, start with interviews.

What it is

User interviews are a qualitative UX method used to understand , motivations, and through direct conversation.

They are a core part of and are used to uncover how people think, what they do, and why they do it.

They are not about collecting opinions. They are about understanding real experiences.

At a surface level, people will often give answers that sound reasonable. At a deeper level, they reveal what actually drives their .

The goal is to understand what people have done, why they did it, and what got in their way.

The value of interviews is not in what sounds reasonable. It is in what reveals what actually drives behaviour.

When to use it

Use this method when you need depth and that analytics or cannot provide.

They are most useful when:

You are starting a project and need to understand the problem properly
Behaviour in analytics or funnel data does not make sense
Stakeholders are making decisions without evidence
You need to understand decision-making, not just outcomes
You are working with a new audience or domain
They are less useful when:
You need validation at scale
The problem is already clearly defined
You are measuring performance rather than understanding behaviour
User interviews are often used alongside usability testing and analytics to build a complete picture.

Key takeaway

Interviews are most useful when the problem needs depth, context, and explanation rather than quick validation.

How to run it

Set up properly.

Before you start, be clear on what you are trying to learn, what decisions this will inform, and who you need to speak to.

Recruit people with real experience of the problem. Avoid using whoever is easiest to access.

Run the method.

A good interview feels like a conversation, not a script.

Start broad, then move into specifics. Focus on real experiences, not opinions. Ask open questions. Let people talk without interrupting. Ask for examples and details.

Good questions: Tell me about the last time you did this. What happened next. Why did you choose that.

Avoid: Would you use this. Do you like this idea.

These to hypothetical answers, which are unreliable.

Capture and make sense of it.

The value comes after the interview.

Look across to identify repeated , common , shared behaviours, and differences between users.

Group so they become usable, not just interesting.

What to look for

Focus on:

Behaviour over opinion
What people do matters more than what they say
Specific moments
Details reveal what is really happening
Workarounds
These often highlight gaps or broken experiences
Decision triggers
What caused them to act
Language
How users describe things often differs from internal terminology

Where it goes wrong

Most issues come from:

If you leave with your assumptions confirmed, you probably did not go deep enough.

asking hypothetical questions
leading the participant
talking more than listening
rushing through topics
trying to confirm an existing idea

What you get from it

Done properly, this method gives you:

a clear understanding of user behaviour
context behind decisions
insight into real problems
better framing of what needs to be solved

Key takeaway

It turns assumptions into something you can actually act on.

Get in touch

If this sounds like something you need, we can help you understand what your users are actually doing and why.

No guesswork. No assumptions. Just clear you can act on.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What are user interviews in UX?

User interviews are a method used to understand , needs and motivations through direct conversation.

When should you use user interviews?

Use them when you need depth and explanation, especially in early or when analytics alone cannot explain .

How many users do you need for interviews?

Usually 5 to 8 relevant participants per group is enough to uncover strong behavioural , depending on the complexity of the problem.

What is the difference between interviews and surveys?

User interviews provide depth and . provide scale and measurable .

Are user interviews the same as usability testing?

No. User interviews focus on understanding and experiences, while focuses on how well someone can use a product.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20