Flow analysis maps the movement of people, information, materials, or data through a system to reveal bottlenecks, redundancies, and failure points. In UX and service design, it is applied both to digital user flows — the sequence of screens and decisions a user traverses to complete a goal — and to operational flows — how requests, tasks, and handoffs move through an organisation. Understanding flow before designing a solution consistently prevents the creation of well-designed interfaces sitting atop broken underlying processes.
What It Is
A user flow diagram charts every step, decision point, and outcome a user encounters between a starting point and a goal. An operational flow diagram charts how a task or request moves through an organisation, including handoffs between departments, systems, and people. Both types of flow analysis identify where volume accumulates, where wait states occur, where errors are introduced, and where the designed path and the actual path diverge.
How to Run It
- Define the scope: which user goal or operational task are you mapping?
- Document the current state by interviewing users, observing the process, and reviewing system logs where available.
- Draw the flow starting from the trigger event through each step, decision, and outcome.
- Annotate each step with frequency, duration, error rate, and emotional quality where data is available.
- Identify bottlenecks, wait states, redundant steps, and divergences between designed and actual flows.
- Design a future-state flow that addresses the most critical friction points identified in the current state.
When to Use It
Flow analysis is essential when designing or redesigning complex multi-step user journeys, checkout flows, onboarding sequences, or multi-department service processes. It is particularly valuable when analytics data shows that users are dropping off or failing at specific steps, and the team needs to understand the structural cause rather than immediately iterating on interface design. Use it to distinguish UI problems from process problems.
Tips for Success
- Map the actual flow, not the intended one — they are almost always different in important ways.
- Include all decision branches, not just the happy path: error states and alternative routes are where flow analysis is most instructive.
- Annotate flows with qualitative data from user research alongside quantitative data from analytics.
- Share flow diagrams with developers early: they often identify technical constraints that affect flow design before any prototype is built.
