It is worth understanding that this is “different” than… all the other layoffs in tech at this point.
MS acquired ABK. Any acquisition almost always leads to “downsizing”. At a high level: ABK would have had their own payroll department. Now they go through MS payroll. Why do you need an entire department whose job is now superfluous? Obviously this gets a LOT more complex with developers and the like (as well as local management) but that is the mindset.
But… holy fucking shit that is a lot of people getting laid off at one of the worst times to be unemployed in “tech” in the past decade.
It is indeed a lot of people. A quick search says ABK employed 17,000 people. Laying over over 10% of your workforce is… intense, to say the least. Though, how much of that 1,900 is just from ABK is hard to say, so the percentage could be lower.
You’re right though; HR, payroll, legal, and social media/PR departments would definitely be among the first on the chopping block, depending on how much MS wants to integrate ABK into their existing departments.
In this case, it kills unproductive jobs. Payroll people are necessary but at the end of the day, they don’t produce anything you would want to buy. This means that if you keep more administrative jobds than you need, there will be fewer actuall things to go around. Hence everyone will be poorer on average (or realistically speaking, the rich will be poorer in the current system, but that is a different issue).
Anyway, keeping unproductive jobds to reduce unenployment is a dumb idea and is one of the main reason why communism sucked so much.
I have a better idea. Fire the whole payroll division and hire just one accountant. Since clearly, clearly, any number of payroll employees can sustain any company size, this is the most cost efficient way to go.
Oh you say one staff in payroll is not enough? Oh then I miss your point.
How about you take your strawman argument somewhere else? I never said you need just one. But the company clearly did not need as many, if they were able to let them go. Economy of scale I guess.
Yeah, I’m a bit skeptical that this is just about “downsizing” or eliminating redundant positions after the acquisition. Based on what I’ve seen on Twitter, a lot of junior, middle, and senior level positions were victims of these cuts, across a ton of different departments. Animators, artists, developers, no one was safe. Apparently like the entire Overwatch lore team was cut - you can’t tell me that team has any overlap whatsoever with any existing Microsoft employees.
That gets into the mess of what the reality of “gaming” is. Most people will acknowledge that Call of Duty and… uhm… Halo? Sure, let’s go with that. CoD and Halo compete. They are both games in a similar genre. Same with the hilarity of Horizon Zero Dawn meaning that a critically acclaimed open world game is coming out.
But the reality is that CoD and Fortnite compete with Squid Game and Reacher. Breath of the Wild competes with both Elden Ring AND The World Cup. The resource is increasingly time. When people get home from work they generally aren’t saying “I am going to play three hours of video games and it will either be Battlebit or CoD”. They are saying “I have three hours so maybe I’ll watch an episode or two of Demon Slayer or I could do my dailies in Fifa?”
And, in that regard, Overwatch is an increasingly “failed” live service game with an IP that has lots almost all of its good will. Whereas Halo… Master Chief had a sweet ass? But Overwatch DOES compete with the other big live game that MS acquired alongside them… Call of Duty. And so forth.
Its all a giant mess where labor suffers. But… yeah.
It is worth understanding that this is “different” than… all the other layoffs in tech at this point.
MS acquired ABK. Any acquisition almost always leads to “downsizing”. At a high level: ABK would have had their own payroll department. Now they go through MS payroll. Why do you need an entire department whose job is now superfluous? Obviously this gets a LOT more complex with developers and the like (as well as local management) but that is the mindset.
But… holy fucking shit that is a lot of people getting laid off at one of the worst times to be unemployed in “tech” in the past decade.
It is indeed a lot of people. A quick search says ABK employed 17,000 people. Laying over over 10% of your workforce is… intense, to say the least. Though, how much of that 1,900 is just from ABK is hard to say, so the percentage could be lower.
You’re right though; HR, payroll, legal, and social media/PR departments would definitely be among the first on the chopping block, depending on how much MS wants to integrate ABK into their existing departments.
Finance too. They’re almost always first from the multiple I’ve personally been through. The new owners want those hands out of the pot asap.
Also considering the apparent toxicity of certain Blizzard employees it’s probably a good opportunity to “purge” the Kotic gang and his following.
So that’s a dozen people. 1900 is more than a hundred times that. (#mathFTW)
These cuts will seriously hurt product.
Also, I sense my less-than-new windows version will be unsupported; and I only had it so the one game ran better.
Blizzard Products were polished turds.
They need a huge cultural shift and I’m all for it.
Oh it’s ok since competition is getting killed too. See you soon at the bottom of the barrel.
Hence why acquisitions need more scrutiny. It literally kills jobs.
In this case, it kills unproductive jobs. Payroll people are necessary but at the end of the day, they don’t produce anything you would want to buy. This means that if you keep more administrative jobds than you need, there will be fewer actuall things to go around. Hence everyone will be poorer on average (or realistically speaking, the rich will be poorer in the current system, but that is a different issue).
Anyway, keeping unproductive jobds to reduce unenployment is a dumb idea and is one of the main reason why communism sucked so much.
I have a better idea. Fire the whole payroll division and hire just one accountant. Since clearly, clearly, any number of payroll employees can sustain any company size, this is the most cost efficient way to go.
Oh you say one staff in payroll is not enough? Oh then I miss your point.
How about you take your strawman argument somewhere else? I never said you need just one. But the company clearly did not need as many, if they were able to let them go. Economy of scale I guess.
Yeah, it’s brutal out there right now. Reminds me of 2008 or 2000.
Yeah, I’m a bit skeptical that this is just about “downsizing” or eliminating redundant positions after the acquisition. Based on what I’ve seen on Twitter, a lot of junior, middle, and senior level positions were victims of these cuts, across a ton of different departments. Animators, artists, developers, no one was safe. Apparently like the entire Overwatch lore team was cut - you can’t tell me that team has any overlap whatsoever with any existing Microsoft employees.
That gets into the mess of what the reality of “gaming” is. Most people will acknowledge that Call of Duty and… uhm… Halo? Sure, let’s go with that. CoD and Halo compete. They are both games in a similar genre. Same with the hilarity of Horizon Zero Dawn meaning that a critically acclaimed open world game is coming out.
But the reality is that CoD and Fortnite compete with Squid Game and Reacher. Breath of the Wild competes with both Elden Ring AND The World Cup. The resource is increasingly time. When people get home from work they generally aren’t saying “I am going to play three hours of video games and it will either be Battlebit or CoD”. They are saying “I have three hours so maybe I’ll watch an episode or two of Demon Slayer or I could do my dailies in Fifa?”
And, in that regard, Overwatch is an increasingly “failed” live service game with an IP that has lots almost all of its good will. Whereas Halo… Master Chief had a sweet ass? But Overwatch DOES compete with the other big live game that MS acquired alongside them… Call of Duty. And so forth.
Its all a giant mess where labor suffers. But… yeah.