user-flow-web

User Flow Template

Help UX and product teams improve user experience with the User Flow Diagram. Create conditions for creative solutions.

About the User Flow Template

A user flow diagram (also known as an interaction or task flow diagram) is a step-by-step visual mapping process, outlining what a user does to finish a task or complete a goal through your product or experience. 

Diagramming the user flow can help interpret the quality or experience of the path a user chooses. The flow can also reveal how many steps they chose to complete a task and what pathways they decide to take when interacting with your product or service to solve a pain point. 

While this type of diagram focuses on how a user moves through a particular product, a Screen Flow Template presents a wireframe-style page layout in the form of a flowchart. 

Keep reading to learn more about user flows.

What is a User Flow?

User flows are diagrams that help UX and product teams map out the logical path a user should take when interacting with a system. As a visual tool, the user flow shows the relationship between a website or app’s functionality, potential actions a user could take, and the outcome of what the user decides to do. 

The main elements of a user flow are:

  • A start or endpoint: this makes clear where the flow begins or finishes

  • Process or action: shows what steps the user takes, such as “login” or “purchase”

  • Decision points: shows when a user has to make a choice

  • Arrows: they show where the user is headed based on decisions made

Try a user flow if your team is trying to gauge or improve how the existing user experience can lead to better customer conversion rates. 

The process can help you keep your user in mind and pinpoint the business objective, such as a purchase, newsletter sign-up, or opting for a free trial.

When to use a User Flow Template

User flow diagrams can help you:  

  • Build intuitive interfaces: does your flow feel easy to move through, efficient to use, and intuitive to the user?

  • Decide if your existing interface is fit-for-purpose: what’s working, not working, or needs improvement? Does the flow feel seamless and make sense?

  • Present your product flow to internal teams or clients: can your design team see what your customer says or does during the purchase, sign-up, or log-in process? Can clients get a step-by-step overview to align with your vision?

When creating – or recreating – a user flow, ask yourself and your team:

  • What’s the user trying to do?

  • What’s important to the user and will give them the confidence to keep going?

  • What extra information will the user need to be successful?

  • What are the user’s hesitations or barriers to accomplishing the task?

A user flow map can help designers (and their teams or clients) stay user-centered, even when mapping out complex processes. 

As a designer, you can use user flow diagrams to decide how you’ll design pages, screens, or surfaces on your website or app and rearrange what content and navigational tasks to include.

Create your own User Flow

Mapping your own user flow is easy. Miro’s whiteboard tool is the perfect canvas to create and share your diagram. Start by selecting the User Flow Template, then take the following steps to make one of your own:

Decide on your business objectives and your users’ objectives

Figure out where you’d like your users to end up. If you don’t have one already (or need to update it), use a customer journey map to create a shared vision of your customer experience. Every team member can benefit from a shared understanding of your customers’ feelings at every potential touchpoint with your product or service. Building user empathy will inform every step of your user flow process. 

Discover how visitors find your website. 

Are they finding your product or service through direct traffic, organic search, paid advertising, social media, referral links, or emails? These points will be the start of your user flow diagram, depending on what you find out. 

Find out what information your users need and when they need it

Users convert when they’re served the right information at the right time, so consider what your customer wants from your digital touchpoint and how they may be feeling. Engagement – for example, a chatbot interaction – is still a potential success metric – it’s not all about leading to a final purchase.

Map out your user flow

You can edit the existing shapes and arrows from our User Flow Template to accommodate the user research you’ve uncovered in the previous steps. After your customer discovers your first touchpoint, what do they do next? How many steps until they complete a task? Use the basic user flow on the template to start drawing your own. Change touchpoints and drop-offs and connector lines arrows directions to fit your user flow diagram better.

Get feedback from your team. 

Invite your team, clients, or cross-functional stakeholders to view your Miro Board. You can choose to leave feedback asynchronously with sticky notes or @mentions for peer review. You can also hop on a video call in your Miro Board and assign someone on your team to play a note-taker role. Once you have enough team input, make adjustments accordingly.

