Opinion: Why words matter when we prioritize ‘core teams’ in game development
A discussion about terminology in game development has sparked debate within the industry following a Gamesindustry.biz feature on Fuse Games’ “distributed development” model used for Star Wars: Galactic Racer. The model categorizes development teams around a central “core team,” a framework designed to manage complex production involving hundreds of developers across multiple areas of game creation.
The controversy emerged after a Bluesky post from an industry outlet discussing the approach, prompting frustration from members of the game development community. The debate centers on the language used to describe team structures and roles in game production, with developers questioning how terminology shapes development processes and workplace dynamics.
According to the opinion piece, the way the industry describes game development methodologies inevitably influences how those processes are actually implemented. The “core team” framework, while potentially useful for organizing large-scale distributed development, has raised concerns about how it might affect team culture, worker classification, or development priorities.
The story highlights an ongoing tension in the game industry around how organizational language and structure can have real implications for developers and production workflows. The distributed development model represents one approach to managing the complexity of modern AAA game production, but the terminology used to describe it—and who gets classified as part of the “core” versus peripheral teams—carries broader significance for industry practices and culture.