UX
Workflow Mapping
A practical UX and service design method for visualising how work moves across roles, systems, and touchpoints so teams can improve efficiency and experience.
How to use workflow mapping to understand real processes, identify bottlenecks and handoffs, and improve how work flows across people and systems.
What it is
glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term mapping is a UX and serviceService DesignMap what happens across teams, systems, and touchpoints so services feel more joined up for users and easier to deliver internally.Open service method used to visualise how tasks, glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term, and interactions flow across people, systems, and touchpoints.
It captures the sequence of activities, who is involved, what glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term are used, and how information moves through the glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term.
Unlike guideTask AnalysisBreaking down a specific task into steps, decisions, and dependencies so complexity can be reduced and workflows improved.Open guide, which focuses on an individual user, glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term mapping looks at the broader glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term, often involving multiple roles, teams, and tools.
It highlights glossaryDependencyA dependency is a component or system that another part of the system relies on to function.Open glossary term, handoffs, and bottlenecks.
The goal is to understand how work really happens and identify opportunities to improve glossaryEfficiencyEfficiency measures how quickly and easily users can complete tasks once they are familiar with a system.Open glossary term and experience.
Workflow mapping is most useful when the real problem lives between people, teams, or systems rather than inside a single interface.
When to use it
Use this method when glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term involve multiple steps, people, or glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term.
It is most useful when:
It is less useful when:
Workflow mapping is often used alongside service design, journey mapping, and task analysis.
Key takeaway
Use workflow mapping when better outcomes depend on understanding how work moves across roles and systems, not just how one user completes one task.
How to run it
Set up properly
Be clear on where the glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term starts and ends and which roles are involved. Workflows cross teams, so the boundary is usually an organisational decision.
Map the real glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term rather than the documented one, by observing it and asking the people who do it.
Run the method
glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term mapping documents how work moves between people, glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term and steps. It focuses on handoffs, which is where most operational problems live.
- Define the start and end points explicitly, including what triggers the glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term.
- Identify every role and actor involved, including people outside the immediate team.
- Map each step in sequence, noting who performs it and how long it takes.
- Capture the glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term, tools and glossaryDataData is raw, uninterpreted information collected and stored so it can be analysed, processed, or used to inform decisions. On its own it carries no meaning; context and interpretation are what make it useful.Open glossary term flows at each step, including the spreadsheets nobody admits to.
- Highlight handoffs and glossaryDependencyA dependency is a component or system that another part of the system relies on to function.Open glossary term, marking where work waits.
Follow the waiting as well as the working. In most glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term the elapsed time is dominated by things sitting in queues, and that is invisible in a step-by-step map.
Capture and make sense of it
The value comes from seeing how work really flows. After mapping, document:
- The steps, roles and glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term involved
- Handoffs where work is delayed or lost
- Duplicated effort and rekeying between glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term
- The gap between the documented glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term and the real one
Use this before automating or redesigning a glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term. Automating an unmapped glossaryWorkflowA workflow is a defined sequence of tasks or steps required to complete a process.Open glossary term reliably encodes its existing problems.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If it doesn’t reflect real work, it won’t improve it.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps you design systems and services that actually work.
Get in touch
If this sounds like something you need, we can help you map your workflows and improve how your systems and teams work together.
No guesswork. No assumptions. Just clarity that drives better outcomes.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is workflow mapping in UX?
It is a method used to visualise how processes and tasks flow across people and systems.
When should you use workflow mapping?
Use it when analysing complex processes or improving operations.
How is it different from task analysis?
Workflow mapping looks at multiple roles and systems, while task analysis focuses on an individual task.
What does a workflow map include?
Steps, roles, systems, handoffs, and dependencies.
Does workflow mapping improve UX?
Yes. It helps streamline processes and improve efficiency and experience.
Quick take
If you want to understand how work actually gets done across people and systems, map the workflow.
Related Services
