
Team from id Software refutes statements about layoffs
Comparing the current structure with the tumultuous development cycle of DOOM (2016) in an attempt to mitigate the crisis was a colossal mistake by the leadership. Former employees recalled that the project endured nearly seven years of production, underwent painful revisions, and demanded an overwhelming period of excessive work. Furthermore, the studio once delivered the product after suffering a massive exodus between 2010 and 2011, being forced to hire in haste and rely on the support of outsourced teams. Using a period marked by such strain to justify the current situation reveals a striking insensitivity to those who carried the development burden.
The controversy gained traction following an investigation by the Game Developer portal, which interviewed workers upset with Hugo Martin, the franchise's co-director. The executive tried to downplay the recent layoffs made by Xbox, claiming the studio hadn't been weakened by the cuts. However, anonymous developers disputed this position, asserting that the director minimized the impact of the downsizing and showed disrespect towards the dismissed professionals.
"If you reduce an attribute by half, everyone would say it was nerfed. The DOOM team is halfway here, halfway cast aside," confided one of the affected developers.
To try to contain the damage, the co-director argued that id Software continues to operate with about 50 producers and that the graphics engine id Tech will keep evolving in partnership with MachineGames and the Frankfurt team. This justification doesn't hold when analyzing the scale of the cuts: the restructuring promoted by Microsoft in the Xbox division swept away about half of the workforce of the shooter game creator, adding up to over 1,600 layoffs across the company.
Treating the dismissal of half of a talented team as if it were a routine adjustment is a regrettable move. When executives attempt to sugarcoat internal deterioration while the publisher is cutting jobs en masse, the community's trust and the developer's creative environment inevitably suffer.



Comments
Log in to your account or create one for free on MG Community to participate in comments.