A Rough January, a Careful Forecast
Amir Satvat opened February 2026 with a number nobody wanted: 32 layoff events across the games industry in January alone, cutting 2,015 jobs in a single month. Satvat runs ASGC, a free industry layoff-tracking project that has become one of the closest things games has to an independent count, and he used that January data to build a full-year projection rather than just reporting the month.
His forecast landed at approximately 10,138 layoffs for 2026: the 2,015 already confirmed plus a projected 8,123 more before December. "January came in heavier than expected," Satvat said, placing his own number between the industry's two recent extremes, 10,500 layoffs in 2023 and 9,197 in 2025. It read as a careful, data grounded estimate from an analyst running a live tracker with no reason to inflate it.
The Number That Moved
Five months later the same tracker told a different story. By July 27, 2026, Satvat's full-year forecast for games industry layoffs had climbed to 14,259, itself revised up by 381 in the space of seventeen days from a July 10 figure of 13,878.
Confirmed layoffs, the actual count rather than the projection, rose from 9,464 to 9,781 in that same update, a jump of 317 jobs in weeks. Measured against the trajectory the February forecast implied, the July number represented a 78 percent increase. The analyst had not gotten careless. The year had kept compounding faster than any single month's data could show.
What Microsoft's Disclosure Actually Reset
Part of the upward revision had a name attached. Microsoft disclosed that it had already laid off 1,600 workers across its games division and planned to cut another 1,600 in the following year.
A single company's disclosure reset the baseline the whole forecast was built on. A number that size from one publisher changes the shape of the rest of the year's trend, and that is the mechanism a January snapshot cannot see coming: the event that moves the whole model usually has not happened yet when the model gets built.
Why a Q1 Forecast Lies About the Full Year
This story teaches a lesson that has nothing to do with games. It applies to any operator building an annual plan on the first quarter's real numbers, whether the plan covers headcount, an annual budget or a vendor-risk assessment.
Early-year data understates a trend that keeps compounding through the year, and it does so systematically rather than randomly. Satvat's February number was not wrong because ASGC's methodology was weak. It was wrong in the direction a Q1-anchored forecast tends to be wrong: too low, because the disclosures that reset a baseline (a Microsoft-sized event, an acquisition, a policy change) mostly land after the quarter closes.
Building the Re-Forecast Checkpoint In
An operator who takes one thing from this story should take a single rule: a forecast built on the first quarter's data is a floor for planning, not a midpoint. That holds whether the plan being built is a games-industry layoff count, an annual budget or a vendor-risk assessment for a completely different sector.
Build a re-forecast checkpoint into the plan itself, a fixed date mid-year to test the January number against new disclosures before committing further. Satvat's own tracker did exactly that in public, revising itself twice within seventeen days once mid-year data started arriving.
Servola Journal
We do this for everyone trying to keep up with what technology is doing to our lives. The people who build it, and the people it happens to. The Servola Journal exists so that what we learn belongs to all of them.
Nobody pays us for this. No ads, no paywall, free to everyone. We just believe that understanding what's happening to all of us shouldn't depend on who can afford to pay for it.
If it gave you something today, tell us to keep going. Follow us, leave a like, or write a positive comment. We read every one, and they are what keeps us going.
Read next: Apple's 2011 CEO Shock Cost 12 Times More Than 2026's | Xbox's U-Turn Was on Marketing, Not the Games
