Microsoft Ditches the Stack Ranking System. Yahoo! Lays off 600 because of It
Yahoo! has recently laid off about 600 employees based on a ranking system introduced last year, while Microsoft is ditching their system to relieve some of the pressure from their staff.
Under its new CEO Marissa Mayer, Yahoo! introduced last year an employee evaluation system resulting in the layoff of some 600 people during the last several weeks, according to AllThingsD. Not only that, but the system has upset many inside Yahoo! including managers who are forced to label certain team members as underperformers in order comply with the bell-curve-based evaluation system:
I was forced to give an employee an occasionally misses, was very uncomfortable with it. Now, I have to have a discussion about it when I have my QPR meetings. I feel so uncomfortable because in order to meet the bell curve, I have to tell the employee that they missed when I truly don’t believe it to be the case. I understand we want to weed out mishires/people not meeting their goals, but this practice is concerning. I don’t want to lose the person mentally. How do we justify?
Using an internal anonymous message board, one Yahoo! employee argued that the ranking system should be applied to managers also:
Will the ‘occasionally misses’ classification apply to L2 and L3 execs also? At every goals meeting, we find senior staff who missed even the 70% goals. Thus, by definition, they should be classified as ‘occasionally misses.’ Two such classifications, and that person should be let go, amiright? How about we set an example for the rest of the company and can a few of the top execs who miss (or who sandbag their goals to make sure they ‘meet’)?
In the meantime, Microsoft’s departing CEO Steve Ballmer has decided to eliminate the stack ranking system used for many years, a system considered by many inside and outside the company as Microsoft’s most destructive process:
The Verge: Vanity Fair contributing editor Kurt Eichenwald blamed a combination of Microsoft’s obsessive focus on Windows and Office and the company’s internal stack ranking-system for a "lost decade" and cannibalistic culture. Eichenwald interviewed a number of current and former Microsoft employees who all cited stack ranking as the most destructive process inside the software giant.
Bloomberg Businessweek: David Auerbach, a former Microsoft employee, recently told Bloomberg Businessweek that the practice had employees feeling helpless and “encouraged people to backstab their co-workers.”
Forbes: Stack Ranking – forcing managers to rank their employees and get rid of the bottom ones — is a horrible idea that Microsoft’s Steve Ballmer imported from GE. As I wrote in July 2012, stack ranking at Microsoft was a mess.
The Wall Street Journal: The rankings were a key factor in promotions and in allocating bonuses and equity awards under Chief Executive Steve Ballmer, who in August said he plans to retire within a year. But many current and former Microsoft employees complained the system resulted in capricious rankings, power struggles among managers, and unhealthy competition among colleagues.
According to an internal memo sent to the employees by Microsoft HR Chief Lisa Brummel, there will be “No more curve”, “No more ratings”, the emphasis being on employee growth and team collaboration in the future:
- More emphasis on teamwork and collaboration. We’re getting more specific about how we think about successful performance and are focusing on three elements – not just the work you do on your own, but also how you leverage input and ideas from others, and what you contribute to others’ success – and how they add up to greater business impact.
- More emphasis on employee growth and development. Through a process called “Connects” we are optimizing for more timely feedback and meaningful discussions to help employees learn in the moment, grow and drive great results. These will be timed based on the rhythm of each part of our business, introducing more flexibility in how and when we discuss performance and development rather than following one timeline for the whole company. Our business cycles have accelerated and our teams operate on different schedules, and the new approach will accommodate that.
The bell-curve ranking system was popularized by GE Chief Executive Jack Welch back in the 1980s being used by many companies, but some of them have dropped it in the last years, including Adobe and Expedia. The main idea of the system is that a company’s employees performance follows a bell-curve, having a small percentage of high performers, a large number of average performers and, at the lower end, another small percentage of underperformers. The system would be used to find and get rid of underperformers in order to improve the overall performance of the workforce and resulting in a smaller standard deviation which corresponds to a more homogeneous company, as show in the following chart (from Punishing by Rewards: When the Performance Bell-curve Stops Working For You - PDF):
But several studies performed in the last years indicate that the bell-curve ranking system has a number of flaws. The Best and the Rest: Revisiting the Norm of Normality of Individual Performance (PDF) indicates that instead of a Gaussian distribution the picture of performance if better represented by a Paretian distribution, as shown in the following chart:
According to this research, the majority of workers are underperformers (left) with a few of them being high performers (right). The recommendation of the research is not to keep the top performers and lay off the rest, but to “selectively source superstars for key positions where they will make the most impact to the bottom line.”
Another study, Punishing by Rewards: When the Performance Bell-curve Stops Working For You – PDF, outlined a series of other problems with the bell-curve ranking system including the pressure put on employees when the system is applied:
We observe that pressure, if maintained below a certain level, can lead to higher performance. However, as the lay-offs take place, constant pressure demoralizes employees, leading to drop in performance. As the bottom performers depart, the rigid distribution of the bell-curve forces managers to categorize a high performer (when compared to the rest of the labor market) as a mediocre. A high performer, unmotivated by such artificial demotion, behaves like a mediocre. Further, in a shrinking company, managers find it difficult to differentiate employees. As a result, they begin to reward visible performance over the actual. Beyond a certain point, the erosion of social capital has the potential to cripple the company.
The recommendations of this study are to maintain a balance between pressure and morale, and to decouple performance evaluation from lay-offs:
We recommend the use of a semi-bell-curve that does not follow the rigid percentage distribution, and where someone who performers like a top performer is rewarded as one. Further, we recommend balancing pressure and morale. We recognize that this balance is very difficult to strike, especially in a company that is constantly shrinking. The only way we see of keeping the pressure at the optimum level and the morale high in such an organization
is to decouple to some extent the performance evaluation process from the issue of lay-offs.
attracting new talent to ms?
That's the problem with arbitrary processes
The opinions and views expressed in this post are my own, and do not necessarily reflect the opinions or views of my employer.
Shane Hastie on Distributed Agile Teams, Product Ownership and the Agile Manifesto Translation Program
Shane Hastie Apr 17, 2015