game-retrospective

Run a structured game development post-mortem by guiding a facilitator and team through six analytical lenses, a mandatory kill list review, and a single synthesized learning to produce a publishable retrospective document.

The six lenses framework for game project retrospectives diagnoses project health by analyzing Core Loop Validation, Pillar Integrity, Scope Tier Review, Flow State Analysis, Technical Debt Audit, and Ludonarrative alignment.

Yes, you need prior playtest data to facilitate a rigorous game retrospective, along with a designated facilitator and access to project artifacts to properly analyze pillars, scope, technical debt, and ludonarrative alignment.

The best way to evaluate what game features to cut during a milestone review is applying kill list discipline, which mandates reviewing all elements to decide what to cut and preserve to ensure a coherent product.

Distill findings from a game retrospective into actionable insights by using the One Thing synthesis, which compresses all data-driven discoveries from the six lenses into a single, actionable lesson to guide the next phase.