Xbox is set to close or sell five studios next week — and the games are supposed to survive the people

Gaming 4 min 80 sources

Microsoft plans studio closures and cuts starting July 6, even as its own developers strike elsewhere to prove an unfinished game dies when its team does.

Key takeaways

Microsoft is expected to close or sell five of its own game studios on July 6 and cancel Marvel's Blade, part of a wider industry contraction.
The same week, Quantic Dream's developers went on strike arguing that Star Wars Eclipse "literally cannot be finished" if the layoffs remove the people who know how it's built.
Across Xbox, Quantic Dream, and IO Interactive, the shared assumption is that a game can survive losing its team — and the workers are betting that it can't.

Next week is bracing for the largest single day of games-industry cuts this year. According to reports from The Verge, Bloomberg, and GamesBeat gathered this week, Microsoft is preparing to close or sell off five of its own studios on July 6 — Compulsion Games, Double Fine, Ninja Theory, Undead Labs, and Arkane — and cancel Marvel’s Blade, the game Arkane had been building since late 2023 [4][16]. None of it is confirmed by Microsoft yet. But the signs are already showing: at Compulsion Games, the studio behind South of Midnight, bosses have quietly told staff they’re allowed to look for new jobs, and a wave of developers has posted on LinkedIn that they’re on the market [6].

The mechanism: a studio is cheaper to cut than to keep

When a big platform owns dozens of studios, each one is a cost on a spreadsheet that has to justify itself against every other. A studio that hasn’t shipped a hit recently — or is deep in a project that keeps slipping — reads as money going out with nothing coming back. The new Xbox leadership has said the company found itself “over-extended” [6]. In plain terms: they bought more studios than the current sales can carry, and closing or selling a team is the fastest way to shrink the bill. Blade had gone more than two years without a public update [4]. To an accountant, that’s a project to stop, not a game to finish.

The same week, a different studio’s developers went on strike to save their game

In France, developers at Quantic Dream — the studio behind Detroit: Become Human — walked out and formed a picket line [8][49]. The trigger: an “internal reorganisation” the French union STJV says puts 115 jobs at risk [49]. What makes this strike unusual is what the workers are striking for. They say Star Wars Eclipse, the studio’s long-delayed big project, “literally cannot be finished” if the layoffs go through [28][49]. One developer told the French site Gamekult the strike is “far from being an act of sabotage” — they’re trying to keep the game alive [49]. The studio had insisted Eclipse was “not affected” by the cancellation of its failed live-service game Spellcasters Chronicles, which shut just three months after early access [9]. Its own developers say otherwise.

And a third studio cut staff on a game that hasn’t launched

IO Interactive — the Danish maker of Hitman and the upcoming 007 First Light — announced layoffs this week too [11][67]. The cause: a “relationship with an external partner” on its unannounced fantasy RPG, reportedly funded by Xbox, ended [11]. The funding vanished, so the team building the game shrank [67]. The game was never even released. The pattern across all three: the projects are supposed to continue, but the people building them are the thing being removed.

Why this is one story, not three

These aren’t separate news items. They’re the same contraction seen from three angles. A live-service bet fails (Quantic Dream’s Spellcasters, Bungie’s Destiny 2), a publisher’s funding pulls back (IO’s fantasy game), or a parent company decides it owns too many teams (Xbox) — and in every case the response is the same: cut the people, keep the plan. Bungie, owned by Sony, cut 292 staff at its Bellevue headquarters this month with a separation date of July 9, its third round of layoffs in three years [17]. The studio once had over 1,000 people there [17]. The recurring assumption underneath all of it is that a game is a set of files and a roadmap that a smaller team can carry forward. The strikers at Quantic Dream are betting their jobs on the claim that it isn’t.

What players see

This is why so many announced games quietly disappear, and why the ones that survive often arrive changed. When the team that knew how a half-built game fit together is gone, finishing it isn’t a matter of hiring replacements — it’s a matter of rebuilding knowledge that was never fully written down. Marvel’s Blade may simply never exist. Star Wars Eclipse may not either. The question isn’t whether the studios can afford the people. It’s whether the games can survive without them.

02 · Lesson · why it matters

The part of the work that was never written down

