Microsoft's id Software Cuts Reshape Xbox Strategy

id Software faces significant restructuring

id Software is changing. Recent official filings confirm that 136 positions have been eliminated, leaving a staff of fewer than 50 employees from the 185 that were recorded in December 2025. This signals a departure from its historical role as a primary engine of development. So the scale of the departure has left observers and former staff questioning the future capacity of a team once defined by its independent creative output. It's a fundamental change. But can they still create?

Strategic shift toward support functions

It's a stark trajectory. The broader pattern in gaming suggests a move toward centralizing resources, but the specific path here involves senior engine-related roles and many coding positions being cut, so the studio appears to be transitioning away from its legacy as a creator of both proprietary technology and full-scale titles. Instead, it's being positioned to serve as a support unit. And this fits a pattern where established talent is moved to assist other teams on high-profile projects rather than spearheading new initiatives.

Loss of creative autonomy

This move creates a difficult environment for the development of new intellectual property. We’ve lost a lot. Several concepts were in motion before the restructuring took effect, yet none were formally greenlit for production, and so here's what we've lost: the following pitches were among those identified before the workforce reduction.

• Fury, a John Wick-style project combining sci-fi and noir elements with Gun Fu gameplay.
• A new entry in the Perfect Dark franchise.
• Ironwood, a survival-focused title inspired by Westworld themes.
• A multiplayer and co-op iteration of the Doom series.

The abandonment of these concepts highlights the shift away from autonomous development. It's a huge problem. So it's left the studio without the personnel required to manage the lifecycle of a large-scale project, and they can't fix it easily.

Expert perspectives on internal shifts

It's a heavy loss. The impact on the team's culture and technical expertise has been described as a profound drain of institutional knowledge, and the internal reaction reflects just how intense this change really is.

Former principal VFX artist Derek Best noted: "I'm still in shock at how brutal the layoff cuts were. Collectively decades of knowledge was wiped out of the studio. Great job Microsoft. Nothing says business success like nuking a team into the dirt and relegating them to support studio size while also throwing out massive technological achievements.

This move shows how fast a corporate directive can redefine a studio's identity. Leadership said their goal was to make tool use more efficient and cut spending on outside vendors, but that priority apparently clashed with the need to keep the very engineers who manage internal technology. So the outcome is tough to reconcile. It's hard to see how a unified engine was the real priority when key technical personnel have left.

Market realities and technology decisions

The decision to move away from internal development creates a clear divide in technical strategy. But the studio was historically known for the id Tech engine, and the reliance on external tools for other active projects creates a disconnect. This is a major shift. If internal tools are being phased out in favor of external solutions, the logic behind the workforce reduction becomes clearer, since it points to a consolidation of assets rather than a preservation of specific studio workflows.

The industry is still consolidating. Companies are evaluating their rosters with an eye toward immediate efficiencies, and the focus is now on immediate project needs rather than long-term technical innovation. So id Software functions as a localized partner instead of an independent powerhouse. But it's unclear how the remaining team will integrate into the broader production schedule for upcoming titles like those rumored in the Wolfenstein series.

Future of the studio entity

No clear path exists for the studio to return to its previous scale. But the focus is now on the next production cycle and the integration of the remaining personnel into existing workflows, with no active work on the Quake franchise and a decimated coding department ensuring that support roles are the only real priority. That era is over. The studio’s time as a standalone developer of its own engine and its own game concepts has concluded, and there's simply no way to get it back.