GLOSSARY

What is a User Interview?

Table of content
Definition

Definition

A user interview is a research conversation used to understand a participant’s goals, behavior, context, experiences, needs, and reasoning in their own words.

TL;DR

  • User interviews are structured conversations used to learn about users’ real experiences and context.
  • Good interviews ask about past behavior more than hypothetical preferences.
  • Open, neutral questions produce better evidence than leading questions.
  • Interviews are useful for understanding motivations and problems, not proving market size.
  • Patterns across several interviews matter more than one memorable quote.

What does a user interview uncover?

A strong interview can reveal what the user was trying to accomplish, what alternatives they considered, where they struggled, what workarounds they created, and why the outcome mattered.

That context is much more useful than asking “Would you use this feature?”

Good user-interview questions

  • “Tell me about the last time you did this.”
  • “What happened next?”
  • “What was difficult about that?”
  • “How did you solve it?”
  • “What made that important?”

These questions anchor the conversation in real behavior.

User interview vs. usability test

A user interview primarily explores experiences, needs, and reasoning through conversation. Usability testing observes someone using an interface or prototype to complete tasks.

Teams often combine them.

How do you run a user interview?

  1. Define the research question.
  2. Recruit participants who match the target context.
  3. Prepare a flexible discussion guide.
  4. Start broad before probing details.
  5. Ask for concrete examples.
  6. Avoid teaching or selling during the conversation.
  7. Capture notes or recordings with consent.
  8. Synthesize patterns across participants.

Common mistakes

Leading the participant

“Wouldn’t this save you time?” contains the desired answer.

Talking more than listening

The participant should do most of the explaining.

Asking only future hypotheticals

Past behavior is often more reliable than imagined future behavior.

Overgeneralizing from one person

One interview is a clue, not a market.

The bottom line

A user interview asks: what happened in the user’s real life, and what can that teach us about the product decision?

Related terms

User research · User need · Pain point · Research insight

Relevant Figr resource

Read User Research Methods for interview planning and complementary methods.

Related Figr Projects

No items found.