User Interviews
Qualitative interviews with users to gain insights into needs, goals, and context of use.
Classification
- ComplexityLow
- Impact areaBusiness
- Decision typeDesign
- Organizational maturityIntermediate
Technical context
Principles & goals
Use cases & scenarios
Compromises
- Confirmation bias from non-neutral questioning.
- Incorrect conclusions from incomplete synthesis.
- Privacy or consent issues when recording.
- Use semi-structured guides to ensure comparability and depth.
- Prioritize short question sets and focus on observations.
- Summarize interviews promptly and share insights.
I/O & resources
- Interview guide with goals and core questions
- Recruited participant profiles
- Recording or note-taking tools
- Transcripts or notes with quotes
- Thematic synthesis and insights
- Prioritized recommendations for product decisions
Description
User interviews are a qualitative research method to uncover users' needs, motivations, and context. Through structured or semi-structured conversations they yield deep insights into behaviors and pain points. They are especially useful in early discovery, hypothesis validation, and prioritizing user problems.
✔Benefits
- Direct insight into users' needs and motivations.
- Quick validation of assumptions before investments.
- Qualitative contextual information for prioritization.
✖Limitations
- Not representative for statistical claims without larger samples.
- Requires careful recruitment of relevant participants.
- Result quality depends on the moderator's interviewing skills.
Trade-offs
Metrics
- Number of validated hypotheses
Shows how many assumptions were supported or refuted by interviews.
- Recurring pain points
Number of distinct users reporting the same problem.
- Time to actionable insights
Time from interview to documented, actionable recommendations.
Examples & implementations
Onboarding Improvement in a FinTech App
Interviews with new users revealed comprehension gaps in identity setup; the team reduced steps and added help text.
Validation of a Payment Feature Hypothesis
Before implementation, interviews showed users prioritized differently than assumed; the feature roadmap was adjusted.
Usability Tests for a B2B Dashboard
User interviews with customer administrators identified recurring navigation misunderstandings; quick wins were prioritized.
Implementation steps
Formulate goals and research questions.
Create participant profiles and recruit.
Develop and pilot the interview guide.
Moderate and record interviews.
Transcribe, code, and synthesize thematically.
Communicate insights and translate into product decisions.
⚠️ Technical debt & bottlenecks
Technical debt
- Lack of structure for storing and reusing interview insights.
- Incomplete or non-standardized transcripts hinder analysis.
- No clear ownership for following up on recommendations.
Known bottlenecks
Misuse examples
- Using interviews to confirm internal assumptions without open questions.
- Interview colleagues as proxies instead of real users.
- Not documenting interview data and thus losing knowledge.
Typical traps
- Using too small or homogeneous samples for generalized claims.
- Over-interpreting results without cross-checking quantitative data.
- Lack of participant diversity leads to biased insights.
Required skills
Architectural drivers
Constraints
- • Observe privacy and consent when recording.
- • Participants' availability may be limiting.
- • Plan budget for recruitment and incentives.