The Automation Projects That Quietly Fail
Nobody announces an automation failure. The workflow just slowly returns to spreadsheets, and the licence renewal gets questioned once a year.
Automation failures are quiet. There is no outage, no incident review, no post-mortem. There is just a gradual drift back to the manual process, a bot that someone keeps meaning to fix, and a subscription that survives a few budget cycles before anyone asks why.
Automating the mess
The most common cause is deceptively simple: we automate processes we have never examined. A workflow that has accreted over years — exceptions, workarounds, tribal knowledge — gets encoded exactly as it exists. The automation inherits every flaw and adds a new one: it is now harder to change.
Automation without process becomes chaos — faster, more consistent, more expensive chaos.
The discipline is to simplify before you automate. Map the process as it should be, not as it is. Remove steps before you digitise them. The best automation projects I have seen spent most of their effort on subtraction.
Choose boring, high-frequency work
The highest-return automations are unglamorous: reconciliations, report generation, ticket routing, provisioning. High frequency, low ambiguity, clear rules. They build organisational confidence and free real hours. The ambitious edge cases can wait until the muscle exists.
And decide upfront who owns the automation after launch. A bot without an owner is a failure on a timer.
Stay in the loop
Get new perspectives by email — written occasionally, never noisily. Unsubscribe anytime.