UX Foundations · Step 3 · 4 min read
Short user interviews
A 30-minute conversation with the right person can save weeks of design. How to plan a short interview, ask about real past events instead of opinions and predictions, avoid leading questions, decide how many to do, and turn your notes into findings.
People are bad at predicting what they'll do, and good at telling you what they did. "Would you use this feature?" gets a polite yes. "Tell me about the last time you had to do this" gets a real story: the workaround, the spreadsheet, the colleague they called. A short interview built on real stories is one of the most useful things a designer can do, and it takes less than an hour.
What you'll be able to do after reading:
- Plan a short interview with a clear goal
- Ask open questions about past behaviour
- Avoid leading questions
- Decide how many interviews you need, and make sense of the notes
1. Plan it in ten minutes
- Goal: what do you need to learn? ("How do people prepare their expense claims today?")
- Who: people who actually do the task, not colleagues who can imagine it.
- Guide: five or six open questions, from broad to specific. You won't ask them all in order; they're a safety net.
- Consent: say what it's for, ask before recording, and say how notes will be kept and anonymised. (This is the course's advice; follow your organisation's rules too.)
2. Ask about real past events
NN/g's advice: "Jog the memory by asking about specific events rather than about general processes", and a good opener is "Tell me about the last time you [did something]" (NN/g, Rosala and Pernice, User Interviews 101, 2023).
Predictions are unreliable.
People say yes to be politeA real event, with details.
Then: what happened next?Leads towards your answer.
You hear what you wantedShows workarounds and real needs.
Spreadsheets, notes, colleaguesThen follow the story: "What happened next?", "How did that feel?", "What did you do about it?". The best moments come from following up, not from the next question on your list.
3. Leading questions
A leading question pushes people towards an answer: "Wouldn't it be easier if…?", "How much do you like…?". NN/g explains how they bias what you hear (NN/g, Schade, Leading Questions, 2017). Rewrite them as neutral, open questions: "How do you feel about…?" becomes "Tell me about the last time you used…".
Also avoid asking people to design for you ("What features should we add?"). Their needs are the data; the solutions are your job.
4. How many?
"Unfortunately, there isn't a golden number", says NN/g. Start with a small sample ("say 5-6"), analyse as you go, and stop when new interviews stop telling you new things (NN/g, Rosala, How Many Participants for a UX Interview?, 2021). For broad, exploratory questions you'll need more; for a narrow question, five may be enough.
5. From notes to findings
Right after each interview, write down the three things that surprised you. After a few interviews, put notes on cards and group them (see Affinity mapping). A finding is a pattern across several people, with quotes, not one memorable story.
6. Common mistakes
- Asking what people would do, instead of what they did.
- Leading questions and pitching your idea.
- Talking more than the participant.
- Interviewing only colleagues or friends.
- Reporting one vivid quote as if it were a pattern.
7. Vocabulary
| Term | Meaning |
|---|---|
| Interview guide | A short list of open questions, used as a safety net |
| Open question | One that can't be answered yes or no |
| Leading question | One that pushes towards a particular answer |
| Follow-up | A question that digs into what the person just said |
| Saturation | The point where new interviews add nothing new |
8. Try it (no tools needed)
- Pick a friend or family member and a task they do regularly (paying bills, planning meals).
- Ask: "Tell me about the last time you…". Then only follow up for ten minutes: no other questions.
- Write down three things you didn't expect, and one thing they did that no app helped with.
Reflection questions: How often did you want to suggest a solution? What did following up reveal that your first question didn't?
9. If you already practise
- Record (with consent) and re-listen to one of your own interviews: count how often you talked, and how often you led.
- Steve Portigal's Interviewing Users (Rosenfeld Media) is the classic book on this craft.
- Rob Fitzpatrick's The Mom Test is a short, practical guide to asking questions people can't lie to you about (momtestbook.com).
Checklist
Learn more
- NN/g: User Interviews 101 (2023) · How Many Participants for a UX Interview? (2021) · Leading Questions (2017)
Books, courses and videos to go deeper
- Interviewing UsersSteve PortigalBook · Rosenfeld Media (Amazon)
- The Mom TestRob Fitzpatrick (external site)
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
How people think · Usability testing with five people · User needs and jobs to be done · Affinity mapping · Contextual inquiry · AI in UX research