What a user need statement actually is
You have a whiteboard, a timer, and a team ready to brainstorm.
Someone asks the question that stalls the session: do we actually know what problem we are solving?
Writing a user need statement first feels like a delay, but skipping it can send the whole session toward solutions nobody needs.
This article covers when a user need statement earns its place before ideation, when a lighter version is enough, and how to write one you can use.
A user need statement is a short, actionable problem statement that summarizes who a specific user is, what that user needs, and why the need matters to them.
It is also called a problem statement or a point-of-view statement, and it is the primary tool of the define stage in design thinking.
According to the Nielsen Norman Group, define what you want to solve before generating solutions, because a great solution to the wrong problem will fail (source).
The classic three-part format looks like this:
- User: a specific person, not “users” in general.
- Need: phrased as a verb—a goal or end state, not a feature.
- Insight: why the need matters to that user.
The Nielsen Norman Group's example: "Alieda, a multitasking, tech-savvy mother of 2, needs to quickly and confidently compare options without leaving her comfort zone.
She wants this in order to spend more time doing the things that really matter."
A development statement for the same situation would read: “A user needs a comparison table in order to see different prices.”
The first describes a person and a goal; the second describes a generic user and a solution (source).
That noun-versus-verb distinction is the heart of the tool.
Users never need a dropdown; they need to see the choices available and select one.
The statement should capture what you want to achieve, not how (source).
Why the define stage comes before ideation
Design thinking is a user-centered process with six phases: empathize, define, ideate, prototype, test, and implement.