Crunch is often described as passion, commitment, or the price of shipping. Workers usually know better. Most of the time it is a production-management problem that gets pushed downstream onto developers, artists, QA, support, and everyone else expected to absorb bad planning.
Why crunch persists
Crunch survives because the cost is pushed onto workers' bodies, relationships, and future prospects while the studio keeps the short-term benefit. That is why it rarely gets solved by better individual boundaries alone.
What to compare
- schedule changes and milestone slips
- staffing levels versus release expectations
- comp time promises versus reality
- who gets hit hardest: QA, live ops, outsourced teams, junior workers
- whether layoffs follow the "heroic" push once the release lands
Why game work needs its own lane
Game workers often deal with tighter cycles of crunch, credit anxiety, post-launch layoffs, vendor segmentation, and studio closure risk than generic tech guidance captures. The emotional culture around "shipping" can also make overwork feel like loyalty when it is really a management strategy.
What not to do
Do not treat heroics as organizing. Durable campaigns come from structure, not sacrifice theater.