Week 18 Guide: Formal User Testing

24-week programme, Project 2 Phase. A more rigorous version of the Week 7 testing skills.

Learning goal: run a structured usability test with a clear protocol and success measures, across both stakeholders, and write it up as a usability report.
Estimated study time: 3 hours.
Evidence to upload: your test protocol, your observation notes, and a completed usability report.

The Real Problem This Solves

Informal testing catches obvious problems. Formal testing gives evidence you can defend: a consistent protocol, defined tasks, and measures such as time taken and task success. For Project 2 you test both stakeholders the same way, so results are comparable.

Running projects. Test your Week 17 high-fidelity prototype with both Project 2 stakeholders. Use the Feedback Form Template per tester and the Usability Report Template to write up.

Key Ideas You Need First

1. A protocol makes results comparable

Write the tasks, the wording, and the measures once, and use them with every tester. Same protocol, comparable results.

2. Measure, do not just watch

Add simple measures: did they complete the task, how long did it take, how many errors. Numbers reveal patterns across users.

3. Same test for both stakeholders

Run the identical protocol with each stakeholder group so you can compare how the design serves both.

Consent And Ethics

Take consent as in Week 7: explain you are testing the design not the person, take notes without names, ask before recording, and allow them to stop. Test respectfully.

Step-By-Step Walkthrough

Write the protocol: two or three tasks, exact wording, and your measures (success, time, errors).
Recruit testers from both stakeholder groups.
Run each test the same way, observing in silence and recording measures.
Ask open follow-ups after each task.
Write the usability report: results per task, patterns, and prioritised recommendations.

Demonstrated Example

Task: "Reset the desk from your setup to your housemate's, ready for them to start."

Measures across four testers: success 4 of 4; average time 38 seconds; errors: two testers left one tool in the other half.

Pattern: the reset works, but the boundary between halves is not obvious, causing the stray-tool errors.

Recommendation: mark the centre line more clearly. High impact, low effort.

Why this is strong: the same protocol was used with both groups, measures reveal a pattern, and the recommendation is prioritised.

Architecture and spatial track version. Give both session groups the same walkthrough scenario with the model, measure setup time and any confusion, and report comparable results for each use.

Submission Checklist

Upload item	Pass standard
Test protocol	Tasks, wording, and measures, used with every tester.
Observation notes	Behaviour and measures from both stakeholder groups.
Usability report	Results, patterns, and prioritised recommendations.

Assessment And Pass Criteria

A consistent protocol was used with all testers.
Simple measures were recorded, not just impressions.
Both stakeholder groups were tested and compared.
The report gives prioritised, evidence-based recommendations.

Common Mistakes

Changing the test each time. Keep the protocol fixed.
No measures. Add success, time, and errors.
Testing one group. Project 2 needs both.
Coaching the user. Observe, do not rescue.

Extension Challenge

Add a simple satisfaction rating after each task and see whether it matches the measured performance.

When To Ask For Tutor Help

Book a tutor check-in if your measures are unclear, or if you cannot recruit from one stakeholder group. Bring your protocol.

Back to course materials