Make room for disagreement from the start
Rapport helps a participant feel comfortable describing what they actually do and think. It does not require the participant to like the interviewer’s idea. In a customer interview, that distinction matters: a warm conversation can still produce misleading findings if the interviewer’s enthusiasm makes agreement feel like the polite response.
Begin by explaining the participant’s role in simple terms. You might say that you are trying to understand their experience, that there are no right answers, and that it is useful to hear what did not work as well as what did. If you are showing a concept or product, clarify that the participant is not being tested. Then make the invitation credible through your behavior. A reassuring opening means little if you later defend every feature they question.
Show interest without signaling a preferred answer
Small conversational choices shape what people feel safe saying. Greet the participant, explain how the conversation will work, and give them time to finish a thought. Use brief acknowledgments such as “I see” or “Tell me more” to show you are listening. Try to respond with the same level of interest to praise, criticism and uncertainty. An excited “Exactly!” after a positive comment may tell the participant which answers earn approval.
Notice how your question frames the possible response. “How helpful was the new dashboard?” assumes it was helpful. “What, if anything, did you use the dashboard for?” leaves more possibilities open. Rather than asking whether someone would use a feature, ask them to describe the last time they faced the problem it is meant to solve. Past examples can reveal constraints that a friendly hypothetical answer might miss.
A prepared interview guide can help you keep wording reasonably consistent across conversations. It should not turn the discussion into a script that ignores the participant’s account. Ask an open question, listen, and follow up on the details they introduce rather than steering every answer back to the idea you hoped to validate.
Probe for detail, not confirmation
A useful follow-up helps you understand what an answer means. If someone says a checkout process was “fine,” ask what happened from the moment they decided to buy until they finished. If they say a feature seems confusing, ask which part gave them pause. Questions such as “Can you walk me through that?” and “What led you to do it that way?” invite a fuller account without supplying one for them.
Be especially careful with summaries. “So you’d use this every day?” can turn a tentative comment into a commitment. Instead, reflect the participant’s own words and check your understanding: “You said it might help when you have several orders to track. Is that the situation you mean?” Give them an easy way to correct you. A correction is valuable information, not a setback.
Silence can also help. After a participant answers, leave a moment before moving on. They may add a qualification or example. Avoid using the pause as pressure, however; if they seem finished, continue rather than repeatedly asking for more.
Keep warmth when the feedback is difficult
Participants may soften criticism if they think they are speaking to someone responsible for the thing being discussed. When they raise a problem, thank them for explaining it and ask what happened. Do not rush to clarify the intended design or suggest that they missed something obvious. The interview is a chance to learn how the experience appeared to them, even if you know why it was built that way.
You can also make space for mixed or uncertain answers. “What worked, and what got in your way?” allows both sides of an experience. If a participant says they cannot remember, do not push them toward a plausible story. Ask whether another specific occasion comes to mind, then move on if it does not. Respecting that limit supports rapport and keeps guesses from being mistaken for observations.
Review the interview for signs of influence
Afterward, separate what the participant said from your interpretation of it. In your notes, capture their examples and qualifications, not just labels such as “liked it” or “confused.” Mark places where you explained a concept before asking about it, offered answer choices too soon, or reacted more strongly to one kind of response. Those moments do not make the entire interview useless, but they deserve caution when you interpret the findings.
Across interviews, look for patterns without treating politeness as proof of demand. Compare favorable comments with the situations participants described and the actions they said they took. The aim of rapport is to make an honest account easier to give. When participants can disagree, hesitate and correct the interviewer without friction, the conversation becomes more useful for deciding what to investigate or improve next.
