An insight statement converts a raw research observation into a precise, actionable claim about human behaviour, motivation, or need. It is one of the most important and most underestimated steps in the design process, because the quality of insights directly determines the quality of ideas that follow. A powerful insight does not merely describe what users do — it reveals why they do it in a way that reframes the problem and suggests new directions for design.
What It Is
An insight statement is typically a single sentence that articulates a tension, a contradiction, a latent need, or a surprising truth revealed by research. A strong insight has three qualities: it is grounded in specific research evidence, it reveals something non-obvious about the user's experience, and it opens up a productive design space rather than closing down options. Insights are different from observations, which describe behaviour, and from solutions, which prescribe responses. They exist in the space between: they explain what is really going on.
How to Run It
After completing research synthesis, review your clusters of observations and ask of each one: why is this happening? What does this tell us about the user's underlying need, belief, or motivation? Write candidate insight statements and test them against the evidence. A useful format is: '[User] needs [need] because [insight about underlying motivation or tension].' Generate multiple candidate insights from each data cluster and select those that are most surprising, most actionable, and most specific to your user population. Present insights to the team and stakeholders as the foundation for the ideation phase.
When to Use It
Insight statements are written during the synthesis and framing phase, after research analysis is complete and before ideation begins. They serve as the creative brief for ideation and ensure that the solutions the team generates are genuinely responsive to real human needs. They are also useful for communicating research value to stakeholders: a well-crafted insight statement can shift a stakeholder's perspective more effectively than pages of data, because it offers interpretation rather than mere information.
Tips for Success
Avoid writing insights that are too vague to act on, such as 'users want things to be simpler.' Good insights are specific, surprising, and falsifiable. They should make the team feel like they have learned something genuinely new about their users. Test each insight by asking: could this apply to any product in any domain? If so, it is probably too generic. The best insights feel specific to your users and your context in a way that makes them immediately generative for the design challenge you are trying to solve.
