Process Mapping

Short answer: Process mapping produces a diagram of a business process, such as customer onboarding, hiring or handling a delivery complaint. The map shows each step, the person or team responsible and the systems they use. It also shows the decisions that change the path and the handoffs between people. Everyone involved gets a shared, concrete picture of the current process. That picture usually differs from what any single person assumed.

Process maps come in several forms. A simple flowchart shows steps and decisions in order. A swimlane diagram gives each role or team its own lane, so handoffs and gaps in ownership are easy to see. A high-level overview lists only the main stages, inputs and outputs before the team adds detail. A team usually maps the current process first and then designs an improved version. Process mapping usually comes before automation. It shows which steps the team should remove or simplify instead of automating them.

The team picks one process and sets clear start and end points. The people who actually do the work, not only their managers, walk through real recent examples step by step. For each step, the team records who does it and which system or document they use. It also records how long the step takes, how long work waits before it and how often it goes wrong. The team then adds decisions and exception paths. It checks the draft against a few more real cases. Then it looks for duplicate steps, unnecessary approvals, long waits and data that staff type in twice. With measured timings, the team can compare the current process with the improved one.

A distributor maps its order process for 500 orders a month. The map shows 14 steps, 5 handoffs and an average of 4 days from order to dispatch. Only about 3 hours of that is active work. One day goes on waiting for a manager to approve every order. But managers almost never refuse orders under 2,000. About 60% of orders, or 300 a month, fall under 2,000. The company drops the approval for those orders, so 300 orders a month each ship a day sooner.

Process mapping gives leaders facts on which to base improvement and automation decisions. It shows where time and errors actually occur, which steps add no value and who owns each part of the work. Mapping before buying software helps the company avoid automating a broken process. It also gives vendors a clear description of what the business needs.

Maps built from interviews show how people believe the work happens. They can miss workarounds, exceptions and informal steps. A map is a snapshot, and it goes out of date as the business changes. Mapping in too much detail can take weeks without leading to decisions. A more reliable picture combines interviews with real examples and timings. Where possible, add process mining, which rebuilds the real process from the time stamps that systems record for each step.