Quebec is home to more than three hundred active video game studios, the highest density of this industry in North America outside California. That concentration has begun to hollow out. Ubisoft, Warner Bros Games, Beenox, Eidos Montreal, and Ludia all appear on a list of cuts that led the provincial government to publicly acknowledge a sector in crisis. This isn't just a rhetorical flourish: it's the first time in the young history of this regional industry that layoffs have consistently outpaced hiring.
What separates an AI-induced layoff from one driven by budget restructuring? The first occurs when a specific task gets automated and the position disappears because the machine does the work at lower cost. The second arises when a company shifts capital toward another priority — in this case, generative AI infrastructure — and cancels projects that no longer fit, dragging the associated jobs down with them. These are distinct dynamics that produce the same visible outcome.
Records from the Institut de la statistique du Québec and reports from the Syndicat des travailleurs et travailleuses de l'industrie du jeu vidéo au Québec show that most recent adjustments were concentrated in studios dependent on funding from parent companies in the United States or France. The crisis wasn't born locally: it arrived imported from decisions made in Redmond, Burbank, or Paris, and Quebec absorbs it because that's where the skilled labor lives.
What's happening with studios in other countries? The same pattern shows up. In the United Kingdom, Rocksteady and Crystal Dynamics faced rounds directly tied to Xbox. In Japan, Bethesda teams under the Microsoft umbrella reported smaller but concrete cuts. In Spain, MercurySteam and Tequila Works saw reductions or closures. The geography confirms this isn't an issue exclusive to Quebec, but a trend affecting projects linked to certain large-scale corporate bets.
The most solid reading is that AI functions as an indirect factor, not as the literal cause of each layoff. Microsoft is pouring tens of billions into data centers, chips, and proprietary models. That capital has to come from somewhere. When the budget reorients toward AI, video game projects with slower or more uncertain returns become dispensable — not because an AI replaces a level designer one-for-one, but because that designer is competing for the same resource as a cluster of GPUs.
I've seen similar dynamics in other technological shifts where capital was massively redirected. Money that once sustained payrolls now builds algorithmic infrastructure, and jobs adjust as a consequence. This process isn't new, even if corporate vocabulary tries to obscure it.
There's also an ironic layer here. The video game industry spent decades perfecting reward systems, progression mechanics, and instant feedback loops to retain players — mechanics that later spread to other fields. Now that same industry is being reorganized by the algorithmic optimization of human costs, the very logic it helped normalize. Its own titles use AI for NPC dialogue, background textures, or automated bug testing while shrinking design teams. The contradiction doesn't prove direct causation, but it does reveal a tension the industry is only beginning to acknowledge.
"Stones Don't Lie" offers a framework for examining these moments when certain capabilities are prioritized over others, similar to historical episodes where entire societies lost accumulated knowledge by radically reallocating resources. I still don't have a clear picture of how this tension resolves at full scale. Quebec unions are pushing for transparency clauses in collective contracts, an experiment inspired by earlier strikes. I keep exploring these cases because we need to precisely distinguish between literal automation and AI-induced budget reorganization. Only then can we act where priorities are actually being decided.
What will happen when future historians review these layoffs and ask not just how many jobs vanished, but why the true cost of that reallocation stayed invisible for so long?
