Mapping a process means describing, step by step, how work is really done today: who does what, with which systems, how long it takes and where time and money are lost. It is the first step of any improvement, because without it you automate blind. The best source of information is the people who live the process every day.
What a process map is and what it is for
A process map is an organised description of a process that records its steps, the people involved, the systems used, the time each step takes and the points where errors or waits occur. It is not a decorative diagram: it is the basis for deciding what to improve.
It serves three purposes:
- Seeing the real process. The one that is actually carried out, not the one in the manual.
- Finding where time goes. Repetitive tasks, double checks, waits between departments.
- Prioritising by impact. Deciding what to improve first with data, not hunches.
Why you need to talk to the people who live the process
The documented process and the real one almost never match. Over time, shortcuts, side spreadsheets, reminder emails and checks nobody wrote down creep in. Only the people doing the work know where they are.
That is why the map starts with interviews. A few well-prepared conversations with the people involved reveal more than weeks of reading documents. Ask:
- What reaches you, from whom and through which channel?
- What do you do with it, step by step, and in which system?
- How long does each step take and how often do you repeat it?
- What usually goes wrong, and what do you do when it does?
- Who do you hand it to, and what do you wait for in between?
What a good process map should capture
A useful map goes beyond boxes and arrows. For each step, it records the following:
| Element | What to note |
|---|---|
| Step | What is done, with a clear verb |
| Owner | Person or role who does it |
| System | ERP, CRM, email, spreadsheet or paper |
| Volume | How many times a day, week or month |
| Time | Minutes per case |
| Errors | What fails and how often |
| Waits | Idle time between one step and the next |
With this table complete, the process stops being an opinion and becomes a measured starting point.
How to spot lost time, errors and bottlenecks
With the map in front of you, the losses usually stand out. These are the most common signs:
- Data typed twice. The same data entered into two different systems.
- Bridging spreadsheets. A spreadsheet joining what the systems do not.
- Checks that add nothing. Manual controls a system could do better.
- Waits between departments. The case stalls because nobody knows it is their turn.
- Reliance on one person. The process only moves if a particular person is available.
A bottleneck is the step that limits the speed of the whole process. Improving any other step does little while that one stays the same.
How to prioritise improvements by impact
Not everything the map reveals deserves equal attention. For each possible improvement, estimate three things: how many hours it frees up, how many errors it prevents and what risk it reduces. Then rank them.
Example: if a step takes 10 minutes per case and is repeated 1,500 times a month, it accounts for 250 hours a month. Another, more eye-catching step repeated 50 times weighs far less.
The result is an improvement roadmap prioritised by impact. Some improvements are solved by simplifying the process, with no technology at all. Others call for automation, AI agents or custom software. We explain this in which processes to automate first.
Which tools you need to map a process
Fewer than you might think. For a first map, a spreadsheet or shared document holding the table of steps is enough, together with a simple diagram anyone on the team can follow. Specialist modelling tools help with very large processes, but they do not replace the interviews.
What does help is backing the map with data from the systems. Many ERPs and CRMs record when each document is created and changed. Those logs let you check the times people describe and uncover waits nobody had mentioned.
Three practical rules keep the map useful:
- One verb per step. “Post the invoice”, not “invoice management”.
- One person or role per step. If nobody owns it, you have already found a problem.
- One source for every figure. An interview, a system or a sample counted by hand.
What to do after the map
The map is not the end; it is the beginning. Once the roadmap is approved, each chosen improvement is defined in detail with the team, built, tested with the people who will use it and rolled out progressively. It is then measured against the starting point the map itself established.
In more than a decade of improving processes, the lesson that comes up most is simple: the time spent understanding the process is repaid many times over. You can see how this work is organised in how we work.
Which mistakes to avoid
- Mapping from an office, without talking to the people who do the work.
- Describing the ideal process instead of the real one.
- Recording steps without measuring times or volumes.
- Automating before simplifying.
Where to start
Pick a process everyone considers burdensome and ask two people to describe it step by step. The differences between their accounts will already tell you a great deal. If you would rather do it with us, request a first conversation to get to know your company and see where we can help, or see how we approach process consulting.