Growth, culture, and reinvention in game studios

My 2024 essay tried to explain why game studios rise, decline, and reinvent themselves by comparing several famous companies. It moved too quickly from public events—a disappointing console generation, a delayed game, a studio closure—to claims about culture and management. Those claims sounded explanatory, but the evidence I had cited did not establish the causes.

I now think the more useful question is smaller: what can an outside observer responsibly learn from a studio’s public history, and what remains unknown without the people and decisions behind it?

Success is visible; its causes are harder to see

Company records can show that a product sold, a business changed its structure, or a platform reached a particular audience. They rarely reveal the complete mix of creative choices, timing, budgets, team experience, market conditions, and luck behind the result.

Nintendo’s own sales table records a striking contrast between the Wii U and Switch: 13.56 million Wii U hardware units and 156.59 million Switch units worldwide, according to the company’s figures through 30 June 2026 (Nintendo sales data). That contrast documents different commercial outcomes. By itself, it does not prove which design or management decisions produced them, or that another studio could reproduce the later result.

Likewise, a reorganization is evidence that leaders chose to change the operating model; it is not evidence that the new model will succeed. Ubisoft’s January 2026 announcement described a major organizational and portfolio reset intended to restore growth and creative leadership (company announcement). The intention is public. The eventual effects need to be judged from later evidence, not inferred from the announcement.

People are part of the system

Financial and product records leave out much of the working experience. The International Game Developers Association runs a Developer Satisfaction Survey with Western University to study developers’ demographics, quality of life, and career satisfaction (IGDA survey). Survey results are useful signals about respondents and the questions they were asked; they are not a complete census of every studio or a direct measurement of why a particular project succeeded or failed.

That is a limit worth keeping visible. It is easy to turn a public outcome into a neat story about “good culture” or “bad leadership.” But culture is not a single variable, and a studio is not a controlled experiment. Teams work inside constraints that outsiders may not see. A responsible account should separate what a source documents from what the writer is interpreting.

A more useful way to discuss reinvention

When I read about a studio changing direction, I now look for questions before conclusions: What changed in the product or portfolio? What did the company say it wanted to change? What happened to the people doing the work? Which results are measured, over what period, and by whom? Where is the information missing?

For leaders in any software organization, the transferable point is not that a game studio’s trajectory predicts another company’s future. It is that growth changes the conditions of work, while a new strategy has to be evaluated by what it actually enables. Public success can establish that an outcome occurred; understanding why requires better evidence than a retrospective slogan.

Editor’s note

Originally published on 4 February 2024 and substantially rewritten in September 2026. This version removes stale forecasts, unsupported company-culture claims, and the suggestion that a small set of studio histories predicts the future of other technology companies. It uses public company data and an industry survey with their limits stated explicitly. No employer or customer information is involved.