Checklist and tours together
The onboarding pattern most accounts end up with: a short welcome tour that opens a checklist, and a checklist whose tasks each launch a tour or open a resource. The generated Onboarding Space holds both halves; this page wires them.
The pattern

Welcome tour
Three to five steps, shown once on first login. Its last button launches the checklist.
Checklist
Four to six tasks, one per action a new user has to do to get value. Each task launches a tour that shows the action, and is completed when the action is done.
Resource Center
Later, holds the checklist so users find it again after closing it.
Build the tours first, one per task, each short. Then the checklist. Then the link from the welcome tour.
Wire a task to a tour
Set the completion condition
Under the completion condition, pick how the task gets checked: when the tour is completed, when a URL is visited, or when an event from your app is received. For a first version, "tour completed" works without any developer. See Checklist behavior.
Link the welcome tour to the checklist
Open the welcome tour, select the button of its last step, and set its action to Launch experience with the checklist. See Available actions.
Make it work for users who are not very digital

A task that only launches a tour assumes the user will follow it. For audiences who need to come back to the explanation, put the explanation in the task itself as well: a short video, a PDF or a link to a how-to in the task's content block, next to the button that starts the tour. The user watches, then does, then checks.
Keep it short
A checklist with twelve tasks is a to-do list nobody finishes. Six is the upper bound for a first version. If you have more, you have two checklists, for two moments or two roles: Patterns that work shows how a survey can pick which one a user gets.
Related
Checklist behavior, for the Dismissible option and what happens when a user closes it
Resource Center, to embed the checklist
Last updated
