News for hackers. Stuff that matters.
Re:Blizzard Lays Off 600, Including About 60 Developers by ars on Wednesday February 29, 2012 @04:35PM (#3649813)
Why do it in one shot like this? Why not lay people off incrementally?
Re:Blizzard Lays Off 600, Including About 60 Developers by efsavage on Wednesday February 29, 2012 @05:40PM (#3650069)
"For injuries ought to be done all at one time, so that, being tasted less, they offend less; benefits ought to be given little by little, so that the flavour of them may last longer."

http://www.constitution.org/mac/prince08.htm

Re:Blizzard Lays Off 600, Including About 60 Developers by CptCodeMonkey on Wednesday February 29, 2012 @04:48PM (#3649871)
I've been in a situation where the company was laying people off incrementally over the span of 18 months. I hated going to work, didn't give a shit about the company, and I was not unique or alone in that opinion. If you have to lay people off, do it as quickly and with as much dignity as possible.
Re:Blizzard Lays Off 600, Including About 60 Developers by downwithmycrew on Wednesday February 29, 2012 @04:53PM (#3649890)
sounds like a big IT company
Re:Blizzard Lays Off 600, Including About 60 Developers by weaksauce on Wednesday February 29, 2012 @04:49PM (#3649875)
Morale wise it's probably better to do it in one large chunk instead of smaller servings where people are wondering if they are going to get cut in the next round.
Re:Blizzard Lays Off 600, Including About 60 Developers by talmand on Wednesday February 29, 2012 @05:51PM (#3650120)
But how would you know the one large chunk will be the only one? Layoffs are bad for morale regardless of how it is handled. I've been through both sides of a layoff and it wasn't fun either way.
Re:Blizzard Lays Off 600, Including About 60 Developers by gwern on Wednesday February 29, 2012 @06:28PM (#3650252)
> But how would you know the one large chunk will be the only one?

You can at a minimum guess from the size. Take for example this cut - roughly cutting 600 from 6-7000 means cutting 10%. Unless Blizzard is seriously inefficient, another such cut of 10+% would start doing major damage to operations. Hence, you know there probably won't be such a cut.

Re:Blizzard Lays Off 600, Including About 60 Developers by Devilboy on Wednesday February 29, 2012 @08:32PM (#3650568)
Layoffs are bad for morale either way, but one big round is much better morale-wise than 20 small rounds.
Re:Blizzard Lays Off 600, Including About 60 Developers by digitalchaos on Thursday March 01, 2012 @12:21AM (#3651033)
A big reason is that it's much easier to do from a legal perspective. Letting go of low performing people in a layoff is way easier than going through all the hoops of giving them warnings, putting them on probation, etc.

Also, a slow trickle of firings is just horrible for everyone. You have no idea if you are next, etc. A big layoff followed by a company meeting of "hey, we did a layoff because of X. There will be no additional layoffs as long as we hit our current goals."