How to make a user flow diagram

Learn how to make a user flow diagram: pick one goal, draw the happy path, add every error and exit, list edge cases and start from a free template.

Written by
FlowDraw Team
Published
Reading time
6 min read
A FlowDraw board with a user flow for buying a plant at Leaf & Pot: Cart, In stock?, Signed in?, Shipping address, Payment and Approved?.

Most checkouts work for the shopper who does everything right. A user flow diagram makes you draw the others too: the sold-out item, the guest, the declined card. This guide follows a shopper buying a plant at Leaf & Pot.

Quick Answer

A user flow diagram shows the screens and decisions one person meets on the way to one goal. To make one, name the person and goal, draw the happy path from the entry point, add every error and exit, label each branch, then list the edge cases.

What is a user flow diagram?

It is a map of one task, seen from the person doing it. Six kinds of box cover most flows. The notation is a convention rather than a standard, so keep a key on the board.

Six shapes from the board: a black start pill, a screen box, a blue decision diamond, a green success end, a red error state and a red error end.
The six shapes in the example

Draw one before you design screens, or when a task has enough branches that people remember it differently.

User flow, flowchart or journey map?

These get mixed up because they all use boxes and arrows, or at least stages in order.

DiagramWhat it followsPick it when you ask
User flowOne person on screensWhat must we build for this task?
FlowchartAny process, people or systemsHow does this work?
Journey mapThe experience over timeHow does this feel, and where does it hurt?

How to make a user flow diagram

Pick one person and one goal

Write the goal as something you could confirm happened: buying a plant, with the order confirmed. A second goal, such as changing an address later, gets a second flow.

Then find where the person really starts. Here it is “Taps the cart”, not the home page, because everything before that belongs to another flow.

Draw the happy path

Draw the route with no problems, left to right, one box per screen. Write each decision as a question with a yes or no answer.

The first half of the happy path: Taps the cart, Cart, In stock?, Signed in? and Shipping address, joined by arrows with Yes labels.
From the entry point to the first form

A decision is not always the person’s choice. The system answers “In stock?” for them, yet it belongs here because the answer changes what appears next.

The second half of the happy path: Shipping address, Delivery options, Payment, Approved? and Order confirmed.
From the first form to the goal

Do not branch yet. A straight line first lets everyone agree on the route, and shows how many screens stand between the person and the goal.

Add every error and exit

Go back to each decision and draw the “No”. Every branch needs an answer to two questions: what do they see, and where can they go from there?

The No branches for stock and sign-in: Item sold out returns to Cart by Remove item, and Sign in or guest continues to Shipping address.
Two branches that rejoin the main path

Not every “No” is an error. “Sign in or guest” is an ordinary screen, so it stays white, and red marks only what went wrong. Starting with these branches is a good habit in general, since they are where the screens nobody planned come from.

A dead end needs drawing too. Some shoppers give up, and that outcome deserves a box:

Card declined under Approved?, with Try again going back to Payment and Gives up leading to the red end Order not placed.
One error state, two ways out

Label each way out

Every line leaving a decision or an error state gets a label. Without one, readers have to guess from the shapes.

The same part of the flow twice. The left has no labels on its lines. The right reads Yes, No, Try again and Gives up.
The same lines, unlabelled and labelled

List the edge cases

Some cases are too rare or too scattered to draw as branches. List them beside the flow, because each one still needs its own screen or message.

Edge case on the boardWhat to decide
Address outside the delivery areaWhat can they do instead?
Promo code expiredDoes the total change before they pay?
Session times out on PaymentIs the cart still there?
Plant too large for gift wrapWhen do they find out?

Drawing a user flow in FlowDraw

The template is free on every plan, and nothing in it needs Pro.

The FlowDraw Templates page with User flow as the one result.
Find it under Templates in the sidebar
  1. Open the template

    Search for “User flow” under “Templates”, open the card, then choose “Use template”.

  2. Rename the screens

    Double-click a box or diamond and type your own words. Press Esc to finish.

  3. Add a screen

    Hover over a box and a spot appears beyond each side. Click one to add a copy with no text, joined by a line. If a shape already lies that way, the click joins the two instead.

  4. Label a branch

    Select the line, then type in “Add a label” under “Line properties”. Lines stay attached, so they find a new route when you move a box.

  5. Fill in the edge cases

    The dashed “Add an edge case” boxes are ordinary shapes. Double-click one and type.

  6. Check it with your team

    Choose “Share” and add people. On Free everyone you invite can edit. On Pro only one person can, so others press C and comment.

The User flow template open in the FlowDraw editor, with the key and the edge cases below the flow.
The template open in the editor

On a blank board, press R for a box, D for a diamond and L for a line, with Esc between them. The pill is “Terminator” in the Flowchart library, under “Shape library”. Once the flow is settled, a wireframe of each screen comes next.

User flow mistakes to avoid

  • Several goals in one flow. Buying and returning a plant are two diagrams.
  • Starting too early. If the first box is your home page, ask whether that is where this person begins.
  • Only the happy path. It is usually the part everyone already agrees on.
  • Screens as verbs. “Cart” is a screen, while “Reviews the cart” is an action. Pick one style for boxes.
  • Decisions with no question. A diamond that says “Payment” cannot be answered with a yes or no.
  • Dead ends nobody chose. A box with no line out should be a deliberate end, drawn as one.

FAQ

It shows the screens and decisions one person meets on the way to one goal. Designers and developers use it to agree what must be built, including what happens when things go wrong.

Continue Reading

A FlowDraw board with a sign-in sequence diagram: User, Web app, API and Database lifelines, with POST /sessions and a 201 Created reply.

Guides·

How to draw a sequence diagram

Draw a sequence diagram one message at a time: lifelines, replies, activation bars and fragments explained through a sign-in flow, with a free template.

A FlowDraw board with an empathy map for Priya, a freelance designer: sticky notes under Says, Thinks, Does and Feels, with Pains and Gains beside them.

Guides·

How to make an empathy map

Learn how to make an empathy map: pick one user and one moment, fill in says, thinks, does and feels, name pains and gains and turn them into next steps.

A FlowDraw board with a business model canvas for Fetch & Co., fresh dog food by subscription: nine blocks filled with sticky notes.

Guides·

How to fill in a business model canvas

Learn how to fill in a business model canvas: what the nine blocks mean, which order to use, how to check they fit together and a free template to start from.

Ready to create your first diagram?

Turn your ideas, notes, or documents into a clear,
editable flowchart in seconds.

Get Started Free