Problem Statements: The North Star of Design
If you don't define the problem correctly, you will design an excellent solution for the wrong issue. A problem statement is the synthesized translation of your user research into a single, actionable challenge that the team must solve.
The Structure of a Perfect Problem Statement
In the UX industry, we often use the "Point of View" (POV) framework. It consists of three parts: The User, The Need, and The Insight.
[User Name/Persona] needs a way to [User's Need] because [Surprising Insight from Research].
Example from the Real World
Bad Statement: "We need to build a food delivery app." (This is a solution, not a problem).
Good Statement: "Sarah, a busy single mother, needs a way to confidently order healthy meals under 30 minutes because she feels guilty when feeding her kids fast food due to lack of time."
How Might We (HMW) Questions
Once you have a problem statement, you can translate it into "How Might We" questions to spark ideation. Taking the example above:
- "How might we reduce the guilt Sarah feels about quick dinners?"
- "How might we make healthy meal selection as fast as ordering a pizza?"
The 5 Ws Frame
Before finalizing your statement, check it against the 5 Ws: Who is experiencing the problem? What is the problem? Where does it occur? When does it happen? Why does it matter? If your statement can't answer these, it needs refinement.