Week 7 Worked Example: Testing Your Design
Test Script
Consent lines: "This is a rough prototype I am testing, not you. No wrong moves. Notes only, no name, stop any time."
Task 1: "You have just finished working. Show me how you would pack these tools away and carry them."
Task 2: "Now set yourself back up to start work again."
Observation Notes (two testers)
| Tester A | Tester B | |
|---|---|---|
| Packing away | Rolled easily, two end tools slid out | Rolled easily, one tool slid out |
| The tie | Fumbled, used two hands, about 20s | Managed but said "slow" |
| Setting up | Unrolled and started in about 10s | Fast, no problem |
| Exact words | "I expected it to just clip." | "The pockets are good, the tie is annoying." |
Write-Up
What worked: the roll and the deep pockets. Setup was fast and intuitive for both.
What failed: curling edges let end tools slide; the ribbon tie was slow and fiddly for both testers.
Top problems to fix, ranked
- Stop the end tools sliding (stiffer edge or fold-over flap).
- Replace the ribbon tie with a faster one-hand fastening (elastic loop or clip).
Why This Passes
- Real tasks were set, not a demo, and the learner stayed quiet and observed.
- Consent was taken and two testers were used, revealing a pattern.
- Behaviour and exact words were recorded, and failures were reported honestly.
Weak Versus Strong
Weak
"I showed two friends and they said it looks great." No tasks, no observation, only polite praise, nothing to fix.
Strong
Task-based tests, silent observation, a clear pattern across two users, and a ranked list of real problems to solve next.