Write a usability testing plan for an arts service
Plan a workshop-booking study through research questions, participants, realistic tasks, consent, logistics, observation, and analysis while keeping claims proportionate to the work actually performed.
Connect a product decision to observable tasks
A usability testing plan connects a product decision to observable tasks. For a workshop service, you might need to understand whether people can choose a suitable session and recognize a confirmed booking. Define those questions before scheduling sessions or preparing a long list of interface opinions you hope participants will validate.
Plan participants, consent, and observation
Describe the participant characteristics relevant to the task, the prototype or service being examined, and the planned session format. Prepare informed-consent information and a privacy-conscious recording approach. Include access requirements and a practice run. Decide how observations will be captured and reviewed so the sessions produce usable evidence rather than memorable anecdotes alone. Prepare the work so that another person can inspect its reasoning without a live presentation. Use concrete examples, readable labels, and links to supporting material where appropriate. Avoid relying on a dense board whose meaning exists only in the facilitator's memory. The point is not to document every conversation; it is to preserve the context and distinctions that matter when somebody acts on the output later.
Prepare three booking tasks
Draft a plan for evaluating a fictional booking prototype. Include one suitability task, one correction task, and one status-checking task. List the questions each task can address and the prototype limitations that might affect interpretation. Prepare a moderator introduction that explains the activity without teaching the intended interface path. Use a small worked example to examine the mechanics of the method. Keep invented material clearly labeled and separate from any real research evidence. The example should expose decisions about wording, grouping, order, or responsibility that would otherwise remain implicit. Where the activity requires a fact you do not have, leave a question rather than manufacturing a convenient answer to complete the diagram or make the exercise look finished.
Avoid liking questions and route-giving tasks
If the plan asks whether participants like the design but never lets them use it, it cannot reveal the full task behavior. If every task names the exact control, the study may hide finding problems. If a prototype breaks, record the interruption rather than interpreting the resulting difficulty as a product finding. Watch for a convenient example becoming the only situation the team considers. Add a case with a different starting condition, incomplete information, or an interruption, then inspect which assumptions no longer hold. Do not invent research findings to justify the additional case. Use it as a deliberate challenge to the working model and identify the real evidence or expertise needed to assess whether the concern matters.
Align the plan before sessions begin
Review the plan with the people who will moderate, observe, and act on findings. Confirm that the decision, questions, tasks, and participant criteria align. Leave room to investigate unexpected behavior without abandoning the research purpose. After actual sessions, report what occurred and its limits; a well-written plan alone is not evidence that the product works.
Worked decision
A status-checking task asks someone to identify whether their place is reserved. Record the answer and route without teaching the confirmation wording first.
References & further reading
Examples and exercises in this guide are original teaching scenarios.
