A user interview is a one-on-one conversation between a researcher and someone who uses (or might use) a product. User interviews aren't sales calls. They're a way to understand how the person experiences the product, what problems they encounter, and what they actually do when those problems come up.
User interviews are one of the most common methods product teams use to learn directly from the people they're building for. Done well, they surface the why behind user behavior in a way that surveys and analytics can't.
This guide explains what user interviews are, the main types, when teams use them, and how they fit alongside other research methods. If you're looking for a step-by-step walkthrough of running one yourself, see our companion guide on how to conduct user interviews.
What User Interviews Are and Why They Matter
User interviews are structured conversations designed to surface the experience, motivation, and context behind user behavior.
A user interview is a guided conversation with a single participant, usually lasting 30 to 60 minutes. A researcher asks open-ended questions and listens for patterns in how the participant describes their experiences, their challenges, and the way they currently solve problems.
Most interviews happen one-on-one, either in person or over video. The focus is depth, not breadth. Five to eight conversations with the right people will often surface insights that thousands of survey responses miss, because interviews let researchers follow an unexpected thread or ask "why" in real time.
Product teams use interview findings to:
- Identify problems users face that don't surface in support tickets or analytics
- Understand how people use products in their actual environment
- Discover unmet needs before committing engineering resources to a solution
- Validate assumptions before they turn into expensive mistakes
The value comes from the qualitative depth. Analytics can tell a team that users abandon a flow at step three. An interview can tell them why.
Types of User Interviews
Different research goals call for different interview formats.
There's no single "user interview" format. The most useful distinctions are how structured the conversation is and where it takes place.
Structured vs. semi-structured vs. unstructured
Structured interviews use the same fixed questions in the same order with every participant. They make it easier to compare answers but limit how deeply a researcher can explore a single thread.
Semi-structured interviews use planned questions with room to follow up or change direction when something interesting comes up. This is the format most product teams use because it gives you structure without locking you into a script.
Unstructured interviews are open conversations with only a few starting prompts. They work best in early exploration when researchers don't yet know enough about the problem space to ask focused questions.
Contextual vs. remote interviews
Where the interview takes place also matters. Contextual interviews happen in the user's environment, their home, office, or wherever they actually use the product. They let researchers observe details that participants wouldn't think to mention: workarounds, habits, environmental constraints.
Remote interviews happen over video or phone. They offer access to participants in different locations, faster scheduling, and built-in recording. Most product research uses remote interviews unless the environment itself is part of what the team needs to understand.
When Teams Use User Interviews in Product Development
User interviews appear across the product development lifecycle, with different goals at each stage.
Product teams use user interviews at several points during development. Each stage answers a different kind of question.
In discovery, interviews help teams understand whether the problem they think they're solving is actually the problem users face. Findings here often reframe the work before any design begins.
During the design phase, interviews validate that proposed solutions match how users think about the problem. Researchers test early concepts and listen for the gap between intent and understanding.
In development, interviews surface friction with specific features before launch. They catch small confusions that don't appear in design reviews but show up later as support tickets.
After launch, interviews show how users actually adopt and apply the product in practice. Teams use that signal to decide what to build next.
For specific advice on what to ask at each stage, see our guide on how to conduct user interviews.
How User Interviews Differ from Other Research Methods
Interviews answer different questions than surveys, usability tests, or analytics. The most common mistake is treating one method as a substitute for the others.
User interviews are one tool among several. Knowing what they're good for, and what they're not, helps teams choose the right method for the question at hand.
- Surveys scale to thousands of users but only capture answers to the questions researchers thought to ask. They're best for statistical confidence in measurable behavior.
- Usability testing observes whether users can complete specific tasks with a product. It evaluates a solution rather than uncovering a problem.
- Analytics track behavior at scale across an entire user base. They show where users drop off, not why.
- Focus groups gather multiple participants at once. They suit research where group dynamics are part of what teams want to study, but offer less depth per person than a one-on-one interview.
User interviews complement all of these. They explain the why behind what analytics measure, the friction that usability tests reveal, and the context that surveys miss.
Ready to Run a User Interview?
If you're planning to run user interviews yourself, our step-by-step guide on how to conduct user interviews covers preparation, technique, the question bank to draw from, and how to analyze what you learn afterward.
For teams running ongoing user testing programs, user interviews give the qualitative depth needed to interpret what broader feedback data is saying. Centercode helps product teams gather structured feedback at scale, so decisions aren't based on eight conversations alone when hundreds of real users could validate the pattern.
Frequently Asked Questions
What are user interviews used for?
Product teams use user interviews to understand why users behave the way they do, what problems they're trying to solve, and how they think about the space a product operates in. The output usually informs product decisions: what to build, what to change, or what to remove from the roadmap.
What's the difference between a user interview and a survey?
User interviews are one-on-one conversations that produce qualitative depth: motivations, context, mental models. Surveys collect structured answers from many participants and produce quantitative breadth: how many people do X, how often, in what proportion. Most teams use both. Interviews uncover the questions worth asking; surveys measure how widespread the answers are.
What's the difference between a user interview and usability testing?
User interviews focus on understanding context and experience through conversation. Usability testing observes a participant attempting specific tasks with a product, often with limited verbal explanation. Interviews answer why something matters to users. Usability tests answer whether users can actually do the thing. Both are valuable, but they answer different questions.
Who conducts user interviews?
User interviews are usually run by product managers, UX and customer experience researchers, designers, or user behavior specialists. A formal research background helps but isn't required. The most important skills are active listening, neutral phrasing, and resisting the urge to lead the conversation toward what the team hopes to hear.
