Revise and explain the product
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
Design work becomes more credible when a reader can see why a change happened. A polished final image alone may conceal unsupported assumptions. The final brief should preserve the need, alternatives, prototype, access review, and test records. It should distinguish usability learning from demand, commercial success, technical accessibility, or safety validation.
A useful design story shows the need, evidence, change, and next test.
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
Review the need brief, concept table, first prototype, access note, and simulated test log. Select two observed issues that matter directly to the return task, rather than changes based only on decoration or personal taste.
- 2
Create Version 2 and connect each change to a specific observation or access finding. Preserve the fictional item, deadline, and location so the revision can be compared fairly with tested Version 1.1.
- 3
Write a plan to test the revised design. Give a task without hinting at the answer and say what evidence you would collect. If you have not run a second test, say so; the changes are still untested.
- 4
Assemble a short design case study showing need, alternatives, prototype versions, access review, simulated evidence, and remaining limits. Add a practical next step that stays within the course’s low-risk scope and does not require customers, purchases, or publication.
See how it works.
Fictional practice: Dev changes the location field to “Return location: Community Room Desk, ground floor,” places the ground-floor detail on its own line, and replaces “Return by” with “Return no later than.” The first change addresses B’s location confusion; the second responds to D’s wording question. The next test would check whether those revisions improve understanding without introducing new ambiguity. Because no new observations are supplied, Dev does not claim the revised version passed. The portfolio retains Version 1, tested Version 1.1, and untested Version 2, with a change log and the five simulated records; no real users or customers were recruited. The product remains a low-risk educational prototype.
Did you cover these?
- Each revision links to a specific issue
- Version 2 is marked untested
- The case study distinguishes simulation from real research
What to finish
A product design case study with a three-version history, evidence-linked changes, and an honest next-test plan.
Watch for this
Reporting a revised design as validated when it has not been tested.
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
Opened the public resource page and read its description of empathize, define, ideate, prototype, and test modes. Page displays CC BY-NC-SA 4.0. No cards, exercises, illustrations, or syllabus are copied; no Stanford affiliation is claimed.
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 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.