How to Map a Workflow Before You Automate It

Automation projects that skip process mapping almost always hit the same wall: the automated workflow breaks at an edge case nobody thought to document, or it faithfully reproduces a broken process at higher speed.

Mapping a workflow before you automate it is not overhead. It is the work.

What Process Mapping Actually Means

Process mapping means writing down, in enough detail, what actually happens — not what is supposed to happen. The gap between the documented process and the lived process is where most automation failures originate.

Start by talking to the people who do the work. Ask them to walk you through the last five times they completed the process. You will quickly discover:

• Steps that happen informally and have never been written down
• Judgment calls that are made the same way every time — and could be encoded as rules
• Handoffs that create delays because the recipient does not know what to do next
• Exceptions that happen more frequently than anyone realizes

A Simple Structure to Use

For each step in the process, capture:

• What triggers this step
• Who performs it
• What inputs they need
• What they do with those inputs
• What the output looks like
• Where the output goes
• How long it typically takes
• How often it goes wrong, and what happens when it does

This is not glamorous work. It is also the only way to know what you are actually building before you start building it.

The Automation-Ready Indicator

A process is ready to automate when you can describe it completely in writing and hand that description to someone who has never seen the process — and they can follow it without asking clarifying questions. If they have questions, the process is not sufficiently defined. Define it first.