What is it?
A Process Map shows how work actually happens. It turns conversations into something visible, making it much easier to understand how work flows from one step to the next.
What's it really for?
The map has an awkward habit of exposing folklore. Every organisation has work that everybody understands slightly differently. A Process Map simply introduces those different versions to each other.
You know when…
You ask two experienced people to explain how the work flows. Neither of them is wrong, but neither description quite matches the other.
By the time a third version appears, somebody usually says, “Perhaps we should draw it.” They are normally right.
Have a go
- Mark the first step and the last.
- Add the activities that happen in between.
- Include decisions, delays, handovers and loops.
- Walk the map with the people who do the work and change it until it feels true.
Why it works
Memory is surprisingly unreliable. Ask five people to describe the same process and you will often end up with five different versions, each perfectly believable. Drawing the process changes the conversation. Instead of debating whose memory is correct, people begin improving something they can all see together.
Look for…
Handovers deserve a second look. That is where work often slows down, waits, gets misunderstood or quietly disappears. Notice the loops too. If something keeps coming back for another attempt, it is usually trying to tell you something.
Watch out…
Try not to map the process from a meeting room. Processes have an unfortunate habit of becoming much tidier when they are described from memory. Go and see the work instead. The map should reflect reality, even when reality is untidy.
Worth noticing…
Every process is perfectly designed to produce the results it is currently producing. The map simply helps you see why.
Try next…
Use a Value Stream Map when the map reveals queues, waiting or rework. Use a Fishbone Diagram when a recurring problem needs its possible causes explored.