Turn the kickoff minutes into a plan for the onboarding redesign.

Here’s a plan for the Halcyon onboarding redesign, drafted from the kickoff minutes.Source 1: Minutes of meeting: Halcyon kickoff It covers the goal and the approach from the project brief,Source 2: Project brief: onboarding redesign the action items agreed in the kickoff thread,Source 3: Thread in #halcyon-kickoff and the sprint dates from the planning email.Source 4: Re: Halcyon sprint dates Select any part of the document to change it.

The agent can make mistakes. Check important details.

Onboarding redesign planDrafted from 6 sources

Halcyon onboarding redesign

Goal

The onboarding redesign aims to lift week-one activation from 31% to 40% by the end of the quarter.Minutes of meeting: Halcyon kickoffQ4 roadmap: growth team

Background

Today a new team signs up, lands on an empty dashboard and is left to find the invite flow, the template gallery and the integrations on its own. Fewer than a third of teams create a shared project in their first week, and most of the ones that do not never come back.

First-week support tickets tell the same story: people do not know what to do first, and the product does not tell them. The redesign answers that question on the first screen.

Approach

The new flow ships behind a feature flag and runs as an A/B test against the current one, with the analytics events kept identical so the numbers compare cleanly between the two.Project brief: onboarding redesignOnboarding flow v3

The flow

  1. A welcome step asking what the team is here to do, with three answers and a skip.
  2. A starter project built from that answer, so the first screen is never empty.
  3. An invite step in context, with the link already on the clipboard.
  4. A checklist in the sidebar until the first shared project ships.

Success metrics

  • Week-one activation: new teams that ship a shared project within seven days.
  • Time to first invite, measured from signup.
  • First-week support tickets tagged onboarding.

Action items

Three action items came out of the kickoff, each with an owner and a date. Anything that will not fit someone’s bandwidth gets raised before Thursday.Thread in #halcyon-kickoff

TaskOwnerDue
Review the wireframes and lock the flowMayaFri, Oct 23
Instrument the activation eventsDevWed, Oct 21
Write the experiment planPriyaThu, Oct 22

Timeline

  • October 23: wireframes reviewed and the flow locked.
  • October 26: the first sprint starts.
  • November 9: starter projects and the invite step reach staging.
  • November 23: the A/B test opens to 10% of new teams.
  • December 7: the new flow launches to everyone.

Next steps

Progress is reviewed at Thursday’s sync along with the first prototype, ahead of the first sprint starting Monday, October 26.Re: Halcyon sprint dates

Dependencies

The welcome step needs the template service platform is shipping on November 2, and the invite step reuses the share dialog the collaboration team is rebuilding this quarter. Both teams have a reviewer on the kickoff thread.

Out of scope

Paid-plan trials, the mobile apps and the enterprise admin console stay as they are.

Risks

If the flag ships before the activation events are instrumented, the test measures nothing, so Dev’s Wednesday date is the one to protect. The redesign also lands in the same sprint as the billing migration, which shares two of its reviewers.Thread in #halcyon-kickoffQ4 roadmap: growth team

Open questions

Whether teams invited by a teammate skip the new flow, and who owns the welcome email once it moves out of lifecycle marketing.Minutes of meeting: Halcyon kickoff

Upgrade to Kobra Pro

Get full access to the library, or take just the component you came for.

Get Pro