Run an honest usability rehearsal
See this course’s project requirements
A product design case study with a need brief, concept comparison, prototype, access review, simulated usability log, and evidence-linked revision.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- A product-need brief with simulated observations, a task-centered statement, constraints, and a success measure.
- A three-concept comparison with a selected prototype, two decision criteria, and a switching condition.
- A versioned low-risk reminder prototype with fictional content, a text description, and a core task sequence.
- An access-review note with three corrected barriers, a text alternative, and explicit untested areas.
- A neutral usability script and simulated observation log with a 60% unassisted completion result and issue notes.
- A product design case study with a three-version history, evidence-linked changes, and an honest next-test plan.
Review and revise
Use these criteria to check your work and choose what to improve.
- Need and concept reasoning: distinguishes simulated observations from assumptions and compares three functionally different concepts against the same task and constraints.
- Prototype and access continuity: preserves the fictional content across named versions, documents obvious access improvements, and distinguishes paper review from untested digital behavior.
- Test integrity: uses a neutral voluntary test script, keeps assisted completion separate, computes three of five as 60%, and labels the records simulated rather than customer research.
- Evidence-linked iteration: connects each Version 2 change to a specific tested issue, preserves the version history, and states that the revision still needs a new test.
Want more background?
The idea in everyday life
A usability test asks whether a person can complete a task with the prototype. Leading instructions can hide problems by teaching the answer. Real testing needs voluntary participation, appropriate consent, safe tasks, and privacy controls. The required exercise uses a complete simulated record, so nobody must recruit customers, contact strangers, or conduct research with minors.
Observe what happens without coaching the answer or inventing participants.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Write a neutral task that names the goal without pointing at the answer. Add a short voluntary-participation statement for any future real test, including the option to stop and the absence of sensitive data collection.
- 2
Use the five supplied simulated records. Mark each result as success without help, completion with help, or an unresolved error. Also record the specific problem.
- 3
Calculate the unassisted completion fraction and percentage. Count assisted completion separately, since coaching can change the result and should not be hidden inside the unassisted total.
- 4
For the location and wording problems, write what happened, a possible explanation, and a question to investigate next. Keep guesses separate from observations. Label every record simulated; no real recruitment or testing is required.
See how it works.
Fictional practice: Dev tests Version 1.1 with “Using this card, tell me when and where the kit should be returned.” Five simulated records follow: A finds both fields without help; B finds the date but overlooks the ground-floor location detail; C finds both without help; D asks what “by” means and then succeeds after clarification; E finds both without help. Three of five complete the task without assistance, or 60%. Dev records B’s location confusion and D’s wording question separately from the count. Dev does not rename this a real customer study or assume the five fictional records predict market demand.
Did you cover these?
- The task does not reveal the answer
- Assisted completion is separate
- Three of five is 60% and labeled simulated
What to finish
A neutral usability script and simulated observation log with a 60% unassisted completion result and issue notes.
Watch for this
Coaching participants toward the answer or presenting invented records as real customer validation.
How can I tell I understand it?
You can demonstrate all three checks using your lesson deliverable and explain the reason for each decision.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-10
Read initial barrier review, participant variation, evaluation limits, and combining user evaluation with standards. Web-specific conformance claims are not applied to paper prototypes; the course claims no accessibility certification.
Access: Public reading verified without an account; optional further reading, no paid course or certificate required.
Reuse: Reference only; original Life Starter explanations and practice. Public access is not permission to copy materials or logos.
Source & access notes · checked 2026-09-10
Read human-centered design concepts, multiple iterations, prototype feedback, expertise limits, and participant roles. The fictional practice protocol is original and does not reproduce government templates.
Access: Public reading verified without an account; optional further reading, no paid course or certificate required.
Reuse: Reference only; original Life Starter explanations and practice. Public access is not permission to copy materials or logos.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.