Define a useful product need
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 useful product helps someone complete a task under real constraints. An idea such as “build an app” skips the question of what people need to do. This course uses a fictional borrowing-reminder tool so you can practice with paper or a local document. No customers, interviews, account, paid software, or real personal data are required.
Start with a task and obstacle before choosing a solution.
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
List the supplied events and requests without inventing motives or assumptions about people. Label all the records simulated—made up for practice—so readers cannot mistake them for real customer research.
- 2
Identify the task, obstacle, and context shared by the observations. Write one need statement that describes the task outcome and leaves room for paper, digital, or other simple solutions.
- 3
Separate known constraints from questions: return date and location must be clear, large text is requested, and smartphone access is unknown. Keep a possible app as an option rather than the definition of the problem.
- 4
Set a small project boundary: a reminder for one fictional item with no payment, account, safety-critical instruction, or personal tracking. Define one observable success measure that can be tested through the supplied practice data.
See how it works.
Fictional practice: A community equipment shelf lends drawing kits. Three supplied observations say borrowers cannot find the return date on the current card, one person mistakes the pickup location for the return location, and another asks for a large-text version. These are invented observations, not research findings. Dev writes the need as “Borrowers need to identify when and where to return a drawing kit from a simple reminder.” Dev avoids assuming an app is required because no smartphone access information exists. A teen can design for the fictional shelf; an adult can use the same case or a similarly low-risk household task.
Did you cover these?
- Observations are labeled simulated
- The need statement leaves solution choice open
- The scope excludes sensitive or safety-critical functions
What to finish
A product-need brief with simulated observations, a task-centered statement, constraints, and a success measure.
Watch for this
Inventing customer interviews or defining the problem as a preferred technology.
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.