Make a low-risk prototype
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 prototype makes an idea concrete enough to examine. It can be a paper card, a storyboard, or a local slide with no working software. Keep the test low risk and reversible. This course excludes products that administer treatment, handle dangerous equipment, collect payments, or ask participants to reveal private information.
A prototype needs enough detail to answer a question, not production polish.
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
Choose the paper-card concept and list the minimum information needed for the core return task. Use the supplied item, date, time, and location; label them fictional and exclude names or contact details.
- 2
Build one complete prototype with a clear heading and separate date and location fields. A typed text layout is sufficient; do not require design software or spend the practice block building a real service.
- 3
Write a short interaction sequence: receive the reminder, locate the deadline, locate the return desk, and identify what to do if more time is needed. Check that the prototype itself supports each step.
- 4
Save a version label and a written description of your prototype. Remove one part that distracts from the task and explain why. The description should let someone understand the design without seeing the sketch.
See how it works.
Fictional practice: Dev makes a card headed “Drawing Kit Return.” It contains “Return by: Friday, October 16, 5 p.m.” and “Return to: Community Room Desk, ground floor.” A second block says “Need more time? Ask the desk before the return date.” All details are fictional. The first prototype places pickup information at the top, but the chosen task concerns returns, so Dev removes that competing line. A text description records the card’s layout for anyone who cannot inspect a drawing. The prototype is complete enough to test date and location finding without a database, login, purchase, or actual equipment loan.
Did you cover these?
- Date, time, and location are complete
- Prototype has a version label and text description
- No sensitive, payment, or hazardous functions are included
What to finish
A versioned low-risk reminder prototype with fictional content, a text description, and a core task sequence.
Watch for this
Building a polished system before making the basic task understandable.
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 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.