Module 01
Users, tasks and context: the three things you must know
Write a context-of-use statement, and spot the conditions your design is quietly assuming.
Not filmed yet
The transcript beside this is the full lesson — read it now, or come back when the video lands.
Check yourself · 6 questions · pass at 70%
- 01
'Nurses need to record patient vitals.' What's missing from this as a basis for design?
- 02
Why is designing in ideal conditions a specific hazard?
- 03
Which is a properly formed context-of-use statement?
- 04
Why is emotional state part of context?
- 05
Why is your stakeholder's mental model often as unrepresentative as your own?
- 06
You write one context-of-use statement that covers every user group. What does this suggest?
Revision · 8 cards
These come back on a schedule, spaced to catch you just before you’d forget.
The three things you must know before designing
User (who), task (what they're doing), context (under what conditions).
Context-of-use statement template
A [user] needs to [task] while [context], so the design must [implication].
Which of the three is most often skipped?
Context — and it usually carries the surprises.
The ideal-conditions trap
You design with a big screen, fast connection and full attention, then ship into conditions with none of it.
Eight dimensions of context
Device, connection, attention, posture, interruptions, environment, expertise, emotional state.
Test for a good implication clause
It must be falsifiable. 'Operable one-handed' passes; 'simple and intuitive' is a mood.
Why isn't your stakeholder the user either?
Years of familiarity means they can't see it fresh — an unrepresentative model, held by a decision-maker.
How many context-of-use statements per product?
One per user group. If one sentence covers everyone, it's too general to constrain anything.
Signifier