72h to a playable prototype
The format, the constraints, an honest example, and why time pressure creates direction instead of just cutting it short.
The starting constraint
In 72 hours, there is no time to get the scope wrong. You have to scope, code and deliver a playable build. Not a document. Not a mockup.
The format works precisely because it forces brutal reduction. There is no room for five average mechanics, so you have to decide which one deserves to exist. That is where direction shows up: not in a brainstorm, but in a constraint that refuses the comfort of 'we'll see later'.
When this format earns its time
It's useful when a mechanic is still just a hunch and you hesitate to commit weeks to it. Three days are enough to know whether the idea holds up in your hands, or whether it was only appealing on paper.
The goal is not to finish a game in three days. The goal is to move past intention and have something to judge, instead of something to imagine.
What the three days look like
- Day 1: scoping, minimal architecture, first playable loop.
- Day 2: systems integration, game feel, first complete tests.
- Day 3: adjustments, blocking fixes, short documentation, build delivery.
A concrete example
On Minigame Factory, several prototypes were produced with the same logic: tight scope, playable build, standardized API. Color Flood, Stack Tower, Orbit Tap.
They were not equal. Some held up well enough in hand to justify continuing. Others showed their limits within a few minutes of play, and I left them there. The format doesn't make an idea good. It just makes it very fast to know when it isn't, before you've spent weeks on it.
What the format does not do
No HD assets, no custom audio, no backend, no final polish. A functional prototype is not a finished product, and mistaking one for the other leads straight to disappointment.
What it does do is replace weeks of doubt with three days of verification. That is not nothing, but it is only that.
What I take away
The real value of the format is not speed for its own sake. It's that it forces an early decision, on something concrete, instead of pushing the decision behind a bit more preparation.
A 72h prototype that fails is not a failure: it's three days that saved me thirty. The only bad outcome is the one you never put in someone's hands to find out.