The evil, destructive, part of stack ranking is when you need to apply the 20%/70%/10% breakdowns to all teams equally, meaning that even a team of 5 people needs to have one and only one "exceeds expectation" person and one person who "needs improvement", regardless of overall team level. It's not clear from this writeup that Amazon and Facebook are applying curves at such a micro level.
My understanding of my group (which may not apply to all parts of Microsoft, of course) is that our 6-person groups are too small to stack rank, so stack ranking rolls up to the next level. So Microsoft doesn't apply stack ranking at such a micro level either.
Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
31–40 of 168 posts
Re: Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
#32So what's a better way to do it? You need a documented system. If you don't have a documented system then there will be an undocumented system which is the same problem with less documentation.
Each employee receives a single unit of value. Let's call it a 'credit.' Each employee then has to distribute all of his 'credit' to other employees. Each employee then gives away any credit received according to the same original distribution. Each employee continues doing so until the credit received and distributed reaches an equilibrium. Each employee is then ranked by the total amount of 'credit' they've accumul…
Re: Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
#33The main reasons I can think of has to do with the dangers of getting comfortable in a large company.
It's very easy for a lazy manager to just hand out "A"s to everyone on the team and just cruise along. Slackers are poisonous, but painful to deal with for a conflict-shy, comfortable manager. Actually being forced to think critically about which of your employees are the top performance, and which aren't (and it's a mathematical fact that they're not going to be the same) is a useful tool to keep such a manager on his toes.
Another effect is simply to encourage a certain rate of churn in all teams, to get some fresh blood flowing through the system.
Stack-ranking directly forces the manager to use his human capacity for critical thinking to evaluate his employees, and in such is a useful distraction from that even more disastrous evaluation method: Objective metrics (hours worked, lines of code committed, bugs closed, sales numbers etc).
Re: Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
#34So what's a better way to do it? You need a documented system. If you don't have a documented system then there will be an undocumented system which is the same problem with less documentation.
How about approaching managers in the same way we always like companies to approach developers, i.e., hire good ones and empower them do their job in the best way they know how? Using a system that is enforced from the top down is a perfect way to guarantee you'll only get the kind of below mediocre managers we love to bitch about. All of these systems are based on the assumption that companies can't trust the people…
Re: Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
#35The evil, destructive, part of stack ranking is when you need to apply the 20%/70%/10% breakdowns to all teams equally, meaning that even a team of 5 people needs to have one and only one "exceeds expectation" person and one person who "needs improvement", regardless of overall team level. It's not clear from this writeup that Amazon and Facebook are applying curves at such a micro level.
Stack ranking at Microsoft has a min populaton size (x) - you generally walk up the org chart until the number of employees >= x, and then apply stack ranking to that group.
Re: Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
#36Re: Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
#37Earlier quoted context omitted.
Each employee receives a single unit of value. Let's call it a 'credit.' Each employee then has to distribute all of his 'credit' to other employees. Each employee then gives away any credit received according to the same original distribution. Each employee continues doing so until the credit received and distributed reaches an equilibrium. Each employee is then ranked by the total amount of 'credit' they've accumul…
Presumably this leads to people passes their credit to the worst candidate, in an effort to stop the good candidates from surpassing their own score.
In this model there's no reason to believe the worst candidate isn't passing his credit to employees just about to surpass you, which would defeat the purpose.
Re: Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
#38Re: Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
#39So what's a better way to do it? You need a documented system. If you don't have a documented system then there will be an undocumented system which is the same problem with less documentation.
Each employee receives a single unit of value. Let's call it a 'credit.' Each employee then has to distribute all of his 'credit' to other employees. Each employee then gives away any credit received according to the same original distribution. Each employee continues doing so until the credit received and distributed reaches an equilibrium. Each employee is then ranked by the total amount of 'credit' they've accumul…
It's useful, but no replacement for performance reviews.
Re: Why are Amazon, Facebook and Yahoo copying Microsoft's stack ranking system?
#40So what's a better way to do it? You need a documented system. If you don't have a documented system then there will be an undocumented system which is the same problem with less documentation.
A peer review-driven process. Productivity lost to that can't possibly be worse then the culture of backstabbing that stackrank promotes. For another point, the article seems to be making a heavy statistical error in assuming that Google's average developer lifespan is 1 year. Taking the average lifespan biases the result heavily towards new hires (Of which there are a lot of). A more relevant metric would be average…