Test improvements against task completion and inspect who gets excluded.
Start with everyday situations, predict an outcome, and test your ideas. You need basic arithmetic, percentages and graph reading; explanations introduce additional ideas where needed. No coding or account is required. Every investigation has school, college and workplace extensions—you can choose any of them.
What you will learn
Investigate a user task, author a prototype, diagnose exclusions and prioritize a testable product increment.
Before you begin
Interpret task counts and simple rates.
No drawing or coding expertise is required for a textual prototype.
Prototype transitions are deterministic fixtures; real user choice needs observation.
The original two-investigation starter remains available. Choosing the full course adds its published lessons to your selected scope; your earlier work stays saved. Skipping does not count as completion or understanding.
Free exploration: no completion scope selected yet. Project reports and independent evidence are tracked separately.
Course outline
Choose a unit, then open a lesson on its own page. This outline lists the sequence; it does not combine the full lessons into one page.
Problem discovery and hypothesis tests2 lessons
Choose task evidence and distinguish interest, usability and commitment.
○ Not marked complete · Included · Practice check available
Lesson preview
Can a faster average conceal a design failure?
Four authored task observations compare a pointer-only menu, a basic accessible revision and a streamlined revision. These fixtures are not real usability study data.
○ Not marked complete · Included · Practice check available
Lesson preview
Do equal percentage-point improvements produce equal results?
Synthetic course signup funnel. Visitors may sign up, then signed-up people may finish a task. A repair adds 10 percentage points to exactly one stage.
Design and revise a small flow that helps a learner resume an investigation. Submit the user problem, original and revised screen flows, task script, outcome table and prioritized next increment. Textual screen prototypes are valid artifacts.
Save a report, compare captured evidence, and attempt three new cases. A completed report records submitted work; the rubric supports a separate human review of its quality.