Faster tasks do not guarantee cheaper projects
Making one task faster does not necessarily make a game cheaper. In an October 8 interview with GamesIndustry.biz, Glen Schofield argues that creative decisions can currently offer greater savings than AI. It is a pointed contribution to the debate, but not a measured verdict on every tool or studio.
Schofield brings a long development career to that argument. His work includes senior roles connected to Call of Duty, Dead Space and The Callisto Protocol, as well as leadership at Sledgehammer Games and Striking Distance Studios. He announced his retirement earlier in 2026 and is now concentrating on art.
That experience gives his perspective weight. It does not turn an interview into an industry-wide productivity study. The reporting available here does not establish a comparative figure showing how much money AI saves, or fails to save, across different types of game production.
The distinction is important because development costs arise from more than the speed of individual tasks. A project may become expensive through changing requirements, unnecessary complexity, late revisions or features that do not fit together. Producing material faster does not automatically resolve those problems.
A creative decision can work differently. Simplifying a mechanic, choosing a more coherent visual direction or removing a feature that weakens the experience may reduce work across several departments. The saving comes from deciding what the game should be, rather than accelerating everything already on the schedule.
AI tools still need to be assessed according to specific uses. Assistance with a repetitive task is not the same proposition as generating a finished game world. A useful evaluation asks whether an output is accurate, consistent, legally usable and easier to integrate than an alternative.
It must also count the work that follows generation. Review, correction and integration consume time. If an apparently quick result needs extensive repair, the initial speed advantage may tell only part of the story.
For Moroccan students and small studios exploring game development, this debate has practical relevance. Tool selection should follow a clear production problem and a testable objective. A small experiment can reveal more than a broad promise that an entire workflow will become cheaper.
Schofield’s intervention is best understood as a challenge to simplistic accounting, not proof that innovation should stop. Games need efficient production, but they also need direction. The most valuable question is not whether a studio uses AI; it is whether its choices reduce unnecessary work while protecting the quality and identity of the game.
Schofield brings a long development career to that argument. His work includes senior roles connected to Call of Duty, Dead Space and The Callisto Protocol, as well as leadership at Sledgehammer Games and Striking Distance Studios. He announced his retirement earlier in 2026 and is now concentrating on art.
That experience gives his perspective weight. It does not turn an interview into an industry-wide productivity study. The reporting available here does not establish a comparative figure showing how much money AI saves, or fails to save, across different types of game production.
The distinction is important because development costs arise from more than the speed of individual tasks. A project may become expensive through changing requirements, unnecessary complexity, late revisions or features that do not fit together. Producing material faster does not automatically resolve those problems.
A creative decision can work differently. Simplifying a mechanic, choosing a more coherent visual direction or removing a feature that weakens the experience may reduce work across several departments. The saving comes from deciding what the game should be, rather than accelerating everything already on the schedule.
AI tools still need to be assessed according to specific uses. Assistance with a repetitive task is not the same proposition as generating a finished game world. A useful evaluation asks whether an output is accurate, consistent, legally usable and easier to integrate than an alternative.
It must also count the work that follows generation. Review, correction and integration consume time. If an apparently quick result needs extensive repair, the initial speed advantage may tell only part of the story.
For Moroccan students and small studios exploring game development, this debate has practical relevance. Tool selection should follow a clear production problem and a testable objective. A small experiment can reveal more than a broad promise that an entire workflow will become cheaper.
Schofield’s intervention is best understood as a challenge to simplistic accounting, not proof that innovation should stop. Games need efficient production, but they also need direction. The most valuable question is not whether a studio uses AI; it is whether its choices reduce unnecessary work while protecting the quality and identity of the game.