16 Nov User Flows: Mapping the Path From Landing to Contact, Donation, or Booking
Part 3 of Build Wireframes and Low-Fidelity Prototypes — a series on the UX principles I use in client work.
A storyboard tells you a visitor’s story. A user flow turns that story into a map. If the storyboard is the movie, the user flow is the directions: every action the visitor takes, every decision they make, and every screen they land on, from the moment they arrive to the moment they finish the job — or give up.
A user flow maps the path a typical visitor takes on a website or app to complete a task from start to finish. That definition sounds simple, and it is. Its power is in what it forces you to decide before you design anything: what actions will visitors take, what decisions will they face, and what screens will they see after each action or decision? Answer those three questions on paper and half the design arguments disappear, because you already settled the structure.
I draw user flows before I design screens, and I recommend clients do the same, for one plain reason: it is far easier to rearrange boxes and arrows than to rearrange a finished website. A flow you can redraw in five minutes is a flow you will actually improve. A finished site you have to rebuild is a site you will live with, flaws and all.
Four shapes, one map
User flows use a small set of shapes, and the smallness is the point. Everybody on a team — designer, developer, client — can read the same four shapes without training.
A circle is an action: something the visitor does. Tapping a button, entering information, choosing an option. A rectangle is a screen: a page the visitor sees, like a homepage, a schedule page, or a confirmation page. A diamond is a decision: a question the visitor must answer, where the answer sends them down one branch or another — forward, or back to try again. Lines with arrows tie the shapes together and show the direction of travel.
That is the whole vocabulary. With it, you can map almost any website task.
Three flows from real client work
Take a donor on a nonprofit site. The flow might start with a landing screen, then an action: read a story. Then a decision: do they want to give? A ‘no’ branches the flow back to more stories or to a newsletter signup. A ‘yes’ opens the donate form. Next comes an action: enter an amount and details. Then a decision: is the information complete and valid? An incomplete form sends them back with a clear error. A complete one leads to a confirmation screen, with a clear next step — not a dead end. Drawn out, that flow is maybe a dozen shapes. It also immediately shows you the places where donors get lost: the story page that never leads to the form, the form that never explains what happens next, the confirmation that strands them.
Take a first-time church guest. Landing screen, action: look for service times, decision: is this Sunday clear enough to come? If the answer is no — times buried, no picture of Sunday, no kids’ information — the flow ends, and it ends politely, which is the worst kind: nobody complains, they just do not come. A flow makes that dead end visible, which is the first step to fixing it.
Take a festival attendee on event day. Landing screen, action: find today’s schedule, decision: which stage or time? Then a details screen, then parking, then done. On a phone, in a hurry, that flow should be short. If your drawn flow has twelve steps between landing and schedule, your website has a problem, and you just found it on paper instead of in a parking lot.
Draw for the typical visitor, not every visitor
A common mistake with user flows is trying to map every possible circumstance. Do not. A flow should focus on the needs most visitors will actually face. If your problem statement changes — if you learn visitors want something new before they finish the task — then the flow probably needs to change too, with a branch to that new screen. But you do not need a separate flow for every edge case. One clear flow for the typical visitor, with branches at the real decisions, beats five tangled flows nobody can read.
That discipline also helps with existing websites, which is most of my client work. A new site gets a new flow from scratch. An existing site already has a flow, so I examine it first, then reorganize, expand, or trim screens to match how visitors actually work through it. The research from the earlier series tells you where the current flow breaks. The new flow is the fix, drawn before I redesign a single page.
A flow is a promise to the wireframe
Here is why user flows sit exactly where they do in this series: they are the bridge between story and screen. The storyboard said what happens and how it feels. The flow says, in order, what the visitor does, what they decide, and what they see. The next post — wireframes — takes that flow and turns each rectangle into an actual screen layout, with the elements a visitor needs on it.
If the flow is wrong, the wireframes will be wrong too, no matter how pretty they are. If the flow is right, the wireframes get dramatically easier, because you already made the hard decisions — what comes first, what branches where, what happens on a wrong turn. That is the quiet value of a diagram that takes an hour to draw and saves a week of rework.
Try it on one task
Pick one task on your site, the one that matters most, and draw its flow with the four shapes. Circles for actions, rectangles for screens, diamonds for decisions, arrows for direction. Start at landing and end at done — contact sent, donation confirmed, booking made, schedule found. Count the steps. Mark every decision where a visitor could get stuck or drop out. Mark every screen that ends without a next step.
If the map is short and every branch leads somewhere sensible, your site’s structure is probably sound, and the work is in the details. If the map is long, tangled, or full of dead ends, you have just found your redesign brief — and you found it before spending anything on design.
The next post turns each rectangle in that map into a screen: wireframes, the skeleton of a website, drawn on paper before you build anything.
Want your site’s path mapped before it’s redesigned? Shaun M. Johnson, owner of Signature Web Design is a full service Web designer, SEO, UI/UX, Graphic Design, and Logo and Branding Expert serving Goldsboro, Greenville, Kinston, Raleigh, Wilmington, Wilson and surrounding areas in North Carolina — with websites designed across the country. Get a free consultation or see recent work.
Previous in this series: Storyboards · Next: Wireframes: Paper Sketches to Low-Fidelity Screens