Why Done Is Better Than Perfect

'Done is better than perfect' is a cliché because it's true and because so many developers need to hear it. Perfectionism—the endless pursuit of a game with no flaws—is one of the leading causes of unfinished games, and a finished, imperfect game in players' hands is worth infinitely more than a perfect one that exists only as an ever-receding goal. Embracing good-and-done over perfect-and-endless is what lets developers actually ship.

Perfect is a finish line that doesn't exist

A game has an effectively infinite list of things that could be improved, refined, polished further, so 'perfect' is not a state you can reach—it's a horizon that recedes as you approach it, because every improvement reveals more that could be improved. Developers who pursue perfection therefore never finish, not because they lack skill or dedication but because they've set a goal that by its nature can't be achieved, and the pursuit consumes them indefinitely. This is the trap of perfectionism: it feels like the responsible, high-standards path, but it's actually a path with no end, and games lost to it are lost not to failure but to the inability to ever declare them done. The alternative isn't sloppiness—it's recognizing that 'good enough to ship' is a real, achievable bar, while 'perfect' is not, and that aiming for the former is what gets a game finished while aiming for the latter is what keeps it forever unfinished. Done is a state you can reach; perfect is not, and choosing to pursue done is choosing to actually finish.

A finished imperfect game is worth vastly more than a perfect unfinished one, on every dimension that matters. The perfect game that never ships helps no one, reaches no players, earns nothing, teaches you little about shipping, and exists only as a private burden, while a finished imperfect game is played, enjoyed, sold, learned from, and built upon. The imperfections that perfectionism agonizes over are almost always far less important than perfectionists believe—players enjoy imperfect games all the time, the flaws that loom enormous to the developer often go unnoticed or unmind by players, and the things that actually matter are usually a much smaller set than the perfectionist's endless list. Shipping also teaches you things no amount of polishing can, generates the feedback that makes your next game better, and builds the crucial skill of finishing. This doesn't mean abandoning quality—a good game still requires real effort and care—but it means distinguishing the polish that matters from the endless refinement that doesn't, drawing the line at good enough, and shipping. The developers who build a real body of work are the ones who internalized that done beats perfect: they make their games good, then finish and ship them, rather than chasing a perfection that keeps the game forever in progress. Aiming for good and done, recognizing perfect as an unreachable trap, and having the resolve to ship an imperfect game is one of the most important mindset shifts in all of game development, because it's the difference between finishing games and endlessly almost-finishing them.

Polish where players actually look

Polish is not evenly valuable. Players form an impression in the first minutes and spend most of their time in the core loop, so effort spent there returns far more than effort spread thin across content few people reach. The opening, the moment-to-moment feel, and the things every player touches are where polish converts directly into how good the game feels.

Be deliberate about it. Make the first impression strong and the core interactions satisfying before widening out, because a great core with less content almost always beats a sprawling game that never feels good to play.

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.

Perfect never ships because it can't be reached. A finished imperfect game beats a perfect unfinished one every time.