Insight Wall: Synthesize Mixed Research Data

WHY IT EXISTS: User research produces fragments of understanding from many channels, yet those fragments do not become design decisions on their own. The source emphasizes that user interviews alone will not magically create successful design; it is what you do with the insights that matters. When teams collect qualitative interview data alongside quantitative information and input from stakeholders, the connections between them often stay buried in separate documents. The insight wall exists to bring together all of this mixed data so that patterns become visible and can be transformed into meaningful decisions.

THE MENTAL MODEL: Treat the insight wall as a single canvas where isolated data points are forced into proximity. A quote from one user subgroup might seem minor on its own, but when placed next to behavioural data from another source, it reveals a shared need or goal. The wall is not a storage shelf; it is a thinking tool. Its purpose is to turn scattered findings about user needs, goals, behaviours, and attitudes into a coherent picture that the whole team can act on.

HOW IT WORKS: You gather outputs from every relevant source, not only user interviews, and place them into one shared view. The data stays in its mixed formats, qualitative notes living alongside quantitative findings. The team then looks across the collection for recurring themes, contradictions, or gaps related to user needs and behaviours. The goal is to interrogate the combined body of evidence and ask what the mix of sources reveals that no single source could. This synthesis step becomes the bridge between raw data and concrete design decisions.

WHEN TO USE IT: Use an insight wall when you have data from multiple sources and formats and need to align stakeholders around what matters most. It is especially valuable after discovery work that included interviews with diverse subgroups, because it prevents variables and perspectives from staying siloed in separate files. Deploy it when stakeholders need to understand the reasoning behind design proposals, since their attendance at interviews and participation in the discussion guide creation means they are already invested in the findings.

WHEN NOT TO USE IT: Skip the wall when your data set is small or comes from only one source. If you have conducted a handful of similar interviews with no quantitative or stakeholder input to compare against, a full wall may be overkill. Also avoid it if the team is unwilling to do the analysis work together. Collecting data without synthesis creates a false sense of progress; the source warns that conducting interviews is not the finish line, and a wall covered in unclustered data is no better than a stack of unread transcripts.

ONE CANONICAL EXAMPLE: A product team interviews users from multiple subgroups and discovers scattered complaints about a workflow. They also have quantitative metrics and stakeholder concerns raised during the discussion guide phase. Viewed separately, each source suggests a minor tweak. Placed together on an insight wall, the mixed data clusters around a single theme: users struggle with the sequence of steps. The team now has a unified insight that drives a redesign of the workflow rather than disconnected fixes, turning raw observations into an evidence-based decision that increases organisational UX maturity.