How to Create a User Journey Flowchart, Step by Step

Published October 31, 2026 · Updated October 31, 2026 · 7 min read · by the Sakura5 team

To create a user journey flowchart, pick one persona and one goal, list the stages they move through from first contact to outcome, write every touchpoint under each stage, then connect those touchpoints with arrows and add a diamond wherever the user or your business makes a decision. Finally, mark the points where people drop out, so the chart shows not just the ideal route but where the journey breaks.

A user journey flowchart sits between two familiar tools. A journey map shows stages and feelings but rarely shows branches. A user flow shows screens and taps but usually stays inside one app. The flowchart version keeps the branching logic of a user flow and stretches it across every channel the person actually touches — a search result, an email, a text message, a front desk.

This guide covers why most journey charts end up as a straight line that hides the real problems, a six-step method for building one, a full worked example for a fictional bike repair shop, how to handle the awkward cases, and the questions people ask most often.

Why most user journey charts miss the point

The usual first draft is a row of boxes: Discover, Consider, Buy, Use, Return. It looks tidy and tells you almost nothing. Every product has those stages. What makes your journey yours is what happens between the boxes — the confirmation email that lands in spam, the customer who calls instead of booking online, the person who quits at the price page.

The second trap is drawing the journey you designed instead of the one people take. A team that built a booking form tends to start the chart at the booking form. Real users start earlier: a map search, a friend’s recommendation, a reminder they set themselves. If the chart starts at your product, it can’t show the moments before your product where people are lost.

The third trap is mixing personas. A first-time customer and a returning one take different routes, and a single chart that tries to show both ends up with notes like “(new users only)” scattered everywhere. One chart, one persona, one goal keeps every branch honest.

How to create a user journey flowchart, step by step

The method below works on paper, on a whiteboard or in any diagram tool. The order matters more than the software.

1. Name the persona and the goal

Write one sentence at the top: who this person is and what they are trying to get done. “A commuter whose bike has a flat and who needs it fixed before Monday” is useful. “Our customers” is not. The goal defines the end oval, so make it an outcome the person would recognize, not a metric your team tracks.

2. Set the stages as swimlanes or columns

Pick four to six stages that describe the journey from the user’s side, such as Notice the problem, Look for help, Book, Visit, Follow up. Draw them as columns across the page. Every shape you add later will sit inside one stage, which makes it obvious when a stage is empty or crowded.

3. List every touchpoint before you draw arrows

Under each stage, write every place the user meets you or a stand-in for you: a web page, an email, a phone call, a sign on the door, a review site. This is a brainstorm, not a diagram yet, so a mind map is the fastest format — one branch per stage, one child per touchpoint. If you use Mindmap AI, a Pro subscriber can type the persona sentence as a topic and get a starting map of stages and touchpoints, then tap any node to expand it into sub-ideas you might have missed.

4. Connect the touchpoints and add decisions

Now turn the list into a flowchart. Use a rounded oval for the start and each possible end, a rectangle for each touchpoint, a diamond for each decision, and an arrow for each move. Label every arrow with what the person does: “Taps Book now,” “Calls the shop,” “Ignores reminder.” If you need a refresher on which shape means what, our guide to user flow diagram shapes covers the full set.

5. Mark the exits and the pain points

Add an exit oval wherever someone can give up, and put a short note on the arrow leading to it explaining why. Then mark pain points — slow steps, confusing screens, places where the user must repeat information — with a consistent marker such as a red dot. Keep these grounded in evidence you actually have: support tickets, session recordings, interviews, your own test run.

6. Walk it with someone who didn’t draw it

Hand the chart to a colleague and ask them to narrate it as the persona. Wherever they hesitate or ask “what happens if…”, you have a missing branch. Add it, then walk it again.

A worked example: booking a bike repair

Say you run a fictional repair shop called Spoke & Chain. It has a booking page, sends text reminders, and fixes bikes in a workshop that takes 6 bookings a day. The persona is Mai, a commuter with a flat tire on Friday evening who needs her bike back by Monday at 8 a.m.

Stages and touchpoints

Five stages: Notice, Search, Book, Drop off and repair, Pick up and review. Listing touchpoints under each produced 11 boxes: a map search result, the shop’s Google listing, the booking page, a slot picker, a confirmation text, a reminder text the evening before, the front counter, a repair-status text, a payment screen, a pick-up shelf and a review request email.

Decisions

Four diamonds turned the straight line into a real journey. “Open on Saturday?” sits in the Search stage — if Mai can’t tell from the listing, she calls or leaves. “Slot free before Monday?” sits in Book; with 6 slots a day, a busy Saturday fills up, and the no branch either offers a Sunday drop-off or ends at an exit oval labeled “Books elsewhere.” “Extra parts needed?” sits in Repair; yes sends a text asking Mai to approve the cost, and a second diamond, “Approves within 2 hours?”, decides whether the bike makes the Monday deadline.

What the chart revealed

Once the arrows were labeled, two problems were obvious. First, the Saturday hours appeared only on the booking page, not on the map listing, so the earliest exit in the whole chart happened before Mai ever reached the shop’s own site. Second, the parts-approval text had no reply option, so the “Approves within 2 hours?” diamond depended on Mai noticing a text and phoning back. Neither problem would show up on a five-box journey map. Both showed up because the chart had diamonds and exits.

The fix list wrote itself: put opening hours on the listing, add a reply-YES option to the approval text, and send the reminder text with the counter’s closing time. Each fix is attached to a specific box or arrow, which is what makes a journey flowchart useful to the people who have to act on it.

Edge cases and how to handle them

The journey is too long for one page. Split it by stage, not by channel. Keep one chart per stage and join them with lettered connector circles, so “A” at the bottom of Book matches “A” at the top of Drop off. The same connector habit is explained in how to make a flowchart for a process.

Part of the journey happens without you. Draw it anyway, with a dashed outline. Asking a friend, reading a forum thread or checking a calendar are real steps that decide whether the person reaches you.

You don’t have research yet. Draw an assumption chart and say so in its title. Then test the riskiest diamond first. The Nielsen Norman Group’s Journey Mapping 101 is a good reference on separating assumption-based maps from research-based ones.

Several personas matter. Draw the most valuable persona first, then copy the chart and change only the branches that differ. Comparing two charts side by side shows exactly where the journeys split. Keeping the outline in Mindmap AI helps here, because the outline view shows each branch as a collapsible list and your maps sync between iPhone, iPad and Mac through iCloud.

FAQ

What is a user journey flowchart?

A user journey flowchart is a diagram that follows one person through every step and channel involved in reaching a goal, from first noticing a need to the final outcome. It uses flowchart shapes — ovals, rectangles, diamonds and arrows — so it can show decisions, branches and drop-off points, not just a sequence of stages.

What is the difference between a user journey and a user flow?

A user flow usually tracks screens and actions inside a single product, such as a sign-up sequence in an app. A user journey covers the whole experience across channels, including search, email, phone calls and in-person visits. A journey flowchart borrows the branching shapes of a user flow and applies them to that wider journey.

How many stages should a user journey flowchart have?

Four to six stages works for most journeys. Fewer than four tends to hide important steps inside vague labels, and more than six usually means you are describing several goals at once. If a stage holds only one touchpoint, merge it with its neighbor; if it holds a dozen, it probably deserves its own chart.

What tools can you use to make a user journey flowchart?

Any diagram tool with ovals, rectangles, diamonds and connectors will work, as will a whiteboard and sticky notes. The harder part is the thinking before the drawing, so many people brainstorm stages and touchpoints in a mind map or outline first, then redraw the result as a flowchart once the branches are clear.

← All articles