I build systems that delete recurring engineering work.
Your team does work a system should be doing. I build the system.
Proof
Three things I removed
-
67
pull requests, 30 days
The merge that files its own paperwork
Merging used to be the start of ten minutes of clicking. Now it is the end of the work.
-
8 → 0
ideas in, builds out
The idea pipeline that mostly says no
Six rejected, two parked, nothing built, in two days, for $11.81. That is the system working.
-
5–12
tabs, every morning
The inbox I stopped opening
The reviews that need me are open in one window before I sit down. No digest, no dashboard.
Work
The rest of it
The case studies go into the parts that are actually hard: what happens on the second run, where a system is not allowed to decide, and what each tool still gets wrong. They are grouped by the kind of problem rather than by the year.
Method
How I work
Find the step nobody would ever write down. Find the seam between the systems that already know it happened. Deliver the state somebody was assembling by hand, not a report about it. Decide where the model is not allowed to act. Then make the whole thing safe to run unattended, indefinitely, because an automation you have to supervise is not an automation — it is a second job.
The longer version, with the case studies as evidence.
Next
Working together
If there is a process your team runs by hand every week, I would like to hear what it is and how often it happens. That is usually enough for me to say something useful in a reply — contact@aarongorman.dev.