User Flows and Edge Cases
Level 1 · What UX is
How to map the steps a person takes to finish one task. The happy path where all goes well, and the rare cases a design must still handle.
Course contentsLesson 3 of 21
Level 1 · What UX is
Level 2 · Finding out from users
Level 3 · Making sense of research
Level 4 · Designing the interaction
After this lesson you can
- Draw a user flow for one task
- Mark the happy path
- List the edge cases for each step
10 mincovers 3 glossary entries
Worth reading first: Information Architecture
How to map the steps of one task
A user flow is a diagram of the steps a person takes to finish one task. Boxes are screens or actions. Diamonds are choices, like is the user logged in? A checkout flow might have five boxes and two diamonds. Drawing it shows every path before anyone writes code.
The happy path is the way through when each step works. The user is logged in, the card is fine and the address is right. Most designs are drawn for this path first, because it is the one most people take. It is also the one that needs the least thought.
An edge case is a rare case the design must still deal with. A 40 letter name. No internet. A card that is declined. An empty list on the first day. Each one is rare, but across 10,000 users a day, a one in a hundred case happens 100 times.
Edge cases are where products feel broken. The happy path gets tested every day by the team. The declined card gets tested by a real customer at midnight. If the screen just goes blank, that customer is gone, and they will tell others.
To find them, walk the flow one box at a time and ask what could go wrong here. What if this is empty? Too long? Too slow? Not allowed? Write each answer as a dashed box hanging below the step. Then decide what the screen says for each.
A flow is about one task, not the whole site. That is what keeps it readable. Sign up is one flow. Reset a password is another. A diagram that tries to show everything becomes a map nobody can follow.
The common slip is to draw only the happy path and call the flow done. It looks clean in a meeting. The edge cases then show up during building, when they cost ten times more to fix. Draw them early, while they are only boxes.
Worked example
A food app finds its empty list
A food app's team drew the order flow with 6 steps. Asking what could go wrong at each one turned up 9 edge cases.
One was a restaurant with no items left. The old screen showed a blank page. The new one says sold out today and lists 3 nearby places.
The words for this lesson3
Check yourself
Why do edge cases matter if each one is rare?
Finished this lesson?
Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.