Process mapping
In short. Process mapping is drawing out how a piece of work actually moves through a business, step by step, from the first trigger to the finished result. It shows who does each step, in which system, and where work waits or gets redone, so delays and duplication become visible.
Last checked against its sources on 10 October 2026. How we write these.
A process map can be as simple as boxes and arrows on a whiteboard. Each box is a step, each arrow a hand-off, and the useful detail is written beside them: who does it, which system they use, how long the work takes and how long it waits before the next step.
Take a business that receives enquiries by email. One person copies the details into a spreadsheet, a second checks availability, the owner approves the price and someone else sends the quote. Mapped out, it is easy to see that the same details are typed twice and that most of the elapsed time is spent waiting for the owner.
The aim is not a beautiful diagram. Lean practitioners make the same point about the related technique of value-stream mapping: a perfect drawing is not the goal, finding and removing waste is. Map what really happens, not what the procedure document says.
Once the map exists, the questions follow naturally: which steps can be removed, where is the bottleneck, which hand-offs lose information, and what is the first change worth making.
Questions people ask
When should you map a business process?
When work is regularly late, different people describe the same process differently, mistakes keep recurring, or you are about to buy software to fix it.
Do you need special software to map a process?
No. Paper, a whiteboard or a simple worksheet is enough for most processes. Software helps when maps need sharing or updating often.
Sources
- Value Stream Mapping (Lean Enterprise Institute) checked 10 October 2026