Learnability: onboarding that teaches instead of touring
Learnability is one of the seven UXE criteria: how quickly a first-time user becomes a confident one. Why product tours rarely work, what does, and how to measure time-to-first-value honestly.
Learnability is the criterion that asks how quickly a first-time user becomes a confident one. Teams usually answer it with a product tour — a sequence of tooltips pointing at things — and editors usually find that the tour is the weakest part of the entry.
Why tours rarely work
A tour teaches in the wrong order and at the wrong moment. It explains the interface before the user has a reason to care about any of it, then disappears exactly when the questions start. People dismiss tours for the same reason they skip manuals: they came to do something, and the tour is in the way.
A tour
- Teaches the interface, not the job
- Front-loads everything, remembers nothing
- Blocks the product while it runs
- Can't be re-read at the moment of need
Teaching
- Gets the user to one real outcome
- Explains each thing where and when it's used
- Never blocks — the product is usable throughout
- Stays available when the question returns
Design for the first real outcome
The most useful question in onboarding design is: what is the smallest genuinely valuable thing this person can do in their first session, and how fast can they do it? For a design tool it's a first export; for an invoicing product it's a first invoice sent; for an analytics product it's one real question answered.
- 01
Name the first win
One specific outcome, not "explore the dashboard".
- 02
Remove what's in the way
Defer every setting that isn't needed to reach it.
- 03
Seed the state
Sample data that behaves like real data, clearly labelled and easy to clear.
- 04
Teach at the moment
One line of help where the question arises, not in a tour.
Empty states are your curriculum
The empty state is the only teaching surface you can guarantee every new user will see. A good one names what will appear, explains what it's for, and offers the action. A great one shows an example of what a populated version looks like, so the person can picture where they're going.
It costs an afternoon and it lifts three criteria — learnability, usability and content design — which makes it the highest-leverage screen in most products.
Help at the point of need
- Inline, one sentence. Beside the field that raises the question, not behind an info icon that opens a panel.
- Examples, not definitions. "For example, INV-2026-014" teaches a format faster than a paragraph about formats.
- Answer the question actually being asked. Next to a tax field, the question is usually "do I need this?" — not "what is tax?"
- Let the user find it again. Help that only exists during onboarding fails everyone who returns after a fortnight away.
Confidence compounds
Learnability isn't only about the first session. It's about whether the product teaches its own patterns well enough that the tenth feature is easier than the first. Consistency does most of that work: if a list behaves the same way everywhere, a user who has learned one list has learned all of them.
The best onboarding is a product whose second feature costs nothing to learn because the first one taught it.
Measuring it honestly
| Compared on | Meaningful | Vanity |
|---|---|---|
| Time to first value | Median minutes to the first real outcome | Time spent in onboarding |
| Completion | Reached the outcome without support contact | Finished the tour |
| Return | Came back and did it again unaided | Logged in twice |
| Help | Which questions stopped being asked | Article views |
The most persuasive thing you can put in an entry is a change: "time to first invoice fell from 11 minutes to 4 after we removed the company-profile step from setup and asked for it later." One sentence, one decision, one measured consequence.
What to send
A genuinely new account — not a seeded demo — so we see what a first-time user sees. Your empty states. The moment of first value. And whatever you measured, with the method attached.
Learnability is weighted heavily in Product Experience and AI & Emerging Experience, where nobody has prior expectations to lean on. Enter a project.
Sample data that teaches instead of lying
Seeding a new account with example data is one of the most effective onboarding techniques available, and it goes wrong in a specific way: the sample data behaves differently from real data, so everything it taught has to be unlearned.
- Make sample records obviously samples — labelled, and removable in one action.
- Use realistic volume and realistic mess. Three perfect rows teach nothing about the product at 300.
- Let every sample record be edited and deleted, so exploring is safe.
- Never let sample data silently persist into production reporting.
The second session, which nobody designs
Onboarding design stops at the end of session one. But the moment that decides retention is the return: someone comes back two days later, having forgotten half of it, and has to pick up where they left off.
- 01
Remember where they were
Return them to the work, not to a generic home screen.
- 02
Show what changed
Anything that happened while they were away, briefly.
- 03
Offer the next step
One suggestion based on what they actually did, not a checklist of everything.
- 04
Keep help reachable
The explanation from session one should still be findable.
Questions we get asked
Are product tours always bad?
Not always, but they're usually the weakest tool available. If you keep one, make it skippable, short, and resumable — and put the real teaching in the empty states and inline help where the questions actually occur.
How do we measure learnability?
Time to first real outcome, completion of that outcome without a support contact, and whether people return and repeat it unaided. Onboarding completion rate measures your tour, not your product.
Should onboarding be personalised by role?
If roles genuinely need different first outcomes, yes — but ask one question, not five. A long personalisation quiz before any value is a cost paid up front for a benefit that may never arrive.
What should we send in an entry?
A genuinely new account so editors see a real first run, your empty states, and whatever you measured about time to first value.
- onboarding
- learnability
- scoring
Written by
The UXE editors
The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.
Keep reading
Judging & criteria5 min read
How usability is scored, and why most entries lose points in the first minute
Usability is the heaviest-weighted question in any UX review: can people finish what they came to do? What editors measure, the first-minute failures that cost the most, and the evidence that moves the number.
The UXE editors
Craft & practice6 min read
UX writing that scores: the words editors actually notice
Interface copy decides how competent a product feels. The error messages, empty states, button labels and confirmations that raise a UX writing score — and the habits that quietly lower one.
The UXE editors
Craft & practice5 min read
B2B SaaS UX design awards: judging software people are paid to use
B2B software is judged differently: the user didn't choose it, the data is messy, and the admin screens matter. What we look for in enterprise and B2B SaaS entries, and how to enter one well.
The UXE editors