What it is
A short, structured statement that names the user, their need or struggle, the context, and the desired outcome, without prescribing a solution. It becomes the shared reference the team returns to when scope drifts.
When to use it
At the very start of a project or feature, and whenever the team is arguing about solutions before agreeing on the problem. Anchors the Initiate framing work and feeds Synthesize.
Why (value)
Prevents solving the wrong problem. A good problem statement aligns stakeholders, sets guardrails for ideation, and gives you something to measure success against.
How to run it
- Gather what you know about the user, their goal, and the obstacle.
- Draft a one- or two-sentence statement: who, needs to, but, because.
- Strip out any implied solution language.
- Pressure-test it with stakeholders and revise until there is genuine agreement.
- Keep it visible and revisit it as evidence accumulates.
Inputs and outputs
- Inputs: Initial context, stakeholder input, any early research or assumptions.
- Outputs: A concise, solution-agnostic problem statement the team commits to.
Time and effort
Low. An hour to a workshop session; the hard part is agreement, not writing.
Evidence and limitations
This is a framing artifact, not evidence. It is only as sound as the assumptions behind it, so mark unvalidated claims as assumptions to test rather than facts. See Evidence and limitations.
Tips and pitfalls
- Do not embed a solution in the statement.
- Avoid vague nouns like “users” without specifying which.
- Revisit it, a stale problem statement quietly misdirects the whole project.
Variations
Point-of-view statements (d.school), “How might we” reframes, and problem framing canvases.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Jobs-to-be-done framing — Frame what people are trying to accomplish, and why, rather than what features they ask for.
- Design briefs — A one-page contract that aligns everyone on goals, scope, constraints, and success before design starts.
- How-might-we framing — Reframe a problem as an open, optimistic question that invites many solutions.
