duo-progression-design

Decide what a product teaches, in what order, and with how much support — then design the removal of that support instead of leaving it in forever. Covers sequencing by task rather than by the subject's taxonomy, borrowing an external standard as the progression spine, scaffolding and fading on a schedule, user-removable training wheels, the crutch that exists because it makes content cheap to build, recognition-then-production ordering inside one session, ranking content by the cost of getting it wrong, frequency-first coverage with an explicitly optional tail, and picking one canonical variant out loud. Use when someone asks what order should this go in, should onboarding start with fundamentals or with a real task, what do we cut from the tutorial, when do we take the training wheels off, why do users finish onboarding and still fail the real task, or should we invent our own levels.

Version

2.0.0

License

MIT