Priorities

it takes a position.

Turns context into priorities and product decisions.

Memos

DraftIn review

Prioritize onboarding

Drafted by Selixa · Sep 25 · 3 min read

01Problem

New workspaces stall at the integrations step. 38% never finish setup, and activation is down 8% since the Aug 12 release.

02Evidence

  1. 4customer calls name the integrations step.MeetingProduct review · Sep 24 · 02:41“People still stall at the integrations step.”Open in Meetings
  2. 7feedback notes say onboarding takes too long.IntercomIntercom · 7 notes“Onboarding takes too long.”Open in Research
  3. 3competitors ask for integrations after the first project.ResearchResearch brief · Onboarding“3 of 6 competitors ask for integrations later.”Open in Research
  4. 9%Setup completion fell 9% the week of the release.PostHogPostHog · Setup completion“62%, down 9% since Aug 12.”Open in Analytics

03Options considered

  1. Shorter first-run flow, integrations after the first project.Recommended
  2. Guided setup call for every new workspace.LaterLater: worth testing once v2 ships.
  3. Revert the Aug 12 integrations step. (rejected)RejectedRejected: teams that connect tools early retain better. Reverting fixes setup and hurts retention.

and it defends it.

04Recommendation

Ship a shorter first-run flow and ask for integrations after the first project.

05Impact

Recovers most of the activation drop within two release cycles. Measured weekly. Analytics

06Next steps

  1. Draft the requirement
  2. Size it with engineering
  3. Review on Thursday
Recommendation: prioritize onboardingCreate roadmap itemDraft PRD

stop guessing what to build next.

Get a recommendation you can argue with.

Works with Slack, Linear, Notion and the tools you already use