Share with other stakeholders or clients and keep reiterating as needed. 

Your user flow will change over time as your customers’ attitudes and motivations evolve. Adapt accordingly, stay user-centered.

FAQ about the User Flow Template

What is a user flow example?

Imagine you are developing a site for an event. If you want to improve your user experience, you must map out all the necessary steps to the event’s registration and purchase of tickets. You can start by tracking your customer flow and where they begin their journey to buy your event’s tickets. The user flow diagram helps you visualize at a glance how the customer will complete their purchase (your website’s ultimate goal), from registration to payment page.

User Flow Template

Get started with this template right now.

Related Templates
research-topic-brainstorm-thumb-web
Preview

Research Topic Brainstorm Template

Works best for:

Desk Research, Brainstorming, Ideation

Coming up with a topic for a research project can be a daunting task. Use the Research Topic Brainstorm template to take a general idea and transform it into something concrete. With the Research Topic Brainstorm template, you can compile a list of general ideas that interest you and then break them into component parts. You can then turn those parts into questions that might be the focus for a research project.

Research Topic Brainstorm Template
Product Roadmap Basic-thumb-web
Preview

Product Roadmap Template

Works best for:

Product Management, Roadmaps

Product roadmaps help communicate the vision and progress of what’s coming next for your product. It’s an important asset for aligning teams and valuable stakeholders – including executives, engineering, marketing, customer success, and sales – around your strategy and priorities. Product roadmapping can inform future project management, describe new features and product goals, and spell out the lifecycle of a new product. While product roadmaps are customizable, most contain information about the products you’re building, when you’re building them, and the people involved at each stage.

Product Roadmap Template
DFD Maker Thumbnail
Preview

Data Flow Diagram Template

Works best for:

Flowcharts, Software Development, Diagrams

Any process can get pretty complex, especially when it has multiple components. Get a better grasp of your process through a data flow diagram (DFD). DFDs create a simple visual representation of all components in the flow of data and requirements in an entire system. They’re most often used by growth teams, data analysts, and product teams, and they’re created with one of three levels of complexity—0, 1, or 2. This template will help you easily build the best DFD for your process.

Data Flow Diagram Template
Scenario Mapping Thumbnail
Preview

Scenario Mapping Template

Works best for:

Desk Research, Mapping, Product Management

Scenario mapping is the process of outlining all the steps a user will take to complete a task. The scenario mapping template helps you create a visual guide to what different personas are doing, thinking, and feeling in different situations. Use scenario mapping to outline an intended or ideal scenario (what should happen) as well as what currently happens. If you’re trying to outline the ideal scenario, user mapping should take place very early on in a project and can help inform user stories and the product backlog. If you’re just trying to get a better sense of what currently happens, you can do user mapping when conducting user interviews or observation.

Scenario Mapping Template
Service Blueprint Thumbnail
Preview

Service Blueprint Template

Works best for:

Desk Research, Operations, Market Research

First introduced by G. Lynn Shostack in 1984, service blueprints allow you to visualize the steps that go into a service process from the customer’s perspective. Service blueprints are useful tools for understanding and designing a service experience – and finding ways to improve it. Service blueprint diagrams make it simpler for teams to design new processes or improve existing ones. To create a service blueprint, map out each process and actor that contributes to the customer experience, from in-house contributors to third-party vendors.

Service Blueprint Template
prune-the-product-tree-thumb-web
Preview

Prune the Product Tree Template

Works best for:

Design, Desk Research, Product Management

Prune the Product Tree (also known as the product tree game or the product tree prioritization framework) is a visual tool that helps product managers organize and prioritize product feature requests. The tree represents a product roadmap and helps your team think about how to grow and shape your product or service by gamifying feedback-gathering from customers and stakeholders. A typical product tree has four symbolic features: the trunk, which represents the existing product features your team is building; the branches, each of which represents a product or system function; roots, which are technical requirements or infrastructure; and leaves, which are new ideas for product features.

Prune the Product Tree Template