The Two Faces of Game Development Crunch

When a Diablo 4 lead developer recently spoke publicly about crunch in game development, the framing was straightforward enough: small studios and major publishers face fundamentally different pressures, and the reasons behind overtime vary accordingly. That distinction sounds reasonable on its face. Scratch the surface, though, and it opens onto a much thornier set of questions about power, profit, and who gets to define what counts as acceptable sacrifice in an industry that generated over $180 billion globally in 2025.

The developer's core argument, as reported via social media, was that indie teams often crunch because of passion and limited runway — a small studio burning through savings to meet a launch window that determines whether the company survives. AAA studios, by contrast, crunch under the weight of massive budgets, publisher expectations, and the logistical complexity of coordinating hundreds of contributors across multiple time zones. The pressure is real in both cases. The causes are not the same.

That distinction matters, but not necessarily in the way the industry usually presents it.

The Indie Exception and the AAA Default

The romantic narrative around indie crunch is familiar: a handful of developers pouring everything into a passion project, choosing to work weekends because they believe in what they're building. That story has the advantage of being partly true. Indie studios frequently do operate on tighter margins, with fewer people wearing more hats, and the decision to push harder often sits closer to the individuals making the game than to any corporate directive.

What gets elided in that framing is the coercive dimension that persists even in the absence of an explicit mandate. When your studio's viability depends on hitting a release window, the overtime isn't precisely voluntary — it's the product of a structural bind. You crunch because the alternative is watching the company fold. You crunch because health insurance, for American developers, flows through employment. You crunch because the industry has normalized "crunch is part of the culture" as a sentence that somehow absolves the people doing the requiring.

At AAA studios, the dynamics shift, but not always in the direction the developer's framing might suggest. Large publishers can, in theory, absorb the costs of longer development cycles. They have capital reserves, publishing infrastructure, and revenue streams from back-catalog sales that smaller studios lack. The choice to compress a development timeline is frequently a business decision made at the executive level — one that translates into concrete overtime requirements for the people actually building the game.

This is where the Diablo 4 lead developer's distinction, as reported, risks serving as exculpatory language. "Small teams often crunch for different reasons than we do" can function as a way of partitioning guilt: their crunch is authentic, born of necessity; our crunch is structural, born of planning. Both statements may be accurate. Only one of them points toward accountability.

The Business Case for Exploitation

The economics of modern game publishing create persistent incentives to extract maximum output from development teams during critical windows. A blockbuster game — the kind that justifies a studio's existence in the eyes of a corporate parent — carries an enormous reputational and financial weight. Delays carry costs: marketing spend locked into release windows, competitor positioning, shareholder expectations for quarterly revenue. When those pressures compound, they tend to resolve downward, toward the people who actually write code and design environments.

The gaming industry has, over the past decade, experienced a slow-rolling reckoning on this front. High-profile exposures of brutal crunch conditions at studios including Rockstar, Naughty Dog, and CD Projekt Red have forced a grudging acknowledgment that something is wrong. Industry associations have published guidelines. Studios have issued statements. The problem, as with many labor issues in creative industries, is that the power asymmetry that produces the crunch remains largely intact.

Game developers, particularly senior talent, have meaningful bargaining power in a tight labor market. They can leave. They can negotiate. They can, occasionally, win concessions. But the fundamental dynamic — where the cost of a delayed or underperforming game falls on a corporation's balance sheet, while the cost of meeting that deadline falls on individual workers' bodies and relationships — has proven resistant to voluntary reform.

What Accountability Actually Requires

The Diablo 4 lead developer's comments, insofar as they acknowledge that crunch exists and operates differently across contexts, represent a kind of progress. The industry has spent years treating overtime as an embarrassing footnote, something that happens but that nobody quite owns. The fact that a lead developer at a major studio is willing to discuss the phenomenon, even in sanitized terms, suggests that the silence is finally breaking down.

But discussion is not the same as accountability. The useful question is not whether indie and AAA crunch differ — they plainly do — but whether the current distribution of costs and choices is acceptable, and to whom. If the answer is that crunch is regrettable but unavoidable, that answer should come with a clear account of who decided it was unavoidable, and whether those decision-makers absorbed any of the downside.

The evidence, across the industry, suggests they largely have not. Publisher profits remain robust. Executive compensation tracks revenue targets that presuppose timely, high-quality releases. The workers who deliver those releases through sustained overtime carry the health and personal costs. When that ledger is made explicit, the "different reasons" framing begins to look less like honest analysis and more like a structural justification for an arrangement that benefits one side disproportionately.

That is not an argument that crunch can be eliminated overnight, or that game development is uniquely victimized by the pressures that shape most knowledge-industry labor. The economics of creative work have always been difficult, and the specificity of game development — the integration of engineering, art, narrative, and live operations — creates genuine scheduling challenges. But the existence of difficulty does not determine the distribution of sacrifice. That is a choice. And choices can be made differently.

The Diablo 4 developer's comments offer a useful opening. Whether the industry uses it to interrogate its own structures or simply to draw cleaner moral boundaries between indie authenticity and AAA necessity will say more about where things actually stand than any individual statement can.

Monexus covers the gaming industry as part of its culture desk, tracking the intersection of creative labor, corporate governance, and platform economics. This article draws on developer-reported comments circulating on social media and contextualizes them against industry reporting on working conditions at major studios.