Measuring and Reducing Toil
You'll learn how to quantify toil and systematically eliminate it through automation.
What Is Toil Measurement?
In the previous lesson, you learned that toil is manual, repetitive work that doesn't add lasting value. But how much toil do you actually have? Measuring toil as a percentage of time is the first step to reducing it.
Track how your team spends its time across categories:
- Toil: Manual operational tasks (ticket responses, manual deploys, log diving)
- Engineering: Building automation, improving systems
- Project work: New features, migrations
- Overhead: Meetings, training, planning
If your team spends 60% of their time on toil, that's 60% of human potential wasted on tasks a computer should handle.
Strategies to Reduce Toil
1. Identify High-Impact Targets
Not all toil is equal. Focus on tasks that are:
- Frequent (daily or weekly)
- Time-consuming (>30 minutes each)
- Error-prone when done manually
2. Automate Systematically
Build tools and scripts to eliminate repetitive work:
- Automated deployment pipelines instead of manual releases
- Self-service dashboards instead of answering "how's the system?" questions
- Automated alerts with runbooks instead of constant monitoring
3. Set Toil Budgets
Just like error budgets limit unreliability, toil budgets limit manual work. SRE teams typically target 50% or less time spent on toil, reserving the rest for engineering.
Key Takeaway: Measure toil as a percentage of time, identify high-frequency manual tasks, and systematically automate them—treating toil reduction as an engineering priority, not an afterthought.