Automating the boring parts: a framework for business process automation
July 24, 2026 · 5 min read
Every operations team has a list of processes everyone agrees are painful. Not every item on that list deserves automation, and treating them all the same way is how automation budgets get wasted.
The processes worth automating first share three traits: they happen often, they follow a rule a person could write down in a sentence, and getting them wrong is expensive. A process that happens twice a year, however annoying, is rarely the right place to start.
The processes to be suspicious of are the ones where "it depends" comes up in almost every sentence someone uses to describe them. That's usually a sign the process needs to be redesigned before it's automated — otherwise you've just made an inconsistent process run faster.
The automations that actually stick are the ones built with an escape hatch: a clear, visible way for a human to intervene when the automation hits a case it wasn't built for, rather than silently doing the wrong thing or grinding to a halt.
Measured well, the return on automation isn't just time saved. It's the number of times a person no longer has to context-switch out of real work to babysit a repetitive task — and that's usually worth more than the hours on the spreadsheet suggest.