What is an onboarding checklist?
An onboarding checklist is a short, visible list of the setup steps a new user needs to complete before a product becomes useful, shown inside the product and ticked off as each step is done. It gives a new user a to-do list to work through at their own pace instead of a scripted tour to sit through.
What goes on an onboarding checklist
The steps that stand between a new user and the first thing the product is for. In a SaaS onboarding checklist for a team tool that usually means connecting whatever the product runs on, such as a data source, a repository, or a calendar, inviting the first teammate, and creating or importing the first real object, whether that is a project, a campaign, or a page. Each item links to the screen where the step happens, and the list is ordered so the prerequisites come first. The first item is often marked complete on arrival, since signing up already counts, so the user starts with visible progress.
Why checklists beat tours
A user works through a checklist when they want to, in the order the product suggests, and can leave and come back. Each completed item is a real change in the account rather than a dismissed tooltip, so progress on the checklist is progress on setup. That is the reason checklist completion is worth tracking and tour completion tells you little. productonboarding.com, a site we also run, has a longer guide to the pattern in how to build effective product checklists and a component reference at checklist.
Where checklists break
The common failure is padding. A list that includes "explore the dashboard" and "read our getting started guide" next to the real setup steps teaches users to ignore it. The second failure is one list for every role, so an admin and a viewer see the same items even though the viewer cannot complete the admin's steps. The third is that a checklist can only point. When a user clicks into an item and gets stuck on the screen it sent them to, the checklist has nothing more to offer, and that is where the setup stalls. And like every scripted piece of onboarding, a checklist built in March can send users to a screen that was redesigned in June unless someone keeps it current.
How a checklist is measured
Completion rate for the whole list and for each item. The item with the biggest drop-off is the setup step users cannot get through on their own, which is usually more useful to know than the overall rate. Time to complete tells you how long setup really takes. And comparing activation for users who finished the list against users who did not tells you whether the items on it are the right ones.
How Frigade fits
Engage includes a code-first Checklist component, so the list lives in the product's own codebase and behaves exactly as written. The assistant covers the part a checklist cannot. When a user clicks into an item and gets stuck, they ask, and the assistant walks them through that step on the live screen or completes it for them. Suggestions can point users with unfinished items back to the list, targeted by user property.
Common questions
- How many items should an onboarding checklist have?
- Three to six, and every one of them should be a step the user has to complete before the product does anything useful for them. Connecting a data source, inviting a teammate, and creating the first project belong on the list. Reading the docs and watching a welcome video do not, because the product works without them.
- Is an onboarding checklist better than a product tour?
- For any product that needs setup before it is useful, yes. A tour shows the interface once and disappears. A checklist stays on screen until the setup is done, tracks progress, and sends the user to the right place for each step. Finishing a checklist means the account is configured, which is why checklist completion tracks activation far more closely than tour completion does.
- User onboardingUser onboarding is the process of getting a new user from their first session to the point where they get value from the product on their own. It covers account setup, the first valuable action, and the guidance that carries a user through both.
- Product tourA product tour is a scripted sequence of in-app steps, usually tooltips or modals, that introduces a new user to a product's interface. Most tours are shown on first login and follow a fixed order regardless of what the user came to do.
- Product adoptionProduct adoption is the process by which a user goes from signing up for a product to using it as a regular part of their work. It is measured as the share of new users who reach a defined activation milestone and keep coming back, rather than as raw signups or logins.
- In-app guidanceIn-app guidance is help delivered inside the product interface, where the user is working, instead of in a separate help center, email, or support ticket. It includes tooltips, walkthroughs, checklists, contextual hints, and in-product assistants that answer questions and complete tasks.