Send it back, or approve?
The pilot with no way to fail
The situation
New-account onboarding has been a known problem for three quarters: users sign up, land on an empty dashboard, and a meaningful share never configure anything. It has been discussed in three planning cycles without a fix shipping. Marcus's Guided Setup plan is approved by Engineering, Design and Support, with kickoff on Monday.
Marcus Aliyev · Product: “Three teams have signed off and we kick off Monday. Anything you need from me before then?”
The plan is the most complete onboarding document the team has produced: a timeline, a risks table, named reviewers. It lands the Friday before kickoff. Choose one part to read closely, then decide what goes back.
What you can see
E01 · Approach and timeline
Build a five-step wizard (data source, invite, first view, notification prefs, tour) over six weeks and roll it out to 200 new accounts. Weeks 1–2 build steps 1–3; weeks 3–4 build steps 4–5 and help content; week 5 instrumentation and QA; week 6 rollout; weeks 7–8 monitor and gather feedback; week 9 readout and rollout recommendation.
E02 · Success criteria as written
Positive qualitative feedback from pilot users. Improved step-level completion through the wizard. Increased early engagement in the pilot cohort. Learnings documented and shared with the wider team.
E03 · Measurement
The plan tracks wizard step completion, time-to-first-view and 7-day engagement in the pilot cohort. The objective is stated as 'improve the new-account onboarding experience and increase early engagement'.
Step 1 of 2
What do you read closely before replying?
Your first choice is kept. Changing your mind later counts as a retry.