Every process exists in two versions. One is the version people describe in meetings, or draw on a whiteboard, or write in a handbook. The other is the one that actually runs on a Tuesday afternoon when someone is off sick and a customer has just changed their order. Almost every improvement project that goes wrong starts from the first version.
Mapping the current state means documenting the second one. It sounds like an admin exercise. In practice it is the most valuable piece of analysis in the whole project, because everything that follows, including requirements, automation choices and software selection, depends on it.
Processes drift. A step is added after a mistake and never removed. A spreadsheet appears because the system does not quite do what someone needs. One person learns a shortcut and everyone nearby copies it. Exceptions that were rare become routine, and the handling of them lives in people’s heads. None of this is careless. It is what happens when a business grows faster than its documentation.
The result is that if you ask three people how an order is processed you often get three different answers, each one correct for that person. Only by following real work from beginning to end do you see the whole thing.
A good map shows who does each step, what triggers it, which system or document they use, what information goes in and out, where decisions are made, and where work is handed from one person or team to another. It also shows exceptions, meaning what happens when something is missing, wrong or late. Most of the hidden cost lives in the exception paths, so a map that only shows the happy path is not much use.
Swimlane diagrams are the usual format, with one lane for each person or team. BPMN 2.0, which is now an international standard published as ISO/IEC 19510, gives a shared set of symbols for events, tasks and decisions. You do not need the full notation to get value, but using consistent symbols means that a business analyst, a developer and a vendor can all read the same diagram without a translator.
The most useful measurement in current state mapping is the difference between touch time and elapsed time. Touch time is how long someone actually works on an item. Elapsed time is how long the item takes to get through the process from start to finish. In many business processes the gap is large, because items spend most of their life waiting in an inbox, a queue or a folder for someone to pick them up.
Consider an illustrative example. A purchase approval takes six minutes of real work, but it waits in the approver’s inbox for two days on average. If someone proposes automating the six minutes, they are working on the wrong problem. The delay is the queue, and it will not shrink until the business changes who approves, when, or what needs approval at all.
Measuring the two separately changes the conversation. It moves the discussion from working faster to waiting less, and it shows where a change in the process will pay back before any money is spent on technology.
Every handoff is a place where information can be lost, delayed or re-entered. Mapping the current state makes these visible. Typical findings include the same data entered in two systems, a form that is sent back three times for the same missing field, and a step where someone exports a report, edits it by hand and sends it on. Each of these is a candidate for redesign, and none of them appears on an org chart.
Do not ask people how the process should work. Ask them to walk you through the last three real cases from start to finish. Ask what they did first, what they opened, who they asked, and what they did when something did not match. Follow one real item, such as a single order or invoice, through every team that touches it. Note each moment someone opens a spreadsheet, sends a message to check something, or says it depends.
Then play the map back to the people who do the work, not only to their managers. Corrections at that stage are the most valuable ones.
A common pattern in order processing shows why this matters. The official process says an order is confirmed once payment clears. In practice, one person on the team checks a separate stock spreadsheet before confirming anything, because the system’s stock figures are not fully trusted. That step is not written down anywhere. If a new system is specified from the official process, it will not include a stock check, and the business will discover the gap when orders are confirmed for items that are not available.
A current state map would have caught it in the first week, because the person doing the check would have mentioned opening the spreadsheet as soon as they were asked to walk through a real order.
Maps go wrong in predictable ways. They are drawn in a meeting room without watching the work, so they show the ideal path. They go into too much detail on one step and skip the handoffs entirely. They are produced by one person and never reviewed by the team, so errors survive. And they record steps but not time, so the map cannot show where the delay is. Each of these is avoidable with a clear scope, a set of real cases to follow and a review with the people who do the work.
A current state map has three uses. It shows where the waste is, so you can decide what to fix, what to automate and what to leave alone. It becomes the input for requirements, because you cannot specify a new system without knowing what the old one really does. And it is the baseline that lets you prove an improvement. Without a measured starting point, any claim about time saved or errors reduced is an estimate.
Mapping current state processes is a core part of our process improvement and business analysis work. We follow real cases, document the process as it runs including the exceptions, measure touch time against elapsed time, and hand you a clear set of maps and findings along with a prioritised list of changes. You do not need a business analyst on the payroll to get it done.
If you would like a quick view of where your own processes stand before committing to anything, the Process Health Checker on groowfuse.com is a good starting point.