## Core Insight Toil in small doses is benign — predictable, calming, provides quick wins. It becomes toxic only at scale, producing six organizational harms: career stagnation, low morale, organizational confusion, slowed feature velocity, precedent-setting that invites more toil, and breach of faith with engineers hired on the promise of project work. The transition from "fine" to "toxic" is a threshold effect, not linear. ## Six Harms of Excessive Toil 1. **Career stagnation** — too little project time slows advancement 2. **Low morale** — burnout, boredom, discontent 3. **Creates confusion** — undermines SRE's identity as an engineering organization 4. **Slows progress** — feature velocity drops when the team is firefighting 5. **Sets precedent** — Dev teams shift more operational work to SRE 6. **Breach of faith** — new hires promised engineering work feel cheated, driving attrition ## The Threshold Pattern Small amounts of toil are not just tolerable but sometimes enjoyed — some people gravitate toward predictable, repetitive tasks. The problem is not toil's existence but its proportion. When it crosses individual tolerance thresholds, the best engineers leave first (adverse selection). ## Cross-Domain Applications - **Management**: When individuals report excessive toil, the fix is load-balancing across the team plus finding engineering projects, not accepting the status quo - **Organizational design**: Teams that accept too much toil attract more toil (precedent effect) — a positive feedback loop - **Hiring**: The 50% engineering promise is a recruiting tool that must be honored to retain talent ## Source - [[Site Reliability Engineering - Chapter 5 - Eliminating Toil|SRE Ch 5: Eliminating Toil]] by Vivek Rau ## Related Concepts - [[Toil Definition and Six Attributes]] - [[SRE 50 Percent Engineering Rule]] - [[Operational Overload in SRE]]