The Allure of Democratic Development
When embarking on a collaborative game development project, it's natural to assume that everyone should have an equal say in decisions. After all,集思广益 (collective wisdom) sounds like a recipe for success. Many teams start with the best intentions, holding endless meetings where every member's opinion is valued equally.
But this democratic approach often leads to a surprising outcome: project paralysis, scope creep, and ultimately, failure. The truth is that while collaboration is essential in game development, unstructured democracy can be its undoing.
The Two Phases of Game Development
To understand why democratic decision-making fails, we must first recognize the two distinct phases of game development:
1. The Brainstorming Phase
In the early stages, when the game is still just an idea, democratic input is not only valuable but essential. This is the time for wild ideas, creative exploration, and considering multiple possibilities. Team members should feel free to contribute their thoughts on gameplay mechanics, art style, narrative direction, and technical feasibility.
This phase thrives on collaboration and open discussion. It's where the foundation of the game is built through collective creativity.
2. The Production Phase
Once the core concept is established and development begins in earnest, the dynamics must shift. This is where the democratic approach often falls apart.
During production, decisions need to be made quickly and consistently. Every change to the game requires adjustments across multiple disciplines—art, programming, sound, and design. When every decision is subject to group consensus, progress slows to a crawl.
Why Every Project Needs a Leader
Game development isn't unique in this requirement. Every successful project, regardless of industry, needs a clear leader:
- Filmmaking: A director who makes the final creative decisions
- Software development: A product manager who prioritizes features
- Construction: A project manager who coordinates all aspects
- Sports: A coach who sets strategy and makes in-game decisions
In game development, this role is typically filled by a producer or game director. Their responsibilities include:
- Setting the overall vision for the game
- Making final decisions when consensus can't be reached
- Prioritizing features and managing scope
- Resolving conflicts between team members
- Keeping the project on schedule and within budget
Case Studies: When Democracy Failed
History is littered with game development projects that foundered due to excessive democratic decision-making:
Case Study 1: The Never-Ending MMO
A small indie team set out to create an MMORPG with a democratic approach. Every feature, from character classes to quest design, was put to a vote. Meetings dragged on for hours as team members debated every detail. After two years of development, they had only completed a fraction of their planned features. The project was eventually abandoned when funding ran out.
Case Study 2: The Genre-Shifting Nightmare
A team of four friends decided to make a game together, with each member having equal say. They started with a 2D platformer, but after a few months, one member wanted to switch to a 3D action game. Another preferred a visual novel approach. They spent months reworking the game to accommodate everyone's vision, resulting in a disjointed, unfocused product that failed to find an audience.
Case Study 3: The Feature Creep Disaster
A mid-sized studio adopted a "flat hierarchy" approach, where every team member could propose changes to the game. What started as a simple puzzle game eventually included RPG elements, a crafting system, multiplayer modes, and a branching narrative—all requested by different team members. The game became bloated and buggy, missing multiple release deadlines before finally launching to lukewarm reception.
The Myth of "Design by Committee"
These examples illustrate a phenomenon known as "design by committee," where a product is created through collective decision-making rather than a singular vision. While this approach can work in some contexts, it's particularly problematic for creative endeavors like game development.
Games are immersive experiences that require consistency and coherence. When too many cooks are in the kitchen, the result is often a Frankenstein's monster of conflicting ideas and mechanics that don't work together.
Striking the Right Balance
This doesn't mean that team members should be silenced or that their input isn't valuable. The key is striking the right balance between collaboration and leadership:
1. Establish Clear Roles
From the outset, define who is responsible for what. Identify a producer or director who will have final decision-making authority, while other team members focus on their areas of expertise.
2. Create Structured Feedback Channels
Implement regular feedback sessions where team members can share their thoughts, but make it clear that the final decision rests with the leader. This ensures that everyone's voice is heard without slowing down progress.
3. Trust the Experts
While the producer sets the overall vision, they should defer to subject matter experts in specific areas. The lead programmer should have final say on technical implementation, the lead artist on visual style, and so on.
4. Embrace Iteration
Even with strong leadership, some decisions will need to be revisited. Build in regular review periods where the team can assess what's working and what isn't, with the producer making the final call on adjustments.
Success Stories: Strong Leadership in Action
Contrast the failed projects with successful games that had clear leadership:
Stardew Valley
Eric Barone (ConcernedApe) single-handedly created Stardew Valley, making all the design decisions himself. While he sought feedback from friends and fans during development, the final vision was entirely his own.
Celeste
While Celeste was developed by a small team, Matt Thorson served as the game director, making the final creative decisions. This clear leadership resulted in a cohesive, focused experience that won multiple awards.
Hollow Knight
Team Cherry, a studio of just three people, had a clear division of responsibilities, with Ari Gibson and William Pellen co-directing the project. Their unified vision resulted in a critically acclaimed game that sold millions of copies.
Conclusion
Collaboration is essential to game development, but unstructured democracy is a recipe for disaster. The most successful projects are those where a clear leader sets the vision and makes the final decisions, while still valuing input from the team.
In the end, game development is more like filmmaking than a democracy. A director doesn't make every decision in a vacuum—they collaborate with writers, actors, and crew—but they are ultimately responsible for the final product. Similarly, a game director or producer must guide the team toward a unified vision.
So, can you商量着来 (make decisions democratically) in game development? Yes, but only during the brainstorming phase. Once production begins, clear leadership is not just helpful—it's essential for success.
The next time you embark on a collaborative game development project, remember: a ship without a captain may have lots of interesting ideas about where to go, but it will never reach its destination.