People say stack ranking is bad within Microsoft because you're not ranked against all 50k+ employees but against 10+ people that report to the same manager.
If 2 out of 10 people are guaranteed low ranking, then it's better to be a mediocre programmer in a team of poor programmers than to be a very good programmer in a team of even better programmers.
It also means that it makes sense to sabotage the performance of your 9 colleagues because you only care about looking better than them, not about doing best possible job for the company or your team.
A global stack ranking, if it was actually possible, would be great. You do want to get rid of low performers (and hire better replacements) and in a large enough pool the bottom 20% will really be worth replacing with better people.
This is really wrong, to get rid of the 20% low performers, you install a system that destroy everyone's confidence and promote short term decision making.
In the end, you get rid of 20% of people that just don't play the game AND you decrease the overall performance the group of people.
I remember reading a good article showing how rewards affect people performance by changing their goal, but I can't find it. Anyone?
Disclosure: I recently started in a full time position at Microsoft.
But how do you implement a global stack ranking in such a diverse company like Microsoft? There is no good criteria for comparing the kernel developers to the frontend programmers, for example. I doubt you could even find 100 employees working on the same kind of task.
One of the pleasures of teaching is working in a (loosely coupled) team of good teachers with complementary strengths and weaknesses. Teachers are 'loosely coupled' because they spend most of their time with students rather than other teachers or managers, but being able to compare notes, get support and give support is really important to the role.
http://www.dailykos.com/story/2012/07/05/1106417/-Gates-s-Ca...
Here's the Gates quote the whole article is built around. You can judge for yourself how much it reflects a desire for a "Cannibalistic Culture" or its general merit as an approach to education reform:
"What should policymakers do? One approach is to get more students in front of top teachers by identifying the top 25 percent of teachers and asking them to take on four or five more students. Part of the savings could then be used to give the top teachers a raise. (In a 2008 survey funded by the Gates Foundation, 83 percent of teachers said they would be happy to teach more students for more pay.) The rest of the savings could go toward improving teacher support and evaluation systems, to help more teachers become great."
Because intrinsic pleasures of the job are more important to you than your compensation package, you initially find dealing with "lousy coworkers" demotivating. But you endeavour to make the best of a bad situation by finding out how to help your coworkers become better at their jobs. You end up developing a far deeper satisfaction in your work than you'd previously thought possible.
Did I guess right?
In essence, it works as you describe: rather than trying to make managers give ratings using an arbitrary metric they don't understand (which can be avoided with behaviorally-anchored rating scales, but most companies don't spend the effort to create them), you basically ask them to decide whether they're in the club or not.
There is a bit more to it than that, such as training for and having managers justify their ratings, but it's simplicity is the draw.
I'd agree that's an important aspect, even a very important aspect, but hardly all that matters.
I could work with 10 of the nicest people on the planet, but if we all like each other & don't accomplish anything, is that really, well, good for the company?
Then again, that does explain most board of directors.
And if you take it after the projects done then you must have done something so the hypothetical isn't relevant there.
He made a point about whether you'd work with a team again, and how this is all that matters.
You made a point about whether it'd be good for the company for you to work with people you think are nice and can hang out with.
That's not at all the same thing. You're not countering what he said. He's talking about actually working and getting things done, and how productive your team is as a functional unit. You're talking about how much you like your team.
It's implicit in "would I work with this team again" that you'd be trying to work with the team and not just hang out for a beer or five.
Some of the best people I've worked with, and people I'd work with again, are people I don't personally like. But if they're productive and we have good professional chemistry, I don't need them to think Aaron Rodgers is the best quaterback to work with me.
The takeaway is this: you can work with a team and be extremely productive together, but you don't have to desire working with them again because they're nice or you like them. You should desire to work with them again because they're awesome and complement you well professionally.
Compliments the notions of Self Selecting Teams [1] and Roman Evaluation Interview Method [2].
[1] http://orgpatterns.wikispaces.com/SelfSelectingTeam
[2] Anything less than unanimous Yes is a No. h/t Luke Hohmann http://innovationgames.com/about/team/luke-hohmann/
I think everyone should say, at the end of a project, yes/no for wanting to work with other people. It's fine to not want to work with someone else, and that person doesn't feel discipline, unless a lot of people start refusing to work with him.
Everyone in life has disagreements, petty jealousies, things they struggle with in other people. The beauty of the question, Would you work with her or him again?, is that it specifically doesn't try to disentangle those things––because to a productive team the quality its members' relationships with each other as important as the quality of their work. If one or the other is off, it's not necessarily anyone's fault, and it may not even be cause for termination. But it's as good a metric as you need.
But it's utterly foolish to winnow on a percentage basis. You'll break up good teams and prevent better ones from forming. You'll destroy morale. You'll encourage a leadership culture of cutthroat sociopaths whose success is at best tangentially related to the quality of their work. Do not do it.