Skip to content
Tutorials Center
My learning

Topics

Lesson 11 of 36 ยท User Research

User Interviews

Learn how to run good user interviews. Write open questions, avoid leading and hypothetical questions, probe for stories, take notes and turn them into themes.

A user interview is a guided conversation that helps you understand how someone thinks, behaves and feels about a topic. It is one of the most useful and most misused research methods. Done well it reveals needs nobody had thought to mention. Done badly it simply collects polite opinions.

When to use interviews

Interviews are best early, when you do not yet know what to build, and for questions like "How do people handle X today?" or "What matters to them?". They are not good for measuring how many people feel something, nor for judging usability of a design (use a usability test for that), nor for predicting whether someone will buy.

Prepare a discussion guide

A discussion guide is your outline, not a script. It usually has:

  1. Introduction: thank them, explain the purpose, say there are no wrong answers, ask for permission to record, confirm they can stop at any time.
  2. Warm-up: easy background questions ("Tell me about your work").
  3. Core topics: three to five areas drawn from your research questions.
  4. Wrap-up: "Is there anything I didn't ask that I should have?" Thank them.

Plan about 45 to 60 minutes. Keep a pilot interview with a colleague to fix confusing questions.

Ask about the past, not the future

People are unreliable at predicting their own behavior. "Would you use a feature that did X?" gets a polite "yes". Better to ask about real recent behavior:

  • Weak: "Would you use an app that reminds you to water plants?"
  • Better: "Tell me about the last time one of your plants died. What happened?"

Stories reveal context, workarounds and emotions that opinions hide.

Question types

  • Open questions: "How do you decide what to cook?" invite stories.
  • Probes: "Can you tell me more about that?", "What happened next?", "Why was that important?"
  • Silence: wait a few seconds after an answer. People often add the most useful detail.
  • Avoid: leading questions ("Don't you find it frustrating?"), double-barreled ("Do you use search and filters?"), jargon, and yes or no questions.

The five whys technique asks "why?" a few times to move from a surface statement to a root cause; use it gently, as it can feel like an interrogation.

Interview dos

Ask for stories Last time you...
Stay quiet Let silence work
Probe Tell me more
Listen Do not sell or defend

You are there to learn, not to convince.

1 / 2

A stand-in: a question quality checker

This stand-in flags common problems in draft questions using simple word patterns. It is crude (real judgment needs a human), but it trains your eye.

JS Interview question checker (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

During the session

  • Build rapport; smile and show you are interested.
  • Record (with consent) so you can listen instead of scribbling. Keep brief notes of surprises.
  • Follow the person's thread when it is relevant; return to the guide when it is not.
  • Do not correct, teach or defend the product. If they are wrong about how it works, that is data.
  • Have a second person take notes if possible.

After the session: from notes to insight

Within a day, write up while memories are fresh. Then analyze across participants:

  1. Extract observations: single facts or quotes on separate notes ("Pays by phone because the desktop site logs her out").
  2. Group them into clusters with similar meaning. This is called affinity mapping.
  3. Name each cluster as a theme, in plain language.
  4. Turn themes into insights and recommendations: what it means and what to do.

Count patterns, but avoid over-claiming numbers from a small sample: "five of eight participants kept a paper backup" is honest; "62.5 percent of users" is not.

Ethics

Respect privacy: anonymize quotes, store recordings securely, delete them when promised. Do not pressure people to share sensitive details. Compensate fairly.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which question is best for an interview?

    It asks for a real past story rather than a prediction or a leading opinion.
  2. 2. Why use silence in an interview?

    After a pause, participants often share the most useful information.
  3. 3. What is affinity mapping?

    You cluster similar observations and name each cluster.
  4. 4. How should you handle a participant who misunderstands the product?

    Misunderstanding reveals gaps in the design or communication.

Summary

  • Use interviews to understand needs and context early on.
  • Prepare a guide with intro, warm-up, core topics and wrap-up.
  • Ask open questions about past behavior; probe and use silence.
  • Analyze by extracting observations, clustering them and naming themes.
  • Treat participants ethically and do not over-claim from small samples.

Next: Surveys and Questionnaires