interaction design
Onboarding
What is onboarding in UX?
Onboarding is the first-run experience that helps a new user get from arriving to their first real success - understanding what the product does, completing a meaningful first action, and reaching the moment they feel its value. Good onboarding gets people to that "aha" quickly with as little friction and explanation as possible; poor onboarding dumps them in, or buries them in tours, and loses them.
Also known as: onboarding, user onboarding, first-run experience
Prefer to watch?
Watch the recap 1:05
The demo
You've just opened a new note-taking app for the first time. Experience the first run two ways - one that strands you, one that walks you to a quick win. See which makes you want to stay.
What this demo shows (text version)
A new note-taking app's first run is shown two ways. In "dumped in", you face a blank, unexplained screen (or a long feature tour to click through) with no clear starting point, so you feel lost and are tempted to leave before getting any value. In "guided", setup is minimal and you're led to one meaningful first action - writing and saving a first note - reaching a quick "aha" where the product's value clicks, with the rest left to learn in context.
That's onboarding's real job: the shortest path to a first success, not a tour of every feature. Reduce setup, guide one valuable action, front-load the payoff, and teach the rest as people need it. Long upfront tutorials and mandatory setup are anti-patterns that delay value and get skipped - reach the aha moment fast and the product earns a chance.
The job of onboarding is to get a new user to value fast, not to explain every feature. People judge a product in the first minutes and abandon if they feel lost or see no payoff, so the goal is the shortest credible path to a first success - the "aha moment" - not a feature tour. Reduce setup to the essentials (defer the rest), guide a single meaningful first action, show progress, and let people learn the rest in context as they need it. Long upfront tutorials, walls of tooltips and mandatory setup are onboarding anti-patterns: they delay value and get skipped. Teach by doing, get out of the way, and front-load the payoff.
Dumped straight in with no guidance, you didn't know where to start and nearly bailed; guided to one meaningful action and a quick win, you "got it" and wanted to continue. Same product - the difference was whether onboarding carried you to value or left you stranded. That first-success moment is the whole job: reach it fast, and the rest of the product gets a chance.
Effective onboarding is organised around the "aha moment" - the point where a new user first experiences the core value - and the activation milestone that reliably predicts retention. The aim is the shortest honest route there: strip first-run setup to what's essential (smart defaults defer the rest), and guide one meaningful action rather than explaining the whole interface. Empty states, sample data and contextual hints teach by doing.
Common anti-patterns delay or replace value with explanation: long carousels of feature screens before anyone has used anything, coachmark overlays plastered over the UI, mandatory profile/setup walls (forced action), and tooltips no one reads. These get skipped and forgotten, and they push the payoff further away - the opposite of what onboarding should do. It also overlaps with shaping (build the behaviour in small rewarded steps) and progressive disclosure (reveal complexity over time).
Design it as a path to first success: minimise required setup, lead to one clear valuable action, show progress and celebrate the first win, and surface guidance in context exactly when it's needed rather than all up front. Different users need different depths, so make help available but not mandatory, and keep teaching as people grow into advanced features. Measure success by activation and early retention, not by tour completion.