How to Create a User Flow Diagram in Miro
Miro excels at the early exploration phase where flows are sketched, debated, and iterated quickly with the full team. Its real-time collaboration features and flowchart shape library make it the default tool for collaborative user flow workshops.
This guide covers creating user flow diagrams in Miro from initial sketch to a polished diagram ready for engineering handoff.
Step-by-step guide
Start with the User Flow template or a blank board
In Miro, click Create Board. Search templates for User Flow — Miro ships a built-in User Flow template with pre-configured shapes for actions, decisions, and screens. Alternatively, start blank and use the Flowchart shape library accessible from the left toolbar under Shapes > Flowchart. The library includes standard UML shapes with correct semantic meanings.
Define your starting point and goal state
Every user flow needs two anchors: a starting state (user lands on the homepage, user opens the app) and a goal state (user completes checkout, user creates their first project). Place the start state in the top-left and the goal state in the bottom-right. Draw the flow left-to-right as the primary direction.
Add action and decision shapes in sequence
Use rectangles for actions (things the user does or the system does), diamonds for decisions (Yes/No branches), and rounded rectangles for screens or states. In Miro, hold Alt and drag any shape to duplicate it. Chain shapes horizontally for the happy path, then branch down for alternate paths and error states.
Connect shapes with labeled arrows
In Miro, hover over a shape until the blue dots appear on the edges. Click and drag from an edge dot to connect shapes with arrows. Double-click the connector line to add a label: User clicks Submit, Payment succeeds, Token expired. Miro connectors have smart routing and automatically avoid overlapping shapes.
Use sticky notes for inline annotations
Add Miro sticky notes adjacent to decision nodes or complex steps to explain business rules: 3-attempt lockout rule applies here or Only Premium users see this step. Use a distinct color for annotations (yellow) versus the flow shapes (white). This keeps context visible without cluttering the diagram.
Run a collaborative flow review using cursor sharing
Share the Miro board link with your team. In the review meeting, use the Follow me cursor feature (click your avatar > Share my presence) so everyone sees your walkthrough. Use the Miro Voting plugin (Plugins > Voting) to let the team vote on contested decision paths.
Export and embed the completed flow
Once finalized, select all flow shapes and right-click > Export selection as PNG or SVG. Embed the Miro board in your Notion PRD using Miro's embed feature: copy the board URL, open Notion, type /miro and paste the link. The flow stays interactive and live-updating in Notion.
Common mistakes
Flows that go in all directions
Flows that branch left, right, up, and down are impossible to follow. Establish a primary flow direction (left-to-right or top-to-bottom) and keep all alternative paths as secondary branches in one consistent direction.
Too many steps on one flow
A flow with 30+ steps covering the entire product is a sitemap, not a user flow. Each flow should cover one user goal. Split large flows into smaller, focused diagrams for each distinct task.
Using sticky notes instead of proper flowchart shapes
Building flows entirely out of sticky notes bypasses Miro connector logic and makes the diagram look informal. Use the Flowchart shape library for production-quality flows that communicate rigorously to engineering.
Tips
Use Miro's Smart Drawing feature (paid plans) — draw a rough shape and Miro converts it to a clean flowchart shape automatically
Create a reusable flow template in your Miro team by saving a completed flow as a Team Template
Use color consistently: blue for system actions, white for user actions, red for error states
Add a legend in the top corner of the board explaining your shape and color conventions
How Vantage helps
Miro flows are excellent for collaborative exploration. Vantage generates structured user journey data that can inform and validate your Miro flow diagrams. Export Vantage journey map output and use it as the basis for your Miro flow — saving initial brainstorming and ensuring the flow is grounded in your PRD requirements.