How do you mitigate confirmation bias when a user validates your solution?

WHAT THIS TESTS: This question evaluates whether you can recognize confirmation bias in real time when you have invested months in a design, and apply methodological safeguards during both data collection and synthesis. Interviewers want to see that you understand a single confirming anecdote is not proof, and that you have concrete tactics to protect the integrity of qualitative findings when your own design ideas are at stake.

A GOOD ANSWER COVERS: A strong response separates in-the-moment tactics from post-session synthesis. In the interview, you should describe pivoting to disconfirming questions such as asking when the described workflow breaks down, what exceptions exist, or what workarounds the user employed in the past. You should also mention explicitly documenting the match as one data point rather than validation. For synthesis, a good answer includes triangulating this signal against contradictory evidence from other sessions, using a structured coding framework rather than memory, and inviting a neutral reviewer to audit your themes or attend synthesis sessions to challenge your interpretations.

COMMON WRONG ANSWERS: Red flags include treating the participant's description as definitive proof that the whiteboarded solution is correct, which is especially tempting if you have worked on the design for months. Another weak pattern is suggesting you would only ask follow-up questions that deepen the confirming narrative without probing for edge cases. Saying you would handle bias later in synthesis but do nothing in the moment is also insufficient, because the interviewer specifically asked for both phases.

LIKELY FOLLOW-UPS: The interviewer may ask how you would react if the next three participants described completely different workflows, or how you would distinguish between a genuine user mental model and leading questions you accidentally asked. They might also probe whether you would share your whiteboard with the research team before synthesis, and how you would weigh a small sample of confirming evidence against business pressure to ship.

ONE CONCRETE EXAMPLE: Suppose you whiteboarded a one-click reorder feature and a participant says they always reorder the same weekly grocery list. In the moment, you would ask when they last chose not to reorder, whether they ever modify quantities mid-flow, and how they handle out-of-stock items. During synthesis, you would tag this as supports one-click reorder but also tag the exceptions as friction points, then compare against participants who abandoned repeat purchases. You would ask a peer researcher to review your tag sheet to ensure you did not overweight the confirming story.

Source: nngroup.com