Map a process before automating it

Choose a scope

A useful process map starts with one journey: from the initial request to the result handed to the next person. Record its trigger, expected outcome and owner. "The entire sales department" is too broad; "handle a new enquiry" gives you concrete steps to follow.

Look at several recent cases rather than describing only the ideal procedure. The path people actually followed reveals informal handoffs and decisions nobody documented.

Describe the real workflow

For each step, record who acts, which tool they use, what data they need and when the work moves to someone else. Include possible decisions: approval, rejection, waiting for information or sending the task back.

Exceptions matter as much as the normal path. An incomplete request or a duplicate may change the owner, timeline and response. If the map ignores these cases, the automation will have to improvise.

Find the friction

Mark repeated data entry, waits without an owner, checks performed too late and information lost between tools. For each issue, assess frequency and impact using observations or available data rather than inventing a potential gain.

A step may be unnecessary, badly placed or necessary but poorly supported. Removing a redundant approval can be more useful than automating it.

Decide what to automate

Start with frequent steps governed by a stable rule and a verifiable outcome. Define the required data, error handling and the person who takes over when a case falls outside the rule.

Rare, ambiguous or sensitive decisions can remain human. Mapping a process does not mean automating every step: the value lies in a more reliable journey, not the greatest number of scenarios.

Test the future workflow

Ask someone who does the work and someone who receives its result to walk through the map. Have them identify the next step for a normal case and an exception. If their answers differ, the process is not yet clear enough.

After a change, compare delays and rework on a small scope. Update the map if actual work begins to diverge from the intended path again.

Keep the map useful

The map remains a decision tool if its owner updates it whenever a role, tool or rule changes. A readable, tested page is worth more than a detailed diagram nobody consults.

• Define one journey from start to finish.
• Record people, data and exceptions.
• Remove unnecessary steps before automating.
• Test and update the map with the team.