Indie Dev Stories: Kill Your Darlings (And Other First Ideas)

Posted by Gemma Ellison

August 4, 2025

Here’s what I wish I knew when I started making games.

Dear Past Me: Kill Your Darlings (And Other First Ideas)

You’re so excited, right? You’ve got this amazing game idea, the one that’s going to make you famous. You can practically see the Steam reviews rolling in. But listen to me, future game dev superstar: that first idea? It’s probably not the idea. It’s just the starting point.

Beginner game developers, myself included back then, often fall in love with their initial concept. We cling to it like a life raft, even when it’s taking on water. We resist changing it, tweaking it, or even admitting that parts of it just don’t work. This, my friend, is a recipe for wasted time and a potentially terrible game. You need to learn to “kill your darlings.”

The Problem with Perfection (Or Perceived Perfection)

That initial spark is important, it’s what gets you going. But it’s crucial to understand that it’s just the beginning of a long process of refinement. The problem is, that initial idea is often based on assumptions, wishful thinking, and a lack of real-world testing. You might think players will love a certain mechanic, but until you put it in front of them, you’re just guessing. And guessing is a bad strategy in game development.

Clinging to your initial vision, without any critical evaluation, leads to stagnation. You’ll spend months (or even years) building something that nobody actually wants to play, or that’s fundamentally flawed. You’ll miss opportunities to improve the game, explore new directions, and create something truly special. Don’t be afraid to let go.

Idea Validation: Is Your Darling Worth Saving?

Before you even write a single line of code, take a step back and validate your idea. This isn’t about asking your friends if they think it sounds cool. It’s about gathering real data.

Market Research: Are there similar games out there? What are they doing well? What are their weaknesses? Is there a market for your niche, or is it already saturated? Look at sales data, Steam reviews, and community forums.
Target Audience: Who are you making this game for? What are their preferences? What other games do they enjoy? If you don’t know who your target audience is, you’re shooting in the dark.
Unique Selling Proposition (USP): What makes your game stand out? What are you offering that other games don’t? If you can’t answer this question clearly, you need to rethink your concept.

Prototyping: Where Ideas Meet Reality

Once you’ve done some initial validation, it’s time to prototype. Don’t get bogged down in art assets or fancy features. Focus on the core mechanics. The goal is to quickly and cheaply test your fundamental assumptions.

Paper Prototyping: Seriously, grab some paper and pencils. Sketch out the core gameplay loop. Play it with friends. This is the fastest way to identify major flaws.
Digital Prototypes: Use a simple engine like Unity or GameMaker to create a basic, functional prototype. Focus on the essential elements. Grey boxes are your friend.
Iterate, Iterate, Iterate: Playtest your prototype. Gather feedback. Analyze the data. Then, make changes. Repeat this process until you have something that’s genuinely fun.

Embracing Feedback: The Hardest Part

This is where “killing your darlings” comes into play. You’ll get feedback that contradicts your original vision. Players will struggle with mechanics you thought were brilliant. Features you loved will be universally disliked.

Listen to this feedback. Don’t get defensive. Don’t dismiss it out of hand. Analyze it objectively. Is there a pattern? Are multiple players having the same issue? If so, it’s probably a real problem.

Be prepared to make tough choices. Sometimes, you’ll have to cut features you’re really attached to. Sometimes, you’ll have to completely overhaul a core mechanic. It’s painful, but it’s necessary.

Staying Motivated During the “Killing” Phase

This is tough, I know. It’s disheartening to see your beloved ideas fall apart. You need a way to track your progress and stay motivated. This is where a game dev journal becomes your best friend.

Document Everything: Record your design decisions, your prototypes, your playtesting results, and your reflections. This creates a valuable record of your journey.
Celebrate Small Wins: Acknowledge your progress, no matter how small. Did you fix a bug? Did you successfully implement a new feature? Write it down and give yourself credit.
Reflect on Lessons Learned: What did you learn from each iteration? What mistakes did you make? What can you do better next time? Documenting your lessons will help you grow as a developer.

Keeping a detailed game development log will help you stay focused, track your progress, and learn from your mistakes. It’s also a great way to show potential publishers or investors that you’re serious about your project. Regular devlogs are also a great way to start building your community and hype for your game.

If you are looking for a simple, effective way to track game development progress, consider checking out our journaling tool to record your progress and reflections along the way. Start your game dev journal today.

The Reward: A Better Game

Killing your darlings isn’t easy, but it’s worth it. By embracing a flexible, data-driven approach, you’ll create a stronger, more polished game that players will actually enjoy. You’ll learn more about game design, improve your skills, and increase your chances of success.

So, don’t be afraid to let go of those initial ideas. They were just the starting point. The real magic happens when you’re willing to kill your darlings and build something truly special. Good luck, future game dev superstar! You’ve got this.