"We Aimed for the Stars": How Scope Sank 'Project Nova'
"We Aimed for the Stars": How Scope Sank ‘Project Nova’
Project Nova. The name still stings a little. It was ambitious. We dreamt of an open-world RPG with crafting, base building, and a branching narrative that rivaled the greats. We were three people, fresh out of university, fueled by passion and…well, mostly caffeine.
The reality, unsurprisingly, was a messy, unfinished heap of code, assets, and shattered dreams. The post-mortem revealed a harsh truth: our scope killed us. It wasn’t malice or incompetence; it was simply biting off way more than we could chew. This isn’t just a cautionary tale; it’s a roadmap of what not to do, and how to avoid our mistakes.
The Grand Vision, and the Grand Failure
Open the Wayline editors — pixel sprites, sheets, palettes, scenes — and export drop-in assets for Unity, Unreal, and Godot. Free to start, no signup.
We started with a beautiful concept document. Pages upon pages detailed Project Nova’s sprawling world, complex combat system, and intricate character relationships. Every single cool feature we could think of went in.
That document was our first mistake. A static, overly detailed plan created before we even built a prototype. We spent weeks perfecting it, instead of focusing on proving the core mechanics were even fun.
The open-world, a core pillar of our vision, became a massive time sink. We envisioned vast landscapes and dynamic weather systems.
But we hadn’t even nailed down character movement or basic enemy AI. The allure of the epic overshadowed the fundamentals.
We were building a cathedral when we hadn’t even laid the foundation.
Prototyping: Where Dreams Meet Reality (and Die)
Prototyping should have been our savior. It’s the stage to validate core gameplay and identify potential roadblocks. We did prototype, but we didn’t prototype smart.
Instead of focusing on one key mechanic, we tried to prototype everything at once. Combat, exploration, crafting, and dialogue all got half-baked implementations.
None of them felt good.
The combat was clunky, the exploration felt empty, and the crafting system was a spreadsheet nightmare.
We stubbornly tried to polish all of these aspects at the same time. The result was scattered effort with zero tangible progress. We mistook quantity for quality.
We should have focused on a single, playable core loop. Nail the combat, or the movement, and then expand. We didn’t, and the scattered prototype reflected that.
Pre-Production: A False Sense of Security
Pre-production is about planning and organization. It’s about defining pipelines and creating realistic schedules. We thought we were doing this.
We created a task list, assigned roles, and even set deadlines. But our estimates were wildly optimistic. We underestimated the time required for everything, from asset creation to bug fixing.
We told ourselves “we’ll just crunch.”
Crunch, as many of you know, leads to burnout, mistakes, and ultimately, a worse product. It’s not a sustainable solution, but we embraced it as one.
Communication also started to break down. We had different visions for what the game should be, but these differences were never openly addressed.
Small disagreements festered into major conflicts, slowing development even further. We were a team pulling in three different directions.
Production: The Wheels Fall Off
Production is where the bulk of the game gets built. It requires discipline, focus, and a clear understanding of the game’s scope. We had none of these.
Scope creep became rampant. Every week, someone would suggest a new feature, or a new art style, or a new platform to target.
Since our initial vision was so broad, it was difficult to say no.
“It’ll only take a week!” someone would claim.
Of course, it never did.
Meanwhile, bugs piled up, features remained unfinished, and morale plummeted. We were drowning in a sea of unfinished tasks.
The project became unsustainable. Eventually, we had to make a choice: continue down this path, or cut our losses.
We chose the latter.
Lessons Learned: Avoiding the Nova Trap
So, how can you avoid making the same mistakes we did? Here’s a practical guide:
Define Your MVP (Minimum Viable Product): What’s the smallest, most fun version of your game? Focus on that. If the core isn’t fun, no amount of extra features will save it.
Prototype Ruthlessly: Prototype one core mechanic at a time. Iterate until it feels good. Then, and only then, move on to the next mechanic.
Realistic Scope: Be honest with yourself about your team’s capabilities and resources. It’s better to create a small, polished game than a large, broken one.
Agile Development: Embrace iterative development. Break down tasks into small, manageable chunks. Regularly test and get feedback. Adjust your plan based on what you learn.
Communicate Openly: Have clear and honest communication within your team. Address disagreements early and often.
Say No: Learn to say no to features that don’t directly contribute to the core experience. Scope creep is a silent killer.
Time Estimation: Track how long tasks actually take. Use this data to create more accurate estimates in the future. Add buffer time to your estimates to account for unforeseen problems.
Target Platforms Avoid trying to release on multiple platforms at once if you are indie, especially if each has its own bespoke architecture.
Real-World Examples
Consider Stardew Valley. Eric Barone (ConcernedApe) initially focused on the core farming loop: planting, watering, harvesting, and selling crops. He iterated on this loop until it was addictive. Only then did he add more features like fishing, mining, and relationships.
Or think about Undertale. Toby Fox prioritized a compelling story and unique combat system. The graphics were simple, but the gameplay and narrative were strong enough to carry the experience.
Both of these games are examples of successful MVPs. They focused on delivering a core experience that was fun and engaging, and then built upon that foundation.
Project Nova taught us a painful but valuable lesson. Aim for the stars, yes, but start with a solid foundation. Build a fun, polished core. Don’t let ambition blind you to the realities of development. Your game, and your team, will thank you for it.