Onboarding checklist
One step per screen, until somebody is set up.
What it is for
Walking a new user through the two or three things they have to do before your product does anything for them. Each screen carries one step and one button, so nobody is looking at a list of six things they have not done yet — which is the version of this that makes people close the tab.
When to use one
When setup has a real order to it. Connect, then configure, then invite — where skipping the first leaves the second broken. A walkthrough earns its interruption when the alternative is somebody deciding the product does not work, and it is worth nothing when the alternative is somebody simply getting on with it.
When not to use one
When your product needs no setup. A walkthrough laid over a page somebody could already use is an obstacle, and the only button they will press is the one that closes it. If there is exactly one thing to do, say it once in a notification instead.
Questions
- How many steps can it have?
- As many screens as the walkthrough needs, though three or four is where most stop being read. Each screen is edited on its own, with its own blocks and its own buttons.
- Can somebody skip it?
- Yes, unless you say otherwise. A widget nobody can close is a widget that traps the page it is on, so closing is the default.
- Does it work on a phone?
- Yes. One step per screen is the shape that survives a small screen best — it is a list of six that stops fitting.