Run User Interviews That Inform A Real Decision
Prepare a focused study, listen for what happened and turn the evidence into next steps.
- For
- Product teams and researchers
- Level
- Research practice
- Steps
- 5
Name The Decision Before Recruiting
Write the decision your team is struggling to make. Perhaps customers abandon account setup, or staff keep exporting a dashboard into a spreadsheet. List the assumptions behind your preferred explanation, then choose questions that could change your mind. Decide who has direct experience of the situation and who might experience it differently. Avoid recruiting only colleagues or enthusiastic customers, because their circumstances may leave important problems outside the study.

Prepare For Consent And Useful Notes
Explain the purpose of the session, what you will record and how the material will be used. Obtain consent before recording and agree who can access the notes. Keep unnecessary personal information out of shared documents. Prepare a discussion guide with a few broad topics and prompts for recent examples. Leave room to follow an unexpected answer, while keeping the same core questions across sessions so you can compare experiences.
Ask About A Recent Experience
Invite the participant to describe the last time they tried the task. Ask what started it, which tools they used and what happened next. Follow up on a specific action rather than asking whether they would like your proposed feature. When possible, ask them to show the relevant workflow using safe example data. Let a pause happen before filling it with another question. Leading explanations can turn your own assumptions into apparent evidence.

Separate Observation From Interpretation
After each session, capture what you heard or saw, the context and your interpretation in separate columns. Remove identifying details where they are unnecessary. Group related observations across sessions and keep contradictory examples visible. A memorable quote can explain a problem, but it cannot establish its frequency. Distinguish recurring patterns from isolated incidents, and record gaps in the sample before sharing conclusions with the team.
Connect Findings To The Product
For each finding, write the product decision it affects, the supporting observations and a sensible next action. Some questions need a design change, while others need a usability test or more research. Share a small set of priorities with the people making the decision, including what the study cannot tell them. Keep the research question and evidence links with the decision record so future discussions can return to the original context. Use a short shared readout with the product decision owner to agree what will change, what needs testing and what should remain explicitly open.