A simple way to understand user flow (without diagrams)
Forget the arrows and boxes. User flow is a story — and you can test it out loud.
User flow, as a discipline, has a PR problem. It comes with diagrams. Rectangles, arrows, conditional branches, swimlanes. Ten minutes in, everyone’s eyes have glazed and the flow is being optimised on paper while the real product still feels confusing.
Here’s a simpler way that works better in practice: tell it as a story. Out loud. Without the tool.
The narration test
Pick a flow — say, a first-time user signing up and reaching their first ‘wow’ moment. Instead of drawing it, narrate it as if you’re describing what happened to a friend.
‘A founder clicks an ad on Twitter. Lands on the homepage. Sees the one-line pitch and a demo video. Watches 20 seconds. Clicks ‘Try it.’ Types an email. Gets a magic link. Clicks it. Lands in a dashboard with three sample items already loaded. Clicks the first one. Sees the output. Says huh.’
If you can narrate the flow smoothly, it probably works. If you stumble — ‘and then they… um, they have to find the settings, and, uh, choose a plan first I think…’ — that stumble is the flow problem. The places your voice slows down are the places users will.
“Every time your sentence breaks, the user’s attention breaks.”
Why narration beats diagrams
Diagrams abstract the emotion. A user flow on paper is a tidy graph. A user flow spoken aloud carries pacing, hesitation, surprise. That emotional track is what you’re actually designing for — not the logical branches, but the feeling of moving through them.
Diagrams also flatten importance. Every node looks equal. In narration, the critical moments naturally get more words. The cheap moments get fewer. You can hear where the weight is.
A small exercise
Take your product’s most important flow and describe it out loud to a colleague in under 90 seconds. Don’t rehearse. Record it. Play it back. Listen for three things:
Friction — places you hesitated or had to explain too much.
Gaps — places you jumped, suggesting the user has to figure something out on their own.
Apology — places you said ‘then they have to…’ in a tone that meant ‘which is annoying, I know.’ Those apologies are the design debt.
What good flows sound like
Good user flows, narrated, sound calm. Each step is earned by the one before. The listener can predict what happens next. There’s a satisfying moment of payoff near the end.
Bad flows sound anxious. There’s a lot of ‘they have to,’ ‘they need to,’ ‘and then they…’. The narrator is doing work the product should be doing.
Diagrams are fine for documentation. For understanding, nothing beats speaking the flow out loud and listening to where it gets stuck. Your mouth knows what your users will feel.