prototype-coach

Kill criteria for a game prototype are predefined failure conditions, like a mechanic not feeling responsive by day two, that trigger you to discard the idea. This prevents over-investing by enforcing strict timeboxes and outcome-focused evaluation.

Game prototype types include Mechanic, Art, Tech, and Vertical Slice prototypes, each designed to validate specific elements. You use them to isolate and test individual goals like movement feel, visual style, or technical performance before full integration.

Structuring a timebox for prototyping a game mechanic involves setting a strict limit, such as a two-day maximum, alongside a clear core question. This focused approach ensures solo developers maintain efficient iteration and avoid scope creep.

Yes, prototype evaluation integrates directly into your game design document and workflow through decision journaling and scope management. This connects post-build evaluation and archiving directly to your ongoing game design documentation.

The best way to manage a disposable game prototype is to follow a structured workflow from pre-build planning to post-build evaluation and archiving. Emphasizing disposability ensures you extract validation data without attachment to the code.

Your game development workflow needs a vertical slice prototype to validate the integration of mechanics, art, and tech together, rather than testing them in isolation. It proves the combined experience works before committing to full production.