The do-not-automate list is the most valuable page in the plan
Every workflow audit I run ends with a list of processes that should stay manual. Clients are often surprised by how much money that page saves them.
By Stanley Watterson
When someone commissions a workflow audit, they expect a list of things to automate. They get that. But the page they end up quoting back to me months later is usually the other one: the list of processes that should stay exactly as they are.
Three reasons a process should stay manual
The volume does not justify it. A task that takes twenty minutes a month is four hours a year. A build that removes it might take forty hours and then need maintaining forever. The arithmetic is not close, and no amount of enthusiasm fixes it.
Automation multiplies the risk. Some processes are slow precisely because a human is checking something. Speeding that up does not remove the check — it removes the checking. If the cost of being wrong is a regulatory problem or a lost client, the friction was doing a job.
It is the part of the job people like. This one gets dismissed as sentimental, and it should not be. If you automate away the interesting twenty percent of someone's role and leave them the exception handling, you have not made them more productive. You have made them more likely to leave.
Why it belongs in writing
The value is not the decision, it is the record. Six months from now someone will ask why the invoice reconciliation was never automated. Without a written answer, you re-run the analysis. With one, you spend thirty seconds.
It also protects you from the next vendor. When someone arrives promising to automate everything, a document explaining exactly why three of those processes were deliberately left alone is a very efficient conversation.