Insight Statements: Frame Problems, Not Solutions
Insight statements frame what users must achieve, not how. Teams use them in design thinking's define stage to align on the right problem before ideating. The footgun is writing solutions like 'needs a dashboard' instead of goals like 'needs to compare'.
Insight statements frame what users must achieve, not how to build it. In design thinking's define stage, these three-part sentences align cross-functional teams on the real problem before anyone sketches a solution. The format is simple: a specific user needs something in order to reach a goal. The footgun is letting nouns sneak in. Teams write 'Alieda needs a dashboard' when they should write 'Alieda needs to digest varied information in one place.' Locking onto features before validating the underlying need guarantees suboptimal designs.
Read the original → nngroup.com
- #ux-research
- #design-thinking
- #product-strategy
- #problem-framing
- #user-needs
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.