A task with
a clear purpose.
Usability work begins with the task and the question behind it. The team may need to understand whether a person can find a function, interpret a label or complete a sequence without help.
We define a realistic starting point and an observable finish. Tasks should invite the person to use the product, rather than quietly telling them which control to choose.
Make the prototype
ready for the question.
The product does not have to be finished, but the relevant path needs to be testable. We review the prototype, known gaps and any account or environment requirements before sessions begin.
Where the prototype cannot behave like the intended product, that limitation is recorded and considered during interpretation.
- Inputs
- Product or prototype access, priority tasks, known constraints and the team’s existing questions.
- Preparation
- A session plan, task guide and agreed participant criteria.
- During sessions
- Observed attempts, follow-up questions and notes that distinguish behaviour from interpretation.
- Handover
- Issues or themes with supporting observations, followed by a discussion with the team.
Notice the attempt,
not only the answer.
A completed task can still contain hesitation, workarounds or a misunderstanding. An incomplete task may have several causes. We pay attention to the sequence and the person’s explanation rather than reducing the session to a single result.
Participants are not being examined. The work is a way to understand the product experience and the questions it raises.
Turn the observations
into design work.
We describe the issue, the conditions in which it appeared and the material supporting the interpretation. The team can then discuss potential changes and the questions a next iteration should test.
Prepare a usability brief