Process mapping before automation: a practical guide

01

Define the start and the outcome

Name the event that starts the process and a clear result. “Order handling” is too broad; a useful scope may begin when a complete order arrives and end when dispatch is confirmed and settlement data is sent.

Assign a process owner and the people responsible for each activity. Automation cannot repair unclear ownership.

02

Show data, systems and waiting

For every step, record where data comes from, where it is changed and where it goes. Include email, spreadsheets, forms, CRM, ERP, WMS and work completed outside systems.

• active handling time and waiting time;
• manual copying and re-entry;
• missing data, duplicates and repeated checks;
• decisions requiring expert judgement;
• exceptions and escalation routes.

03

Make exceptions visible

Costs often arise outside the happy path: an incomplete document, incorrect address, missing approval or unavailable system. Name each exception, estimate its frequency and assign responsibility.

A safe automation can stop, explain the cause and hand the case to a person with the required context instead of forcing every case through.

04

Turn the map into a pilot

Select a frequent, stable section of the process. Define inputs, outputs, error controls, execution logs and a fallback plan.

Compare the same measures before and after the pilot. This is the only reliable way to show whether the solution creates value.