Hook
If you do it twice, script it.
Problem
Manual automation gaps in CI/CD are slow, inconsistent, and error-prone. Teams spend time on toil instead of improving the system.
Why it matters
Automation makes outcomes reliable and frees people to focus on higher-value work. It also encodes knowledge so it does not live only in a few experts.
Signals you are here
- Runbooks are mostly copy-paste commands
- On-call repeats the same manual tasks
- Provisioning or deployments are slow and manual
- Quality depends on who is doing the work
Anti-patterns
- Manual approvals for routine tasks
- One-off scripts that only one person understands
- Automation without ownership or maintenance
- Copy-paste operations across environments
Try this
- Automate workflows end-to-end in CI/CD (build, test, release)
- Provide self-service tooling for common requests
- Use infrastructure as code for repeatable changes
- Build bots for routine operational tasks
- Treat automation as production software
Example
User provisioning required a ticket and manual steps. A simple workflow and API integration reduced turnaround from days to minutes and eliminated frequent errors.
Reflection prompt
List the top three tasks you repeat every week. Which one would you automate first?
More like this
Heuristic
Work in Small Batches
Small batches make failure cheap and learning fast.
Heuristic
If You Cannot Automate It, You Do Not Understand It
Automate to learn, not just to save time.
Heuristic
Make Infrastructure Disposable
Cattle, not pets.
Heuristic
Avoid Local Optimization
Optimize the system, not the silo.
Heuristic
Empower Autonomous Teams
Autonomy with guardrails.
Heuristic
Every Output Is Someone Else's Input
Handoff quality sets the pace of flow.