What are probing questions?

Also called: Probes, Follow-up questions

Probing questions are follow-ups an interviewer asks in response to what a participant just said, to get the detail, reasons, examples or clarification the first answer left out, without introducing a new topic or suggesting an answer.

Updated

Eight types of probe

  • Elaboration: "Tell me more about that."
  • Example: "Can you walk me through the last time that happened?"
  • Clarification: "When you say the handoff is messy, what does that look like?"
  • Reason: "What made you choose the spreadsheet over the built-in report?"
  • Consequence: "What happened after that?" or "What did that cost your team?"
  • Comparison: "How does that compare with how you did it before?"
  • Echo: repeat their last few words with a rising tone, "Too many approvals?", and wait.
  • Silence: pause for a few seconds after an answer. Most people add the detail they held back.

Probing without leading

A good probe uses the participant's words and leaves the answer open. A leading probe adds your interpretation. Compare:

  • Leading: "So that was frustrating?" Neutral: "How was that for you?"
  • Leading: "Was it because the button was hidden?" Neutral: "What were you expecting to see?"
  • Leading: "Would a template have helped?" Neutral: "What would have made that easier?"

Probing in usability tests

In a usability test, probes are mostly about expectations and intent: "What are you looking for?", "What do you think will happen if you click that?", "Is that what you expected?" Keep probes short while the participant is working, and save "why" questions for after the task, so you don't interrupt the behaviour you came to watch.

Writing probes into a discussion guide

  • Write probe triggers instead of a script: "If they mention a workaround, ask how often they use it and what it costs them."
  • Give each core question two or three probes, and expect to improvise the rest.
  • Probe hardest on whatever relates to your research objective. Not every answer needs digging into.
  • For unmoderated or written studies, add follow-up prompts in the task text, such as "Please describe a specific time this happened."

Common mistakes

  • Asking "why" over and over. It can feel like an interrogation. Vary it: "What made you...", "What was going on at the time?"
  • Probing hypotheticals ("Would you pay for that?") instead of past behaviour.
  • Stacking two or three probes in one breath, so the participant answers only the last one.

Go deeper

Questions

How many probing questions should you ask per question?

There is no fixed number. Keep probing while each answer adds something new about your research objective, and move on when you hear repetition or generalities. Plan two or three per core question and expect to use fewer on some and more on others.

Is "why" a good probing question?

It works, but used repeatedly it sounds judgemental and pushes people to invent tidy reasons. "What made you decide that?" or "What was happening at the time?" tend to get more concrete answers about what actually drove the decision.

Can you probe in a survey?

Partly. Add an optional open-text follow-up after key answers, for example "What's the main reason for your score?" shown after a rating. You can't adapt to what each person says, so keep the follow-up general and use interviews for depth.

Next step

Run the study, not just the method

Great Question handles recruiting from your own customers, scheduling, incentives, interviews, tests and analysis in one place.

Book a demo

No credit card required.

Related terms

Full glossary
  • Leading questions

    A leading question is worded in a way that suggests the answer the asker expects or wants, so participants drift toward that answer and you learn more about your own assumptions than about their experience.

  • Think-aloud protocol

    A think-aloud protocol is a usability research method where participants say what they are thinking, looking at and trying to do while they complete a task, so you hear the reasoning behind each action instead of guessing at it.

  • Critical incident technique

    The critical incident technique is a research method where participants describe specific past events that went especially well or badly, what led up to them and what happened next, so you learn from concrete behaviour instead of general opinions.