Process mapping makes invisible workflows visible so they can be examined, questioned, and improved. In service design and organisational design, many of the most painful user experiences are caused not by bad interface decisions but by broken internal processes that users encounter as friction, delay, or inconsistency. Making those processes explicit is the first step to redesigning them. A process map creates a shared picture that enables teams across different organisational functions to see the same reality at the same time.
What It Is
A process map is a visual diagram that shows the sequence of steps, decisions, actors, and handoffs involved in completing a task or delivering a service. Formats range from simple flowcharts to swim lane diagrams that separate activities by actor or department. The level of detail can vary from high-level overviews to granular step-by-step flows depending on the needs of the analysis. Process maps document both the official process as it is designed to work and the actual process as it is practised in reality, which are often significantly different.
How to Run It
Begin by choosing a process to map and defining its start and end points. Gather data through interviews and observation with the people who carry out the process: frontline staff are usually more accurate sources than managers. Build an initial map using sticky notes on a wall so it can be easily revised. Walk through the map with participants to check for accuracy and identify missing steps or informal workarounds. Once the current-state map is validated, analyse it for bottlenecks, handoff failures, duplication, and unnecessary complexity. A future-state map can then be created that addresses the most critical pain points.
When to Use It
Process mapping is essential in service design projects where the challenge spans multiple departments, digital and physical channels, or multiple organisations. It is also valuable in digital product design when a complex workflow needs to be translated into a clear and logical interface. Use it when user research reveals recurring frustrations that cannot be explained by interface design alone, since these often point to underlying process problems that need to be addressed at the service level rather than the screen level.
Tips for Success
Document what actually happens, not what is supposed to happen. The gap between the two is usually where the most important design opportunities lie. Use consistent symbols and notation so that the map is readable by everyone on the team. Colour-code pain points, handoffs, and decision points to make patterns immediately visible. Validate the map with multiple people who work in the process to ensure accuracy: individual accounts are often incomplete, and cross-validating across perspectives produces a far more reliable picture.
