A prototype review can turn into a demonstration before anyone notices. The designer explains the mechanism, points to the control and rescues the first awkward moment. By the end, everyone has seen the product work. The team still does not know whether someone could use it without that help.
Give the test a narrower job. Find out where a person gets stuck, what they expected, and what the next model needs to change. The example below is a proposed exercise for a simple handheld object, not a report of a BDWY client test.
Write the task before the invitation
Imagine testing a storage case with a new latch. The task might be: put this object in the case, close it, then take it out again. Avoid naming the latch or showing the opening gesture before the attempt.
GOV.UK's guidance on moderated usability testing recommends realistic tasks that do not reveal the answer, with actual or likely users. That guidance addresses services. The same task-writing principle is useful when planning an early handling study for a physical object.
Keep a record that another person can read
Give the prototype a revision name and photograph its starting state. Record any loose parts, unfinished surfaces or substitute materials that could affect the task. A lightweight shell may be useful for reach, but it cannot settle a question about handling the full product's weight.
Use one line for each event. For example: "P02 pulled the lid twice, then turned the case over." Put your interpretation on a separate line: "The opening cue may be hard to find." The first line is something you observed. The second needs further evidence.
Mark every intervention
Decide in advance when to stop an attempt and when to help. If you point, explain or hold a part, note what you did and when. A completed task after that intervention belongs in the notes as an assisted attempt.
After the attempt, ask what the person expected at the point where they paused. Do not offer a new shape or explain your preferred fix while asking for feedback. The next design review can consider solutions with the observation still intact.
Choose a change you can check
Suppose several participants search the underside of the case before finding the opening. The next model could make the opening cue easier to see. Keep the other features stable where practical, then repeat the task and compare the observations.
A handful of sessions can reveal issues worth investigating. It does not establish a population-wide success rate. Keep the number of attempts, the context and the model's limits alongside any conclusion. A handling study also does not prove strength, durability or product safety.
A compact test note
Prototype revision: [file and physical model ID].
Question: [what this round should resolve].
Task: [goal stated without a hint].
Participant context: [relevant experience, without unnecessary personal details].
Observed action: [what happened].
Help given: [what and when, or none].
Interpretation: [possible explanation].
Next check: [change or question to test].
Keep this note with the model photographs. It gives the next build a reason to exist and makes the review useful to someone who was not in the room.
BDWY Studios
Start a project Back to the journal