Structural Design

User Flow

A representation of the steps, decisions, screens, and paths a user follows to complete a task or reach an outcome.

Concept facts

A user flow represents the sequence of steps, decisions, screens, actions, and system responses a user follows to complete a task or reach a goal.

Also known as
Flow diagram, task flow, interaction flow, screen flow, path flow
Used in
Product design, form design, application journeys, service portals, onboarding, dashboard workflows, usability test planning
Interpret with
User goal, task sequence, decision points, error paths, content requirements, system states, permissions, and service rules

Plain-language explanation

A user flow shows how a person moves through a digital task. It may include entry points, screens, decisions, actions, branches, errors, confirmations, and exit points.

User flows are useful when a task involves more than one screen or when the path changes depending on user decisions, eligibility, role, status, or system response.

A user flow is not the same as a journey map. A journey map may include emotions, channels, offline steps, and service touchpoints. A user flow usually focuses more tightly on the interaction path inside a product or service system.

Why it matters

Complex systems often fail because the path is unclear, not because individual screens are unusable. Users may not know where to start, what comes next, how to recover, or which branch applies to them.

User flows help teams identify missing steps, confusing decisions, dead ends, repeated work, and unclear status transitions.

They also help implementation teams align design with business rules, permissions, data requirements, and operational responsibilities.

Use contexts

  • Multi-step form design
  • Application and registration journeys
  • Onboarding and account setup
  • Role-based dashboards
  • Service portal workflows
  • Error and recovery path planning
  • Usability test task design

Application guidance

Start with a clear user goal. Then map the entry point, main path, decision branches, error paths, confirmation states, and recovery options.

Use realistic conditions. Include cases where the user is ineligible, has missing documents, loses connectivity, lacks permission, or needs staff review.

A strong user flow should show not only the ideal path, but also the paths users are likely to take when something goes wrong.

Practical example

A digital lending platform maps the flow for small business onboarding. The user must check eligibility, provide business identity information, link a mobile financial account, upload trade documents, review repayment terms, and wait for approval.

The flow diagram reveals a risky branch: if KYC verification fails, users are sent back to the start without knowing which document caused the failure. Adding a specific correction path reduces duplicate applications and support-center escalation.

Interpretive boundaries

  • A user flow is not the same as a full service journey.
  • User flows should include error and exception paths, not only the ideal path.
  • A flow diagram can look clear while the actual interface remains confusing.
  • User flows should be validated against real tasks, policies, and system states.
  • Flow simplification should not remove required checks in regulated or high-risk services.

Applied at Userhub

User flows are relevant when Userhub evaluates or designs multi-step forms, application journeys, dashboards, learning systems, public-service portals, and regulated digital workflows.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

  • ISO. (2019). Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems (ISO Standard No. 9241-210:2019). International Organization for Standardization.
  • Garrett, J. J. (2011). The Elements of User Experience: User-Centered Design for the Web and Beyond (2nd ed.). New Riders.
  • Brown, D. M. (2010). Communicating Design: Developing Web Site Documentation for Design and Planning (2nd ed.). New Riders.
  • Stanton, N. A. (2006). Hierarchical task analysis: Developments, applications, and extensions. Applied Ergonomics, 37(1), 55–79. https://doi.org/10.1016/j.apergo.2005.06.003

—

Cite this entry

APA

Userhub. (2026). User Flow. UX Reference. https://userhub.com.bd/reference/user-flow/