Skip to content
NewTemplates & toolkits are on the way — join the waitlist
Hecham Gazhi

UX Design · Lesson 04 / 13

User interviews

A complete guide to user interviews: planning, writing a discussion guide, asking great questions, running the session, taking notes and synthesising findings with affinity mapping.

6 min read · 5 quiz questions

When to use interviews

User interviews are one-to-one conversations with people who represent your users. They are the most common UX research method because they are flexible, cheap and reveal the why behind behaviour: goals, motivations, workarounds, frustrations and the context people live and work in.

  • Use them to explore a problem space, understand needs before designing, or dig into why something is happening.
  • Don't use them to measure how many people do something (use a survey or analytics), to test whether a design is usable (use usability testing), or to ask people to design the product for you.

Planning the interviews

  1. 1Write 3–5 research questions — what the team needs to learn.
  2. 2Define who you need to talk to and write a screener to recruit them.
  3. 3Decide the format: in person, video call or phone. 45–60 minutes is typical.
  4. 4Write a discussion guide (see below).
  5. 5Run a pilot interview with a colleague to check timing and wording.
  6. 6Schedule sessions with breaks between them for notes.

How many interviews? For one fairly similar user group, patterns usually start repeating after about 5–8 interviews. If you have several distinct groups — say, buyers and sellers — plan interviews for each.

The discussion guide

A discussion guide is your script — but a flexible one. It makes sure you cover the important topics while leaving room to follow interesting threads. A typical structure:

PartTimePurpose
Introduction5 minThank them, explain the purpose, consent to record, "there are no wrong answers"
Warm-up5 minEasy questions about their role or routine to build rapport
Main topics30–40 minOpen questions about experiences related to your research questions
Wrap-up5 min"Is there anything I didn't ask that I should have?", thanks, incentive
Exampletext
INTRO
"Thanks for joining. We're learning how freelancers handle invoicing.
 We're not testing you — there are no right or wrong answers.
 Is it OK if I record this so I can focus on our conversation?"

WARM-UP
- Tell me a bit about your work. What does a typical week look like?

MAIN
- Walk me through the last time you sent an invoice.
  - What did you do first? Then what?
  - What tools did you use? Why those?
  - What was the hardest part?
- Tell me about a time an invoice went wrong.
- How do you keep track of who has paid?

WRAP-UP
- If you could wave a magic wand and change one thing about
  invoicing, what would it be?
- Anything else I should have asked?

Asking great questions

Open, not closed

Closed questions get yes/no answers and stop the conversation. Open questions invite stories.

Past, not future

People are poor predictors of their own future behaviour. "Would you use this?" almost always gets a polite yes. Ask what they did the last time instead.

Neutral, not leading

"How frustrating was it?" assumes frustration. "How was it?" lets them tell you.

Specific, not general

"How do you usually…" gets an idealised summary. "Tell me about the last time…" gets a real, detailed story.

Instead of…Ask…
Do you like our app?Tell me about the last time you used it. What were you trying to do?
Would you pay for this feature?How are you solving this today? What does it cost you?
Isn't it annoying when…?What happens when…?
How often do you check your bank balance?When did you last check it? What made you check?
Do you want a dark mode?Tell me about when and where you use the app.

Running the session

  • Listen more than you talk. Aim for the participant speaking 80% of the time.
  • Embrace silence. After an answer, wait a few seconds. People often add the most valuable detail to fill the pause.
  • Follow up. "Why was that?", "Can you tell me more?", "What did you do next?", "Can you show me?"
  • Repeat their words. "You said it felt risky — risky how?" keeps them talking without leading.
  • Don't defend or explain the product. If they're confused, that's data.
  • Don't pitch solutions. You're there to learn about their world, not sell yours.
  • Watch for contradictions between what people say and what they show you, and gently explore them.

Common mistake: Asking participants to design the solution. "What features should we build?" produces wish lists, not insights. Understand the problem deeply and let the team design the solution.

Taking notes

If possible, have a second person take notes so the interviewer can focus on the conversation. Record the session (with consent) and use automatic transcription as a backup.

  • Write down what people say and do, using their exact words where you can.
  • Mark your own interpretations separately, e.g. with "[I think…]".
  • Note emotions, workarounds and tools mentioned.
  • Within an hour of the session, write a short summary of the top 3–5 things you learned.

Synthesis with affinity mapping

After the interviews, you'll have hundreds of observations. Affinity mapping (also called affinity diagramming) turns them into themes.

  1. 1Write each observation or quote on its own sticky note (physical or digital, e.g. in FigJam or Miro).
  2. 2As a team, put all notes on a wall, mixed together.
  3. 3Silently move notes that seem related next to each other.
  4. 4Name each group with a sentence that describes the theme — written from the user's perspective, e.g. "I don't know if my invoice is legally correct".
  5. 5Group related themes into bigger clusters.
  6. 6Turn the strongest themes into insights: what you learned, why it matters, and what it implies for design.

Example · From quotes to insight

Notes: "I copied my friend's invoice template", "I googled what VAT number means", "I was scared the client would think I'm an amateur".

Theme: New freelancers are unsure what a correct invoice must contain.

Insight: New freelancers fear looking unprofessional more than they fear the paperwork itself — so reassurance and good defaults matter more than extra features.

Key takeaways

  • Interviews reveal goals, motivations and context — the 'why' behind behaviour.
  • Plan with research questions, a screener and a flexible discussion guide; pilot it first.
  • Ask open, neutral questions about specific past experiences.
  • Listen more than you talk, use silence and follow-up questions, and never pitch.
  • Synthesise with affinity mapping to turn observations into themes and insights.

Exercise

Run a practice interview

  1. Choose a topic, e.g. "how people plan their weekly groceries".
  2. Write a discussion guide with an intro, two warm-up questions, five main questions and a wrap-up.
  3. Review every question: is it open, neutral and about past behaviour? Rewrite any that aren't.
  4. Interview one person for 20 minutes and take notes.
  5. Write down the three most surprising things you learned.

Test yourself

User interviews quiz

5 questions. Score 70% or more to complete the lesson.

  1. 1.Which is the best interview question?
  2. 2.'How frustrating was the sign-up?' is a problem because…
  3. 3.Why stay silent for a few seconds after an answer?
  4. 4.What should you do if a participant is confused by your product?
  5. 5.What is affinity mapping used for?