User Interview
A user interview is a qualitative research method where a researcher asks a participant guided questions to learn about their experiences.
40 resourcesbeginner
Conducted one-on-one, it uncovers user motivations, workflows, frustrations and mental models. The goal is discovering authentic human context rather than gathering statistical market percentages.
How it works
A successful user interview follows a semi-structured discussion guide designed for deep empathy.
- Warm-up questions build mutual rapport and establish comfortable conversation dynamics before discussing sensitive workflows.
- Open-ended prompts encourage participants to share rich stories about their actual past behaviour rather than hypothetical opinions.
- Probing follow-ups ask 'why' or 'can you show me how you did that' to uncover root frustrations and manual workarounds.
- Session recordings capture spoken thoughts, pauses and emotional reactions for post-interview synthesis with product teams.
When to use it
Conduct user interviews during generative discovery or when troubleshooting mysterious analytics drops.
- Generative problem discovery validates whether a suspected customer pain point actually exists before writing code.
- Contextual workflow mapping reveals the messy external tools, paper notes and spreadsheets users juggle alongside your software.
- Concept evaluation explores user reactions to early strategic value propositions before investing engineering cycles.
- Persona development gathers authentic quotes and behavioral patterns that ground fictional personas in empirical reality.
Common mistakes
Researchers frequently corrupt interview insights by introducing bias into their questions.
- Asking leading questions such as 'Would you like a feature that saves time?' which forces polite affirmative answers.
- Asking users to predict future behaviour, when humans notoriously misjudge their future habits and purchasing willingness.
- Pitching product features during the session rather than listening silently to understand the user's personal reality.
Key takeaways
- User interviews reveal the human context, motivations and struggles behind user actions.
- Ask about past real-world behaviour rather than hypothetical future preferences.
- Open-ended questions and active listening prevent researcher bias from skewing findings.
- Five to eight well-targeted interviews uncover the majority of core user perspectives.
Learn this
Lessons and exercises mapped to this concept.
CourseProduct Management FoundationsMaster modern product leadership: root-cause problem discovery, customer-driven vision, cross-functional collaboration, agile execution, and measurable business impact.CourseUser Research & DiscoveryMaster the methods of user research: recruit unbiased participant cohorts, conduct non-leading qualitative interviews, design valid quantitative surveys, and synthesize raw notes into actionable evidence.
Common questions
- How does a user interview differ from a usability test?
- A user interview is a conversation focused on beliefs, habits and past experiences. A usability test observes a participant attempting realistic tasks on an active interface.
- When should researchers avoid user interviews?
- Avoid interviews when trying to measure quantitative frequencies or market pricing willingness, which require structured surveys and telemetry.