vertical-slice

A vertical slice validates production feasibility by demonstrating one complete start-to-challenge-resolution cycle at polished slice quality, confirming both feasibility and player-fun before committing to full production.

A vertical slice in game development is a near-production build of your core loop that executes one complete start-to-challenge-resolution cycle, used to validate production feasibility and player-fun before committing to full production.

Prevent scope creep during pre-production playtesting by enforcing falsifiable validation questions and maintaining a tight three-to-five-minute slice scope with a hard time limit before implementation begins.

Yes, you need a completed or nearly completed game design document, architecture, and UX specs, because vertical slice validation applies to pre-production teams preparing for a hard schedule-relevant go/no-go production gate.

Make a go/no-go production decision by generating a report from iterative playtest debriefs and a day-by-day velocity log, yielding a definitive PROCEED, PIVOT, or KILL verdict to gate the pre-production to production transition.

You should not use a vertical slice approach if your pre-production lacks completed game design documents, architecture, and UX specs, as this gating method requires those foundational deliverables to validate production feasibility.