UX Design · Lesson 08 / 13
User flows & wireframes
How to map task flows, user flows and wire flows; design for unhappy paths; and create low-, mid- and high-fidelity wireframes that focus discussion on structure and content.
5 min read · 5 quiz questions
From structure to screens
Information architecture decides what content exists and where it lives. User flows decide how people move through it to complete a task. Wireframes then decide what each screen contains and in what order of importance.
Working in this order — structure, flow, screen — prevents a common trap: designing beautiful individual screens that don't connect into a sensible journey.
Types of flows
| Type | What it shows | When to use |
|---|---|---|
| Task flow | A single, linear path to complete one task, no branches | Early, to agree on the core steps |
| User flow | The path for a specific user, including decisions and branches | To design all the routes through a task |
| Wire flow | Flow diagram where each step is a wireframe of the screen | Complex interactions on few screens; handoff |
| Screen flow / sitemap | How all screens connect | Overview of the whole product |
Flow diagram notation
Flow diagrams use a few standard shapes. Keep it simple and consistent so anyone on the team can read them:
- Rounded rectangle / oval — start or end point ("User opens app", "Order placed").
- Rectangle — a screen or step.
- Diamond — a decision with yes/no or multiple branches ("Logged in?").
- Arrow — direction of movement. Label arrows with the action that triggers them ("Taps Pay").
( Start: taps "Checkout" )
│
◇ Logged in? ◇ ── no ──▶ [ Log in / sign up ] ──┐
│ yes │
▼ │
[ Delivery address ] ◀───────────────────────────┘
│
[ Payment ] ── taps Pay ──▶ ◇ Payment OK? ◇
│ no → [ Error + retry ] → [ Payment ]
│ yes
▼
( End: Order confirmation )Designing for unhappy paths
The happy path is the ideal route where everything works. Real users often leave it. Designing only the happy path leads to dead ends and confusion when something goes wrong — and something always does.
- Errors — invalid input, payment declined, server error.
- Empty states — no search results, no orders yet, empty cart.
- Interruptions — lost connection, app closed mid-task, session expired.
- Edge cases — very long names, out-of-stock items, a user with no permissions.
- Going back — changing a previous step without losing data.
- Cancelling — leaving halfway and returning later.
For every decision diamond, make sure every branch leads somewhere useful. A branch that ends in nowhere is a dead end for a real person.
What is a wireframe?
A wireframe is a simplified visual guide that shows the layout and content of a screen: what's on it, how it's arranged and what's most important. It deliberately leaves out final colours, images, fonts and styling.
That simplicity is the point. When a design looks finished, people comment on colours and fonts. When it's grey boxes, they comment on structure, content and flow — the things that are expensive to change later.
Levels of fidelity
Low fidelity
Fast sketches on paper, a whiteboard or a tablet. Rough boxes, squiggles for text. You can produce dozens in an hour, so they're perfect for exploring many ideas and throwing away the weak ones.
Mid fidelity
Digital, usually in Figma. Greyscale, with real headings, labels and button text, correct proportions and a basic grid. This is the most common level for reviewing structure with a team and testing flows.
High fidelity
Close to the final UI, with real content, typography, colour and components. Usually created after the structure is agreed, as part of UI design.
| Low | Mid | High | |
|---|---|---|---|
| Speed | Minutes | Hours | Days |
| Best for | Exploring ideas | Agreeing structure and flow | Final details and visual design |
| Feedback you get | Concept and direction | Layout, content, flow | Visual polish, details |
| Cost of change | Very low | Low | Higher |
How to wireframe a screen
- 1Start from the user's goal on this screen and the content needed to reach it.
- 2List the content and actions, then rank them by importance.
- 3Sketch several layouts quickly (try a "crazy 8s": eight sketches in eight minutes).
- 4Pick the strongest and build it at mid fidelity on a grid.
- 5Use real or realistic content — real headings, real labels, realistic data.
- 6Add annotations explaining behaviour that isn't visible: what happens on tap, validation rules, empty states.
- 7Connect wireframes into a clickable flow and review it with the team.
Common mistake: Using "Lorem ipsum" everywhere. Placeholder text hides real problems: a product name in German that's three times longer, an Arabic translation that needs right-to-left layout, a user with no data at all.
Annotations
Annotations are short notes next to a wireframe that explain what the drawing can't show. They save a lot of back-and-forth with developers and stakeholders.
① Search field — searches product names and SKUs; shows results after 2 characters.
② Filter chips — multi-select; selected chips move to the start of the row.
③ Empty state — if no results: "No products match 'xyz'" + "Clear filters" button.
④ Price — always shown with currency; strike-through original price when discounted.Key takeaways
- Work in order: structure (IA), then flow, then individual screens.
- Task flows show one linear path; user flows add decisions and branches; wire flows add screens.
- Design unhappy paths: errors, empty states, interruptions, edge cases.
- Wireframes focus discussion on structure and content by leaving out visual styling.
- Pick fidelity by purpose, use real content, and annotate behaviour.
Exercise
Flow and wireframe a password reset
- Draw a user flow for "I forgot my password", from the login screen to logged in.
- Add at least three unhappy paths (email not found, link expired, weak new password).
- Sketch eight different layouts for the "Set a new password" screen in eight minutes.
- Create a mid-fidelity wireframe of the best one with real labels.
- Add annotations for validation rules and error messages.
Test yourself
User flows & wireframes quiz
5 questions. Score 70% or more to complete the lesson.
