Onboarding checklists that don't feel like homework
The five-step ceiling, the dismiss-vs-complete tension, and what to do when users skip the checklist entirely.
Onboarding checklists are everywhere because they work, until they don't. The line between helpful gentle nudge and patronizing tutorial that won't go away is narrower than most teams think.
The five-step ceiling
Past five steps, completion rates collapse. The user does step one, maybe two, then dismisses the rest forever. If you have eight tasks you want new users to complete, pick the five most important and put the rest somewhere else, empty states, contextual tooltips, a docs link.
What belongs in the checklist
- One activation moment. The thing that makes the user understand the product's value. Send the first message, ship the first deploy, invite the first teammate.
- One trust moment. Something that increases their commitment, connect a real account, upload real data, set a real password.
- One competence moment. A small win that proves they can use it, customize a setting, save a preset, create a shortcut.
- One social moment (if collaborative). Invite someone, share something, join a workspace.
- One reminder. A passive item that's already done by default, "Verify your email", to give them an instant win.
Where the checklist lives
Three placements:
- 01A widget in the sidebar. Persistent, dismissible, ungets in the way. Used by Notion, Linear.
- 02A modal on first load. Higher attention, more interruptive. Use only if the checklist is short and the product is otherwise empty (no value to show until setup is done).
- 03A dedicated /welcome page. First page after signup, before the product proper. Highest commitment, also highest abandon rate.
The dismiss problem
Always offer dismiss. Always. A checklist the user can't close becomes an enemy. Let them dismiss it; track that dismissal as a signal that your onboarding flow isn't earning attention.
Bring it back later only if the user's behavior shows they got stuck, they returned twice without doing anything, they hit a feature that depends on incomplete setup. Don't re-show on a timer.
Progressive disclosure
Don't show all five steps at once. Show the next one, with the others as faded out-of-focus rows. Mystery is motivation; a wall of tasks is a wall.
Build one
The onboarding-checklist entry has the anatomy and tuned prompts. Pair with empty states, empty product surfaces are the second-best place to trigger onboarding actions, after the checklist itself.
Keep reading
Auth flows that don't make users rage-quit
Magic links, social, passwords, passkeys. The actual data on what converts, and the small UX details that quietly halve drop-off.
Empty states are your second chance at onboarding
The empty dashboard is the user's first real impression of your product. Most teams ship a shrug, here's how to ship a tutorial instead.