Systems
How to map a messy process without overcomplicating it
A simple method for seeing the real steps, delays and workarounds in everyday operations.
5 min read
A useful process map does not need specialist software or perfect notation. It needs to show what really happens—including the workarounds people normally leave out.
Pick one start and one finish
Define a narrow journey such as ‘customer submits an enquiry’ to ‘first appointment is confirmed’. Broad maps become vague; focused maps reveal action.
Follow a real example
Use a recent piece of work and ask what happened next at every step. Record the person, tool, information and waiting time involved. Reality is more useful than the official procedure.
Mark the friction
Highlight every manual copy, unclear decision, repeated request, approval wait and step that depends on memory.
- Where does information enter twice?
- Where does work sit without an owner?
- Which exceptions happen often?
- What does the customer have to chase?
- Which status questions interrupt the team?
Simplify before automating
Remove unnecessary steps, clarify decisions and standardise the information collected. Automating a poor process only makes its problems happen faster.