Process / journal

The Gauntlet Loop for Game Development

A game prototype can be technically complete and still fail the player. The Gauntlet Loop makes the quality bar explicit, asks a fresh context to inspect the actual build and sends only the biggest gap back into the next pass.

By Jordan ThirklePublished 2026-08-101 min read

Name the bar before the build

“Make it amazing” is not testable. “A first-time player can understand the goal, move, recover from a miss and tell a clean landing from a crash within two minutes” is a bar a critic can inspect.

The bar should include feel, readability, accessibility and performance—not only whether the page loads.

The critic needs the real surface

A fresh reviewer should play or inspect the rendered build, use a phone-sized viewport, navigate with a keyboard where relevant and look at the source metadata. A source review alone cannot tell you whether a jump reads at speed.

Fix the highest-impact failure, then repeat until the criteria pass. Stop when the quality bar is met, not because a round count feels complete.