Skip to content
Cumulative
All resources

Usability · Guide and template

Observe someone using a design

Prepare a task-based usability session and capture what happened without jumping straight to solutions.

Go to the template

Before you start

You have a prototype or existing journey and want to understand where people get stuck.

You’ll have: A session guide and observation notes that connect a difficulty to the task and its impact.

How to use it

  1. 1. Choose a task with a real purpose

    Describe the situation and what the person wants to achieve. Avoid naming the button or path you want them to use. Check that the prototype can support the task and use fictional information where possible.

  2. 2. Make room to observe

    Explain that you are learning about the design, obtain informed consent and make stopping easy. Ask the participant to try the task in their own way. Give neutral prompts and note any help you provide.

  3. 3. Separate observation from interpretation

    Record what happened, the effect on completing the task and your interpretation in separate fields. Review findings across sessions, including what differed. Choose an improvement to test again.

An example

Illustrative task: “You can no longer attend your appointment. Find out how to change it.” This leaves the route open, rather than instructing someone to click “Manage booking”.

Keep in mind: A small set of sessions can reveal problems, but does not establish how common they are across all users. Include people with relevant access needs and report who was not represented.

Use the template

Copy it into your own document or download the Markdown file. Fill it in with your team, using the guide above. No account or email is required.

Download .md

Preview the blank template
# Usability session guide and notes

## Setup
- Research question:
- Participant reference (avoid names in shared notes):
- Relevant experience and access needs:
- Device, browser or assistive technology:
- Version of the design:
- Consent confirmed and recording choice:

## Task (repeat for each task)
- Situation:
- Goal in the participant's language:
- What the prototype supports:
- What would count as completion:

## Observation log
- What happened:
- Task outcome: completed / partly completed / not completed
- Assistance provided:
- Effect on the participant:
- Interpretation (keep separate from observation):
- Follow-up question:

## Across sessions
- Repeated difficulties and differing experiences:
- Evidence references:
- What remains uncertain:
- Change to explore:
- How and with whom we will check it:

---
Cumulative · Observe someone using a design
Guide: https://cumulative.com.au/resources/usability-session

A small set of sessions can reveal problems, but does not establish how common they are across all users. Include people with relevant access needs and report who was not represented.