A team can agree that a process is too slow and still disagree about what should change. One person sees repeated data entry. Another is worried about missing information. Someone else has a spreadsheet that quietly fills the gaps in the official system. If the conversation starts with a tool, those differences can remain hidden until the new solution is already difficult to change.
This is why a process map can be useful before automation. It is not a diagram to make the work look tidy. It is a shared way to see what people actually do when the work is moving, waiting or not quite going to plan.
Map the work, not the ideal version of it
Most teams have a documented route and a lived route. The documented route shows the intended handoffs. The lived route includes the email someone sends because a system field is unclear, the colleague who knows an exception, and the check that happens only when something goes wrong. Neither view should be dismissed. The difference between them is often where the useful question begins.
A practical first map needs only five things:
- Trigger: what starts the work?
- Actors: who performs, approves or depends on each step?
- Handoffs: where does information change owner, system or format?
- Exceptions: what happens when the normal route does not fit?
- Outcome: what observable result means the work is complete?
Start with a whiteboard, a shared document or a simple table. Formal notation such as BPMN becomes helpful when a group needs a more precise language for events, activities, decisions and flows. It is not a requirement for understanding the first version of the work.
Pay attention to the detours
A workaround is not automatically a mistake. It may protect a customer, carry information that the main system cannot hold, or keep work moving while a team deals with a real constraint. But a recurring workaround is worth looking at. It can point to an unclear responsibility, a missing piece of information or a rule that no longer matches the job people need to do.
Instead of immediately asking how to remove the detour, ask what it is helping someone achieve. That keeps the discussion closer to the work. It can also prevent a well-meant automation from making a useful human check disappear before the team understands why it exists.
Use the map to make one decision
The map is not the deliverable. Its value is in the decision it makes easier. Look for one place where work waits, repeats, loses context or depends on a private memory. Then decide whether that part should be simplified, clarified, standardised, automated or deliberately kept human for now.
Choose one question for the mapping session: “Which handoff causes the most avoidable work?” or “Which update exists in more than one place?” If the team cannot answer it yet, the map has already shown what to explore next. If it can, then you have a smaller and more useful starting point than “automate the process.”
Further reading
- Object Management Group — BPMN 2.0.2. A formal standard for describing business-process events, activities, decisions and flows.
- Outmazgin et al. — Workarounds in business processes. An industrial case study of how recurring workarounds can reveal possible goal and process misalignments.