User Onboarding: Reusable First-Run Patterns for Every Product Screen
How a design system guides new users with shared patterns: welcome screens, tooltips, checklists, progress indicators, and empty states.
In short
User onboarding in a design system means shared patterns that guide new users: welcome screens, tooltips, checklists, progress indicators, and empty states.
14 min readFree
What you will learn
This lesson explains how a design system handles user onboarding. In this course, onboarding means the design system’s guidance on how new people are introduced to a product. That guidance uses reusable patterns, so a first visit feels the same across the whole product, not different on every screen.
By the end, you should be able to name the five common onboarding patterns, say when to use each one and when to skip it, follow three principles for good first-run design, and write simple rules that stop a team from piling prompts onto one screen.
Key words
- Onboarding
- Helping a person get comfortable with a product. In this course, it means the shared guidance a design system holds for that job.
- First run
- The first time a person opens a product, from the first launch to the first useful action.
- Activation
- The moment a new user gets a first real result from the product, such as finishing a first task.
- Pattern
- A proven way to solve one common problem, written down so any team can reuse it.
- Tooltip
- A small box that points at one control and explains it.
- Coach mark
- A hint drawn over the screen, often with a dimmed background, that points at one part of the interface.
- Empty state
- What a screen shows before the person has any content on it.
- Trigger
- The event or condition that makes a piece of onboarding appear.
- Dismiss
- Close a prompt without finishing it.
Why does onboarding belong in a design system?
A design system is a shared set of parts and rules. Onboarding fits inside it because new users meet many screens for the first time. If each team builds its own welcome flow, the first experience changes from one part of the product to the next, and the user has to learn the rules again each time.
Researchers at the Nielsen Norman Group, a well-known user research firm, see onboarding as a separate layer of screens and hints that sits outside everyday navigation. Their view also covers existing users. When a redesign or a new feature ships, those people may need onboarding too, so it is not only a first-launch task.
A system handles this by keeping a small set of onboarding patterns. Each pattern has a job, a rule for when to show it, and a rule for when to leave it out. Teams then combine patterns instead of inventing new ones.
What are the five reusable onboarding patterns?
Most good first-run flows mix two to four patterns rather than relying on one. Appcues, a company that sells onboarding tools, makes the same point in its guide to onboarding patterns. The five patterns below are the ones this lesson covers, each with a purpose and a rule for when to skip it.
What is a welcome screen?
A welcome screen is a single screen at the start that greets the person and may ask for a small amount of setup, such as a goal or an interest. Its job is to point the first experience in the right direction. Use it when the product needs one fact about the person before it can be useful, such as a goal, a region, or a role.
Skip it when the product works as soon as it opens. The NN/G mobile onboarding analysis says that for most apps, people can learn the interface by using it, so separate onboarding screens are not needed. NN/G notes that onboarding can apply to existing users when a new feature ships. Keep any questions short, because a long form before the first use is a barrier.
Tooltips and coach marks
A tooltip or coach mark explains one control at the moment a person meets it. Use them for one unfamiliar control, such as a field in a setup form or a button whose result is not obvious.
Skip them for controls that people already understand, and skip long chains. The NN/G coach mark guidance warns that showing many hints in a row makes people dismiss them faster, and it can make the whole app look harder than it is. Present one hint at a time, when the person reaches that part of the app. Keep each one short and point at the thing it describes.
What is an onboarding checklist?
A checklist is a short list of setup tasks that stays visible and shows which tasks are done. It helps people keep track of what is left without a forced walkthrough. Use it when setup takes more than one session, or when a product needs several connected tasks before it is useful.
Skip it when one guided task is enough to reach the first result. A good checklist lists results, such as a first project created, rather than lessons, such as a description of a menu. Checklists work best when they let people finish at their own pace.
Progress indicators
A progress indicator shows how far a person has moved through a set of steps, often as a bar or a ring. It answers one question: how much is left? Use it whenever onboarding has several steps, so users know the flow is short and finite. Skip it for a single screen, because a bar with one step adds noise.
Progress indicators are also a basic check.
What is an empty state?
An empty state is what a screen shows before it holds any data, such as an empty project list, a blank dashboard, or an inbox with no messages. A good one tells the person what will appear there, why it matters, and what to do first.
Empty states are onboarding real estate on screens that start blank. Skip it only when a screen can never be empty for a new user. A blank screen with no words is a common drop-off point.
Principles for good onboarding
The five patterns are tools. These three principles decide which tool to use and when. Teams can check any new onboarding idea against them before it is built.
Show only what is needed to reach the first success
The goal of the first run is one real result, not a full tour of the product. Saas UX notes that good onboarding gets a new user to a first real outcome with as little friction as possible. Anything that does not help with that first result can wait for later.
Let people skip and come back
Every prompt should have a clear way out. People should also be able to stop halfway and return later without losing their place.
Teach in context, not up front
Explain a feature when the person reaches it, not in a block of instructions on the first launch. NN/G says tips work best when they show up at the moment of first use. Teaching in small doses, tied to what the person is trying to do, beats a long tutorial that people will forget.
Tip
Use these three principles as a review checklist. Ask of every new onboarding idea: does it help with the first result, can the person skip it, and does it appear when the person needs it?
Worked example: Duolingo’s first run
Duolingo is a language-learning app. Written reviews of its first run describe a flow built around doing a lesson rather than reading about one. The steps below walk through that first run and show which parts could become reusable patterns. The sources do not describe Duolingo’s internal design rules, so the documentation examples are a model of how a team would write them, not Duolingo’s own documents.
Walking through the first run
- 1
Choose a language and answer one question
The answers let the app personalize its later nudges. This is a short welcome or setup pattern, and it stops at one or two questions.
- 2
Start a real lesson before sign-up
For a design system, this is a rule about the order of screens rather than a visual part, so the rule should say that the first useful action comes before any account form.
- 3
Show a progress bar during the lesson
The lesson shows a progress bar. This is the progress indicator pattern in action. It shows how much remains, so the person can judge the effort. A system would document it as a bar that appears only during a multi-step flow and shows a clear sense of what is left.
- 4
Offer a contextual hint at the moment it matters
This is the tooltip or coach mark pattern. It explains one action when the person is about to use it, not in a tour before the lesson starts.
- 5
Ask for a profile after the first lesson
After a completed lesson, the app asks the person to create a profile and frames the request as a way to avoid losing progress. This is a prompt placed after a result, not a gate placed before one. A system would record the trigger as “after the first completed lesson” and the dismiss rule as “can be skipped.”
- 6
Use an empty state for the next screen
Duolingo’s public reviews do not describe its home screen in this detail. As an illustration, a team could show a new person a screen with a short message and one button that starts the first lesson, instead of a blank page. This is the empty state pattern with a call to action.
Documenting each step as a system component
Once a team has named the steps, it should write each one as a component card. The card records the purpose, when to use the pattern, when to skip it, and the rules for showing and closing it. Three of the Duolingo steps make good examples.
Progress indicator card
Purpose: show how much of a multi-step flow remains. Use when: the flow has several steps. Skip when: there is only one screen. Rules: show the bar only during the flow, never hide it once started, and do not add it to single-action screens.
Setup question card
Purpose: collect one fact that personalizes the first run. Use when: the answer changes what the person sees next. Skip when: the answer changes nothing. Rules: ask one question at a time, keep the set short, and allow the person to skip it and set the answer later.
Empty state with call to action card
Purpose: turn a blank screen into a clear next step. Use when: a list, dashboard, or feature starts with no data. Skip when: the screen can never be empty for a new user. Rules: state what will appear here, offer one primary action, and remove the empty state once data exists.
Documenting onboarding rules in the system
A pattern is only consistent when its rules are clear. Each onboarding component should carry three kinds of rules: when it starts, how it closes, and what comes next. Keep these rules next to the component so builders and designers read the same text.
Triggers: when a prompt starts
A trigger is the condition that starts a prompt. Write each one as a plain, checkable rule. Examples include the first visit to an area, the first time a feature is opened, or the first time a person sees a new feature after a release.
Avoid triggers that depend on time alone, such as a prompt that appears every day. That keeps the prompt tied to the person’s real situation.
Dismissing: how a prompt closes
Every prompt needs a clear exit. Clarity’s guidance says a skipped onboarding should stay hidden until the person brings it back, for example from a help menu.
Decide and write down whether a dismissal lasts for one screen, one visit, or for good. A prompt that returns on every screen teaches people to close everything on sight.
Sequencing: avoid stacking prompts
Sequencing sets the order of prompts and limits how many can appear together. The simplest rule is one active prompt per screen. If two patterns could fit the same moment, the team should choose the one that matches the person’s current task and hold the other for a later visit.
Checklists can handle the rest. Their later items can unlock as earlier ones finish, so the person meets new steps only when they are ready. Feature hints for existing users should fire only when those users reach that feature. Together these rules stop a five-step tour, a welcome screen, and a checklist from all appearing on the same first launch.
Tip
Write the sequencing rule as a single line a builder can check: no more than one active prompt per screen, and a dismissed prompt does not return during the same visit. Then test that rule on the busiest first-launch screen in the product.
Check your understanding
Each question below is a new scenario. Use the principles and documentation rules from this lesson to answer it.
Quick check
A team’s new app shows a five-step tooltip tour, a welcome modal, and a setup checklist all at once on first launch. Users close everything without reading it. Which onboarding principle is being broken, and what would you change?
Quick check
A design team is adding a shared folders feature. Most users have used the app for two years. The team plans a five-screen tour that opens every time anyone signs in. Which choice fits the system’s rules best?
Quick check
A new user opens the Projects screen for the first time. It is blank and shows no words. Which system rule would fix this most directly?
Key takeaways and what this lesson leaves out
Use a small set of patterns
Welcome screens, tooltips, checklists, progress indicators, and empty states each have one job. Use the one that fits the moment, and skip it when the product does not need it.
Follow three principles
Show only what leads to the first result, let people skip and return, and teach in context rather than up front.
Write the rules
Record each trigger, each way to dismiss, and each sequencing limit. A rule such as one active prompt per screen keeps teams consistent.
This lesson does not teach the words on onboarding screens, which belong to the writing and tone lessons. It also does not teach how to build the individual buttons, banners, or badges that appear in onboarding, how to set color, spacing, or type values, how to make onboarding usable with screen readers and keyboards, or how onboarding screens lay out across devices. Those topics have their own lessons in this course.
Sources
- Clarity Design System: Onboarding Pattern
- NN/G: Mobile-App Onboarding: An Analysis of Components and Techniques
- NN/G: Instructional Overlays and Coach Marks for Mobile Apps
- Appcues: Onboarding UX: 10 patterns, best practices, and real examples
- SaaS UX: SaaS Onboarding UX Examples: Patterns That Get Users to First Value
- Fernando UX: Onboarding Patterns: Tours, Tooltips, Checklists, and Empty States
- Kompassify: Progressive Onboarding: How to Teach a Product Over Time
- Appcues: Duolingo's delightful user onboarding experience
- Juno School: The Duolingo Onboarding Experience
- The UXologist: How Duolingo guides a long first-use journey
- Heurio: Audit onboarding flows faster with built-in UX heuristics
- Emergen: Onboarding UX Best Practices: Patterns, Flows and Metrics
- Userpilot: Onboarding UX Patterns and Best Practices in SaaS
- Appcues: Best User Onboarding Examples: 12 Flows Worth Copying
- Jimo: User Onboarding Experience UX Best Practices for 2026
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.