In brief
Process visualisation turns a real workflow into a usable visual model. It should show what happens, who is involved, where choices occur, and how the process changes.

Common tools
- Figma
- Adobe Illustrator
- Spreadsheet
Skills in play
- Research
- Systems thinking
- Technical accuracy
What it is
Process visualisation is the design of a visual model for work that unfolds through steps, decisions, people, and systems. It may take the form of a flowchart, swimlane, service blueprint, or staged overview. Its purpose is to help a reader understand what happens and what to do next. A useful process graphic can also reveal delays, duplicate work, missing ownership, and unclear exceptions.
A process is different from a timeline. A timeline places events in time; a process shows relationships between actions and decisions, often with loops or alternative paths. It is also more specific than a general diagram: the reader should be able to trace an activity from an entry point to an outcome.
Confirm the process before drawing it
Ask what question the visual must answer. Is it a training aid, an operational reference, a redesign workshop, or a public explanation? The audience determines how much detail belongs in the main view. A new employee may need roles and escalation paths; a visitor may need only the next three steps and an expected result.
Interview people who perform the work, not only those who manage it. Observe actual cases and collect the documents, screens, and messages that move between stages. Record where the process differs from policy. If two people describe different hand-offs, keep the disagreement visible until it is resolved. A smooth-looking chart built from one person’s memory can make an unreliable process appear authoritative.
Define the units of the map
List triggers, actions, decisions, owners, inputs, outputs, and exceptions. Decide which actions belong together as one stage and which need their own node. Give each node a clear verb and object, such as βReview artwork proofβ rather than βReview.β Use consistent language for the same role or document throughout.
Create an explicit notation before styling. An arrow should mean one kind of movement; a decision shape should ask a real question; a loop should show where work returns. If several kinds of connection are needed, label them. Limit visual coding to distinctions the reader needs to act on.
Show the right amount of complexity
Start with a simple overview of the normal path. Add branches for common exceptions and link to a detailed view when necessary. An enormous canvas may be precise but unusable on a phone, in a printed handbook, or during a meeting. Use layered views rather than shrinking every detail into unreadable type.
For a service, a blueprint can show both what the user experiences and the supporting work behind the scenes. Digital NSW describes it as a way to connect the customer experience with teams, systems, processes, and data. GOV.UK similarly recommends mapping the user’s whole problem, including where separate services fail to join up. These approaches help designers avoid presenting an internal team chart as if it were the user’s journey.
Make ownership and hand-offs visible
Swimlanes can identify who acts at each step, but keep them few enough to read. Mark where a hand-off depends on approval or a system response. If a delay is important, show the waiting state rather than drawing a direct arrow that suggests instant progress. Separate what is known from what is assumed, especially in a proposed future process.
Use colour sparingly and never as the only way to distinguish states. A reader should be able to follow the route through labels, grouping, and line structure. Provide a text version of essential steps and decisions. W3C guidance for complex images explains why a short alt label alone may not convey the relationships in a rich diagram.
Test it against real cases
Walk through several actual examples with the people involved. Ask them to point to each step and explain what happens when a case fails, changes owner, or returns for revision. Then give the graphic to someone new and ask them to trace a task without help. These tests reveal different defects: experts find inaccuracies, while newcomers find unclear reading paths.
Assign an owner and review date to the source model. Keep the process data or documented steps separate from the drawing file so a future update does not require reconstructing the logic from shapes. Publish the version and scope when the process is operationally important.
Practical checks
- Can a reader identify the start, the next decision, and the possible outcomes?
- Are roles, hand-offs, loops, and waiting states represented accurately?
- Is there an overview that remains readable at the intended size?
- Does a text alternative explain essential relationships?
- Can the model be updated when the real process changes?
Common mistake
Drawing the ideal route and hiding the workarounds that actually keep the process moving. Use the visualisation to expose those gaps, then decide whether the process or the graphic needs to change.
People and practice






