User Flow

You might say

Map out every step a user takes from arriving on the site to finishing checkout.

A path diagram of the steps and branches a user takes to reach one goalA sign-up flow might show entering the sign-up page, filling in details, verification success or failure, and account creation. It keeps the steps that affect progress, not every click on the screen.

Know first

PRD

UX Flow

Map a booking from entry to success or recovery

Start with the role, goal, and entry point: a visitor books from the service page.

A User Flow focuses on one goal for one role. Draw failure and recovery paths alongside the main route.

How a user flow makes a goal testable

Fix the user, goal, and entry：Say who starts where, what they want to finish, and what counts as done.

Connect meaningful actions：Show the pages, actions, and decisions that move the task forward, not every scroll or click.

Add branches and recovery：Show what happens after an unavailable slot, bad details, or failed submission, and how the user returns to the main path.

Quick checkChoose the best answer

A team wants to inspect the path for “a visitor completes a booking.” Which diagram is the best User Flow?

Start at the booking entry, continue through slot selection and details submission, and map available, unavailable, success, invalid-details, and return-to-edit pathsList the hierarchy of Home, Services, Pricing, and Help Center pages without showing booking actions or outcomesDraw the exact size and position of every input and button on the booking screen without connecting the sequence or error branches

You can say this to an AI Agent

Map the User Flow for “a first-time visitor completes a booking.” Use only the rules I provide to show the entry, key actions, branches such as no available slots and invalid details, plus success and recovery endpoints. Ask me about missing business rules instead of expanding this into a site-wide sitemap or detailed wireframe, then walk every branch to check for dead ends.

Learn next

1MVP→2API→