Every successful game we have worked on started with the same question: is the core loop fun for thirty seconds without anything else on screen? Our ten-day prototype sprint exists to answer that question as cheaply as possible.
Day 1–2: write the loop on one card
We describe the loop in a single sentence: what the player does, what the game answers with, and why the player wants to do it again. If the team cannot agree on that sentence, we are not ready to open the editor.
Day 3–6: grey boxes only
The first playable build uses primitive shapes, placeholder sounds and debug text. This is deliberate. Polished art makes weak mechanics look better than they are and makes the team reluctant to throw work away.
- One mechanic, one goal, one fail state.
- Every tunable value exposed in a live debug panel.
- A new build on test devices every single day.
Day 7–9: play, measure, cut
We invite people outside the project to play without instructions. We watch where they hesitate, smile or quit, and we record how long they keep playing voluntarily. Features that do not change those moments get cut.
If players keep pressing “retry” on grey boxes, you have a game. If they don't, no amount of art will save it.
Day 10: decide
The sprint ends with a clear decision: scale up, pivot the mechanic, or stop. All three are good outcomes, because each one is made after ten days instead of six months.