UX Foundations · Step 1 · 5 min read
Users, tasks and context
The three things every design decision depends on: who the users are, what they're trying to achieve, and where and how they do it. Goals versus tasks, the five parts of a context of use, and how to describe them on one page before you design anything.
"Is this a good design?" has no answer on its own. A good design for a nurse at 3 am on a ward is different from a good design for a student on a sofa, even when both are "booking an appointment". Every design decision depends on three things: who is using it, what they're trying to achieve, and the situation they're in. Write those down first, and half of the arguments about the design disappear.
What you'll be able to do after reading:
- Tell a user's goal from their tasks
- Describe a context of use with its five parts
- Write a one-page description of users, goals, tasks and context
- Use it to judge whether a design fits
1. Goals and tasks are different
The usability standard puts it precisely: a goal is an "intended outcome"; a task is a "set of activities undertaken in order to achieve a specific goal". And: "While goals are independent of the means used to achieve them, tasks describe particular means of achieving goals" (ISO 9241-11:2018).
| Goal (stays) | Tasks (depend on the design) |
|---|---|
| Get reimbursed for a work trip | Photograph receipts, fill in a form, wait for approval |
| Have dinner at home tonight | Find a recipe, buy ingredients, or order delivery |
| Know my blood test is fine | Log in to a portal, find the result, read the reference range |
Design changes the tasks; it should never lose sight of the goal. Sometimes the best design removes a task entirely.
2. The five parts of a context of use
Who they are, what they know, what they need.
Experience, language, disabilityThe outcome they want.
Get reimbursed for a tripThe steps they take to get there.
Photograph receipts, fill in a formTime, money, devices, help.
One phone, low batteryPhysical, social and technical setting.
Noisy, in a hurry, shared computerThe standard defines context of use as the "combination of users, goals and tasks, resources, and environment" (ISO 9241-11:2018). In practice:
- Users: who they are, what they already know, what they need (including disabilities, language, experience).
- Goals and tasks: what they're trying to achieve, and the steps they take today.
- Resources: time, money, devices, connection, help from other people.
- Environment: physical (noise, light, moving or still), social (alone, in front of a customer), technical (old laptop, shared computer).
3. Find out, don't guess
The fastest way to learn the context is to go where the work happens and watch. NN/g calls these field studies: research in the user's own environment rather than in your office (NN/g, Field Studies, Jan 2024). Even an hour of watching changes what you design. See Contextual inquiry for a structured way to do it.
When you can't visit, ask people to show you on a video call, share photos of their workspace, or walk you through yesterday.
4. A worked example: a delivery driver's app
| Part | Description |
|---|---|
| Users | Drivers, many new each month; varied languages; some with no smartphone experience beyond messaging |
| Goal | Finish the route on time and get paid without disputes |
| Tasks | Check the next stop, find the door, take a photo as proof, handle "customer not home" |
| Resources | One phone, often low battery; mobile data that drops in basements |
| Environment | In a van or on foot, gloves in winter, one hand busy with a parcel, sun on the screen |
What this tells the designer before any screen: large tap targets, one-handed use, high contrast, offline mode, and very few words.
5. Common mistakes
- Designing for "users" in general, as if everyone were the same.
- Confusing the task people do today with the goal they have.
- Assuming the context is the designer's own: a quiet desk, a big screen, fast Wi-Fi.
- Collecting context and never using it to judge the design.
6. Vocabulary
| Term | Meaning |
|---|---|
| User | A person who interacts with the product |
| Goal | The outcome a person wants, independent of how they get there |
| Task | The activities someone does to reach a goal, with a particular design |
| Context of use | Users, goals and tasks, resources and environment, together |
| Field study | Research done where people actually live or work |
7. Try it (no tools needed)
- Pick a product you use (a banking app, a ticket machine, a work tool).
- On one page, fill in the five parts for someone else who uses it, not for yourself.
- Underline the one line that would most change the design if you took it seriously.
Reflection questions: Where did you have to guess? Who could you ask, or watch, to replace that guess?
8. If you already practise
- Put the one-page context at the top of every design brief; refer to it in critiques ("does this work one-handed?").
- Separate goals from tasks in your requirements: it opens room for solutions that remove steps.
- Alan Cooper's goal-directed design is the classic treatment of this idea (About Face, 4th edition, Wiley, 2014).
Checklist
Learn more
- Standard: ISO 9241-11:2018, usability: definitions and concepts
- NN/g: Field Studies (Jan 2024)
Books, courses and videos to go deeper
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
What UX design is (and isn't) · The design process · Who does what on a product team · Contextual inquiry · Journey mapping and service blueprints