Map the process before you automate it
Most businesses don’t have an automation problem. They have a “nobody has mapped the process” problem. Fix the second one and the first gets cheap.
When a team asks us to automate something, the first thing we do is refuse to automate anything. We map it instead. It sounds slower. It is the step that makes everything after it fast.
Why mapping comes first
A process that lives in one person’s head is not a process. It’s a habit. And habits are full of quiet exceptions: the client who gets invoiced on the 5th, the order type that skips a step, the approval that only Dana can give. Automate the habit and you automate the exceptions too, badly.
Writing the process down surfaces those exceptions while they are still cheap to handle. You want to find the edge cases on a whiteboard, not in production.
What a map actually looks like
We keep it plain. For each process we write down four things:
- Trigger. What starts it? A new invoice, a form submission, a date.
- Steps. Each action, in order, in the reader’s words. “Copy the total into the spreadsheet,” not “sync the data.”
- Decisions. The forks. “If the order is over $500, route it to a manager.”
- Handoffs. Where the work moves between people or tools, and who owns it.
That is the whole artifact. No diagrams unless the forks get complicated.
When automating is worth it (and when it isn’t)
Here is the honest part. Automation pays off when a process is repetitive, rules-based, and runs often enough to matter. Chasing invoices, entering orders, building the same weekly report: good candidates.
It’s not worth it when the process changes every time, or runs twice a year, or needs real judgment at every step. Automating those costs more to maintain than the manual version ever cost you. We’ll tell you when that’s the case, because a workflow you have to babysit is worse than no workflow at all.
Start with one process
You don’t need an automation strategy. You need one mapped process and a clear answer to “what happens when this runs on its own?” Pick the task your team complains about most. Map it this week. The automation part is the easy half.