A useful checklist gives users a short path to a concrete outcome. Choose tasks that match the workflow you want to teach.
A useful checklist gives users a short path to a concrete outcome. Choose tasks that match the workflow you want to teach.
Write each task
Use a verb and a specific result, such as “Create your first report.” Explain why the step matters only when that context helps users complete it. Avoid repeating instructions already visible on the destination page.
Choose the action that fits the task: Read only, Execute JS, Go to Page or Start a tour. Configure the completion setting separately.
Test the workflow
Complete the checklist as a new demo user. Check every link, tour and completion condition. Your application must send any events used by Match Actions.
Review starts, completed checklists and per-task completion after publishing. These measures help identify tasks to investigate; they do not prove that the checklist caused retention or conversion changes. Skipped tasks can also be recorded as complete.
Keep the checklist as short as the workflow permits. There is no required number of tasks.