Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home

The Checklist Philosophy

Learn more about the four reasons we recommend you use the Appcues Checklist to support your users during onboarding.

Written by Ricky Perez

Updated at June 17th, 2024

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • FAQs
  • Support
  • Installation & Developers
    Installing Appcues Web API & Data Extras Troubleshooting Installing Appcues Mobile
  • Web Experiences
    Studio Building Web Experiences Customization & Styling FAQ Targeting Troubleshooting Use Cases
  • Mobile Experiences
    Building Mobile Experiences Installation & Overview Troubleshooting Mobile Analytics & Integrations
  • Account Management
    Subscription Users & Data
  • Analytics
    Experience and Event Analytics Data
  • Best Practices
    Product-led Growth Pro Tips Best Practices Use Cases
  • Integrations
    Integration Documents Extras Use Cases
  • System Status
    System Status & Incidents
  • Workflows
    Use Cases Building & Configuration Workflow Analytics and Integrations
+ More

Checklists have been used successfully in fields ranging from aviation to medicine, to education. In each case, the use of checklists has improved quality, safety, and learning success by a wide margin. In software, the checklist pattern has been used for new-user onboarding in various forms for many years, with a prominent example being LinkedIn's motivational meter for "completing your profile."

There are four reasons we recommend you use the Appcues Checklist to support your users during onboarding:

  1. It's predictable: Users are automatically introduced to the Checklist experience the first time they see it, and they know how to get back to their tasks.
  2. It's motivational: As users complete tasks, the checklist pops up to reward them, update their progress, and clearly show them the next step, which builds momentum. It also breaks down the often daunting task of learning a new product into parts, making users more likely to complete it.
  3. It puts end users in control: Unlike a walkthrough, the Checklist shows the path and gives the user power over their own learning experience, making for a more engaging UX.
  4. It's informative: It informs the user, but it also informs you by quickly unearthing what works and what doesn't in the first moments you meet a new customer. 

Interested in learning more about checklists and some best practices to make them most impactful to your users? Check out our best practices guide!

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • ROI With Appcues: Establishing a Baseline Metric
  • Best Practices for Managing Your Team in Appcues
  • Pro Tip: Display a Flow Before a Checklist
  • Pro Tip: Gather Feedback on a New or Existing Feature
DON'T TAKE OUR WORD FOR IT

Start building with Appcues for free

Try before you buy
No credit card required
Support included
Start building for freeBook a demo
or take an interactive tour
Appcues logo

Product

In-app messaging
Email
Push notifications
Workflows
Data
How it works
Pricing
What's new

Use cases

Onboarding
Free-trial conversion
Feature adoption
Feedback
Support

Integrations

Why connect
All integrations
All workflows

Company

About
Careers
HIRING
Why Appcues
Teams
Customers

Support

Request a demo
Start free trial
Developer Docs
Help Center
Customer Success
Contact

Resources

Product Adoption Academy
Courses
Workshops
Templates
Examples
Made with Appcues
The Appcues Blog
PLG Collective
Product-led Experience Report
The Product Experience Playbook
The Product-Led Growth Flywheel
© 2025 Appcues. All rights reserved.
SecurityTerms of ServiceWebsite Terms of UsePrivacy PolicyCookie Preferences
Expand