Veteran game director Josh Sawyer, renowned for his work on titles like Pentiment and a long tenure at Obsidian Entertainment, has articulated a strategic framework for studios aiming to reduce the often-protracted timelines associated with video game development. Drawing from his extensive experience, particularly with projects of varying scales within Obsidian, Sawyer emphasizes a disciplined approach to development phases and a cautious stance on late-stage experimentation.
Speaking in a recent interview with Bloomberg, Sawyer, who serves as Obsidian’s studio design director, highlighted the development of Pentiment as a case study in efficiency. This critically acclaimed narrative adventure was brought to fruition by a modest team of approximately 15 individuals over a period of three years. This stands in stark contrast to the significantly longer development cycles and larger team requirements of Obsidian’s more ambitious projects, such as the upcoming fantasy RPG Avowed and the sequel The Outer Worlds 2. Sawyer’s philosophy, deeply rooted in pragmatic resource management, informed Pentiment‘s schedule from its inception.
"I’ve always been working on very tight deadlines," Sawyer told Bloomberg, underscoring a career trajectory shaped by the need for efficiency. "And so my approach to everything is usually to be as scrappy as possible and to reuse and be very careful about not reinventing things." This ethos suggests a lean development methodology focused on leveraging existing assets, proven mechanics, and minimizing redundant efforts – a stark departure from the often iterative and experimental nature that can characterize larger, longer productions.
The Critical Divide: Pre-Production Versus Production
A cornerstone of Sawyer’s advice revolves around the strict delineation between the pre-production and production phases of a game’s development. Pre-production, often referred to as the discovery or prototyping phase, is where creative freedom and extensive experimentation are not only permissible but actively encouraged. During this crucial stage, teams are tasked with exploring core concepts, refining gameplay mechanics, establishing art styles, and fundamentally determining the game’s identity and how it will be brought to life. It is a period for "taking big swings," testing innovative ideas, and discarding those that do not align with the project’s vision or feasibility.
However, Sawyer firmly asserts that this exploratory mindset must be curtailed once the project transitions into full production. The production phase, by his definition, should be dedicated to execution: building the game based on the solidified plans and blueprints established in pre-production. Introducing significant changes or embarking on new experimental tangents during this stage, he warns, carries substantial risks. "If then in production, when you’re supposed to be just making the game, you start changing a bunch of things and experimenting, that’s extremely risky, and it’s extremely disruptive," Sawyer elaborated.
The Perils of Late-Stage Iteration and Scope Creep
Sawyer’s cautious approach extends to resisting proposed changes once a design element or feature has been deemed sufficiently "figured out." He tends to be conservative, preferring to avoid redoing work for what he perceives as theoretical, marginal gains in specific aspects of the game. The potential for such late-stage revisions to destabilize the entire project is, in his words, "enormous." Unnecessary changes can lead to wasted effort, substantial time overruns, and a domino effect of complications across various departments. "You’re going to waste a bunch of people’s work. You’re going to eat up a bunch of time," he stated, highlighting the tangible costs.
Despite this emphasis on discipline, Sawyer acknowledges that iteration and unforeseen challenges are inherent to game development. Projects rarely unfold precisely as initially planned. He points out that while being experimental during production is always an option, it comes with a significant cost, potentially adding anywhere from six months to a year and a half to the development schedule. The critical skill, then, lies in a team’s ability to discern when such an investment of time is genuinely warranted for the project’s overall quality and when it crosses the line into inefficient scope creep. This judgment call, he stresses, is an important one that requires both experience and a clear vision for the game.
A notable example from Pentiment‘s development illustrates this point. Even in its beta phase, the team identified that the game’s third act was not meeting their standards. This critical assessment led to a substantial rewrite of significant portions of the game, a decision that undoubtedly added time to the schedule. However, Sawyer affirmed that this particular investment of time was ultimately deemed worthwhile, indicating that strategic, impactful changes, even late in the cycle, can be justified if they address fundamental flaws and significantly enhance the player experience.
The Inevitable Complexities of Game Development
Despite meticulous planning, the realities of game development often introduce unexpected hurdles. Sawyer candidly admits that "Most of my projects will slip by three to six months pretty consistently." These delays can stem from a multitude of factors: initial prototypes that work well but fail during full implementation, fundamental changes in underlying engine technologies (such as Unreal Engine updates requiring pipeline overhauls), or the inherent complexities of integrating diverse systems. Such technical and logistical challenges underscore why even the most disciplined development processes often encounter unforeseen extensions.
The broader context of the video game industry further illuminates Sawyer’s advice. The past decade has seen a dramatic increase in the scale and ambition of AAA titles, leading to ballooning budgets and development cycles that frequently span five to seven years, and sometimes even longer. Games like Cyberpunk 2077 and Starfield, while not Obsidian titles, serve as high-profile examples of projects that underwent lengthy and often turbulent development, punctuated by multiple delays. The average cost of developing a AAA game can easily exceed $100 million, with some reaching several hundred million, making efficient development not just a preference but an economic imperative for studios and publishers alike.
Obsidian’s Own Development Trajectories: A Tale of Two Paths
Obsidian Entertainment itself provides compelling internal comparisons for Sawyer’s development philosophy. While Pentiment was completed efficiently by a small team, the studio’s larger flagship titles have followed a different trajectory. Last year, the studio released a trio of major titles: Avowed, Grounded 2, and The Outer Worlds 2. However, Sawyer revealed that this concentrated release schedule was not entirely by design but rather a consequence of internal challenges and projects not unfolding as initially planned.
Both Avowed and The Outer Worlds 2, in particular, experienced multiple delays and significantly extended development cycles, each reportedly taking more than six years to complete. These prolonged timelines had tangible financial repercussions. Sawyer noted that both games ultimately missed their sales forecasts, a shortfall he directly attributed, in part, to their budgets being inflated by the extended development periods. This illustrates a critical economic principle in game development: longer development times invariably lead to higher costs, which in turn necessitate higher sales figures to achieve profitability. When these targets are missed, the financial health of the studio and its future projects can be jeopardized.
The contrast between Pentiment‘s lean, focused development and the protracted, costly journeys of Avowed and The Outer Worlds 2 highlights a fundamental tension within the industry: the balance between creative ambition and practical constraints. Sawyer acknowledges this inherent conflict, stating, "Other people want to push things, experiment more… And that can lead to more interesting games and more interesting experiences. So what do you value more, right?" This question encapsulates the dilemma faced by many game directors and studio heads: whether to prioritize groundbreaking innovation and potentially lengthy, expensive development, or to embrace a more constrained, efficient approach that prioritizes timely delivery and financial viability, potentially at the cost of some experimental freedom.
Broader Industry Implications and the Call for Efficiency
Sawyer’s insights resonate with a growing conversation within the video game industry about sustainability and developer well-being. The phenomenon of "crunch culture," where developers work excessive hours, often unpaid, to meet tight deadlines, has drawn increasing scrutiny. While Sawyer’s advice focuses on process efficiency rather than explicitly addressing crunch, streamlining development cycles through better planning and disciplined execution could inherently mitigate some of the pressures that lead to unsustainable work practices. Shorter, more predictable timelines could contribute to healthier work-life balances for development teams.
Moreover, the success of smaller-scope, narrative-driven titles like Pentiment – which garnered significant critical acclaim for its unique art style, historical setting, and engaging storytelling – offers a compelling alternative model to the prevailing trend of ever-larger, open-world AAA games. It suggests that compelling and commercially successful experiences can be crafted with smaller teams and shorter development times, provided there is a clear vision, disciplined execution, and a willingness to embrace creative constraints. This model could be particularly appealing to studios seeking to diversify their portfolios, manage risk, or foster environments where innovative ideas can be brought to market more quickly.
The increasing prevalence of unionization efforts within the game industry, as highlighted by the related article concerning workers sending a message to industry executives, further underscores the need for more predictable and humane development cycles. Demands for better working conditions and fairer compensation are intrinsically linked to the financial health and operational efficiency of studios. When projects run significantly over budget and schedule, it creates financial strain that can directly impact employee welfare and job security.
In conclusion, Josh Sawyer’s counsel for shortening game development times is not merely a set of tactical suggestions but a philosophy rooted in strategic foresight and pragmatic execution. By rigorously separating pre-production from production, exercising caution with late-stage changes, and understanding the true costs of iteration, studios can potentially navigate the complex landscape of modern game development with greater efficiency and predictability. While the allure of boundless experimentation remains strong, Sawyer’s experiences at Obsidian Entertainment offer a powerful argument for the value of discipline, focus, and a clear understanding of what a project values most: groundbreaking innovation at any cost, or the strategic delivery of exceptional experiences within sustainable parameters. The industry’s future may well depend on finding a harmonious balance between these two compelling objectives.
About the Author
