The Production Bubble: Why Studios Lay Off Staff Right After Launch

A game ships, reviews well, sells respectably, and within a few months part of the team that made it is let go. The public reads this as a verdict on the game. It usually is not.

It is a scheduling problem that has been building for two years and arrives on a predictable date.

The Shape of a Production

Game development is not evenly staffed. It ramps.

Early on a small group establishes what the game is — direction, prototypes, core systems. Headcount here is low, because more people would slow the work down rather than speed it up.

Then production proper begins and the requirement rises steeply. Content has to be built at volume: levels, assets, animation, audio, dialogue, UI. This is where most of the labour actually goes.

The peak is at the end. The final twelve to eighteen months need the most people the project will ever need — content completion, polish, optimisation, localisation, QA at scale, certification. A game needs more hands in its last year than in any year before it.

Then it ships, and the requirement falls off a cliff.

The Hybrid Staffing Model

It is often said that games carry these people as permanent staff where film crews simply disperse. That is not right, and the real picture matters.

Games run a hybrid model. There is a permanent core — direction, leads, engineering, the people who hold institutional knowledge. Around it sits a large contract periphery: outsourced QA, co-development partners, art outsourcing houses, contract animators and localisation vendors. A substantial share of the peak is bought rather than employed, and that share ends cleanly by design.

The difference from film is one of proportion rather than kind. A film production is almost entirely a temporary assembly; a games studio keeps a much larger permanent core through the trough. So when the peak passes, some of the reduction is contracts simply ending as planned — invisible, and not reported as layoffs — and some lands on employees, which is the part that becomes news.

That second part is the genuine problem, and it exists because the permanent core is sized somewhere between the trough and the peak. Size it for the trough and you cannot make the game. Size it for the peak and you are carrying people through periods with no work funded for them.

The Gap

In principle the next project absorbs the team. In practice there is a gap, and the gap is where the damage happens.

A new project needs to be greenlit and funded, and that decision often waits on how the last one performed — which is not known for months. Pre-production needs a small team, not a large one. And if the studio was acquired, or the publisher is reviewing its slate, or the market has turned, the decision may not come at all.

So the trough is real and its length is outside the studio’s control. Carrying a peak-sized permanent team through an indefinite gap is a cash problem that eventually becomes a headcount decision.

Why a Sales Milestone and a Layoff Can Share a Quarter

These read as contradictory and are not, for two reasons.

First, revenue reaching the publisher is not revenue reaching the studio. Under a publishing deal, the advance is recovered from the developer’s share before royalties flow. A game can be genuinely successful and the developer still be waiting on an account to clear.

Second, a milestone measures units, not margin. It says nothing about the budget the number had to clear, the discounting that got there, or how much marketing was charged against the project. As we set out in the piece on where the money goes, the developer’s share of a sale is a fraction of what the customer paid.

Why Acquisition Often Precedes It

Acquisitions are frequently followed by reductions, and the mechanism is usually duplication rather than punishment.

A studio that operated independently carried its own publishing, marketing, HR, IT and business functions. Inside a larger group those exist centrally. The overlap is identified during integration and removed, which is the synergy the acquisition was justified by in the first place.

Separately, an acquired studio’s slate gets reviewed against the group’s priorities, and projects that no longer fit are stopped — taking their teams with them.

Reading the Statement

“Restructuring to focus on our core franchises” generally means projects outside a small set of reliable earners have been cancelled.

“Aligning our resources with the current market” usually means revenue forecasts were revised down and cost was taken out to match.

“Difficult decisions to ensure long-term sustainability” is the standard formulation and carries little information on its own.

None of this makes the outcome acceptable for the people it lands on, and none of it is an argument that studios have no choices. Sizing a permanent core, deciding how much of a peak to contract out, and whether to fund a bridge between projects are all decisions someone makes. The point is narrower: post-launch layoffs are mostly a structural feature of how games are staffed, and reading each one as a referendum on the game that just shipped gets the cause wrong.