A plan is what a team knows made visible; cut the team, and you keep the visible part while losing the thing that made it work.

The document is not the knowledge

When a studio announces it will cut most of a team but keep the project alive, it’s making a quiet claim: that the game exists in the files, the design documents, the roadmap — and that a smaller crew, or a new one, can pick those up and carry on. This week three studios made that bet at once. Xbox is set to close or sell five teams while some of their games are meant to continue. IO Interactive lost a partner’s funding and shrank the team on a game that hadn’t even launched. And at Quantic Dream, the developers themselves stood outside the building and said the opposite out loud: without us, this cannot be finished.

They are describing something most work quietly runs on and almost never names. The most important knowledge in any complex project is the part nobody wrote down — because it couldn’t be. Why this system was built the awkward way it was. Which piece will break if you touch that one. The workaround from eight months ago that everyone remembers and no one documented. This lives in people’s heads, and it walks out the door with them.

The plan is the map; the team is the territory

There’s an old confusion at the heart of this. We treat the plan as if it were the thing itself. But a design document is a description of a game, the way a map is a description of a place. You can hold the map after the guides have gone. You just can’t walk the trail with it — not the parts where the path isn’t marked, where you needed someone who’d been there.

A half-built game is almost entirely unmarked path. Half a system, wired to another half-system, held together by choices that made sense to the people who made them and to almost no one else. The document says what. The team held the why — and the why is what you need when something breaks and you have to decide how to fix it without unravelling everything else. Finishing isn’t reading the map. It’s knowing the territory. The strikers at Quantic Dream aren’t being dramatic. They’re being literal.

Who wasn’t in the room

Here’s the shape underneath the event. The decision to cut a team and keep its project gets made by people who can see the plan but were never inside the work. An executive reads a roadmap, a budget, a slipping schedule. They can see everything that was written down. They cannot see the thing that wasn’t — because the whole nature of that knowledge is that it doesn’t appear on a page. So the part of the game that is easiest to see is the plan, and the part that actually finishes the game is invisible to exactly the seat that decides its fate.

This isn’t a story about villains. A company that owns more studios than its current sales can carry has a real problem, and shrinking is a real answer to it. The arrangement that makes cutting feel safe — the belief that a game is its documentation — isn’t a lie someone tells. It’s an honest mistake that the structure encourages, because the structure only shows the decider what’s on paper. The people who know it’s a mistake are the ones being cut, and they weren’t asked.

The survivors tell you nothing

And there’s a trap in how we learn from all this. Some games do survive their team’s departure — a new crew comes in, the thing ships, it’s fine. So the lesson looks like: it can be done. But you’re only seeing the games that made it. The ones where the knowledge left and the project quietly died never get announced as failures. They just stop. Marvel’s Blade had no update in over two years, and it may simply never exist — no press release, no post-mortem, just a game that was going to happen and then wasn’t. The industry is full of these silent gaps. We count the survivors and conclude the crossing is safe, because the ones who didn’t make it aren’t there to say otherwise.

Where you are in this

You are closer to this than it looks. Every place you’ve worked, every group you’ve been part of, ran on knowledge nobody wrote down — the reason the process is the way it is, the person everyone quietly asks, the fix that isn’t in any manual. When that person leaves, or that team is broken up to save money, the thing they held doesn’t transfer with their files. It’s the same in your own life: the plans you keep are the smallest part of what you actually know how to do.

None of us can see this fully, and that’s the humbling part. The executive can’t see the tacit knowledge; the developers can’t see the whole budget; you, reading this, can’t fully see what you yourself know until you try to hand it to someone else and watch it fail to arrive. Everyone in the story is working from a partial map. So when you hear that a team was cut but the work will go on, hold the claim loosely. The plan survived. Whether the game does is a different question — and the only people who could answer it are the ones who just left.

03 · Lab · your turn

Cut the Team, Keep the Game

Rehearse deciding who to cut from a game's team using only what's visible on paper, then feel the invisible knowledge that leaves with them.

04 · Hope · carry this

The developers on the picket line, insisting the game cannot be finished without them, are refusing to let their own knowledge be treated as invisible. People who know their worth, and say so out loud, are hard to write off a spreadsheet.