Insight 1. [Customers wanted a useful first outcome, not a complete configuration.]
Case study · [Company] · [Year]
[Rebuilding onboarding around first value]
[Turning a fragmented setup journey into a clear path to the moment customers first experience value.]
My role
[Strategy through launch]
Team
[X engineers, X designers]
Timeline
[X months]
Stakeholders
[Growth, Sales, Support]
TL;DR for busy readers
[−XX%]
Time to value
[+XX pts]
Activation
[+XX pts]
Retention
[Customers were abandoning a setup process that asked too much before delivering value. I led a focused bet on guided onboarding, cutting everything that did not support the first activation milestone. The launch improved activation and retention, while reducing the support burden.]
01 · Context
Where the business was
[At [Company], a [stage] business in [market], the core product was growing but onboarding had not kept pace. New customers faced an expanding set of configuration steps. Improving early value became critical to the next phase of growth.]
02 · Problem
What was broken, in numbers
[Only [XX%] of new accounts reached the activation milestone. Funnel analysis showed the largest drop at [step], but interviews revealed a deeper cause: users could not connect setup work to the outcome they had signed up for.]
Goal I set:
[Reduce median time-to-value from [X days] to [X days], without lowering the quality of activated accounts.]
03 · Discovery
What I learned
[Combined funnel analysis, [X] customer interviews, support-ticket review and observation of new-account setup.]
Insight 2. [The highest-friction step depended on information users did not yet have.]
Insight 3. [Successful accounts followed a simpler sequence than the official onboarding flow.]
04 · Options & trade-offs
The decision
[We chose a guided activation journey because it directly addressed the root cause within [timeframe]. I cut advanced configuration from launch scope, agreed on guardrails with engineering, and aligned leadership around one measurable activation goal.]
05 · Solution
What we shipped
[Caption: explain the key product change shown above.]
[We introduced a guided first-use flow, moved optional configuration until after activation, and added contextual support at the most difficult step. Each change was tied to a specific discovery insight and a measurable point in the funnel.]
06 · Execution
How we got it out the door
- 01
[Released to a small customer cohort, then ran an A/B test with activation and downstream retention guardrails.]
- 02
[An integration dependency slipped. We isolated the dependency and shipped a narrower flow without compromising the core outcome.]
- 03
[Aligned Growth, Support and Engineering around a shared weekly activation review and a clear rollout decision.]
07 · Results
Impact
[X → X days]
Time to first value
[XX → XX%]
Activation rate
[XX → XX%]
Retention
[The new flow improved activation and reduced time-to-value for the target segment. The commercial impact was [outcome]. We saw less movement in [segment], where an integration prerequisite still limited progress; that became the next discovery focus.]
08 · Reflection
What I’d do differently
[I would bring Support into discovery earlier. Their view of repeated confusion would have helped us separate product friction from missing customer context sooner.]
[Brought focus to a sprawling problem and helped the team deliver a clear, measurable customer outcome.]