Crunch is what happens when the plan stops telling the truth.

You’ve seen it: a milestone slips, but the scope stays the same. Estimates get adjusted in the tracker, but the launch date doesn’t budge. Overtime starts as an exception, then quietly becomes the plan. Before you know it, the team is burning the midnight oil for months, and the people who know the game best are too exhausted to make it better.

Here’s the hard truth: crunch isn’t proof of commitment. It’s a warning light that the plan failed to account for reality. And when it becomes the norm, it’s not just the team that suffers—the game does too.

Scope that never shrinks is a wish, not a plan. I’ve seen this in almost every organization I’ve worked with. A feature is “almost done” but still needs integration, testing, and polish. A decision waits for a meeting while the team keeps building against assumptions. Each department absorbs a small delay, and QA inherits all of them at the end. The schedule isn’t the plan if scope never changes—it’s a wish with dates attached.

Cuts made after burnout hurt more than cuts made early. The hardest launch decision is often what not to finish. But late cuts aren’t just painful—they’re less effective. When you cut a feature at the last minute, you don’t just lose that feature. You lose the time the team could have spent refining what’s left. A cut feature isn’t always lost value—sometimes it’s the space needed to make the remaining game work well.

Protected milestones ship better games. Here’s what I’ve learned:

  • Re-estimate when the work changes, not just when a date slips.
  • Name the features you’ll cut if a milestone misses.
  • Protect time for integration, QA, and polish.
  • Treat sustained overtime as a signal to change the plan, not just to work harder.

Commitment looks like making hard decisions early. A heroic final month can hide six months of avoided decisions. Your team shouldn’t have to work nights to make an old estimate look right. If launch needs months of overtime, the scope is already too big. Crunch isn’t a milestone—it’s a failure to adjust the plan when it mattered most.