When Is a Workflow Stable Enough to Automate?

Automate a stable rule, not a recurring feeling. A workflow is ready for a small automation test when the trigger, steps, exceptions, owner, and expected result can each be written in plain language.

Five stability checks

1. The same trigger appears often enough to matter.
2. The path is mostly the same each time.
3. Exceptions can be named rather than discovered after launch.
4. A person can inspect the outcome without reconstructing the process.
5. Turning it off will not damage a critical relationship or system.

If any check fails, use WAIT. Run the work manually for a bounded period and keep an exception list. That is not delay for its own sake; it is how you avoid automating a moving target.

Google’s SRE guidance describes toil as repetitive, predictable work and stresses measurement, risk assessment, and iterative development before treating automation as a cure-all. The scale is different, but the operating lesson holds: start narrow, observe the maintenance created, and retain a clear way back. Read the source.

Run this workflow through the Matrix

A 14-day test

Automate one step, not the whole system. Record the time saved, exceptions created, failed handoffs, and maintenance required. Review it in 14 days. If exceptions grow faster than the work removed, return to WAIT or DELEGATE.

For the opposite failure mode, read seven signs you automated too early.