How to Kill Your Darlings in Game Design

'Kill your darlings'—cutting the things you love but that don't serve the game—is a hard but essential discipline, because attachment to features, ideas, or content can keep you holding onto things that aren't working or don't fit. Learning to cut what doesn't serve the game, despite your attachment, is what keeps a game focused and good rather than bloated with beloved-but-harmful elements.

Attachment isn't a reason to keep something

The core of killing your darlings is recognizing that attachment isn't a reason to keep something—the fact that you love a feature, idea, or piece of content doesn't mean it serves the game, and your attachment can blind you to the reality that it isn't working or doesn't fit. Developers become attached to their ideas and creations, which is natural, but this attachment becomes a problem when it keeps you holding onto things that harm the game—a beloved feature that doesn't fit, an idea you're proud of that isn't working, content you love that bloats or dilutes the experience. The discipline is to evaluate things by whether they serve the game, not by your attachment to them, and to be willing to cut even things you love if they don't serve the game. This is hard precisely because of the attachment—cutting something you love hurts—but it's essential, because a game kept focused and good requires cutting what doesn't serve it, regardless of attachment. Recognizing that attachment isn't a reason to keep something, and being willing to evaluate your darlings by whether they serve the game rather than by how much you love them, is the foundation of killing your darlings, because the whole difficulty is overcoming the attachment that wants to keep harmful elements.

Serving the game, not your attachment, is what keeps a game focused and good. The principle that resolves the difficulty of killing darlings is serving the game rather than your attachment—making decisions based on what's best for the game, not on what you're attached to. This means when a darling—a feature, idea, or content you love—doesn't serve the game (isn't working, doesn't fit, bloats or dilutes the experience), you cut it, because serving the game is what matters and your attachment is not a good enough reason to keep something harmful. This connects to cutting scope, avoiding filler, and keeping a game focused: all of these require cutting things, and often the hardest things to cut are the darlings you're attached to, which is exactly why killing your darlings is a distinct, important discipline. A game served by cutting what doesn't work, regardless of attachment, stays focused and good, while a game where beloved-but-harmful elements are kept out of attachment becomes bloated, unfocused, or compromised. Serving the game, not your attachment—cutting the darlings that don't serve it, despite the pain—is what keeps a game good. Combining the recognition that attachment isn't a reason to keep something (overcoming the blindness that attachment causes) with serving the game rather than your attachment (making decisions based on what's best for the game, cutting harmful darlings despite the attachment) is what makes killing your darlings the essential discipline it is—keeping a game focused and good by cutting what doesn't serve it, even the things you love. This is hard and painful, because cutting darlings hurts, but it's essential, because the alternative—keeping beloved-but-harmful elements out of attachment—compromises the game. The developers who make good, focused games are the ones who can kill their darlings, serving the game rather than their attachment, cutting the things they love when those things don't serve the game. Learning to recognize that attachment isn't a reason to keep something, and to serve the game rather than your attachment by cutting the darlings that don't work, is what keeps your games focused and good rather than bloated with beloved elements that harm them. Serve the game, not your attachment, and be willing to kill your darlings when they don't serve it.

Plan for the parts you can't see

Once a game leaves your machine, a lot of what happens to it becomes invisible by default. Players run it on hardware you don't own, hit problems you never reproduced, and most of them never tell you — they simply move on. The gap between 'it works for me' and 'it works for everyone' is where a surprising amount of churn quietly lives.

So plan to see what you otherwise couldn't. Watching real players, capturing the bugs and crashes they hit with the context to fix them, and paying attention to where they drop off all turn invisible problems into ones you can actually act on — which protects the reviews and retention everything else depends on.

Consistency beats intensity

Indie development is a long game, and it rewards steady, sustainable effort more than heroic bursts. A little progress made consistently — on the game, on the marketing, on the community — compounds in a way that last-minute sprints never do. The developers who finish and find an audience are usually the ones who kept showing up, not the ones who worked themselves into the ground for a week and then burned out.

Build a pace you can sustain, and protect it. Momentum is fragile and expensive to rebuild, so steady forward motion is worth more than any single intense push.

Let real players be the judge

It's remarkable how differently real players behave from how you imagine they will. The tutorial you think is obvious confuses them; the feature you agonised over goes unnoticed; the thing you almost cut becomes their favourite. None of that is visible from inside your own head, which is why watching real people play is the single highest-leverage thing most developers under-do.

Watch without intervening, resist the urge to explain, and pay attention to what players do as much as what they say. Their confusion and their choices are data, and acting on that data is what turns a game that works for you into one that works for everyone.

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.

Killing your darlings means cutting things you love but that don't serve the game—attachment isn't a reason to keep something. Serve the game, not your attachment, and be willing to cut beloved features, ideas, or content that aren't working or don't fit.