Guide7 min readUpdated
What Is a User Flow? A Simple Guide for Business Owners
What is a user flow? Learn how a user flow diagram maps the steps of one task, how it differs from a user journey, and how it affects cost.
Imagine a customer in Siliguri opens a tiffin service app at 8 pm. She wants to order dinner and pay with UPI. Someone has to decide what she sees first, what she taps next, and what happens if the payment fails. That plan is a user flow.
A user flow is a step-by-step map of the path one person takes to finish one task in an app or website, from the first screen to the last. The task can be small, like resetting a password. It can also be large, like placing an order. The map shows every screen, every choice and every dead end on the way.
What is a user flow, in simple words?
A user flow is a drawing of the steps a person follows to get one job done. Think of the route from your home to a railway station. You leave the house, reach the main road, choose a bus or an auto, and arrive. A user flow draws that route for a screen-based task.
Every flow has three parts. It has a starting point, such as the home screen or a WhatsApp link. It has steps, which are screens and actions. It has an ending, which is either success, such as "order placed", or a stop, such as "payment failed".
People also search for "user flow diagram". A user flow diagram is the drawn version. It uses boxes for screens, diamonds for questions the system asks, and arrows for direction. Some people call it a flowchart for an app. The idea is the same.
What does a user flow look like? An example in words
A user flow for ordering dinner in the tiffin app has six main steps, and several branches. First the steps.
- The customer opens the app and lands on the home screen with today's menu.
- She taps a meal. The meal screen shows the price, the items and the delivery time.
- She taps "Add to cart". The cart screen shows the total.
- She taps "Pay". The app asks for a payment method.
- She picks UPI. Her UPI app opens and she approves the payment.
- The app shows "Order placed" with an estimated delivery time.
Now the branches. What if she is not logged in? She goes to a login screen and enters an OTP (one-time password) first. What if the UPI payment fails? The flow must lead to a screen that says "Payment failed. Try again or choose another method", not to a blank page. What if the kitchen is closed? She should see a clear message and a "Notify me" button.
The branches are where most real problems hide. The happy path, where everything works, is easy to draw. The unhappy paths need thought. I cover the payment side in UPI payment UX and checkout design.
What is the difference between a user flow, a user journey and a task flow?
A user flow follows the steps inside your product for one task. A user journey follows the whole experience of a person over time, including what happens outside your product. A task flow is a plainer version of a user flow that shows only the steps of the task, for anyone.
| Term | Question it answers | Tiffin app example |
|---|---|---|
| User flow | Which screens does she pass through to finish this task? | Home, meal, cart, pay, confirmation |
| User journey | What does she think, feel and do from start to end? | Sees a friend's post, installs the app, orders, waits, eats, orders again next week |
| Task flow | What are the steps of this task? | Choose meal, add to cart, pay |
Use the journey when you want to understand the person. Use the flow when you want to design the screens. A designer often makes the journey first. To learn how to collect the facts behind a journey, read user research for startups.
Why does a business owner need a user flow?
A user flow shows problems before they are built, and fixing a problem on paper is cheaper than fixing it in code. Changing an arrow takes minutes. Changing a finished screen and its code can take days.
Four reasons matter most to an owner.
- It shows the number of steps. If ordering takes 9 taps and you want it to take 4, you see the gap before design begins.
- It exposes missing screens. Owners often forget screens such as "forgot password", "no internet" or "order cancelled". The flow lists them.
- It gives everyone one picture. You, your developer and your designer look at the same drawing. Nobody carries a different idea in their head.
On a seller app I designed for a marketplace in Tanzania, the flows for seller onboarding, verification and listings were the first thing we agreed on, before any screen looked polished.
How does a designer make a user flow diagram?
A designer makes a user flow by choosing one goal, listing every step, adding the failure paths, and then checking the drawing with the owner. The tool can be as simple as Figma or a sheet of paper.
My steps are these.
- Name the person and the goal. For example: "a first-time customer wants to order dinner and pay by UPI".
- Choose the starting point. It may be the home screen, a WhatsApp link or a notification. People rarely start where owners expect.
- Write the steps as plain sentences first. Words come before boxes. This catches gaps early.
- Draw the boxes and arrows. One box for each screen. One diamond for each decision.
- Add the failure paths. No network, wrong OTP, payment declined, item out of stock.
- Read the flow aloud to the owner. Owners spot wrong business rules quickly when they hear the flow as a story.
This work is the second stage of my own process, "Map the flow". It comes after I understand the business and before I draw wireframes. A wireframe is a rough, plain layout of one screen. I explain how wireframes differ from mockups and prototypes in wireframe vs mockup vs prototype.
What should a good user flow contain?
A good user flow contains one clear goal, one starting point, every decision, every error path and a clear end state. It should fit on one page and make sense to a person who did not draw it.
Check a flow against this list.
- One task only. If the diagram covers ordering, refunds and profile editing together, split it.
- Screen names that a non-designer understands. "Cart" is better than "Screen 4B".
- Every place where the person must wait, type or choose.
- The end state, written plainly: "Order placed, WhatsApp confirmation sent".
- A note about roles, if the product has several. A buyer, a seller and an admin see different screens.
What mistakes do people make with user flows?
The most common mistake is drawing only the happy path. Real users on slow networks and busy evenings will meet the unhappy paths.
Other mistakes I see:
- Too many steps for one task. Asking for an address, a pin code, a landmark, a second phone number and a gift note before payment makes people leave.
- Starting from the wrong place. Many designers assume people begin at the home screen. In India, many people begin from a WhatsApp link and land deep inside the product.
- Never testing the flow. A flow looks fine until a real person tries it. A small test with a few people shows where they stop. See usability testing on a small budget.
How do user flows affect cost and timeline?
User flows are a small part of the work, but they decide how large the rest of the work becomes. More flows mean more screens, and more screens mean a higher quote.
I quote UI/UX work for apps and websites by the number of screens and the number of user roles. The flows tell us both numbers early. A simple business website may have one flow and a few pages. A marketplace app with buyers, sellers and an admin may have a dozen flows.
App or website design usually takes me 2 to 4 weeks. Mapping the flows happens in the first part of that time. Two to three revision rounds are included. Payment is 50% to begin and 50% on completion. For wider price drivers, read UI/UX design cost in India or try the cost calculator.
If you are planning an app or website and want the flows drawn before anything is built, I do that as part of UI/UX design.
Frequently asked questions
How many user flows does an app need?
+
One flow for each main task, such as sign up, order, pay and track. A small app may have 4 to 6 flows. A marketplace with several roles may have many more.
Do I need a user flow for a simple website?
+
Usually one short flow is enough, for example from the home page to the enquiry form. Writing it down still helps you spot missing pages and unclear buttons.
Who draws the user flow, the designer or the developer?
+
The designer draws it, with your input on business rules. The developer then reads it to understand what must be built.
Is a user flow the same as a sitemap?
+
No. A sitemap lists the pages of a website. A user flow shows the path of one person doing one task across those pages or screens.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.