design-an-onboarding-flow

# design-an-onboarding-flow Earn setup effort by connecting it to the next useful outcome. ## When to use - Use for first-run, invited-user, workspace, migration, or role-specific onboarding. - Do not force optional profiling, marketing consent, or tutorials before the core task. ## Procedure 1. Define segments, entry routes, prior knowledge, roles, permissions, user goal, and first meaningful outcome. 2. Separate required setup from optional enrichment and explain why each requested input is needed. 3. Map invitations, identity, team, import, preferences, permissions, consent, and product-use states. 4. Let users skip, defer, save, resume, go back, correct, and exit without losing completed work where safe. 5. Use progressive disclosure, real sample data, and contextual help rather than a long detached tour. 6. Design empty, loading, validation, duplicate, expired invite, failed import, permission, and partial-completion states. 7. Preserve accessibility across keyboard, screen reader, zoom, language, captions, and time-based steps. 8. Test time to first value, comprehension, abandonment reasons, recovery, invitation variants, and low-confidence users. 9. Measure success from completed user outcomes, not screens viewed. ## Failure plan - If setup fails after data creation, preserve the state and provide a retry or supported cleanup path. - If the user's role lacks permission, explain the dependency and route the request to an authorized owner. ## Done - An onboarding flow document records segments, required and optional steps, states, permissions, data, consent, and first outcome - Usability and accessibility tests verify completion, skip, resume, recovery, invitation, and failure journeys