Walk me through your next steps after five user interviews

What's really being asked

This question checks whether you understand the difference between raw data collection and collaborative synthesis. Interviewers want to see that you know how to make qualitative data legible to a cross-functional team before imposing formal coding structures. The goal is to surface patterns, build shared understanding, and avoid premature convergence on a single interpretation.

A GOOD ANSWER COVERS four things in order. First, individual extraction: you break raw notes into discrete observations or direct quotes, each written on its own sticky note or digital card, so that every data point can be moved and regrouped. Second, silent or divergent generation: you do this without group discussion first to prevent dominant voices from shaping the dataset too early. Third, collaborative clustering: the team sorts the notes into emergent themes on a wall or digital whiteboard, looking for natural affinities rather than forcing categories. Fourth, prioritization and next steps: once clusters form, the team identifies which themes are most critical or frequent and decides what to design, research, or test next.

The mistakes people make

Jumping straight into a spreadsheet or qualitative coding software to tag every quote before the team has seen the full landscape. Working alone instead of bringing in designers, product managers, or engineers to spot patterns. Imposing a rigid coding framework from the start rather than letting themes emerge from the data. Summarizing each interview into a narrative report before extracting granular observations, which makes cross-interview pattern matching harder.

What usually comes next

The interviewer might ask how you would handle conflicting observations across interviews, how you decide when a cluster is large enough to be considered a valid theme, or how you adapt this process for remote teams. They may also ask how affinity diagramming connects to later formal coding or journey mapping.

A concrete example

After five usability interviews for a healthcare appointment app, you extract thirty discrete sticky notes. One note reads "Patient could not find the reschedule button under the hamburger menu." Another says "User expected reschedule to be on the appointment card itself." During clustering, four similar notes group together under an emergent theme labeled "Reschedule action is buried or mislocated." The team prioritizes this cluster because it appeared in four of five sessions and agrees to run a design sprint on the appointment-card interaction before moving to formal coding of the full transcript set.