Home / Analysis
Onboarding Drop-Off Analysis as a desk craft, not a dashboard skin
This page is the public outline we use when a GB team asks what we actually do. The studio teaches it slowly. You can steal the outline; you cannot skip the recordings.
1. Name the exit
Refuse a single “did not activate” bucket. Split bounce, credential stall, empty workspace, pending human review, and overnight identity queues. If your events cannot support the split, that is the first finding, not a footnote.
2. Keep one person on the table
Choose a timestamped signup that never returned. Reconstruct device, hour, and last screen. Aggregate charts wait until that reconstruction exists, otherwise the room debates averages.
3. Sit through the quiet hour
Watch recordings without pitching solutions. Write colour of toasts, label truncation, and where the cursor hovered. Desire to “just add a tooltip” is noted and postponed.
4. Ask support what the tickets already said
Growth often discovers drop-off six weeks after support has a tag for it. The analysis is incomplete until those tags sit next to the event names.
5. Write the limitation before the recommendation
Sample size, seasonality, sales-assisted accounts, and traffic quality belong above the ask. GB board readers notice when they are missing.
Take it into a taught room
If you want marked maps rather than a sketch, the course list is the next step. If you only need to know whether your tracking plan can support the split, write to the desk with what you can export.