A concrete onboarding flow to react to
The fastest way to plan onboarding is to have something to argue with. This tool generates an onboarding flow concept: an ordered list of steps, the single key action in each, and a progressive-disclosure strategy that keeps the early experience simple. Use it as a straw-man you adapt, prune, and re-order.
How it works
The generator assembles a flow from three inputs:
- Step count — a compact number (three to six), because shorter flows activate more users.
- Key action per step — drawn from a pool of real activation actions (set a goal, connect a data source, invite a teammate, complete a first task) and ordered so each step builds on the last and ends on the core value moment.
- Disclosure strategy — how complexity is revealed: just-in-time tooltips, a checklist that persists after signup, optional skip-able tours, or a guided empty state.
Each step is written as a short instruction so you can read the flow top to bottom and immediately see where the value moment lands.
The four progressive-disclosure strategies
Each generated flow pairs with one disclosure strategy. Understanding the difference helps you pick the right one for your product type:
Just-in-time tooltips reveal a feature only at the moment the user is about to need it — a tooltip appears when the cursor approaches a field for the first time, then disappears. This minimises up-front cognitive load and is ideal for products where the interface is self-explanatory for experienced users but confusing for beginners.
Persistent checklist shows a progress tracker that stays visible after signup until all activation items are ticked off. It works well when users return across multiple sessions before completing setup (a data-integration tool, for example, where the user needs to get IT approval before connecting a source).
Optional skip-able tour presents a brief feature walkthrough that the user can exit at any point. This suits visually complex products — dashboard tools, creative applications — where showing the layout once helps orient new users without forcing it.
Guided empty state fills the product with example data, a sample project, or a pre-populated template so the user sees a realistic picture of what the product looks like in use. When they delete or replace the example, they are already activated. This is especially powerful when an empty canvas is intimidating.
Common mistakes to avoid
- Asking for data the product does not need yet. Every field on a setup screen that is not immediately used to show value is a step that increases drop-off. Collect what you need when you need it.
- Showing a “you’re all set” screen as the last step. End on the value moment itself — the first chart rendered, the first message sent, the first task completed. Confirmation screens delay gratification without adding it.
- Making the tour mandatory. Exit intent in forced walkthroughs is high. Offer the tour, make skipping prominent, and save it for users who revisit Help later.
Tips and notes
- Anchor the flow on one activation metric. Every step should move the user closer to it; cut steps that do not.
- Let users skip. A forced multi-step tour increases drop-off. Make depth optional and keep the required path tiny.
- The last step should be the value moment itself, not a “you’re all set” screen. End by doing the thing, not by promising it.
- Generate several concepts and note which steps appear across all of them — those are likely the non-negotiable activation moments for your product type.