Skip to content
Practices
BP #6: Pivot Gate at Hour 24

BP #6: Pivot Gate at Hour 24

At hour 24: no concept changes. Scope cuts only. Anything that is not a cut is off the table.

Why It Works

At hour 24 the game is never what you imagined and a different idea always looks tempting. That pull is not a good signal. It is exhaustion and frustration making a bad option feel rational.

DDRKirby considered converting his LD37 entry to a visual novel at hour 24. He recognized it was too late and stayed the course, but only because he stopped to think it through. [1] Without that explicit check, the pull toward starting fresh can be mistaken for good judgment.

A full concept pivot at hour 24 means abandoning everything built in the first 24 hours and restarting implementation with half the time remaining and no margin to fix problems. That is almost always how you ship nothing.

What the Gate Allows

After hour 24, you can:

  • Cut Should-Have and Could-Have features
  • Simplify existing systems to reduce build time
  • Reduce level count, enemy count, content volume
  • Swap complex implementations for simpler ones

You cannot:

  • Change the core mechanic
  • Redesign the game concept
  • Add new systems that were not in the original plan
  • Restart any major component

How to Run the Gate

At hour 24, hold a 15-minute check-in:

  1. What is the current state of Must Haves?
  2. What is at risk?
  3. What gets cut to protect the Must Haves?

No redesign conversations. If someone proposes a concept change, the gate answer is: is this a scope cut, or a new direction? New directions are closed.

Methodology Connection

Methodology Connection

Stage-Gate divides development into phases separated by checkpoints with explicit go/kill criteria. In full production, gate reviews evaluate whether a project continues as-is, pivots or gets cancelled. At 48-hour scale, hour 24 is the only gate that matters. The criteria are simple: cut scope and protect shippability. Kaitila frames the same moment as a feature freeze, where new functionality stops and the focus shifts entirely to polish and stability. [2]

Related

BP #3: MoSCoWBP #7: Playtesting Checkpoint