Define — frame the right problem
Synthesize your research into a single, sharp problem statement before solving.
Why it works
The way a problem is framed determines the solution space you can even see. A vague brief ("improve the app") keeps every option open and therefore useless; a point-of-view statement ("busy parents need a faster way to X because Y") narrows attention to a solvable target. Reframing is the lever — most bad solutions are answers to the wrong question.
How to do it
- Cluster your observations into themes and pick the user need that recurs.
- Write a point-of-view statement: [user] needs [need] because [surprising insight].
- Turn it into a "How might we…" question that is neither too broad nor too narrow.
Evidence
Mechanistic. Problem-framing research shows the initial framing strongly constrains the solutions considered; experts spend disproportionate time defining the problem before solving it. (mechanistic)
The specific "How might we" phrasing is practitioner convention; the underlying point is that framing shapes the answer.
Common mistake
Writing the problem statement with the solution already baked in ("users need our new button"), which forecloses the divergent thinking the next stage depends on.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Design Thinking, Step by Step
- Empathize — understand the user first
Observe and interview the people you are designing for before forming any solution.
- Ideate — generate options before judging
Produce many candidate solutions, deferring evaluation until you have quantity.
- Prototype — make it cheap and real
Build the roughest possible version that lets you learn something specific.
- Test — let users break it
Put the prototype in front of real users and treat their confusion as data.
- Iterate — treat the stages as a loop, not a line
Cycle back to earlier stages as testing reveals you framed the wrong problem.