Tutorials: Teach Users by Doing, Right When It Matters
Learn how short, in-product tutorials help a new user reach a first win and build the habit of acting.
In short
A tutorial is a short, in-product lesson that teaches a new user by doing, right when it matters, so they reach a first win.
14 min readFree
What is a tutorial?
A tutorial, in this course, is a short piece of teaching that sits inside the product. It is not a separate manual, and it is not a long lesson the user must finish before starting. It appears on the screen, next to the thing it explains, at the moment the user needs it. Its job is to help a new user reach a first success and then keep acting on their own.
Tutorials are part of a bigger process called onboarding. Onboarding means getting a new user familiar with a product, and it can include setup, feature tours and first tasks. One source describes its main goal as helping users understand the key principles of a product and see how it can be useful to them.
What you will learn
How to teach through doing, so the user learns by acting rather than reading.
Which format to pick
How to match a walkthrough, tooltip, empty state, checklist or short video to the task.
How to know it works
Which numbers to track and how to revise a tutorial after you test it.
Key words
- Tutorial
- Short in-product teaching that shows a user how to do one thing.
- First run
- The first time a person opens a product and tries it.
- Onboarding
- The whole process of getting a new user familiar with a product and set up.
- Walkthrough
- A guided series of steps where the user performs each action in the real screen.
- Tooltip
- A small box of text that points at one element on the screen.
- Coach mark
- A see-through layer on the screen that highlights one part of the interface with a hint.
- Empty state
- What a screen shows before the user has any content, such as no expenses yet.
- Checklist
- A short list of setup tasks that the user ticks off one by one.
- Completion rate
- The share of users who finish a tutorial.
- Skip rate
- The share of users who close a tutorial before finishing it.
- Time to first key action
- How long a new user takes to do the main task of the product for the first time.
How do you teach by doing, in small doses?
The best tutorials let people learn by trying. Nielsen Norman Group, a well-known user research firm, says instructional onboarding should be brief and optional, and should show only the minimum a user needs to use the app. Users do not come to an app to study its interface. They come to finish a task with as little effort as possible.
Teaching by doing also means people remember more. One source notes that a user who is asked to tap a button or finish a task understands the core feature faster than one who reads a long set of instructions. Another says the best approach is to let users learn by trying the app rather than reading long text.
Keep it brief
A few short steps, not a full course. Long tutorials are often skipped before they help.
Keep it in context
Show the hint on the screen where the action happens, not on a welcome screen far away.
Keep it optional
The user should be able to ignore it and still get their task done.
Few products need a long tutorial at all. Nielsen Norman Group says most mobile apps do not need instructional onboarding, and that users should be able to learn the interface by using it. Tutorials are worth the effort when the feature is new, unusual, or needs information from the user before it can start.
Tip
Before you build a tutorial, try the product with no tutorial and watch a new user. If they get stuck at one specific step, teach that step. If they manage fine, you may not need a tutorial at all.
Smaller is also better for each hint. Nielsen Norman Group found that showing many tips at once overloads working memory, and that a user may forget most of what they read in about 20 seconds. So each hint should focus on one action.
Keep the words short too. A coach mark that points at one button and says what it does is far more useful than a paragraph that explains the whole screen.
Tutorials also work best when they hand the user the next step only after the last step is done. One guide describes an interactive walkthrough that reveals the next step only after the user completes the current one. This keeps the user moving forward without a wall of text.
Think about one real case. A walkthrough for a photo app might ask the user to tap the crop tool, drag a corner, and tap Done. Each step is shown when it is needed, so the user never has to remember the full list.
Note that a tutorial can be too early. One review noted that a helpful tip was shown during setup, before the user had seen the screen it described. It would work better shown just before the user starts the task.
Show a tutorial only when it can be used.
The rule is simple: one hint, one action, at the right time. When you are unsure, show less.
Quick check
Your note-taking app adds a new Share with team button. Most users already know how to take notes and will only need help with this one new button. Which tutorial format fits best?
How do you pick the right format for the task?
There is no single correct tutorial format. The right choice depends on how complex the task is and when the user needs help. Some guides group the common options into a short list of patterns, from full product tours to small tooltips and checklists. The table below covers the main ones you will meet.
Interactive walkthrough
The user taps through a real task while the app guides each step. Use it for a core workflow with several steps, such as setting up a first account or creating a first project. One source says it suits an app that is more complex than usual, where the design is new or unfamiliar.
Tooltip or coach mark
A short hint pinned to one element. Use it for one feature that is hard to find or new. One guide says walkthroughs give a tour at the beginning, while tooltips help users throughout their use of the product.
Empty state with a prompt
A blank screen that tells the user what to do first, with one clear button. This is often the best tutorial because it appears exactly when the user has nothing to look at yet.
Checklist
A short list of first-run tasks, such as add a photo, invite a friend or record a first entry. One source notes that each checklist item can open its own interactive walkthrough. Use it when the first success needs several steps.
Short video
A clip of a few seconds that shows a movement or process that is hard to describe in words. Use it sparingly, because a video is passive and the user cannot try anything while watching it.
Avoid the long slideshow at launch. Nielsen Norman Group calls this deck-of-cards style, where screens are shown in a carousel the moment the app opens. They found that deck-of-cards tutorials did not improve task performance and made tasks feel harder.
Tip
Match the format to the number of steps. A long chain of steps is usually a sign that the product itself needs simplifying.
Also give the user control. Most mobile apps let people skip onboarding so they can start the task they came for. Many guides also recommend offering a skip button on every tutorial. A skipped tutorial should still be reachable later, for example from a help menu or a Show me how link, so a user who changes their mind can open it again.
Worked example: Duolingo's first run
Duolingo, a language-learning app, is one of the most discussed examples of a first run. Its design shows how a tutorial can be a real task instead of a lecture. Follow the steps below to see the idea in use. The details are taken from published reviews and analyses of the app's flow, so treat them as reported, not official.
- 1
Ask a few quick questions
The first screens ask which language to learn and how many minutes a day to spend. One review says the user picks a language and a daily time of 5, 10, 15 or 20 minutes, then goes straight to a lesson.
- 2
Start a real lesson
Before any account is needed, the user does a real exercise. One analysis says Duolingo teaches a word before it asks for an email address. The lesson is the tutorial, so the user learns the core action by doing it.
- 3
Keep the first task easy and clear
The first task is a simple match between a spoken word and a picture. One review notes the Continue button stays unavailable until the user makes a choice, so the user must try the action before moving on.
- 4
Set expectations and give an exit
A short, finite promise makes the user willing to start.
- 5
Give feedback at the end
When the lesson ends, the app reports results such as points earned, accuracy and time taken. This is the early win the user came for.
- 6
Ask for sign-up after the win
Only after the lesson does the app ask the user to create an account to save progress. One analysis says the sign-up screen does not appear until after the first lesson.
Why does this work? The user has already felt value before being asked for anything. Treat that as a company claim, not a tested result you can copy for your product.
There is a trade-off. Asking for sign-up late means the company may collect fewer email addresses to bring users back. One analysis points out this cost, but also argues that letting people try the app quickly is a strong way to keep them.
Tip
Copy the principle, not the screens. Ask: what is the smallest real task that proves the product is worth it, and can a new user finish it in a couple of minutes?
How do you measure and improve the tutorial?
A tutorial is a design, so it needs testing like any other screen. A common mistake is to ship a tutorial and assume it works because it looks nice. Instead, track a few numbers and change the tutorial when they tell you something is wrong.
Start with the first key action. Pick the single action that best predicts whether a user will keep using the product. One guide suggests choosing the first lesson, first booking or first saved item, depending on the product. This is the action your tutorial should lead to.
What should you track?
Completion rate
How many users finish the tutorial. A high number is good only if the users then do the key action.
Skip rate
How many users close the tutorial early. A high skip rate often means the tutorial is too long, too early or badly timed.
Time to first key action
How long a new user takes to do the main task. This is the measure that shows whether the tutorial helped at all.
Nielsen Norman Group's research on mobile tutorials compared users who read a tutorial with users who skipped it. They measured task success, how easy people said the task felt, and how long it took. They found the tutorial did not make people more successful, and that it could make the task feel harder. This is why you should measure the real task, not just whether people looked at the tutorial.
Tip
Watch the three numbers together. Completion can be high while time to first key action stays the same. That means people finish the tutorial but still do not act.
How do you revise a tutorial?
- 1
Name the key action
Write one sentence that says what a successful first run looks like.
- 2
Record the starting numbers
Note completion, skip rate and time to first key action before you change anything.
- 3
Change one thing
Shorten the text, move the hint to the right screen, or replace a slideshow with an empty-state prompt. Changing several things at once hides what worked.
- 4
Test the change fairly
Compare the old and new versions with similar groups of new users. The module's testing lessons cover how to run and read these tests in more depth.
- 5
Keep, revise or remove
If the new version gets users to the key action faster, keep it. If it does not, try another change or remove the tutorial, since no tutorial may be the best choice.
Why ask users directly?
Also ask users directly. A few short comments from new users, or watching one person try the first run, can show a confusing step that the numbers miss.
Common mistakes to avoid
Long upfront slideshows
Users want to start quickly. A slideshow before the first action delays the task and is often skipped without being read.
Chains of tips
Showing several hints in a row overloads the user and makes the app look harder than it is. Show one hint at a time.
Teaching too early
A hint shown long before the user needs it is forgotten. Show it when the user reaches the screen it describes.
Popups that look like ads
Pop-up tutorials can be mistaken for advertising, so users close them without reading.
No way back
If a skipped tutorial cannot be found again, users who need it later are stuck. Keep a help entry point.
Key takeaways
A good tutorial is short, shown in context, and built around one real action. It helps a new user do the thing the product is for, then gets out of the way. Choose the format that fits the task, offer a skip, and measure whether new users reach their first key action.
Quick check
Your budgeting app has a 6-screen intro slideshow at launch. About 70 percent of users skip it, and then never add their first expense. What would you change, and why?
Quick check
A team's tutorial shows 85 percent completion, but the time it takes new users to add their first expense has not changed. What does this most likely mean?
Sources
- NN/G: Mobile-App Onboarding: An Analysis of Components and Techniques
- NN/G: Mobile Tutorials: Wasted Effort or Efficiency Boost?
- NN/G: Instructional Overlays and Coach Marks for Mobile Apps
- NN/G: New Users Need Support with Generative-AI Tools
- UserGuiding: In-app Tutorials: Get In App Guidance Right
- Userpilot: 12 Web and Mobile App Onboarding Best Practices
- Qubika: Onboarding UX: Best practices and design tips for apps
- Appcues: The essential guide to mobile user onboarding
- Justinmind: User onboarding: best practices and 20 good examples
- Product Fruits: User Onboarding Guide: Strategies, Tools & Best Practices
- UXCam: 16 App Onboarding Examples (2026) and Why They Work
- Medium: Product Breakdown: 3 Learnings from the Duolingo App
- The UXologist: How Duolingo guides a long first-use journey
- Design Studio UX: Mobile App Onboarding: 11 Best Practices & Examples
- Wikipedia: User onboarding
Last updated on 17 November 2026
Related lessons
- UI/UX basicsPrime User-Relevant Associations: Show Cues That Match What Users Care About
- UI/UX basicsStatus Reports: Tell Users What the System Is Doing
- System designBackground Jobs: Doing Slow Work Outside the User's Request
- System designSecurity: Only the Right Callers Reach the Right Data, and Breaches Stay Small
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.