Toil Reduction

Toil is work that's manual, repetitive, automatable, tactical, and scales linearly with growth — and it's dangerous precisely because each instance feels small. Nobody schedules a project called "toil"; it accumulates one "just do it by hand this once" at a time until an engineer's week is gone before they've built anything.

The fix isn't a blanket instinct to automate everything — some repeated work is judgment, not toil, and automating it badly just moves the risk somewhere less visible. Toil reduction starts with measuring honestly what's actually eating time, not with automating whatever's most annoying today.

1. Measure toil before you fight it

Teams that "know" what's eating their time are usually wrong about the proportion, if not the source — the loud, annoying task isn't always the biggest time sink; the quiet one done fifty times a week often is. Without a number, every automation decision is a guess dressed up as priority.