Start with a clear purpose, not a rigid script
Silence, vague answers, and tangents can feel like obstacles when you are trying to complete an interview guide. They can also tell you something useful: a question may be hard to understand, a participant may need time to recall an experience, or your topic may connect to a concern you had not anticipated. The aim is not to eliminate every awkward moment. It is to learn from it while giving the participant room to describe their own experience.
Before the interview, identify the few things you need to understand, such as how someone chose a product, what made a task difficult, or what they did when a service failed. Prepare open questions about specific experiences and a few neutral follow-ups. Treat the guide as a map rather than a list that must be read in order. This makes it easier to decide when to wait, probe, or redirect.
Give silence a little space
After asking a question, resist the urge to fill the first pause. Participants may be remembering details, deciding what matters, or finding words for something they rarely discuss. If you immediately rephrase the question or offer possible answers, you may interrupt that process and shape the response.
A comfortable pause does not need to be indefinite. Keep your attention on the participant and allow them a moment to continue. If they seem stuck, check whether the question made sense, then ask it in simpler language. You can also narrow it to a recent occasion: ask them to think of the last time they encountered the situation and what happened first. This provides a starting point without suggesting what their answer should be.
Silence can have different meanings, so avoid treating it as evidence of a particular feeling. A participant might be uncertain, distracted, or uncomfortable with the topic. If a question seems too personal, make it easy to skip. Respecting that choice is more important than obtaining a complete answer.
Turn vague answers into concrete accounts
Responses such as easy, expensive, or I usually compare options can be useful signposts, but they leave important details unclear. Rather than asking whether the participant agrees with your interpretation, invite an example. Ask what they were trying to do, which options they considered, what they noticed, and what they did next. A sequence of actions often reveals more than an opinion stated in isolation.
Listen for words that need definition in the participant's own terms. If someone says a process was confusing, ask which part they mean and what they expected to happen. If they say a purchase was worth it, ask what made it feel worthwhile. Follow-ups should seek detail, not defend a product or test a theory. Questions that imply an answer can produce apparent clarity while hiding the participant's actual view.
Not every broad answer needs prolonged probing. If the participant has no relevant example, acknowledge that and move on. Record the distinction between what they experienced directly and what they believe they might do. Both can be interesting, but they answer different research questions.
Explore tangents before deciding to redirect
An off-topic story may contain context that explains a decision. Someone discussing a delivery problem during an interview about checkout, for example, may be explaining why they hesitate to order at all. Listen long enough to understand the connection, then decide whether it serves the research purpose.
When a tangent is relevant, follow it briefly with a question about how it affected the participant's actions. When it is not, acknowledge the point and return to a specific earlier moment or unanswered question. A respectful transition can be simple: note that you want to return to how they made the choice, then ask what happened next. Avoid cutting people off so abruptly that they feel their account was unwelcome.
Time limits help with this judgment. Reserve enough time for the core topics, and note interesting side issues that you cannot explore fully. Those notes may help you refine a later interview guide, but one unexpected tangent is not, by itself, proof that an issue is common across customers.
Use your notes to improve the next interview
After each conversation, review where the discussion slowed down or drifted. Did a question ask for an abstract judgment when a concrete example would have worked better? Did several participants interpret a term differently? Did your follow-up introduce an assumption? These observations can help you revise the guide without rewriting it around a single unusual interview.
In your notes, separate participant accounts from your interpretations. Capture the situation, actions, and stated reasons as accurately as you can, then label any inference you make. Across interviews, look for recurring patterns as well as meaningful differences. A good interview is not one in which every answer arrives quickly and neatly. It is one in which you respond thoughtfully enough to learn what the participant means.
