Notion onboarding: account setup, profiling, team access and product tour
This captured mobile journey starts with account-method selection and email verification, then asks for a profile, intended use, working arrangement, work type, role, company size, interests and planned uses. It then offers team invitations, includes a selected domain-wide joining control, presents a four-part product tour and opens a long mobile getting-started checklist.
The screenshots show a staged sequence and progress indicator; they do not demonstrate commitment, confidence, comfort, reduced drop-off or how the experience is remembered. The important design questions are whether each requested detail has a clear purpose, optional questions can be skipped or changed, marketing and workspace-access choices are fresh and informed, and the tour helps people reach a useful first action without delaying access to the product.
- Captured
- Capture date not recorded
- 17
- Screens
- 1
- Ingredients
- 4
- Applications
Common contexts
Business goals
What works
What the captured flow does well.
- Account access supports several identity providers, passkeys, single sign-on and email verification.
- Profile and profiling questions are separated into focused screens with a consistent progress indicator.
- The interest screen explicitly supports multiple selections and provides a visible Skip action.
- Planned-use options include short descriptions rather than labels alone.
- The team invitation step can be passed without entering addresses and provides a copy-link route.
- The walkthrough separates home organisation, notes and tasks, sharing and device availability into individual topics before opening the workspace.
What could improve
What deserves closer review.
- The flow does not explain why work type, role, company size, interests and intended uses are needed, how they change the product, how long they are retained or where they can be edited.
- Most profiling and tour screens have no visible Skip action, and the progress bar does not state the number or names of remaining steps.
- The marketing control uses a negative opt-out statement inside profile creation instead of a separate, positive and unselected choice.
- Company-size ranges overlap at their boundaries, making values such as 10, 50, 100, 300, 1,000 and 5,000 ambiguous.
- The team screen says Notion works best with others while a domain-wide joining checkbox is already selected; the capture does not explain who can join, their initial permissions or how to reverse access.
- The product tour is a passive Next sequence with no visible skip, back or try-it-now route, then opens a dense checklist rather than one clearly prioritised first task.
Screen-by-screen breakdown
Follow the journey.
Each annotation distinguishes what is visible from our interpretation or hypothesis, then identifies a practical opportunity to investigate.
Screen 01
Choose an account method
Distinguish signing in from creating a new account and say what information each provider shares. Keep passkey, single sign-on and email available without labelling one route as more popular or preferred.
Screen 02
Verify your email
Name the email address receiving the code, provide an Edit email action and explain expiry, resend timing, autofill and recovery from an incorrect or expired code. Announce validation errors without clearing what the person entered.
Screen 03
Create your profile
Explain where the name and optional photo appear and state password requirements before submission. Replace the negative marketing opt-out with a separate, unselected positive choice that is not required to create the account.
Screen 04
Choose how you plan to use Notion
Notion asks how the person plans to use the product on a focused step and shows progress through the wider setup. This is visible staged disclosure; the screenshot does not show whether the question is optional, how the answer is used or whether the sequence improves completion.
Explain how Work, Personal or School changes the initial workspace, allow the question to be skipped and say where the choice can be changed later. Do not imply that one answer is the correct route.
Screen 05
Choose team or solo use
Explain what Team and On my own change, including workspace access and any billing consequences. Let people skip or change the answer later instead of preselecting the most common choice.
Screen 06
Choose your work type
Say why work type is requested and what it changes. Add search and Other, allow Skip, and make the answer editable so people who do not fit the listed roles are not forced into an inaccurate profile.
Screen 07
Choose your role
Notion asks for one role choice on a focused step and shows progress through setup. This is staged disclosure; the screen has no visible Skip action, does not explain how the answer is used and cannot establish reduced effort or drop-off.
Clarify the difference between individual contributor, lead, manager and executive, explain how the answer will be used and provide Other, Skip and later editing. Avoid assuming every workplace uses the same hierarchy.
Screen 08
Choose company size
Use non-overlapping ranges such as 1–9 and 10–49, explain why company size is relevant and allow Skip or later editing. Do not infer a default company size from a previous answer.
Screen 09
Select areas of interest
Keep the visible Skip and multi-select instruction. Explain how selections affect the starting experience, add search, Other and Clear selections, and provide a direct route for changing interests later.
Screen 10
Preparing your workspace
Say what is being prepared and give a useful status if it takes more than a moment. Preserve the person's choices, announce loading accessibly and provide recovery rather than leaving an indefinite “Getting ready” overlay.
Screen 11
Choose what you plan to use Notion for
Keep the short descriptions, but state whether one or several uses can be selected and how the choice affects the workspace. Allow Skip and later editing rather than treating six options as evidence of decision paralysis.
Screen 12
Invite people to the workspace
Default domain-wide joining to off and explain exactly who can join, how they will discover the workspace and what access they receive. Keep Skip, copy-link and direct-invite choices clear, and do not present collaboration as universally better.
Screen 13
Tour: organise your workspace
This walkthrough screen introduces one organisation topic and shows progress through the tour. That is staged disclosure; the capture does not show a Skip route, active practice or whether people understand and retain the explanation.
Show the tour position as a count, provide Back and Skip tour and let people revisit it later. Pair the explanation with an optional try-it-now action instead of adding praise or manufactured urgency.
Screen 14
Tour: notes, tasks and blocks
Keep this topic focused, but provide Back, Skip tour and a way to practise or open the relevant feature. Do not require a passive sequence before the person can reach their workspace.
Screen 15
Tour: share work
This later walkthrough screen introduces one sharing topic while other features remain outside the step. It is a visible staged sequence; its usefulness, optionality and effect on learning would still need to be tested.
Explain what sharing changes and let people try it with a safe example or continue without sharing. Preserve Back, Skip tour and revisit controls rather than assuming this explanation improves learning.
Screen 16
Tour: use Notion on other devices
Use a specific final action such as Open my workspace and keep Back and Skip available. Offer device downloads later in context; do not add celebration solely to manufacture a memorable ending.
Screen 17
Getting started on mobile
Turn the long checklist into a small set of optional first actions based on the person's stated goal. Show completion, dismissal and reset controls, link to help and keep the full workspace usable without finishing the checklist.
Keep exploring