8 follow-up question techniques for user interviews

The point of follow-up questions is to bring a participant's general opinion back to one specific thing that happened, then understand how it unfolded, why, and how they felt. The interview guide decides what you ask; follow-up decides how deep you go. The 8 techniques below cover the situations you'll run into most: answers that are too vague, conclusions without reasons, statements that contradict each other, and participants who stop after one sentence. Each comes with a line you can use as-is and a short example, so you can put it to work in your next interview.

When to ask follow-up questions

Not every answer needs a follow-up. When you see the signals below, stop and ask one more question. That's usually where you learn the most.

• The participant uses generalizations like "usually", "often", or "everyone".
• The participant gives a judgment, such as "it's kind of a hassle" or "it's not bad", without saying what specifically.
• The participant's tone, expression, or wording suddenly changes.
• What the participant says doesn't match what they said earlier, or the behavior data you already have.
• The participant mentions an approach, tool, or person you didn't expect.

8 follow-up question techniques

1. Ask about the last specific time

People are often inaccurate when they generalize about their own habits, but their memory of the most recent specific instance is much more reliable. When you hear a generalization, bring the conversation back to the last time it happened.

• Phrasing: When was the last time that happened?
• Example: The participant said "I usually buy groceries on the weekend." Follow-up revealed that last week they actually bought them on Wednesday on the way home from work, because they had to work over the weekend.

2. Ask for the timeline

Having the participant walk through events in order fills in steps they didn't notice themselves and shows where they got stuck.

• Phrasing: Starting from when you first thought about doing this, what happened next, step by step?
• Example: Asked about the expense reimbursement process, the participant mentioned only when walking through it step by step that they first check with finance in a group chat before submitting, because the form version changes often.

3. Play it back

Restate what the participant said in your own words and ask them to correct you. This avoids misunderstandings and often prompts a more accurate version. Don't add your own interpretation when you play it back.

• Phrasing: So what I'm hearing is ... Is that right? Did I miss anything?
• Example: The researcher played back "So you didn't renew because it was too expensive," and the participant corrected them: "It wasn't the price. I barely used it that month."

4. Ask for a comparison

It's hard to describe one thing on its own, but put it next to something else and the differences become concrete. Compare with how they used to do it, or with another product.

• Phrasing: Compared with what you used before, what was different this time?
• Example: The participant said the new tool was "a bit easier to use". Only when asked to compare did they explain it was because they no longer had to log in again every time.

5. Ask what's behind the emotion

Where participants show emotion is usually where they really care. Don't just note "he was angry"; ask what made him feel that way.

• Phrasing: You said it was a bit annoying. What was the exact moment that annoyed you?
• Example: The participant said the refund "made me furious". Follow-up revealed the problem wasn't a slow refund; it was customer service making them explain the same situation three times.

6. Use silence and wait

When the participant finishes a sentence, don't jump to the next question. Wait quietly for three to five seconds. Many people will add something on their own, and what they add is often more honest than what they said first. While you wait, nod or keep eye contact to show you're still listening.

• Phrasing: Hmm... (pause, say nothing, and wait for them to continue)
• Example: The participant said "It's just okay." The researcher didn't respond, and a few seconds later the participant added, "Actually, I almost stopped using it last month."

7. Ask about exceptions

Participants tend to describe the usual case. Exceptions often hide unmet needs, or can overturn your early conclusions.

• Phrasing: Was there ever a time it wasn't like this? What happened then?
• Example: The participant said they always order on their phone. Asking about exceptions revealed that for large orders they always switch to a computer, because they need to check the invoice details.

8. Ask "what if" to find the limits

Hypothetical questions can't predict behavior, but they can help you find limits: how far a condition has to change before the participant does things differently. Always bring it back to reality afterward by asking whether they've been in a similar situation before.

• Phrasing: If this step took ten more minutes, would you still do it this way? Has anything like that happened before?
• Example: The participant said they don't mind waiting a bit longer, but when asked about past experience admitted that they usually leave if they have to wait in line more than five minutes.

Example: a chain of follow-up questions

This exchange uses two techniques in turn: asking about the last specific time and asking what's behind the emotion. The first answer was "usually with an app". Without follow-up, this person would be recorded as someone who tracks spending as a habit. After three follow-ups, the real picture emerges: they log expenses only occasionally, and the categorization step is the main reason they give up.

Go at most three levels deep on any one answer. Beyond that, participants start to feel interrogated. After one round, switch to a lighter topic and circle back later.