esc
  • WorkflowsPages
  • Case studiesPages
  • Machine Learning FoundationsLearn
  • AI EngineeringLearn
  • AI Guardrails & Red TeamingLearn
  • UI/UXLearn
  • Design SystemsLearn
  • Production System DesignLearn
  • Book a callContact
  • Download ResumeContact
Let’s talk

I’ll build the agent for it.

Educate and Encourage Users Without Lecturing Them

Teach people how your interface works at the moment they need it, and give them reasons to keep going.

In short

Educate and encourage users by teaching how your interface works at the moment they need it and giving them reasons to keep going.

4 min readFree

What You Will Learn

Good design teaches people how to use a product. It also makes them feel able to try. This lesson shows three ways to do both: show less at the start, teach by doing, and explain why each step helps the user.

Key words

Onboarding
The first steps a new user takes in a product, such as a welcome screen or a setup flow.
Tutorial
A set of instructions that walks a user through a product, often in a fixed order.
Progressive disclosure
Showing the most needed options first and revealing the rest only when the user asks for them or needs them.
Contextual help
Short hints that appear right where the user is working, at the moment they are working there.

Why teach at all?

New users arrive with a goal and little patience. A common description of user onboarding says its purpose is to help people grasp a product's key ideas and see how it can be useful to them. If the value stays hidden, people give up early.

A widely cited analysis, reported by one design blog, says the average app loses a large share of its daily users within three days of installation. The source reports this loss but does not give its cause.

Why show less at first?

Progressive disclosure is a pattern that hides advanced or rarely used features on a second screen. The goal is an interface that is easier to learn and makes fewer mistakes. Expert users can still reach everything.

  • Start with the core

    Show the few options most people need on the first screen.

  • Reveal on request

    Put advanced options one tap away, for example behind a More button.

  • Keep it shallow

    Avoid nesting menus deeper than two levels. One design guide, citing Nielsen Norman Group research, says people get lost when they move between many layers.

See the Idea in Code

The sample below splits a menu into two parts. The first three items show at once. The rest wait until the user looks for them.

Python
menu = ["Home", "Search", "Profile", "Settings", "Billing", "Export"]
shown = menu[:3]
hidden = menu[3:]
print("Shown first:", shown)
print("Hidden until asked:", hidden)

Output

Shown first: ['Home', 'Search', 'Profile']
Hidden until asked: ['Settings', 'Billing', 'Export']

How do you teach by doing?

Reading about a feature helps less than trying it. Apple's guidelines encourage interactive onboarding, where people can safely test an action, find a feature, or try a game mechanic.

  1. 1

    Pick one task

    Choose the single action that matters most, such as making a first item or saving a first file.

  2. 2

    Let the user press the real control

    Use the actual button, and make sure the user can undo the result easily.

  3. 3

    Show what changed

    Point to the result so the user sees that the step worked.

Where should tips go?

Apple suggests a set of context-specific tips instead of one long flow. When an tip explains a part of the screen, it should sit near that part.

Tip

Show a hint once, close to the control it explains, and let the user dismiss it. Do not repeat it on every visit.

How do you encourage the user?

Encouragement comes from a clear promise, a short path, and an easy way out. Apple's guidelines ask for onboarding that is brisk, entertaining, and skippable, and only when it is truly needed.

  • Fast

    Keep the flow short so people can start using the product right away.

  • Fun

    Apple's guidance says that when onboarding is quick and entertaining, people are more likely to finish it.

  • Optional

    Let people skip the lessons. Never hide the product behind them.

Explain Before You Ask

If your app needs private data or a device permission before it works, ask during onboarding. Explain what the user gets in return.

Ask only for what you truly need. If a feature does not need the user's location, do not ask for it.

Check Yourself

Quick check

A new user opens a photo app for the first time. Which onboarding choice best follows this lesson?

Sources

How is this lesson?

Last updated on 17 November 2026

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.