# User Interviews

One-to-one conversations that uncover users’ goals, experiences, language, expectations, and reasoning around a product or problem.

- Type: method
- Domain: Research & behavior
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/user-interviews/>)

## What it means

User interviews are guided conversations with people who use, avoid, buy, support, or are otherwise affected by a product. A researcher asks open questions and follows meaningful threads to understand experiences, motivations, vocabulary, and decision processes. Interviews reveal what participants remember and can explain; they do not directly show what people actually do.

## Why it matters

Interviews help teams replace internal assumptions with firsthand accounts and learn how people frame a problem in their own words. They are especially useful for discovering unmet needs, mapping decision journeys, and generating hypotheses. Strong interviews add context to behavioral data without pretending that a small qualitative sample represents an entire market.

## When to use it

Use interviews early in discovery, when entering an unfamiliar domain, exploring why a pattern appears in analytics, or learning about experiences that cannot be observed easily. They also help before redesigning workflows with high emotional, organizational, or privacy stakes.

## How it works

1. Define a focused research question and recruit participants with relevant recent experience.
2. Prepare a flexible guide that moves from context and past behavior toward specific examples and reflections.
3. Build rapport, ask one neutral question at a time, and probe for concrete incidents rather than opinions alone.
4. Capture notes or recordings with informed consent, then code recurring themes, contradictions, and outliers.
5. Turn findings into evidence-backed opportunities and questions for observation, testing, or quantitative validation.

## A practical example

A team designing subscription cancellation interviews recent cancellers and customers who considered leaving. Instead of asking whether cancellation is easy, the researcher asks each person to reconstruct the last attempt. The team learns that uncertainty about retained data—not button visibility—is the main source of hesitation, prompting clearer policy messaging and a prototype test.

## Where it breaks

Participants may forget, rationalize, or tailor answers to please the interviewer. Leading questions and premature solution talk can distort findings, while narrow recruiting hides important perspectives. Interviews are poor evidence for task success, frequency, or population prevalence; pair them with observation, usability testing, analytics, or surveys when those claims matter.

## Common mistakes

- Asking hypothetical “Would you use this?” questions instead of exploring recent behavior.
- Treating repeated comments from a small convenience sample as market-wide demand.
- Following the guide so rigidly that revealing examples and contradictions go unexplored.

## Sources

1. [User Interviews 101](<https://www.nngroup.com/articles/user-interviews/>) — Nielsen Norman Group · Professional guidance
2. [Writing an Effective Guide for a UX Interview](<https://www.nngroup.com/articles/interview-guide/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Contextual Inquiry](<https://wiki.soroush.uk/topic/contextual-inquiry/>)
- [Survey Design](<https://wiki.soroush.uk/topic/survey-design/>)
- [Triangulation](<https://wiki.soroush.uk/topic/triangulation/>)
