HeadspaceDiscovery5 min readAsking why before showing anything
An onboarding survey that doubles as a promise about what the app will do.
- The surface
- The first run experience: the reason for use question, the experience level question, the reminder setup, and the first recommended session.
- What the user wants
- I am stressed and sleeping badly. I want something that works tonight, and I do not want to read a manual about meditation.
The reason for use question
Headspace onboarding has long opened by asking what the person is hoping to get from the app, offering options such as stress, sleep and focus rather than starting with content.
Intent capture before content
A meditation library is undifferentiated until you know why someone opened it, and the user knows their reason far better than any behavioural signal will reveal in week one. Asking converts a browse problem into a recommendation problem. The question also frames the app as a solution to a named problem rather than a practice to take up.
Naming the goal back to the user
The stated goal is reflected in the language of the following screens and in what gets recommended first.
Commitment and consistency
Once someone has said out loud that they are here to sleep better, behaviour that matches that statement feels natural and abandoning it feels inconsistent. Repeating the goal back also proves the question was not decorative. Users stop answering onboarding surveys honestly the moment they suspect the answers go nowhere.
The experience level question
New users are asked how much meditation they have done before, and complete beginners are routed toward a foundational course rather than the full library.
Segment at the door
A beginner and an experienced practitioner want opposite things from the same catalogue, and getting that wrong in the first session is usually fatal. One question separates them cheaply. It also gives the beginner permission to start at the beginning instead of feeling behind.
The guided first session
The first experience is a short guided session with a voice explaining what to do, rather than a timer or an unguided sit.
Lower the bar to the first success
Someone who has never meditated does not know what success looks like, so an empty timer is an invitation to conclude they are bad at it. A voice removes every decision from the activity. The point of session one is to prove the thing is doable, not to be impressive.
Reminder setup inside onboarding
Onboarding asks the user to choose a time for a daily reminder while they are still in the setup flow.
Implementation intention
Naming a specific time turns a vague wish into a plan, and plans with a time attached are acted on more often than intentions without one. Asking during onboarding catches the user at peak motivation, which is the only moment they will happily accept a daily notification. The reminder is then a trigger the user chose, not one imposed on them.
The paywall after the first taste
Headspace has long offered a limited free starting course with the wider library behind a subscription, with the trial offer presented after the user has experienced a session.
Value before the ask
A paywall shown before any experience asks the user to price something they have not felt. Placing it after a completed session means they are evaluating a known quantity. It also means the people who see the offer are pre-filtered for having finished something.
Asking why, then proving it mattered
What not to copy
- The intake survey is only as good as the routing behind it. If choosing sleep and choosing focus lead to broadly similar catalogues, the questions become theatre and the user learns to skip them.
- Stated goals are unreliable. People say they want focus and actually want to stop feeling anxious at midnight, so a product that over-trusts the answer will personalise confidently in the wrong direction.
- Asking for daily reminder permission at peak motivation is effective and slightly opportunistic. The user is agreeing on behalf of a future self who will be far less enthusiastic about a nightly notification.
- Streak and progress mechanics sit awkwardly on a practice about self-compassion. Making someone feel they have failed at relaxing is a real risk in this category, and it is the easiest retention lever to reach for.
The takeaway
Ask users what they came for only if the next screen will visibly change because of their answer.
Finished the teardown? Bank it and the day counts toward your run.
Where the principles come from
- Influence: The Psychology of Persuasion (commitment and consistency), Robert Cialdini
- Tiny Habits (anchors and implementation intentions), BJ Fogg
- Competing Against Luck (jobs to be done), Clayton Christensen
- 10 Usability Heuristics for User Interface Design, Jakob Nielsen, NN/g
Written from public behaviour of the product, not from inside it. Interfaces change often, so treat the flow described here as of the time of writing and check the live product before quoting it.