## Core Insight Toil is operational work tied to running a production service characterized by six attributes: manual, repetitive, automatable, tactical, devoid of enduring value, and scaling linearly (O(n)) with service growth. The more attributes a task matches, the more likely it is toil. Critically, toil is not work you dislike, administrative overhead, or grungy work that produces lasting value. ## The Six Attributes 1. **Manual** — requires hands-on human time, even if running a script 2. **Repetitive** — done over and over, not novel problem-solving 3. **Automatable** — a machine could do it equally well 4. **Tactical** — interrupt-driven and reactive, not strategic 5. **No enduring value** — service state unchanged after completion 6. **O(n) with service growth** — scales linearly with size, traffic, or users ## Key Distinction Human judgment is the dividing line: if a task intrinsically requires human judgment and cannot be designed away, it's probably not toil. But beware — a poorly designed system that requires frequent complex human response is still toil; the system needs redesign, not more operators. ## Cross-Domain Applications - **Process improvement**: Any repeatable task that scales linearly with growth is a candidate for elimination - **Career management**: Spending too much time on toil-equivalent work (reactive, no lasting impact) stalls growth in any role - **System design**: The O(n) attribute is a design smell — well-designed systems grow 10x with zero additional manual work ## Source - [[Site Reliability Engineering - Chapter 5 - Eliminating Toil|SRE Ch 5: Eliminating Toil]] by Vivek Rau ## Related Concepts - [[SRE 50 Percent Engineering Rule]] - [[Toil Toxicity at Scale]] - [[Automation Value Hierarchy in SRE]]