Map the process before you start configuring a tool

First, describe what actually happens

A work guide often describes the ideal process, but the real work includes waiting, follow-up questions, and unexpected cases. Before automating, observe the entire process from beginning to end. Who starts the task? What data is needed? Who makes decisions? Where does the result go? When is the task considered complete?

Write down the steps in order and mark where people use their judgment. Sort exceptions into those that can be handled with another rule and those that need human review. For example, the system could return an incomplete form for more information, while a responsible team member could assess an unusual case. Don’t add a rule just to avoid a conversation about accountability.

Ask someone who uses the process to review your map. They may point out a step you missed or explain that the same word means different things to different teams. Mapping can also reveal unnecessary work that would be better removed than automated. If the process changes every week, first agree on a stable approach, or automate only the part that stays the same. A tool should follow a clear process, not hide the fact that it’s unclear.

As you observe, ask how the official guide differs from the way people actually work. Those differences often explain why errors occur in an automated process.

While mapping a process, you come across a frequent exception that no one can explain. What should you do?

Automation in Practice: Choose Tasks and Check Results

Continue the training

Enter your email address to continue the training.