Onboarding is where first impressions get designed: how quickly can a new user go from signup to productive? We captured 90 onboarding steps across Notion, Slack, Figma, Linear, GitHub, Asana, Airtable, and Atlassian, covering signup flows, verification, profile setup, use-case selection, team invites, plan selection, tutorials, and first-action prompts. The data shows wide variation in flow length (4 steps for GitHub, 16 for Asana) and approach (Airtable uses conversational AI, Linear has an interactive command menu tutorial, most use traditional stepped forms).
Signup & Verification
Every system in the study offers email-based account creation. 7 of 8 also offer Google SSO on the signup page, with Atlassian providing the widest SSO selection (Google, Microsoft, Apple, Slack). Notion goes further with passkey and SAML support. The consensus pattern is email field first with SSO options positioned below or as equal-weight alternatives.

Default to email as your primary signup input with Google SSO as the minimum secondary option. Position SSO buttons below or alongside the email field, never as the only path.
Signup & Verification
Across all 89 onboarding instances, 'Continue' appears as the CTA verb in roughly 40% of steps. Notion, Slack, Figma, Linear, Asana, Airtable, and Atlassian all use it for progression. GitHub is the sole outlier, using 'Create account' and 'Sign in' instead. Final steps tend to shift to 'Get started', 'Open Linear', or 'Finish'.

Use 'Continue' as your default onboarding progression verb. Reserve action-specific verbs like 'Create workspace' or 'Send invites' for steps where the CTA triggers a distinct action beyond advancing.
Signup & Verification
Notion, Slack, GitHub, Asana, and Airtable require entering a six-digit code sent to the user's email. Linear uses a magic link by default with manual code entry as fallback. Figma and Atlassian skip separate verification entirely, handling it through SSO or inline. Slack and GitHub split the code into six individual input boxes; Asana uses a single text field.

Use a six-digit email verification code as your default. Show the email address the code was sent to, provide a resend link, and consider quick-access buttons to open Gmail or Outlook.
Signup & Verification
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →Profile & Workspace Setup
Notion, Slack, Figma, and Airtable ask for just a display name during profile setup, keeping friction minimal. Asana adds a password field. Linear skips name entry entirely and asks users to choose a UI theme instead. Avatar upload is optional across all systems, with 3 of 6 auto-generating an initial-based placeholder.

Collect only the display name during profile setup. Make avatar upload optional with an auto-generated initial as the default. Pre-fill the name from the email prefix to reduce typing.
Profile & Workspace Setup
Slack, Linear, and Atlassian are the only systems that ask users to name a workspace and configure a URL during onboarding. The remaining 5 systems create workspaces implicitly. Linear includes a region selector (United States, Europe) alongside the workspace URL. Atlassian pre-fills a subdomain from the user's email with a green checkmark confirming availability.

Create workspaces implicitly unless your product genuinely requires user-defined naming. If you need an explicit step, pre-fill the workspace name from the user's email domain and validate URL availability inline.
Profile & Workspace Setup
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →Personalization & Use Cases
Notion, Figma, Asana, and Atlassian collect use-case data during onboarding. Figma asks the most questions across 5 separate screens (use case, job role, work setting, org size, prior experience). Asana consolidates three questions onto a single page using dropdowns. Notion uses a simple three-card selector ('For work', 'For personal life', 'For school'). Atlassian uses a 14-option icon grid.

Limit use-case questions to 1 to 3 screens. Use pill buttons or cards for selection instead of dropdowns. Consolidate related questions onto a single screen when possible.
Personalization & Use Cases
Figma dedicates 5 onboarding screens to personalization: use case, job role (10 options), work setting (freelance, company, agency, other), organization size (5 tiers from 'Just me' to 'Over 5,000'), and prior Figma experience. Each screen uses pill-button options with a progress bar and back button. The canvas preview updates dynamically as users make selections.

If you ask multiple personalization questions, use a progress bar and back button on every screen. Update a live product preview to show users how their answers shape the experience.
Personalization & Use Cases
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →Team Invites
Notion, Slack, Figma, Linear, Asana, and Atlassian include team invitation during onboarding. Every system makes it skippable. GitHub and Airtable skip the step entirely. The standard pattern is 3 email input fields with placeholder examples and a copy-invite-link alternative. Atlassian pre-generates the invite URL with a copy button.

Include a team invite step with 3 email fields and a copy-link alternative. Always make it skippable. Use social framing like 'Who else is on your team?' rather than imperative verbs.
Team Invites
Slack and Asana intercept skip attempts with a modal that discourages proceeding alone. Slack says 'To really get a feel for Slack, you'll need a few colleagues here.' Asana shows a tandem bicycle illustration with 'Asana is more valuable when you collaborate with your team.' Both modals offer a return-to-invite primary CTA alongside the skip option.

