User Interview explained
A user interview is a structured conversation about a person's past experiences, needs, and decisions. The aim is to understand their context, not to get approval for an idea. An interview guide keeps the conversation focused while leaving room to follow unexpected answers. Asking about a specific past event, the person's goal, and the constraints they faced produces a richer account.
Why it matters.
Yes-or-no questions often stay on the surface. Asking about specific events can reveal obstacles and expectations the product team had not noticed. People cannot always predict what they will do in the future. Discussing recent decisions is usually more useful for design than asking whether someone likes a hypothetical feature.
Let's look at an example.
Think of a shopping experience.
Instead of asking ‘Would you use this feature?’, ask ‘How did you compare products the last time you shopped?’ The answer describes actual behavior. The interviewer can ask which products they opened, what details they compared, and what changed their mind. This reveals the underlying need rather than just a requested feature.
How to apply it.
- 01
Write down what you want to learn before the interview.
- 02
Ask open questions that do not lead the answer.
- 03
Ask for a real example and the context behind it.
“A good interview hears the context before the answer.