Skip to content
chiltepin

Generated from: “Lay out everything we brainstormed for onboarding v2, grouped around the main idea.

Onboarding v2 — brainstorm

Written by an agent from the skill, validated by chiltepin check, rendered by the renderer — shown as generated, 13 September 2026.

DOCUMENTBRAINSTORM

Onboarding v2 — brainstorm

Every idea from the session, grouped around the one goal they serve.

SECTION 01 · Note

Assumptions

Note
The session notes did not name the product, the metric, or who was in the room. This doc assumes a B2B SaaS workspace product and a goal of first value inside ten minutes. The team is product, design, growth, and one backend engineer. Names of screens and events are invented; replace them with the real ones.

The session produced 24 ideas. All of them serve one goal: a new user reaches their first real result inside ten minutes, without a sales call. The map below groups the ideas by the part of onboarding they change. The quadrant after it ranks them, so the first sprint has a shortlist.

Ideas grouped around the goal

SECTION 02 · Mind map
MIND MAP
Mind map: First value in 10 minutes, 7 branchs, 31 nodesFirst value in 10minutesSign-upGoogle and Microsoft SSOfirstEmail and password moves below the fold.Email and password movesMagic link, no passwordAuto-join by emaildomainAsk for company size androle after first resultWorkspace setupTemplate per role pickedat sign-upSample workspacepre-filled withSkip naming; default tothe company domainData importCSV drag-and-drop withcolumn guessingGoogle Sheets connectorHubSpot and SalesforcesyncPaste a table from theclipboardFirst success momentOne-click first reporton the imported dataShare link to a teammatebefore any setupCelebrate the firstresult once, then neverGuidanceSetup checklist withprogress barThree-step tour,dismissableIn-app assistant answerssetup questionsEmpty states carry thenext actionTeam growthInvite teammates fromthe first screenSlack app install duringonboardingViewer role so inviteesneed no setupMeasurementTracktime-to-first-value perFunnel events on everyonboarding stepExit survey when a userleaves before the first
LegendSign-upWorkspace setupData importFirst success momentGuidanceTeam growth

Four branches change what the user does; Guidance and Measurement change how we learn. The Measurement branch ships first, because it is the only way to know whether the other five worked.

Which ideas earn the first sprint

Effort is engineering weeks; impact is the expected cut in time to first value. Quick wins sit top-left. The CRM sync and the in-app assistant are the two big bets, and each one is a quarter of work on its own.

SECTION 03 · Matrix

Effort vs impact

2×2
QuadrantEffort →↑ Impact on time to first valueDaysQuartersLargeSmallSample workspaceOne-click first reportSSO firstDefer profile questionsEmpty states carry the next actionFunnel eventsCSV with column guessingInvite from first screenHubSpot and Salesforce syncIn-app assistantSlack app installThree-step tourCelebrate the first resultGoogle Sheets connector

Sprint one takes the five top-left items plus funnel events. The two big bets wait until the funnel data says where users still stall.

View the Markdown
```meta
title: Onboarding v2 — brainstorm
subtitle: Every idea from the session, grouped around the one goal they serve.
tag: BRAINSTORM
```

```callout
tone: note
title: Assumptions
body: "The session notes did not name the product, the metric, or who was in the room. This doc assumes a B2B SaaS workspace product and a goal of first value inside ten minutes. The team is product, design, growth, and one backend engineer. Names of screens and events are invented; replace them with the real ones."
```

The session produced 24 ideas. All of them serve one goal: a new user reaches their first real result inside ten minutes, without a sales call. The map below groups the ideas by the part of onboarding they change. The quadrant after it ranks them, so the first sprint has a shortlist.

## Ideas grouped around the goal

```mindmap
center: First value in 10 minutes
nodes:
  - { id: signup, label: Sign-up, accent: blue }
  - { id: sso, parent: signup, label: Google and Microsoft SSO first, note: "Email and password moves below the fold." }
  - { id: magic, parent: signup, label: Magic link, no password }
  - { id: domain, parent: signup, label: Auto-join by email domain }
  - { id: defer, parent: signup, label: Ask for company size and role after first result }
  - { id: setup, label: Workspace setup, accent: teal }
  - { id: template, parent: setup, label: Template per role picked at sign-up }
  - { id: sample, parent: setup, label: Sample workspace pre-filled with realistic data }
  - { id: rename, parent: setup, label: Skip naming; default to the company domain }
  - { id: import, label: Data import, accent: green }
  - { id: csv, parent: import, label: CSV drag-and-drop with column guessing }
  - { id: sheets, parent: import, label: Google Sheets connector }
  - { id: crm, parent: import, label: HubSpot and Salesforce sync }
  - { id: paste, parent: import, label: Paste a table from the clipboard }
  - { id: aha, label: First success moment, accent: amber }
  - { id: report, parent: aha, label: One-click first report on the imported data }
  - { id: share, parent: aha, label: Share link to a teammate before any setup }
  - { id: confetti, parent: aha, label: Celebrate the first result once, then never again }
  - { id: guide, label: Guidance, accent: purple }
  - { id: checklist, parent: guide, label: Setup checklist with progress bar }
  - { id: tour, parent: guide, label: Three-step tour, dismissable }
  - { id: assistant, parent: guide, label: In-app assistant answers setup questions }
  - { id: empty, parent: guide, label: Empty states carry the next action }
  - { id: team, label: Team growth, accent: red }
  - { id: invite, parent: team, label: Invite teammates from the first screen }
  - { id: slack, parent: team, label: Slack app install during onboarding }
  - { id: roles, parent: team, label: Viewer role so invitees need no setup }
  - { id: measure, label: Measurement, accent: gray }
  - { id: ttfv, parent: measure, label: Track time-to-first-value per cohort }
  - { id: funnel, parent: measure, label: Funnel events on every onboarding step }
  - { id: exit, parent: measure, label: Exit survey when a user leaves before the first result }
```

Four branches change what the user does; Guidance and Measurement change how we learn. The Measurement branch ships first, because it is the only way to know whether the other five worked.

## Which ideas earn the first sprint

Effort is engineering weeks; impact is the expected cut in time to first value. Quick wins sit top-left. The CRM sync and the in-app assistant are the two big bets, and each one is a quarter of work on its own.

```quadrant
title: Effort vs impact
xAxis: { label: Effort, low: Days, high: Quarters }
yAxis: { label: Impact on time to first value, low: Small, high: Large }
items:
  - { x: 0.15, y: 0.85, label: Sample workspace }
  - { x: 0.2, y: 0.8, label: One-click first report }
  - { x: 0.25, y: 0.7, label: SSO first }
  - { x: 0.2, y: 0.65, label: Defer profile questions }
  - { x: 0.3, y: 0.6, label: Empty states carry the next action }
  - { x: 0.15, y: 0.55, label: Funnel events }
  - { x: 0.4, y: 0.75, label: CSV with column guessing }
  - { x: 0.45, y: 0.6, label: Invite from first screen }
  - { x: 0.85, y: 0.8, label: HubSpot and Salesforce sync }
  - { x: 0.8, y: 0.6, label: In-app assistant }
  - { x: 0.6, y: 0.35, label: Slack app install }
  - { x: 0.3, y: 0.25, label: Three-step tour }
  - { x: 0.1, y: 0.15, label: Celebrate the first result }
  - { x: 0.7, y: 0.3, label: Google Sheets connector }
```

Sprint one takes the five top-left items plus funnel events. The two big bets wait until the funnel data says where users still stall.