Onboarding pattern
Guided setup wizard onboarding pattern
The guided setup wizard takes users through a focused setup before they can use the product. Used for products where initial configuration is non-optional — integrations, data import, multi-step billing setup. High investment from the user; high completion produces high activation.
Verified · editorial policy
How the pattern works
On first login, the user is presented with a multi-step setup wizard. Each step collects required information (connect integration, choose plan, set workspace name). The wizard blocks product use until complete; on completion the user lands on a fully-configured product.
Best for
Products requiring real configuration to function (integration-heavy SaaS, multi-account platforms). Products where users abandon if setup is asynchronous. B2B SaaS where the setup-time investment correlates with retention.
Worst for
Products with optional setup. Products where users explore before deciding to commit. Consumer SaaS where the bar for first interaction is low.
Activation metric
Wizard completion rate at first session. Anything below 60% completion suggests the wizard is too long or asks for the wrong things.
Implementation considerations
- Identify the absolute minimum information the product needs to function. Cut everything else from the wizard.
- Order steps from least friction to most. Easy wins build commitment; the highest-friction step goes after the user has invested.
- Provide progress indication — '2 of 5 steps' is essential at this length.
- Allow back-stepping. Forcing forward-only progress causes drop-off on the third step.
- Provide a 'save and come back later' option for non-critical fields.
Common mistakes
- Including optional fields in a required-step wizard. The user resents being slowed down for non-essential information.
- Wizards longer than 7 steps. Drop-off after step 7 is severe.
- No back-stepping. Forcing the user forward without let them correct losses 20-40% per step.
- Wizards that surprise the user with cost or commitment late. Users feel trapped and abandon.
Variations
- Wizard with smart defaults — pre-fills as much as possible, requires user confirmation only.
- Conditional wizard — different steps based on initial answers, reducing total time for most users.
Frequently asked
- Can the wizard ask for payment?
- Yes, but place payment at the end of the wizard after the user has invested in setup. Front-loading payment loses most users; back-loading payment loses fewer but creates 'completed setup, did not pay' churn.
Other onboarding patterns
Test the pattern, do not commit blindly
The right onboarding pattern is product-specific. Test the activation rate before fully committing.