Courses / Design and product development / Discover, prototype and improve / A tested path to saved work Build and defend your work A tested path to saved work 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.
Choose an audience, investigate alternatives, copy evidence from your experiments, and produce an artifact. You can open this project at any time. Reports, numerical transfer checks and human review are separate outcomes.
Your project workspace Choose the kind of work you want to produce School investigation College investigation Workplace application Build a paper or textual club website prototype and test a navigation task with classmates; record failures as well as successes.
1. Collect and compare evidence Required experiment sources:
Include every source above and at least one pair with different inputs from the same experiment. Explain confounding changes yourself; the presence check does not judge your interpretation.
Open an experiment and change an input or capture a trial to make evidence available here.
2. Write and revise your report User problem and evidence Name user, task and observed barrier. Separate interview preferences from observed task performance.
Original and revised prototype Provide screens, visible labels, transitions and recovery paths as text or attachments. Explain what changed.
Task script and outcomes Give a repeatable task, group definitions, attempts, successes, blocked tasks and timing with its denominator.
Regression analysis Compare revisions by group. Preserve failed cases and name a new case not used to choose the revision.
Next increment and decision rule Choose work under a capacity bound, cite task evidence and state what observation would stop or change the plan.
Your artifact: code, analysis, prototype or decision brief This field stores up to 12,000 characters of inert text. Code runs only through the explicit bounded editor in the relevant lessons; project attachments never execute.
Load a text artifact Review your work against the rubric Problem statement identifies a concrete task and supporting observations. Prototype specifies actions and destinations, including a recovery path. Testing reports failures and subgroup outcomes without hiding them in timing averages. Revision addresses observed failures and checks for regressions. Prioritization states resources, assumptions and follow-up criteria; fixture success does not establish broad usability. 11 evidence requirements remain Capture evidence from discover the user problem. Capture evidence from prototype a resume flow. Capture evidence from inclusive task test. Capture evidence from test a design revision. Include two different input configurations from the same experiment to compare. Write your user problem and evidence. Write your original and revised prototype. Write your task script and outcomes. Write your regression analysis. Write your next increment and decision rule. Add your project artifact: code, analysis, prototype or decision brief. Record my report Download report and evidence Editing the report or evidence returns it to draft. Recording verifies field presence and input comparisons, not correctness of your reasoning or code.
3. Check transfer to unfamiliar cases These authored cases use different numbers or conditions from the lesson practice. They are public local checks, not secure certification. Each case permits three submissions. Opening, first responses and attempt counts survive imports; no reset creates fresh evidence.
Case new-funnel Open case new-funnel Case success-denominator Open case success-denominator Case subgroup-regression Open case subgroup-regression
Return to the course · My Work and backups
