The 15-20 hours a week a 7-country team lost to manual maintenance

An Application Managed Services team spread across 7 countries was losing between 15 and 20 hours a week to repetitive manual maintenance — backups, database tuning, resource resizing. Automating that work with runbooks, instead of asking the team to absorb it, cut those hours to nearly zero in two months, without adding a single person to headcount.

Nearly half an FTE on tasks nobody questioned

Almost half a full FTE, every week, on tasks nobody questioned because they had always been done that way: running backups by hand, tuning databases, turning cloud resources on and off on a schedule. Necessary, yes. But repetitive, error-prone at that volume, and silently expensive on a team that was also handling client cases every day.

Why automate maintenance instead of just demanding more discipline?

The easy option would have been to document the manual process better and ask the team for more rigor. The real decision was different: that wasn't work people should keep doing by hand indefinitely. We built a set of runbooks that automated backups, tuning routines, and resource scheduling end to end, and validated each one carefully before retiring the manual process it replaced.

How fast is that capacity recovered?

In roughly two months, those 15-20 weekly hours of manual work dropped to practically zero, fully validated. That time went straight back into case resolution and higher-value work, on a team serving seven countries, without adding a single person.

Toil: the name the industry gives this work

In Google's SRE discipline there's a precise term for this kind of work: toil — operational, repetitive, automatable work that delivers no lasting value. The industry recommendation is that no operations team spend more than 50% of its time on toil; when it does, that's exactly the symptom that something needs automating before it needs more people.

The lesson I take

Before asking for more headcount to sustain an operational load, the first question should be how much of that load is repetitive work that could already be automated. Recovering capacity is almost always cheaper — and faster — than hiring to cover the symptom.

Data sources: Google SRE Book — definition of toil and the recommended 50% threshold for an operations team's time.

Frequently asked questions

How do you recover operational capacity without adding headcount? By first identifying how much of the load is repetitive, automatable work (toil), and automating it with validated runbooks before retiring the manual process. In this case, 15-20 weekly hours dropped to nearly zero in two months.

What is toil in SRE? Operational, repetitive, automatable, manual work that scales linearly with service growth and delivers no lasting value. Google SRE recommends it not exceed 50% of an operations team's time.