BoardSnap is an iOS app that reads onboarding flow whiteboards and turns step sequences, decision points, aha moments, and drop-off risks into a structured onboarding document with design and engineering action items.
Onboarding flow design happens on whiteboards. The team sketches the steps, debates where to ask for permission, argues about when to show the aha moment, maps the email sequence alongside the in-app flow. It's a spatial, collaborative problem that whiteboards handle well.
Then the board has to become a spec. Someone takes a photo and tries to translate a complex multi-path flow into a linear document — losing the branching logic, the decision points, the 'if user does X, go to Y' connections.
BoardSnap reads the flow structure, including the branching paths.
The ideal user journey from sign-up to first value. Each step as a box: the action the user takes, the screen they see, the progress marker. Keep the happy path as a straight line across the board.
Diamond shapes at forks: 'Did user complete profile?' → Yes: continue / No: prompt. Label both paths. Decision points are where most onboarding flows go wrong — capturing them explicitly prevents missed engineering cases.
Circle the moment where the user first experiences the product's core value. This is the most important step in the flow — BoardSnap flags circled items as priority elements.
Below or above the in-app flow, map the email/notification sequence: day 0, day 1, day 3, day 7. Connect emails to the in-app steps they support. BoardSnap reads these as parallel tracks.
Mark steps where you expect drop-off with a flag. Write the mitigation: in-app tooltip, email re-engagement, simplify the step. Mitigation notes become action items.
BoardSnap reads the happy path, decision points, aha moment, email sequence, and drop-off risk mitigations as a structured onboarding spec.
An onboarding flow document: step-by-step happy path with screen names and user actions, decision point map with both path outcomes, aha moment highlighted, parallel email/notification sequence, and drop-off risk mitigations as action items. Engineering and design action items are separated for appropriate teams.
A team redesigning their onboarding after a cohort analysis showed 60% drop-off at step three. The whiteboard mapped the current flow and the redesigned flow side by side. BoardSnap captured both and generated twelve action items — seven for engineering, five for copy and design.
Not product onboarding — customer success onboarding. A CSM team mapped the first-ninety-days customer journey: kickoff, training, first review, expansion trigger. BoardSnap's output became the CSM playbook for new accounts.
Yes. BoardSnap AI reads labeled arrows and decision points. Use clear labels: 'YES →', 'NO →', 'IF completed →'. The more explicit the labels, the more accurately BoardSnap captures the branching logic.
Snap each board with a label at the top: 'Onboarding Flow - Part 1 of 2.' The project accumulates all boards, and the project AI chat can synthesize the full flow across parts.
Yes. Employee onboarding flows — from first day through ninety-day checkpoint — follow the same diagram structure. The steps, decision points, and milestones map identically. BoardSnap captures both contexts equally well.
Every time cohort retention data shows a significant drop at a specific step. Monthly for early-stage companies still iterating on onboarding; quarterly for stable products. Snap the revised flow after each review and accumulate versions in the project.
Snap the board, ship the action items in ten seconds.