Use a skip-confirmation modal to add friction without blocking. Frame the message around product value rather than guilt. Show social proof or a visual metaphor to reinforce the team benefit.
Team Invites
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →Plan Selection & Upsells
Notion, Slack, Figma, and Atlassian include plan selection as an onboarding step. All four offer a free tier or trial with no credit card required. Notion and Airtable use strikethrough pricing ($24 to $0, $20 to $0) to emphasize the trial value. Figma shows a three-tier comparison with a 'Most popular' badge. GitHub, Linear, Asana, and Airtable defer pricing conversations entirely.

If you include plan selection during onboarding, always offer a free tier or no-credit-card trial. Place it after profile and use-case steps, before entering the product.
Plan Selection & Upsells
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →Plan Selection & Upsells
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →Tutorials & Guided Onboarding
Slack and Linear are the only systems with explicit tutorial content. Slack shows a 3-slide modal carousel introducing collaboration concepts, channels, and premium features. Linear dedicates 3 steps to its command menu: an introduction with keyboard shortcut illustration, an interactive demo with sample actions, and a 'That was easy!' confirmation. Both use dot pagination for positioning.

If you include tutorial slides, keep them to 3 or fewer. Pair explanatory slides with an interactive step where the user tries the feature, as Linear does with its command menu.
Tutorials & Guided Onboarding
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →First Landing & Empty States
Linear, Asana, Airtable, and Atlassian all create sample tasks or data during onboarding. Linear generates 4 guided issues that double as a tutorial checklist ('Get familiar with Linear', 'Set up your teams'). Airtable's AI cobuilder generates 15 personalized records. Asana pre-populates 3 tasks across To do, Doing, and Done sections. Atlassian creates 2 sample tasks with status and priority columns.

Pre-populate 2 to 4 sample items that serve as both example content and tutorial tasks. Name them after real onboarding actions so completing the task teaches the product.
First Landing & Empty States
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →First Landing & Empty States
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →Flow Structure & Pacing
GitHub has the shortest flow at 4 steps (signup, verification, sign-in, dashboard). Asana has the longest at 16 steps including its 8-step tooltip tour. Excluding tooltip tours, the median flow length is 10 steps. Figma has 13 steps with the most use-case questions. Systems that invest in longer onboarding (Asana, Figma, Atlassian) deliver more personalized first-run experiences.

Target 8 to 12 onboarding steps as a baseline. Each additional step should deliver measurable personalization. If your flow exceeds 10 steps, add a progress indicator.
Flow Structure & Pacing
The dominant sequence is: signup, verification, profile setup, use-case selection, team invite, then entry into the product. The main variations are where plan selection appears (Notion, Slack, and Figma insert it after invites; Atlassian places it before workspace creation) and whether workspace creation is explicit (Slack, Linear, Atlassian) or implicit (Notion, Figma, GitHub, Asana, Airtable).

Follow the consensus sequence: signup, verify, profile, personalize, invite, enter product. Insert plan selection after personalization if needed. Make workspace creation implicit unless your product requires user-defined naming.
Flow Structure & Pacing
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →Decision Frameworks
The consensus signup page uses an email field with a 'work email' label (6 of 8 systems), Google SSO as the minimum secondary option (7 of 8), and 'Continue' as the CTA verb (5 of 8). Marketing opt-in checkboxes default to unchecked in 5 of 6 systems that include them. Legal agreements appear as inline text below the CTA in 7 of 8 systems.

Use 'Continue' as your signup CTA, not 'Create account' or 'Sign up'. Default marketing opt-in checkboxes to unchecked. Place legal text inline below the CTA rather than behind a separate step.
Decision Frameworks
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →Anti-Patterns
GitHub is the only system that requires users to sign in with credentials immediately after creating their account and verifying their email. A green success banner confirms the account exists, but users must re-enter their username and password to proceed. Every other system auto-signs the user in after verification, maintaining forward momentum.

Auto-sign users in after email verification. Never require re-authentication immediately after account creation. The verification step already confirms identity.
Anti-Patterns
Notion (8 steps), Asana (16 steps), and Airtable (10 steps) show no progress indicator during onboarding. Users cannot gauge how much longer setup will take. Slack uses a 'step X of 4' label, Linear shows a 7-dot stepper, and Figma displays a progress bar. Progress indicators reduce abandonment by setting expectations for flow length.

Add a progress indicator to any onboarding flow longer than 3 steps. Use a stepper for flows under 8 steps and a progress bar for longer flows where step count might discourage users.
Anti-Patterns
Data, screenshots, and actionable recommendations. Unlock this and every Pro insight.
See plans →