Learners ages 14 and above, including adults returning to learning. Work independently with fictional data; no job, account, outreach, or adult legal authority is required.
Course 99 · Create course 08
Design and Test a Useful Product
Turn a practical need into a simple prototype, try a practice usability test, and use the results to improve it.
Before you start
Use paper or a local document for a six-part project folder; a calculator is optional.
See everything you’ll needWhat you’ll leave with
A simple prototype and a clear record of how practice feedback helped you improve it.
Start course Start without an account. Sign in to save lesson progress across devices.
Your project
Start with the practice files. Build your project one lesson at a time.
Practice files are free without an account. Sign in to save your project record in My Proof: a description, checklist, and optional work link. Keep the original files in your own app or notebook; saving a project record does not upload them.
- Get your materialsDownload the practice worksheetUse the downloadable worksheet or toolkit alongside the lesson instructions.
- Make your projectView the project checklist Work in your own notebook, document, or software. Use the supplied practice examples when you prefer.
- Keep a private recordSave a project record Sign in to save a description and checklist, then return to update them.
Course handbook
Know the route before you begin.
Here’s what you’ll need and what you’ll make. You can return to this guide during any lesson.
- Use paper or a local document for a six-part project folder; a calculator is optional.
- Choose the fully supplied fictional scenario, or substitute a low-risk situation without personal or sensitive information.
- Plan about 171 minutes of active reading and practice across six lessons; two lessons each week provides three-week pacing. Optional real-world research can be added after the required practice.
Finish with proof you can use.
A product design case study with a need brief, concept comparison, prototype, access review, simulated usability log, and evidence-linked revision.
Save a project record in My ProofSee project checklist and review criteria
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.
Three ideas to help you along the way
Three useful ideas
The rules behind the steps.
Task before format
Define what people need to accomplish before choosing technology.
Test with respect
Use neutral tasks, voluntary participation, and minimal information.
Show the evidence
Label simulated records, preserve limits, and connect revisions to observations.
What do these words mean?
Key words
Key terms worth knowing.
- Need statement
- A description of a user task, obstacle, and context without prescribing the solution.
- Concept
- A proposed way to meet the need.
- Prototype
- A simple model or draft used to test a specific question about a design.
- Usability
- How easily and successfully people can complete the intended task in the setting where they will use the design.
- Assisted completion
- A task completed after a hint or intervention, recorded separately from unassisted success.
- Iteration
- A new version based on what you learned, followed by another question or test.
Your route6 lessons.
6 lessons.
One useful project.
Work in order the first time. Each lesson makes something the next lesson can use.
- 1Up next
Define a useful product need
Use the supplied observations to describe one specific need.
- 228 min
Compare product concepts
Generate distinct concepts and choose a testable option.
- 331 min
Make a low-risk prototype
Build a complete paper prototype for the core task.
- 426 min
Review access before testing
Identify obvious barriers and provide usable alternatives.
- 528 min
Run an honest usability rehearsal
Use a neutral test script and classify supplied task observations.
- 636 min
Revise and explain the product
Connect a prototype revision to evidence and state remaining limits.
Use the tools
See all tools Tools to help you practice.
Source transparency
Sources and further study.
Explore the references behind the lessons and take your learning further. Source notes explain access and reuse.
Stanford d.school — Design Thinking Bootleg
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.
W3C WAI — Involving Users in Evaluating Web Accessibility
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.
Digital.gov — Design Concepts Guide
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.
Ready when you are
Start lesson one Start with the first useful move.
You’ll always know what to do, what to make, and where to go next.
Open collaboration ideaHelp keep this complete course free.
Potential collaboration: Makerspaces, libraries, schools, adult learning centers, entrepreneurship educators, and introductory design programs supporting accessible practical creation.
Partner with LifeStarter