Game delays are a modern norm. They are as expected as day-one patches and pre-orders. News of another delay is met with desensitization. But is there a proper method for handling these inevitable changes to development timelines? According to Mark Darra, an experienced former producer from BioWare, a developer known for sprawling RPGs, the answer is affirmative.
Mark Darra, a veteran ex-producer on the Dragon Age franchise, believes planning, honest self-assessment, and a willingness to be bold about course correction are key. His perspective offers a fresh take on why delays occur and how developers can make them beneficial for a game, not detrimental.
The Problem with Patching Patches
Darra argues that developers often fall into a cycle of successive, incremental delays. Postponing a release by a couple of months repeatedly, while seeming less dramatic in the short term, can be very dangerous.
He explains, "If your game has been pushed back two years, which you're expecting, it completely blows the space of opportunity wide open. You see, you know: 'Well, we're not releasing the game in a month, but in twenty-five months. So let's go back, rethink what we've done, and perhaps undo some of the decisions we made previously when we thought we were making another game. Let's go a different way.'"
He contrasts this with repeated, short delays, stating:
"When your game still changes for two years, but in increments, three months at a time, will there be a point for such a reconsideration? [.] You patch on the patch, and on top — another one. You complicate what likely needed to be done in the first place: burn bridges and take another path."
Burn Bridges and Go Down a Different Road
Darra’s point is well-taken. He theorizes that most minor delays result in a 'patchwork' development approach. Teams become focused on immediate problem-solving, layering features onto existing systems, instead of addressing core issues with the game's design or direction.
A longer, pre-planned timeframe allows for genuine re-evaluation. It gives developers the chance to step back, examine the entire project, and ask critical questions. Are we heading in the right direction? Are there core mechanics or designs needing re-thinking? Should we "burn bridges" with past decisions and create a new, potentially superior path?
Quality and Cost Efficiency
Darra concludes that frequent delays, often blamed on "polishing," are usually a symptom of deeper problems. Honesty about a project's state from the outset, and opting for a larger, initial delay when necessary, can ultimately lead to a higher quality game. It may even lead to more effective and cheaper development in the long run.
This perspective challenges industry norms. It suggests that truly developing a game sometimes requires granting both the project and the development team the gift of time and the liberty to rethink.
