Back to feed
GamingDEVELOPING

Saber CCO Tim Willits Blames Layoffs on Overspecialization: 'Studios with a Couple Hundred Employees That Work on One Game Are Going to Struggle'

In brief

In an interview with PC Gamer, Saber Interactive CCO Tim Willits attributed some of the games industry’s troubles, including layoffs, to heavy specialization and very large teams focused on single titles. He said Saber has mitigated such risks by allocating resources across big projects, remasters and smaller games. Willits pointed to SnowRunner — which began as a one-person experiment and has over 46,000 Steam user reviews — while Saber also works on larger bets such as Space Marine 2 and Jurassic Park: Survival. He described the present moment as “actually, honestly, a good time” for the medium and downplayed alarming scenarios around AI.

Text size
Details and context

What happened

Tim Willits, chief creative officer at Saber Interactive, told PC Gamer reporter Joshua Wolens that some of the games industry’s current troubles are linked to over-specialization and very large teams focused on single titles. He argued that the industry experiences cycles of ups and downs and described Saber’s approach of spreading resources across projects of varying scope.

Willits cited Saber’s slate to illustrate the point: the company is developing big projects such as Space Marine 2 and the upcoming Jurassic Park: Survival, while also producing remasters and smaller games that fund those larger bets. He contrasted this with the kind of extreme specialization seen around mega-games like GTA 6, which he said can include teams specifically “art-directing” background NPCs.

In the interview, Willits emphasised Saber’s internal culture of moving people between projects and allowing developers to work on different titles, which he says helps the studio avoid the “silo problem” found in some large companies.

Why this is happening

Willits explained that large studios often form silos in which hundreds of employees focus on a single game, creating structural risk. He asserted that before a game reaches a vertical slice, it is not necessary to have hundreds of people working on it, implying that this staffing model increases vulnerability for those studios.

Saber’s alternative, as described by Willits, is to distribute resources across a spectrum of projects. Remasters and smaller titles serve as financial support for the studio’s bigger projects, enabling Saber to take larger creative and commercial bets without committing the entire workforce to one product.

He also argued that letting developers pursue smaller passion projects can pay off: experiments can become major successes, even if the interview does not present systematic data proving causation between that approach and overall corporate resilience.

How this will affect

Willits warned that studios employing “a couple hundred employees that work on one game” are going to struggle and “really struggle to survive.” That statement frames his view of the risk facing heavily specialized teams, but the interview does not supply specific examples or industry-wide data linking that staffing model to particular layoffs.

He framed Saber’s model as delivering both financial and morale benefits: moving people between projects and enabling smaller endeavours can lead to unexpected hits and prevents developers from being tied to a single title for five or six years. This, he suggested, supports creativity and employee satisfaction.

As an example, Willits pointed to SnowRunner — which began as an experiment by one person and later became a “mega franchise” for Saber, with over 46,000 user reviews on Steam — as evidence that small projects can grow into substantial successes.

What next

Willits described the current period as “actually, honestly, a good time” for the medium, despite the industry’s reported problems. He also downplayed dire views about AI’s impact, saying that id Software would have used such tools when they were available; Willits served as id’s studio director from 1995 to 2019, a point he invoked in the discussion.

He urged studios to consider taking small, deliberate risks: placing talented developers on modest projects, pricing them cheaply, and seeing if they catch on. The interview offers this as a strategic preference but does not include detailed financial models or implementation guidelines for broader industry adoption.

What the interview does not provide is a quantitative analysis tying overspecialization directly to the wave of layoffs or naming the specific studios most at risk. Willits presents a line of reasoning supported by examples from Saber’s experience, while empirical evidence and third-party case studies are not included in the piece.

In sum, the source presents Willits’s prescription — diversify project scope and enable internal mobility — as a way to mitigate risks he associates with large, single-project staffing, while leaving some questions about scale and external validation open due to lack of additional data in the interview.

What we know

  • Tim Willits, Saber Interactive CCO, told PC Gamer that some industry problems stem from excessive team specialization.
  • Saber balances large projects (Space Marine 2, Jurassic Park: Survival) with remasters and smaller games to fund big bets.
  • Willits said studios with "a couple hundred employees that work on one game" are going to struggle and face a "silo problem."
  • SnowRunner began as an experiment by one person and now has over 46,000 user reviews on Steam, cited by Willits as a success of smaller projects.
  • Willits described the present as "actually, honestly, a good time" for the medium and downplayed alarm over AI's impact.

What is being verified

  • The newsroom is checking the report that tim Willits, Saber Interactive CCO, told PC Gamer that some industry problems stem from excessive team specialization.
  • Reporting from PC Gamer is being compared; a second independent confirmation is not yet available.
If a new independent confirmation or correction appears, it will be added to the story timeline automatically.
View sources1

COMMUNITY

Discussion

0

No comments yet. Start the discussion.