Experiment & Research Method
User Interviews
User interviews are structured one-on-one conversations that uncover the goals, context, and pain points behind user behavior.
- Fidelity
- Medium
- Effort
- Medium
- Time to run
- 1–2 weeks
What is a User Interviews?
A user interview is a moderated, one-on-one conversation with a current or prospective user, designed to understand their goals, workflows, motivations, and frustrations in their own words. Unlike surveys, interviews are adaptive — a skilled interviewer follows the thread, asks "why," and probes the reasoning behind what people do.
Interviews are the highest-bandwidth way to learn why something is happening. They explain the "why" behind the "what" that your metrics and A/B tests reveal, which makes them the natural starting point for any open-ended product question.
When to use it
Good fit
- You are exploring a problem space and do not yet know the right questions to ask.
- Quantitative data shows what is happening but not why.
- You need rich context on workflows, motivations, or unmet needs before designing a solution.
Reach for something else when
- You need statistically representative data — use a survey or A/B test.
- The question is about which of two designs performs better — use a preference or usability test.
- You cannot recruit people who genuinely represent your target users.
How to run it
Define the learning goal
Write down the decision the research will inform and the top questions you must answer. This keeps the conversation focused and the findings actionable.
Recruit the right participants
Screen for people who actually represent the segment you care about. Five to eight well-chosen participants usually surface the dominant themes for a given segment.
Write an open-ended discussion guide
Prepare non-leading questions grounded in past behavior ("Tell me about the last time you…") rather than hypotheticals. Order from broad to specific.
Interview and probe, do not pitch
Listen more than you talk, ask "why" repeatedly, and resist selling your idea. Record (with consent) so you can focus on the conversation.
Synthesize into themes and insights
Cluster observations across interviews into patterns, quantify how often each appears, and translate them into decisions, opportunities, or hypotheses to test.
What you'll learn
Deep, contextual understanding of user goals, mental models, workflows, and unmet needs — the "why" behind your metrics, and a backlog of sharp hypotheses worth validating quantitatively.
Frequently asked questions
How many user interviews are enough?
For a single, reasonably homogeneous segment, five to eight interviews typically surface the dominant themes, with diminishing returns after that. If you are covering several distinct segments, plan roughly that many per segment.
What is the difference between user interviews and surveys?
Interviews are qualitative and adaptive — they explain why people behave as they do and work best with small samples. Surveys are quantitative and fixed — they measure how widespread something is across a large sample. They are complementary: interviews generate hypotheses, surveys size them.
How do you avoid leading questions in an interview?
Ask about concrete past behavior instead of hypotheticals, avoid questions that hint at a "right" answer, and follow up with neutral prompts like "tell me more" or "why was that?". Never pitch your solution during a discovery interview — you will only hear polite agreement.