From Research Findings to Design Insight
Design research often produces large volumes of material: interviews, observations, survey results, usability findings, behavioural signals, and contextual evidence. The value of this material does not come from the volume of data itself, but from the quality of interpretation applied to it.
Without a deliberate analytical process, research outputs can remain descriptive. They may show what happened, but fail to explain what matters, why it matters, or how it should inform design decisions. The role of research is not only to collect evidence, but to support better judgement.
My approach follows a simple progression: what we saw, what that means, and why that is relevant. I use this not as a rigid framework, but as a way to make the movement from evidence to insight more explicit, transparent, and useful for decision-making.
What we saw
The first step is to establish a clear view of the evidence. This means identifying what appeared in the research material before moving too quickly into explanation or solution.
At this stage, the focus is on participant behaviour, statements, reactions, task performance, recurring patterns, contradictions, and contextual conditions. The purpose is to separate observation from assumption. Good analysis begins by making the evidence visible and recognisable to others.
This step is important because teams often jump from isolated observations to premature conclusions. A disciplined view of what was actually seen creates a stronger foundation for interpretation.
What that means
The second step is interpretation. Once the evidence is clear, the task is to understand what the patterns may suggest.
This involves looking across the material, identifying relationships, and considering possible explanations. Interpretation should remain provisional. A pattern may point to issues of trust, cognitive effort, perceived risk, motivation, accessibility, confidence, expectation, or organisational context. The strength of an interpretation depends on how well it is supported across the research material.
This step is where research begins to move beyond description. The objective is not to report findings as isolated facts, but to understand the underlying dynamics shaping behaviour and experience.
Why that is relevant
The third step is to connect interpretation to design relevance. Not every observation has the same weight. Not every pattern should become a design priority.
Relevance is established by asking what the pattern affects: user confidence, completion, adoption, engagement, trust, accessibility, operational efficiency, product performance, or strategic direction. This is where research becomes useful for decision-making.
An insight becomes meaningful when it clarifies why a pattern matters and what risk or opportunity it reveals. At this point, the work moves from identifying research findings to articulating design insight.
From insight to tangible recommendations
Recommendations are only useful when they are grounded in a clear understanding of the insight. Otherwise, they risk becoming generic, reactive, or disconnected from the actual evidence.
A strong recommendation should make the design implication tangible. It should clarify what needs to change, what decision it supports, what behaviour or experience it aims to influence, and how it can be tested. The recommendation should be specific enough to guide action, but open enough to be prototyped, challenged, and refined.
This is where research becomes operational. Evidence informs interpretation. Interpretation clarifies relevance. Relevance shapes the recommendation. The recommendation then becomes a practical direction for design, product, and organisational decision-making.
Reflection on the approach
The distinction between observation, interpretation, and implication is common in human-centred design and applied research practice. What matters is not the terminology, but the discipline of making the reasoning explicit.
This approach helps teams avoid treating research as either raw evidence or immediate solutioning. It creates space for structured judgement. It also makes the analytical process easier to discuss with multidisciplinary teams, because assumptions can be questioned before decisions are made.
In practice, this improves the quality of design conversations. Teams are not only reacting to findings or debating solutions. They are discussing the logic that connects evidence, insight, and action.
Design research does not automatically produce insight. Insight is constructed through interpretation.
By moving deliberately from what we saw, to what that means, and then to why that is relevant, research becomes more useful for design decision-making. It creates a clearer bridge between empirical material and tangible recommendations, while keeping the work open to testing, refinement, and learning.
References
International Organization for Standardization. ISO 9241-210: Human-centred design for interactive systems.
https://www.iso.org/standard/77520.html
Nielsen Norman Group. UX Research Methods Overview.
https://www.nngroup.com/articles/ux-research-cheat-sheet/
IDEO. Human-Centered Design Toolkit.
https://www.ideo.com/tools/design-thinking
