3 ms·
There is nothing inherently poisonous about doing company-wide ranking (though it is infeasible to do precisely since objective measures of "goodness" are non-e
by aidenn0 13y ago
There is nothing inherently poisonous about doing company-wide ranking (though it is infeasible to do precisely since objective measures of "goodness" are non-existent and you can't do subjective ranking of everyone in all but the smallest environments; whether or not good-enough approximations exist is debatable).
However, doing it on a per-team basis is stupid. It guarantees that some teams will have bottom-performers, since a team without bottom-performers will fire or scare away the lowest in the team. Furthermore you incentivize sabotaging your teammates and--even if nobody does it--that makes everyone suspicious of their teammates.
If there were a magical wand I could wave to nearly perfectly rank all the employees at a company I were running, I would do it and base compensation off of it. Doing so on a per-team basis is stupid.
- keithnoizu 13y agoYou still run into problems if you do an org wise stack rank and manager popularity and pull is going to impact which groups are magically determined to have only top performers. A better approach really I think is to just do 360s and if there are clear problems with key employees that are holding back other employees let them go. If you have everyone working on complex code and are pushing for excellence over time it will become clear who is making the grade and who isn't. Even if some of the employees that work well on the team could be replaced by other slightly more efficient or intelligent employees the benefit of doing so is greatly offset by ramp up and recruiting time that takes away from team productivity.
- einhverfr 13y agoBut to do that you need to be able to trust managers to make competent hiring and firing decisions. I have watched firing decisions happen at Microsoft, as well as been hired. I can tell you that managers are definitely not trusted to make these decisions or at least weren't when I was there. So once you establish that you don't trust managers, you pick managers who excel at politics rather than anything else and the problem continues.
- keithnoizu 13y agoWell I think that is a major underlying reason for why they used the forced curve. It's a problem. I can't say I have an answer for avoiding it other than flattening the business hierarchy and taking the first step of trusting managers to make those decisions.
- einhverfr 13y agoIf you aren't trusting your managers to make these decisions, why do you have managers in the first place? Those are two things that Microsoft needs to do, namely use IT to replace depth in business hierarchy, and to empower team managers to make these decisions.
- derefr 13y agoManagers do the dirty glue-work that allows their teams to get things done. Managers interface with other business units, again, to allow their teams to get things done. Managers pull together a clear picture of what everyone else is doing so that they can see when something isn't being done--so that they can communicate that back to the team, so it can, once again, get stuff done. See most of the stuff Rands has written on the topic of management (http://www.randsinrepose.com/ http://www.randsinrepose.com/). Basically, a manager is a glorified secretary who works for everyone in the team at once. The equivalent in sports is the coach. Management is, however, not the command-and-control backbone of your company. That's leadership, and that's an orthogonal role. Management is about oiling teams to run better; while leadership is about taking responsibility for, and ownership of a team's output. Leaders, of course, want their teams to be managed, because it makes them work better--and if nobody else will do it, they can do it themselves. But, importantly, the leader role works better when held by a member of the team--someone doing the work, down in the trenches--while the manager role works better on someone who doesn't have any other responsibilities (since it's a full-time job in and of itself.) Leaders who are also managers become out-of-touch in their leadership, because the job of management deprives them of access to the distributed knowledge they need to make leadership decisions (the kind they'd just pick up naturally by doing the job alongside the team.) Ideally, leaders are just members of teams held in high regard by their peers, who just end up taking ownership of the team's project by default. In contrast, ideally managers are free-floating socialites, working with several teams and ensuring that everyone has everything they need (including introductions to people outside their team they might not know they need!) You'll notice that there's nowhere in this list of requirements for a "boss" who tells you to "get to work." This is because, if your team lead actually has your respect--and if that lead actually cares about the project--then you don't want to disappoint them by giving them any less than your best. And if either of those two things aren't true, then you probably need to rebuild the team, or scrap the project.
- jcheng 13y agoIt doesn't happen on a per-team basis, at least the curve isn't strictly enforced at that level. That really would be insane. As you go up and up the org chart to bigger and bigger collection sizes, the curve is more strictly enforced. (At least according to the 2 stack ranking reviews I took part in before I left.)