User flow whiteboards — every branch captured before you open Figma.
User flows designed on whiteboards move faster than those designed in Figma first. BoardSnap captures the flow — happy path, branches, edge cases — so you have a complete reference when you sit down to design.
Why designers love this workflow
Designers who sketch user flows on whiteboards before opening Figma make better design decisions — the whiteboard's low fidelity forces you to think about flow, not pixels. But the whiteboard flow needs to survive as a reference document when you're deep in the Figma file and questioning what a particular branch should do.
BoardSnap preserves the whiteboard flow in a structured format. Snap the user flow and get a step-by-step description: each screen state, each decision point, each branch condition, and each edge case. The flow is documented in the detail you actually drew it — not simplified to fit in a meeting notes summary.
The exact flow
- Sketch the happy path first
Draw the main user journey from start to success. Label each step and decision point clearly — these labels are what BoardSnap reads as the flow steps.
- Add branches and edge cases
From each decision point, draw the branches. Label each branch condition: 'if logged in → step 4, if not → sign up flow.' BoardSnap reads labeled branches as conditional flow steps.
- Annotate complex interactions
Where a step has a complex interaction — a modal, an animation, a multi-step form — write a brief annotation. These notes become the design specification for that interaction.
- Mark the error states
Write each error state as a branch from the step that can fail. Label the error and the recovery path. Error states are easy to skip — the whiteboard forces you to address them.
- Snap the completed flow
BoardSnap reads the full flow structure — steps, branches, annotations, error states — and produces a written flow description you can reference while designing in Figma.
What you'll get out of it
- Complete flow documentation before Figma is opened — design with a reference, not from memory
- Decision branches and conditions captured explicitly
- Error states documented at the flow design stage, not discovered in QA
- Interaction annotations captured as micro-spec notes
- Flow history as designs evolve — compare the original flow to the shipped version
Frequently asked
Can BoardSnap read a user flow with many overlapping arrows?
BoardSnap AI reads labeled arrows and connectors. Dense flows with many crossing lines are harder to read — draw the flow with labeled waypoints and minimize crossing arrows for best results.
Should I document the user flow in BoardSnap or just use Figma's flow tools?
Both serve different purposes. The whiteboard BoardSnap capture documents the design thinking phase — why certain branches exist, what was considered and rejected. Figma's flow tools document the final implementation. Keep both.
Can I use the BoardSnap user flow summary to write acceptance criteria for the engineering handoff?
Yes. The step-by-step flow description plus the branch conditions and error states map directly to acceptance criteria. Copy the relevant sections into your engineering handoff doc.
Designers: try this on your next user flow.
Three taps. Action items in your hand before the room clears.