Generate a focused UX challenge or build a problem statement from your research.
Investigate the experience of people with low vision identifying products in an unfamiliar supermarket.
It describes an evidenced human difficulty and its impact, giving the team direction without deciding the solution too early.
Who specifically experiences it?
When and where does it occur?
What did you observe or measure?
Why does the problem matter?
Which constraints define the work?
Does it leave room for many solutions?
All examples below are fictional teaching illustrations. Research findings and numbers are invented; never reuse them as evidence.
WeakUsers need a better banking app.
StrongerFirst-time mobile banking customers abandon identity verification when document requirements appear without preparation or explanation. In five usability sessions, four participants paused or left, delaying activation and increasing support requests.
Why it worksSpecific user, context, evidence and impact; no feature is prescribed.
A broad opportunity to investigate before research.
An evidenced user problem, context and impact.
A user, need and insight framed for ideation.
An open question based on a validated problem.
A situation, motivation and desired outcome.
A proposed response after the problem is understood.
Separate what you know from what you believe.
Turn risky assumptions into research questions.
Record behaviour, context, frequency and consequences.
Replace generic claims with repeated evidence.
Choose observable outcomes before features.
Show how evidence shaped the direction.
Yes, as a clearly labelled practice project. Never claim hypothetical details came from research.
Usually no. Describe the user, context, evidence and impact so several solutions remain possible.
Often two to four sentences. Clarity and evidence matter more than a strict word count.
Write an assumption, plan discovery and update the statement when evidence is available.