Sustained overtime during development has been documented repeatedly and studied outside the industry.
What the research shows
Productivity per hour falling sharply beyond sustained long weeks.
Which is established in other industries and applies here.
Error rates
Defects rising with fatigue.
Which produces work that has to be redone.
Retention
Experienced staff leaving the industry.
Which is a substantial documented loss of expertise.
Why it persists
Fixed release dates, underestimated scope and structural incentives.
What the evidence outside games shows
Research across industries consistently finds that output per hour falls sharply after sustained long weeks, and total output can fall below that of a normal schedule.
Which means crunch frequently produces less work rather than more, at higher cost.
Error rates rise at the same time, so a proportion of what is produced has to be redone.
Why it happens anyway
Fixed marketing dates, optimistic scoping and a culture that treats it as normal.
Which are structural rather than individual failings.
Effects on people
Health, relationships and departures from the industry.
Which is a substantial loss of accumulated expertise.
Unionisation
Organising efforts in several studios.
Which is a recent and growing development.
Studios that avoid it
Realistic scoping and willingness to cut features.
Why scoping is the real cause
Crunch is almost always the consequence of a project that committed to more than it could deliver in the time available.
Which means the decision that produced it was made years earlier, at scoping, not in the final months.
Studios that avoid it generally do so by cutting features early and repeatedly rather than by working harder later.
Voluntary and mandatory
The distinction frequently being nominal.
Which staff describe consistently.
Contract and outsourced staff
Less protection and less visibility.
Which affects a large part of the workforce.
Public accountability
Reporting that has changed studio behaviour in some cases.
What players can do
Accepting delays without treating them as failures.
What has actually changed
Public reporting, unionisation efforts and a labour market where experienced developers have options have all applied pressure.
Which has produced visible change at some studios and none at others.
Studios that publicly commit to sustainable schedules generally also ship later and cut more features, which is the actual mechanism rather than better management alone.
Delays as a signal
Announced delays sometimes indicating a decision to avoid crunch.
Which is worth interpreting generously.
The economics
Overtime frequently unpaid for salaried staff.
Which is why it appears free to the project.
Quality assurance
Testing staff affected disproportionately.
Which is a long-standing concern.
Where to read about it
Investigative games journalism has documented this repeatedly.
A note on how this industry reports itself
Games is an unusually opaque business for one with such a visible product. Budgets are rarely disclosed, sales figures are announced selectively, player numbers are quoted in whichever metric flatters, and profitability is almost never stated at all.
Most of what is publicly known comes from court filings, leaked documents, regulatory submissions and former employees speaking after the fact. That material is reliable when it exists and covers a small fraction of the industry, which means any general claim about how games perform commercially rests on a limited and non-random sample.
Where the better information is
Developer conference talks are the single best public source on how games are actually made, and a large number are freely available. Regulatory filings during acquisitions have disclosed more real financial detail than a decade of press releases. Trade publications with industry sources are considerably more informative than consumer coverage on business questions.
Treat anything presented as an industry-wide figure with some caution, including in this article, and prefer sources that say where their numbers came from.
Why the business side is worth understanding
A great deal of frustration with games comes from decisions that look inexplicable from outside and are entirely predictable once the commercial structure is visible. Why a game shipped unfinished, why a beloved studio was closed after a successful release, why a sequel dropped features the previous game had, why a service shut down two years in.
None of these are mysteries. They are the outcomes of funding structures, platform economics, publisher portfolio decisions and the fact that games are made by people working to schedules set before anyone knew what the game would be.
Knowing that does not make the outcomes better. It does make them legible, and it makes it easier to tell the difference between a studio that made a mistake and one that was never given the conditions to succeed.
One thing worth remembering
Games are made by people, mostly people who care a great deal about them, working inside commercial structures they did not design and frequently cannot change.
Criticism of a game is fair. Criticism of the decisions behind it is usually aimed at the wrong floor of the building.