Design Principle
Onboarding should not ask for everything at once; it should get users to a usable result quickly.
Principle
Onboarding should not ask for everything at once; it should get users to a usable result quickly.
Design action
Separate required setup, recommended setup, and later tasks; each step has completion feedback, skip path, and later completion entry.
Examples
Positive example: New projects, team spaces, design systems, AI agents, and integrations start for the first time. Counterexample: Users must complete many resultless steps before first use.
Apply when
New projects, team spaces, design systems, AI agents, and integrations start for the first time. Users need to judge state, scope, risk, or next action quickly.
Source notes
Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries. GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Carbon Patterns: https://carbondesignsystem.com/patterns/ Shopify Polaris: https://polaris-react.shopify.com/ Atlassian Design System: https://atlassian.design/ Design Systems Repo: https://designsystemsrepo.com/
Agent Directive
Separate required setup, recommended setup, and later tasks; each step has completion feedback, skip path, and later completion entry.