How to Run a Useful Retrospective

A retrospective—the team examining a recent period to learn and improve—is useful when it honestly examines what went well and what didn't, and produces concrete improvements to act on, rather than just venting or vague reflection. Examining honestly, identifying actionable improvements, and following through is what makes retrospectives actually improve how the team works.

Examine honestly what went well and what didn't

A useful retrospective starts with an honest examination of what went well and what didn't in the recent period. Examining what went well lets the team recognize and continue their successes (the things that worked, worth repeating), while examining what didn't go well surfaces the problems and difficulties (the things that didn't work, worth addressing). The key is honesty—genuinely examining both the successes and the problems, including the uncomfortable ones, because the honest examination is what reveals the real lessons, particularly the problems that need addressing. A retrospective that glosses over problems (avoiding the uncomfortable truths) or only celebrates (ignoring the difficulties) misses the learning, while one that honestly examines both what went well and what didn't surfaces the full picture to learn from. This connects to running a postmortem: honest examination of successes and failures is what reveals the lessons. Examining honestly what went well and what didn't is the foundation of a useful retrospective, surfacing the successes to continue and the problems to address, which is the basis for improvement. The honest examination, including the uncomfortable problems, is what makes the retrospective reveal the real lessons.

Identify actionable improvements and follow through. An honest examination is useful only if it produces actionable improvements that the team follows through on. Identifying actionable improvements means turning the examination into concrete, actionable changes—not just identifying problems, but deciding specific improvements to make (how to address the problems, what to change to work better), so the retrospective produces concrete actions to improve, rather than just venting about problems or vague reflection. The improvements should be actionable: specific changes the team will make to work better, derived from the examination of what didn't go well. Following through means actually implementing the identified improvements—making the changes, acting on the retrospective's conclusions—because a retrospective that identifies improvements but doesn't follow through is wasted (the same problems recur), while one whose improvements are implemented actually improves how the team works. This follow-through is the crucial step that makes the retrospective worthwhile: not just identifying improvements, but acting on them to actually improve. This connects to the postmortem principle that the examination only matters if the lessons are applied. Combining examining honestly what went well and what didn't (surfacing the successes and problems) with identifying actionable improvements and following through (turning the examination into concrete actions and implementing them) is what makes a retrospective useful—an honest examination producing actionable improvements that the team implements, actually improving how the team works. Running a retrospective this way—honest examination, actionable improvements, follow-through—is what makes it improve the team's work, rather than the venting or vague reflection that a retrospective without honest examination, actionable improvements, or follow-through becomes. Examine honestly what went well and what didn't, identify actionable improvements, and follow through on them, and the retrospective actually improves how the team works, turning the team's experience into concrete improvements that make the team better over time, which is what a useful retrospective achieves. The retrospective only matters if it produces and implements improvements, so the honest examination, actionable improvements, and follow-through are what make it worthwhile.

Scope is a decision, not an accident

Almost every overscoped game got that way one reasonable addition at a time, with no single decision ever feeling like the mistake. The finish line recedes a little with each new feature, and because the project always feels nearly done, the developer rarely notices how far the goal has drifted until they're exhausted and the game still isn't out.

Treat scope as something you actively decide rather than something that happens to you. Write down what the finished game contains, make every addition a conscious trade against that, and keep most new ideas in a backlog where they belong — because a small game you finish beats a large one you abandon.

Measure before you optimise

Intuition about what's slow, what's confusing, or what's driving players away is usually wrong, and acting on it wastes effort on problems that don't matter while the real ones persist. The developers who improve their games efficiently are the ones who measure first — profiling performance, watching real sessions, capturing actual errors — and let the data set their priorities.

It's slower than trusting your gut, but it's the only approach that reliably improves the game instead of just changing it. Find the biggest real problem, fix that, and measure again, rather than optimising guesses.

The first impression is most of the battle

More players leave in the opening minutes than at any other point, which makes the first few minutes the highest-leverage stretch of the whole game — and also the part the developer can least see clearly, having played it a thousand times. What feels obvious to you is often confusing to someone seeing it fresh, and that gap quietly costs you players before they ever reach the good part.

Get the player into the interesting part fast, let them feel competent quickly, and watch first-time players go through the opening without helping them. Nobody quits a game they're enjoying, so making the early minutes land is most of the battle for retention.

Small and finished beats big and abandoned

A folder of impressive unfinished projects teaches far less than a single small finished one, because finishing is where the hardest and most valuable lessons live — the unglamorous final stretch of bug-fixing, polishing, and shipping that ambitious abandoned projects never reach. Each completed game, however modest, builds the finishing muscle and the confidence that make the next one achievable.

So resist the pull of the dream project until you've shipped a few small ones. Scope to what you can actually complete, finish it, and let the experience of shipping make your bigger ambitions realistic.

Trust behaviour over opinions

People are unreliable narrators of their own experience — they're polite, they rationalise, they suggest fixes that miss the real problem. What they do tells the truth that what they say obscures: where they hesitate, where they get stuck, what they ignore, where they quit. The most valuable feedback is usually the behaviour you observe, not the opinion you're offered.

This is why watching beats asking, and why real data about what players actually do beats any amount of speculation. When several people stumble at the same spot, that's a problem worth fixing, regardless of whether any of them mentioned it.

A useful retrospective honestly examines what went well and what didn't, identifies actionable improvements, and follows through—not just venting or vague reflection. Examine honestly, identify concrete improvements, and implement them, so retrospectives actually improve how the team works over time.