Flowchart
Synonyms: flow diagram, flow chart, process flow diagram, UX flowchart, process map
Definition
Use cases
- Happy path only: A checkout chart shows browse, pay, done. Nobody drew the declined card, so engineering invents that screen the day before release.
- The dead end: A password-reset chart has a "Link expired" box with no arrow out. Real users land there with nowhere to go.
- The poster: 1 diagram holds onboarding and billing in 80 boxes. Nobody reads it.
How it's used in practice
- Name the goal first: Title the chart with the user's goal ("Reset password") and mark where they enter.
- Draw the happy path, then every "no": Each diamond needs a labelled exit for every answer.
- Keep 1 direction: Run top to bottom or left to right.
- Split big charts: When a chart outgrows 1 screen, move the detail into a sub-flow and link to it.
- Walk it with QA: Each start-to-end path becomes a test case.
Challenges & limitations
- No screen context: NN/g notes that plain flowcharts lack the page layout, which is why wireflows exist.
- They go stale: The chart stops matching the product after a few releases unless someone owns it.
- Confusing labels: Task flow, user flow and wireflow are all flowcharts at different levels of detail. Agree on 1 name per level.
Commonly used notations & tools:
- ISO 5807 — Best for standard symbols.
- Visual Vocabulary — Best for site and interaction flows.
- Miro — Best for workshops with non-designers.
- draw.io — Best free option; supports Mermaid.
Free resources
- NN/g: Wireflows — where flowcharts fall short in UX and how wireflows add screen context.
- NN/g: User Journeys vs. User Flows — a comparison table of the macro journey and the micro flow.
