"Incidentally, not all systemic changes work. I’ve also learned that certain management techniques can actually make things worse when applied to a distressed culture. For example, I had always worked in companies with yearly and quarterly employee ranking systems, in which people were divided into three groups: overperforming, performing, and underperforming. So not long after I came here, we started a ranking program that graded on a curve: 45% into the overperforming group, 50% into the performing group, and 5% into the underperforming group. I didn’t know—and certainly didn’t intend it this way—that if you got the lowest grade, it was presumed that you were about to be fired. We started getting hate mail from people who argued that there was no way to rank people who worked as a team. The ranking system exacerbated the culture of fear and proved to be such a huge retention and motivation issue that we were forced to stop it after a year. In its place, we introduced a modified ranking program that better reflected overall employee performance."
Also, what you say about a sufficiently large group never happens. What actually happens is each lower level manager is forced to rank his or her team members along the curve so as to make the process "fair". And inevitably, this gives rise to a large host of harmful behaviors - slacking off on work by people who have low self esteem as they will get ranked low "anyways", grandstanding, people trying to take credit for others work, infighting, corporate politics, people waking up and starting to work hard closer to the appraisal cycle to capitalize on the "recency effect", dysfunctional teams that deliver only because of heroic efforts from a couple of the team members.
Any system can be gamed this one has got gamed out long ago, my experience - I have seen it do nothing but harm in every single case.
The other factor would be that there's an idea (which I can't speak to personally) that the only purpose of performance evaluations is to protect the company in case a fired employee sues to reinstate their job, which would mean that an "underperforming" grade was a necessary prereq to firing.
On a scale of 1-5, I felt all three of them were 4.5, but I couldn't submit scores like that because of stack ranking. The question then became whether to piss off one of the veterans or to discourage the rookie by giving a < 4 score.
So after about 3-4 months of working at Microsoft, I was ranked in the bottom 10% (the bucket for people who don't have good prospects for furthering their career at Microsoft.) This was back when they used a 10/70/20 system.
Now, don't get me wrong, I don't think I'm some master developer that deserves to always be in the top 20%. I strive to be above average, but I consider myself to be merely average, especially compared to many of the exceptionally bright people working there.
Here's the real bitch. The reason I was given for this rating had nothing to do with my performance. I shit you not, and this is as verbatim as I remember it: "Somebody has to be in the bottom bucket and since you're new, I can't rank you higher."
The problem is that this stuff fucks with your career there. It's a black mark on your record that follows you around. HR assured me that someone being new is not a valid reason to rank someone like that, you have to base it on actual performance.
An easy fix that my previous company had employed: have a "too new to rate" category.
In retrospect, I just had a shitty boss, and it wasn't necessarily reflective of Microsoft as a whole. I also should have challenged it more vigorously, but I didn't want to create animosity between my boss and myself seeing as I was barred from transferring for.. 18 months was it?
I'm not too bitter about it though; I ultimately ended up resigning after a year and then coming back to work for the same department as a contractor at a much higher salary. As such, I no longer had to participate in performance reviews at all.
The minimum performance required to avoid termination.
While that might have worked out OK for you. It's a beautiful example of this kind of dysfunction.
any sort of 'objective' evaluation of employees is prone to being gamed and any gaming of evaluation is actively harmful to corporate culture/performance. witness google where lower profile or troubled projects are abandoned en masse by any employees with the ability to turn them around
Or I may drop the person who I can get rid of with the least hassle, maybe the new guy who just joined the team or someone who has taken long leave during this period.
See how it works? Nothing to do with performance, and inevitably its the "A" performers who quit in disgust. And companies wonder why they cannot get talent to stay...
But really? Is that why Microsoft has fallen by the wayside (realtively)? Because they don't have good enough engineers?
I disagree. I think they have a wealth of talented engineers.
What they need(ed) are people with vision, a deep understanding of the future of consumer electronics and computing, and a way to execute on that vision. They need to deliver short, medium and long-term products that feed their vision. They need to show people the future of the industry instead of lagging behind it.
Engineering is a crucial component in that, but it's only part of the story IMHO.
Vision doesn't happen in a vacuum. It happens within the wider cultural context of the organisation. A technical lead, a project lead, a manager - they are all affected by the environment they are in. If you spend all your time fighting politics and trying to shore up demoralised engineers, you are not going to waste your time dreaming about ponies and rainbows.
If you want an analogy, you can take the world's greatest general, but if you drop him in a WW-I trench, he is just cannon fodder.
I think that's a fair point. Good reply.
The article started with stack ranking, but clearly there were much bigger issues looming.
>“He didn’t like the user interface, because it didn’t look like Windows,” a programmer involved in the project recalls... “Windows was the god—everything had to work with Windows,” Stone tells Eichenwald. “Ideas about mobile computing with a user experience that was cleaner than with a P.C. were deemed unimportant by a few powerful people in that division, and they managed to kill the effort.”
They could have been years ahead on phones, tablets, and e-readers. But instead they had a culture that tried to shoehorn a standard Windows experience into every device (I imagine for marketing reasons). They are only now getting over it a decade later, though it's probably more accurate to say they have the same philosophy but in reverse: shoehorn a mobile experience into the desktop in Windows 8.
What difference does it make if you have the greatest engineers in the world but management is blocking them at every turn?
I actually laughed out loud when I read that--it's true!
That statement is false in many ways. As a developer, you keep seeing substandard products from Microsoft. Have you looked at the architecture of SharePoint? compare SqlServer CE to SQLite, not to mention the horrible tutorials and source code which Microsoft keeps putting out.
C#/.NET is an excellent platform/language but Microsoft keeps putting out horrible sub standard code/tutorials
My impression of Microsoft (entirely from the outside) is that they have this same problem.
Engineers always think that companies are engineering driven, when in fact mostly they are sales driven. If SharePoint sells well, then its not substandard, even if you don't like its architecture.
Because someone always ends up on the bottom, a fair number of devs don't want to end up on who already has a top quality dev. Worse yet, in order to keep good people, managers don't want / will promise not to bring in more good people. Thus there is an active incentive to recruit( at least internally) mediocre talent since a team needs to hire people to keep headcount and needs to pad the middle of it's stack ranking.
Yeah, in theory this shouldn't happen because the rankings for each team are merge and those on the bottom of a good team should come in above the bottom of a bad team. In practice that seems not to work because both ICs and managers seem to have the above philosophy.
Would the second practice, given sensible and negotiated targets work better?
To begin with, it didn't work the way described in the article (does Microsoft's system actually work that way? if so -- ugh). There were five bands, and the "you get fired" band didn't generally get anyone assigned to it. Furthermore, the percentages in each band were somewhat flexible and applied across the organization, not to any one group of people. It was quite possible for an effective team to all be band 1 and 2. (But then, AC didn't really have fixed teams.)
Of the four non "you're fired" bands, 1 was excellent, 2 good, 3 adequate, 4 was improve or leave. (I don't think we were even required to assign any band 4s.)
But a consulting company is very different from a product company. A consulting company actually WANTS a large proportion of its workforce to leave within a certain time because ultimately it's a pyramid scheme. Only 10% of people who join get to associate partner (or whatever) level and you need to advance at a certain rate or you'll be ticked off, so you need to shed 90% of people before they've lasted X years or you're screwed.
A product company needs people with deep technical skills to hang around. It's one thing to use "up or out" to drive your sales force (and the upper echelons of a consulting company are salesmen) and quite another to do this to your deep technical people.
So it's a misapplication of a management theory and not an intrinsically bad management theory.
However, in terms of how it actually worked, I was also involved in meetings to allocate people to bands, and the percentages had to be respected across the client group (UBS, in that case).
This means that if there were, say, 10 analysts in the UBS client account, then only a couple could get "Exceptional" (or whatever it was called), and so on...
The implication of this was that your performance (and therefore pay raise, promotion, and so on) largely depended on whether:
a) you had made a strong enough impression on your manager so that he/she would be motivated to do a decent job of fighting for you in the meeting;
b) your manager was actually politically competent enough, and had the political capital to spend on getting you a good rating;
c) you had made enough of an impression on all the other people likely to be at the meeting so that they'd know about it and accept it when your manager suggested that you should be rated Exceptional.
If you hit all three of those, you might get a great rating. If you didn't bother to network with everyone who was likely to be at the meeting, or if your manager sucked or didn't like you all that much, you were pretty much fucked.
The problem with Microsoft -- assuming we're talking about an accurate representation of their system -- is that the reward structure rewards visibility rather than results, but the organization actually wants results.
The problem is with what the viable alternative is for companies that are huge like this. It's just tough. Maybe we all just need to stop worrying about how other humans measure our performance/value.
Definitely don't "stop worrying about it" - or you'll get screwed.
I wonder if stack ranking is the same but for getting bad people to leave? Even a weak employee can be better than no employee for a manager...
http://minimsft.blogspot.com/2004/07/microsoft-stack-rank-as...
(b) As I understood it, it is only used to determine comp adjustments
If you go into it with the view "We're all excellent people, and these people are the best of an excellent bunch, so they're getting the biggest raises this year", it seems like a reasonable system.
But when the company is mature, and the stock is flat, and the headcount is under pressure...
I'm trying to say this is a hard problem, and picking on the downsides of "stack ranking" is easy if you don't consider alternatives.
Granted, successful does not necessarily imply they are innovative. This management strategy may be more effective in more sedate and established industries where adhering to best practices may be more important than charting new courses.
If anything, this would seem to be a cautionary tale to tech startups that may be tempted to hastily implement traditional MBA'esque management styles. One size certainly does not fit all.
Basically there are 3 "bands" in the Welch system (with the lowest band being 10%). You reward the top band (20%) heavily, the middle band (70%) modestly, and dump the bottom band (10%) every year.
In some ways, the intent is similar to the economic class system (incentivize the middle class to become the upper class).
GE had a lot of success when they adopted that model, although obviously, they did a lot of other things as well which may have been a more direct effect (getting rid of a lot of businesses they were in, for example).
I can appreciate the ideal of constantly cutting out the bottom-performing resources, provided that the mechanism to track performance is sufficiently quantifiable (and accurate). I haven't heard enough from people at GE as to whether or not that is the case there, though.
‡ http://en.wikipedia.org/wiki/Vitality_curve#Straight_from_th...
This is the most important sentence in the article. Because many companies over the years - a lot of them start ups - would point to this practice by Microsoft and try to follow their lead. Microsoft has been stack ranking almost since conception. It was always a horrible way to run a company. But it took decades for it to actually bring the company down.