I've sat in on hundreds of user interviews over my career. And I can tell you: most of them produce the same thing. The user is polite. They say the product is "nice" or "easy to use." They don't mention the three things that confused them. They don't tell you about the workaround they invented because a core feature didn't work how they expected.
They're not lying. They're just being human. People are social. They don't want to criticise something to the face of the person who built it.
Good user interview technique is about creating the conditions where honest answers are possible. Here's how.
Before the interview
Define what you need to learn
Write down the three most important questions your team has about user behaviour — not about the product, about the behaviour. "Why do users abandon the checkout at step 3?" is a behaviour question. "Do users like our new checkout design?" is a product question. Research the behaviour; validate the design separately with usability testing.
Recruit the right people
Five interviews with the right participants are worth more than twenty with the wrong ones. Define your target user clearly — not "adults aged 25-45" but "people who have moved cities at least once in the last three years and currently manage their own finances." Specificity gets you signal.
During the interview
Start by removing pressure
Open every session with the same sentence: "I want to be clear — we're not testing you, we're testing the product. There are no wrong answers. If something is confusing, that's useful information for us, not a reflection on you." Say it and mean it. It changes the whole dynamic.
Ask about the past, not the hypothetical
- "Tell me about the last time you did X."
- "What happened when you tried to Y?"
- "Walk me through what you did."
- "Would you ever use a feature like X?"
- "Do you think you'd want Y?"
- "How would you feel if Z?"
Hypothetical questions get hypothetical answers. People are notoriously bad at predicting their own behaviour. Past behaviour, on the other hand, is real data.
Follow the hesitations
The most valuable moments in an interview are the pauses, the "well... it depends," the slight frowns. These are signals. Don't rush past them. Slow down. Ask: "I noticed you paused there — what were you thinking?" or "You said 'sort of' — can you tell me more about what you meant?"
"The insight is never in the first answer. It's in what comes after the follow-up."
Embrace silence
Most interviewers talk too much. When a user finishes answering, resist the urge to respond immediately. Count to three in your head. The silence is often uncomfortable enough that the user will keep talking — and what they say next is usually more honest than their first answer.
After the interview
Write your notes within an hour while the memory is fresh. Focus on behaviours, quotes, and moments of confusion — not your interpretations. Save the analysis for when you have data from multiple sessions and can look for patterns across participants rather than treating any one person's experience as universal.
Good user research is a skill that improves with practice. But these principles — asking about the past, following hesitations, embracing silence — will make your very next interview more useful than your last.
