It starts with good intentions. Someone in sales operations builds a workflow that sends quotation data to the ERP. It works, it saves an hour a day, everyone is happy. Three years later that person leaves — and the workflow keeps running. Until it doesn’t.
How shadow automation happens
Most automations are not planned as systems. They are built as shortcuts, by the person who feels the pain most. Nobody reviews them, nobody documents them, and nobody decides who is responsible when they fail. That is not negligence; it is simply how small tools grow into important ones.
Each of these is harmless on its own. Together they mean that a central business process depends on knowledge that walks out of the door with one person.
The day it stops
When an orphaned automation fails, the damage is rarely the failure itself. It is the time spent finding out what the automation did, where it ran, which data it touched and who might know. Hours turn into days — while the process it supported stands still.
That is exactly the kind of downtime that never appears in any statistic. How to put a number on it is covered in What Does an Hour of Downtime Really Cost?.
Four rules that prevent it
- Every automation has a named owner — a role, not just a person.
- Service accounts, not personal logins. Credentials live in one managed place.
- A short description per workflow: what it does, what it depends on, who to call.
- Business-critical automations are monitored like any other system — see Monitoring Is Not Watching: What Real System Monitoring Looks Like.
An automation nobody owns is not saving time. It is borrowing it.
Want to know which of your automations nobody owns? We build, run and monitor systems ourselves — and we know where automation pays off and where it becomes a risk.