Rule 30 of 33 · Chapter VII — People and Sustainability
Sustainable pace beats heroic sprints
Why this rule exists
Crunch feels productive and is a loan against future output at a punishing interest rate, because the tired mind that codes through the night produces bugs the rested mind would catch, and someone spends the next week cleaning them up. A small studio's real advantage is consistency over years, not a heroic month followed by burnout, turnover, and the loss of everything those people knew. We build at a pace we can hold indefinitely because sustained, moderate effort compounds while sprint-and-collapse just oscillates, and the collapse erases much of the sprint's gains. Heroics also quietly corrode the team, because when all-nighters become the way things get done, they become expected, and the people with families or health limits or just good boundaries get pushed out, which is exactly the people you don't want to lose. The goal is a marathon pace, not because we're unambitious, but because the marathon is how you actually finish. Rested people ship better work and stay, and both of those matter more than any single hard week.
In practice
Plan work around a pace you could sustain for a year, not a heroic burst you'll pay for later, and treat regularly needing overtime as a planning failure to fix, not a virtue to celebrate. When a real crunch is genuinely necessary, make it short, acknowledged, and followed by real recovery, not the new baseline. Watch for the signs of burnout in yourself and your teammates, and take them seriously rather than pushing through. Protect evenings and weekends as the default, and notice when 'just this once' is quietly becoming every week. Say no to some things so the yes's are sustainable, because a team that never declines work is a team heading for a wall. Measure output over quarters, where rest is an input to good work, not a reward for finishing it.
When it doesn't apply
Real emergencies, a live incident, a rare genuine deadline, justify a temporary hard push, and that's fine when it's actually rare and actually followed by recovery. The failure mode is when the exception becomes the rule and heroics get baked into how normal work is planned.