Room 01 · 25 min
Start with the problem
UXTurn an intuition into an observable problem before drawing a solution.
01Understand
The mental model
UX starts by understanding a situation, not by opening a design tool. We observe what a person is trying to do, what blocks them and where it happens. A hypothesis is a proposal to test, never evidence by itself.
Precise anchors
- Observation
- A fact described without interpretation: action, context, words or visible result.
- Need
- The progress a person is trying to make, beyond the feature they request.
- Hypothesis
- A provisional explanation or solution that can be confirmed or falsified.
- Success criterion
- An observable signal that shows whether the problem is improving.
02Produce
Optional: explain in your own words
Use your own words and connect ideas through cause or consequence. A good sentence lets another person check what you understood.
Observable rubric
- Facts are separated from interpretations.
- The brief can be used without another meeting.
- The criterion measures a change in use, not only a technical delivery.
Your production is saved as a notebook entry. It is not automatically graded; compare it with the criteria and the example.
Optional: record a decision
Compare with a strong example
Audience: beginner learner on mobile in the evening. Fact: after two difficult cards, they leave without seeing the next one. Questions: What were you trying to do? What made you hesitate? How did you know what to do next? Hypothesis: no visible difficulty or next-step cue increases abandonment. Non-goal: redesign the entire spaced-repetition system. Success: in a test, the person finds the next card without help and explains the session status.
03Verify
These checks verify your choices. Written explanations and projects still need a review or an execution test.