The first phase is the fun one because everything is greenfield. Month three is when you hit the process that only one person understands, and they are on leave.
Building for the Failure Case
Production automation is mostly error handling. The happy path is the small part, and it is the part that gets all the attention during the build.
Every external call can fail, time out, or return something unexpected. A workflow that assumes otherwise will work until precisely the moment it matters.
| Failure | Minimum acceptable handling |
|---|---|
| API timeout | Retry with backoff, then alert a human |
| Unexpected payload shape | Fail loudly, never silently continue |
| Credential expiry | Alert before expiry, not after the break |
Ownership Beats Documentation
Documentation rots. A named owner who feels responsible when something breaks does not, at least not as fast.
The practical test is simple: if this workflow failed tonight, who would notice, and would they know what to do? If either answer is unclear, that is the actual risk.
- One named owner per workflow, not a team
- A one-line description of purpose, written at build time
- An alert that reaches a person, not just a log file
Cost, Honestly Accounted
The build cost is visible and the maintenance cost is not, which is why automation is consistently underestimated by the people commissioning it.
Assume ongoing maintenance runs a meaningful fraction of the original build effort every year, and budget for it explicitly rather than pretending it is zero.
What Changes at Scale
Behaviour that is fine at ten requests a day becomes a problem at ten thousand. Rate limits, cost per call and queue depth all move from theoretical to urgent.
The version of the system that survives scale usually looks more boring than the version that impressed everyone in the demo.
Conclusion
The tooling is rarely the hard part. Scope it narrowly, measure the baseline first, name an owner, and build for the failure case rather than the demo.
Frequently Asked Questions
How long before this pays for itself?
Most well-scoped automations pay back within a few months, but only when the baseline was measured beforehand. Without a baseline you cannot honestly answer this question at all.
Do we need a dedicated person to run this?
Not dedicated, but named. The failure mode is shared ownership, where everyone assumes someone else is watching.