Direct answer
User onboarding is activation, not a tour: its job is to get a new user to their first real result as fast as possible.

User onboarding: what to know
Each rule is listed with its source at the end of this page, read on November 12, 2026.
- Split onboarding from setup: onboarding runs from signup to the moment the product works, and setup runs from there until the user is live on real work.
- Identify the single moment of value, such as the first generated result, and cut every step that does not move the user toward it.
- Prefer sensible defaults to a setup wizard; let users refine settings after they have seen the product work.
- Where the product can show value without an account, put the signup wall after the user has made something.
- Infer the user's segment from one input, such as a company URL or work email domain, instead of a survey.
- Ask an onboarding question only when its answer changes what the user sees next.
- A first-use empty state names what is missing, says why, and gives the one action that fills it.
- Keep a getting-started checklist to three to five items, ordered by value, with progress shown as 2 of 4 complete.
- Let users dismiss or collapse the checklist.
- Prefer inline hints beside the work to blocking modals, and make any tour skippable in one action.
- End onboarding with the result and one next action into setup.
Onboarding and setup are two phases
| Phase | Its job | How to measure it |
|---|---|---|
Onboarding | Its job Show the product working with no effort from the user | How to measure it Share of new users who reach the first result |
Setup | Its job Connect the real data and tools the user will keep | How to measure it The user is live on one real workflow |
Empty states | Its job Teach each screen on first use | How to measure it The one action that fills it gets used |
Checklist | Its job Turn setup into a finite list | How to measure it Usage, not completion |
Re-onboarding | Its job Introduce new features to existing users | How to measure it One hint at the point of use |
Put User onboarding into practice
- Name the single moment of value for the product.
- Remove or defer every step between signup and that moment.
- Seed the first run with sample data or a template the user can edit or clear.
- End the first run with the result and one next step into setup.
- Measure the share of new users who reach the first result.
User onboarding in four steps
The four steps, in the order you take them.

- Step 1: Name the moment of value
- Step 2: Cut the steps before it
- Step 3: Show the first result
- Step 4: Hand off to setup
Caveats to keep in mind
- Setup placed before the first result is a wall in front of an unproven product.
- A finished checklist next to an unused product means the checklist counted the wrong thing.
- A returning user should never be dropped back into the welcome tour.
- A tour the user cannot leave with the keyboard strands them.
Steal this workflow
Run this guide in your own assistant. The prompt carries the guide link and the workflow summary, so the assistant can adapt it to your project.
Read the guide "User onboarding: get new users to first value, not through a tour" at https://better-design.com/blog/user-onboarding and help me apply it to my project.
User onboarding is activation, not a tour: its job is to get a new user to their first real result as fast as possible.
Start by asking what I am building and which tools I use. Then walk me through the workflow step by step, adapted to my answers.Claude and ChatGPT open with the prompt filled in. Gemini copies the prompt to your clipboard first, so paste it when the app opens.
Questions
What are onboarding best practices?
Get the user to one real result before anything else, use defaults instead of configuration, ask only questions that change the next screen, and end with one clear step into setup.
What belongs on an onboarding checklist?
Three to five items ordered by value, where the first item produces a visible result, with progress shown as a count and a way to dismiss it.
Can a coding agent apply these onboarding rules?
Yes. Put these rules in the agent's instructions before it builds, then ask it to check the rendered screen against each one.
Where these rules come from
Each fact comes from Better Design's onboarding guidance, the same guidance its MCP server gives coding agents, read on November 12, 2026.
Related
Build the interface in your own code instead
A coding agent such as Claude Code, Cursor or Codex can build these screens in your own code. Better Design gives that agent a design system, interface principles and review rules, so the result follows rules like these and looks designed.