What is a user interview in UX?
A user interview in UX is a one-on-one conversation where a researcher asks people about their goals, habits and frustrations to understand their real needs.
also calledcustomer interview · discovery interview · one-on-one interview
It sounds almost too simple: you sit down with someone and ask about their life. But a good interview surfaces things no analytics chart can show, like why a person keeps a paper notebook next to a perfectly good app. You come away with stories, and stories change how a team thinks.
- Interviews uncover the why behind behavior, which numbers cannot show.
- Ask about real past experiences instead of hypothetical futures.
- Avoid leading questions and resist the urge to pitch your idea.
- Look for patterns across several people before drawing conclusions.
What interviews are for
Interviews are best for understanding the why behind behavior: motivations, workarounds, context and emotions. They shine early in a project, when you are still working out what problem to solve, and they are cheap compared with building the wrong thing.
They are not good for measuring how many people feel something, or for judging whether a screen is usable. For counts, use surveys or analytics. For usability, watch people attempt tasks.
Preparing for a good conversation
Start with what you need to learn, not with a list of questions. Then:
- Recruit people who match the audience, usually five to eight per group
- Write an open guide with a handful of topics, not a script to read aloud
- Plan for 30 to 60 minutes
- Ask permission to record, and explain how the recording will be used
- Do a practice run with a colleague
The guide is a map, not a railway. Be ready to wander when the person says something interesting.
Asking questions that get real answers
Ask about the past, not the future. "Tell me about the last time you booked a trip" beats "Would you use a feature that did this?", because people are poor at predicting their own behavior and eager to be polite. Stay with specific moments and follow up with "What happened next?" and "Why was that?".
Avoid leading questions like "Don't you find it frustrating when...?". Let silence do some of the work: people often add the most useful sentence after a pause. And keep your own opinions out of the room.
Mistakes to watch for
Pitching your idea instead of listening is the top one. Next comes talking to friends, who say nice things, and asking people to design the solution. Users know their problems well, but they are not the best source for solutions.
Another trap is hearing what you hoped to hear. Write down exact words and look for patterns across several people before drawing a conclusion. One person's strong opinion is a lead, not a finding.
Turning notes into insight
After each session, write a few lines on what stood out while it is fresh. Later, pull quotes and observations onto sticky notes and cluster them into themes, an approach often called affinity mapping. The output might be personas, a journey map or a short list of problems worth solving, shared with the people who will act on it.
User interview: your questions, answered
What is a user interview in UX research?
It is a structured conversation between a researcher and one participant about their experiences, goals and problems. The aim is to understand what people need and why they behave as they do, usually early in the design process.
How many user interviews do I need?
Five to eight per distinct user group is a common starting point, since patterns often appear by then. If every new interview keeps surprising you, do more. If answers start repeating, you have likely learned the main themes.
How long should a user interview be?
Thirty to sixty minutes is typical. Shorter sessions rarely get past surface answers, and longer ones tire both sides. Plan a little extra time for introductions and for the participant's own questions at the end.
What questions should I ask in a user interview?
Use open questions about specific past experiences, such as "Tell me about the last time you did this." Follow up with "why" and "what happened next", and avoid leading or yes-or-no questions that push people toward an answer.
How do I recruit participants for interviews?
Define who you need, then reach them through your customer list, social channels, communities or a recruiting service. Screen with a short questionnaire to confirm they fit, and offer a fair incentive for their time.
More quick answers
What is the difference between a user interview and a usability test?
An interview explores needs and context through conversation. A usability test watches people try specific tasks to see where a design fails.
Are user interviews qualitative or quantitative?
Qualitative. They give rich detail from a few people rather than numbers from many.
Can I do user interviews remotely?
Yes. Video calls work well, and they widen who you can reach. Check audio, share the same ground rules, and keep the setting relaxed.
What is a stakeholder interview?
A conversation with internal people, like managers or clients, to learn goals and constraints. It is different from interviewing users.
What do you do with interview findings?
Group notes into themes with an affinity map, then turn them into personas, journey maps or prioritized problems for the team.
User research in UX is the practice of studying people who use or might use a product, to understand their needs and behavior so design rests on evidence.
Qualitative user research is the study of people's behavior, needs and motivations through observation and conversation, to learn why they act as they do.
An affinity map in UX is a visual grouping of research notes, quotes and observations into themes so patterns across many users become easy to see.
A persona in UX is a fictional but research-based profile of a typical user, describing their goals, habits and frustrations to keep design decisions grounded.
Contextual inquiry in UX is a research method where you observe and question users in their own environment while they do real work with a product.
Stakeholder interviews in UX are structured talks with the people who have a stake in a product, held to learn goals and constraints before design starts.
Found this useful? A GitHub star helps other designers find it.