Vitality curve

From Infogalactic: the planetary knowledge core
(Redirected from Stack ranking)
Jump to: navigation, search

A vitality curve is a leadership construct whereby a workforce is graded in accordance with the individual productivity of its members. It is also known as forced ranking, forced distribution, rank and yank, quota-based differentiation, and stack ranking.

For example, there is an often cited "80-20 rule" — also known as the "Pareto principle" or the "Law of the Vital Few" — whereby 80% of crimes are committed by 20% of criminals, or 80% of useful research results are produced by 20% of the academics, and so forth. In some cases such "80-20" tendencies do emerge, and a Pareto distribution curve is a fuller representation.

According to a 2013 survey by WorldatWork, the method is used by about 12% of US corporations.[1] According to The Corporate Executive Board Company, it is used by 29% of companies.[2][3] According to Dick Grote, a consultant who specializes on the topic, 60% of the Fortune 500 companies used some form of ranking in 2012.[4] According to a statement by CEB Inc., quoted by Washington Post of July 2015, 6% of Fortune 500 companies have stopped using rankings.[5]

Rank-based employment evaluation

Jack Welch's vitality model has been described as a "20-70-10" system. The "top 20" percent of the workforce is most productive, and 70% (the "vital 70") work adequately. The other 10% ("bottom 10") are nonproducers and should be fired.[6][7] Rank-and-yank advocates credit Welch's rank-and-yank system with a 28-fold increase in earnings (and a 5-fold increase in revenue) at GE between 1981 and 2001.[citation needed]

Straight from the Gut

In Straight from the Gut, Welch says that he asked "each of the GE's businesses to rank all of their top executives". Specifically (in accordance with the 20-70-10 model) the top executives were divided into "A", "B", and "C" players. Welch admitted that the judgments were "not always precise".

"A" players

"A" players, Welch claimed, are

  • filled with passion
  • committed to "making things happen"
  • open to ideas from anywhere
  • and blessed with lots of "runway" ahead of them,
  • have charisma, the ability to energize themselves and others,
  • can make business productive and enjoyable at the same time.
  • and exhibit the "four E's" of leadership:
    • very high Energy levels
    • can Energize others around common goals
    • the "Edge" to make difficult decisions,
    • the ability to consistently Execute, or deliver on their promises

"B" players

The vital "B" players may not be visionary or the most driven, but are "vital" because they make up the majority of the group.

"C" players

"C" players are nonproducers. They are likely to "enervate" rather than "energize", according to Serge Hovnanian's model. Procrastination is a common trait of "C" players, as well as failure to deliver on promises.

Consequences

Welch advises firing "C" players, while encouraging "A" players with rewards such as promotions, bonuses, and stock options. However, if such rewards become a meaningful portion of “A” player's overall compensation, it can lead to perverse incentives. This is especially true when the rewards of being an “A” player are predictable and recurring (such as a normal part of the annual review process). When broad based stock compensation is the norm, as in high-tech,[8] avoiding perverse incentives can be difficult.

Turning promotions into pay cuts

When the rewards given to "A" players are significant, accepting a promotion has added risk. For example, consider an employee who is “A” rated at a their current job level. When promoted to the next level, they continue to perform at their exemplary level. But due to higher expectations, the employee may become “B” rated. If the performance based rewards prior to promotion exceed the raise accompanying the promotion, the promotion is an overall reduction in compensation. This creates an incentive for the employee to refuse promotions.

Encouraging sabotage

The vitality curve creates incentive for employees involved in hiring of peers to avoid the best candidates. The personal impact of adding excellent coworkers is more competition at the “A” end of the curve. It is in the individual's personal interest to seek out candidates skilled enough to retain their job, but not skilled enough to excel. This helps to fill the quota of “C” rankings, and makes themselves rank better. This incentive grows over time as sub-par talent is removed, since it becomes increasingly difficult for good employees to obtain good ratings. Simply “working harder” is an unreliable strategy for obtaining good ratings if everyone is doing it.

Criticisms

The model assumes that the players do not change their rating. In practice even the fear of being selected as a "C" player may result in an employee working harder, reducing the number of "C" players.

Some critics believe that the 20-70-10 model fails to reflect actual human behavior.[9][10] Among randomly selected people assigned to a task, such a model may be accurate. They contend, however, that at each iteration, the average quality of employees will increase, making for more "A" players and fewer "C" players. Eventually, the "C" players comprise less than 10% of the workforce.

The style may make it more difficult for employees to cross rate from one division to another. For example, a "C" employee in a company's Customer Service division would be at a disadvantage applying for a job in Marketing, even though he or she may have talents consistent with an "A" rating in the other division.

This is a competitive model of organization. The criticisms of both the morality and actual effectiveness of such a dog-eat-dog method of social cohesion apply. Challenges to the model include: "C" player selection methods; the effect of office politics and lowered morale on productivity, communication, interoffice relations; and cheating. Rank-based performance evaluations (in education and employment) are said to foster cut-throat and unethical behavior.[11] University of Virginia business professor Bruner wrote: As Enron internally realized it was entering troubled times, rank-and-yank turned into a more political and crony-based system.[12] Forced ranking systems are said to undermine employee morale by creating a zero-sum game that discourages cooperation and teamwork.[13]

Rank-and-yank contrasts with the management philosophies of W. Edwards Deming, whose broad influence in Japan has been credited with Japan's world leadership in many industries, particularly the automotive industry. "Evaluation by performance, merit rating, or annual review of performance" is listed among Deming's Seven Deadly Diseases. It may be said that rank-and-yank puts success or failure of the organization on the shoulders of the individual worker. Deming stresses the need to understand organizational performance as fundamentally a function of the corporate systems and processes created by management in which workers find themselves embedded. He sees so-called merit-based evaluation as misguided and destructive.

According to Ryan Smith, the CEO of Qualtrics, stack-ranking (or similar systems) are suitable for ranking sales personnel among whom the management wishes to foster a spirit of competition, but less suitable for engineers, among whom management may want to encourage closer collaboration.[14]

According to a 2006 MIT study cited by Bloomberg Businessweek, forced ranking can be particularly detrimental for company undergoing layoffs: “As the company shrinks, the rigid distribution of the bell curve forces managers to label a high performer as a mediocre. A high performer, unmotivated by such artificial demotion, behaves like a mediocre.”[15]

MIT Research Fellow Michael Schrage has argued that the forced ranking policy has perverse effects even in organizations that are successful: "Organizations intent on rigorous self-improvement and its measurement inevitably confront an evaluation paradox: The more successful they are in developing excellent employees, the more trivial and inconsequential the reasons become for rewarding one over the other. Perversely, truly effective objective employee-evaluation criteria ultimately lead to personnel decisions that are fundamentally rooted in arbitrary and subjective criteria. [...] The coup de grace occurs when the top employees are all told that they must collaborate better with one another even as they compete in this rigged game of managerial musical chairs."[16]

Rob Enderle has argued that "No sane person could sustain the argument for forced ranking once it's applied it to products instead of people. Apply it to automobiles and make 20 percent or even 10 percent of any run unsatisfactory by policy, regardless of actual quality, and you'd immediately see that you were institutionalizing bad quality. With people, though, folks remain blind to the fact that forced ranking is walking example of confirmation bias."[17]

Jeffrey Pfeffer and Robert I. Sutton have criticized the practice on the grounds that there is limited empirical evidence of its overall usefulness to organizations.[18]

Dr Travis Bradberry (co-author of the #1 bestselling book Emotional Intelligence and co-founder of TalentSmart) notes that "Some individual talents follow a natural bell-shaped curve, but job performance does not. When you force employees to fit into a pre-determined ranking system, you do three things: 1) incorrectly evaluate people’s performance, 2) make everyone feel like a number, and 3) create insecurity and dissatisfaction when performing employees fear that they’ll be fired due to the forced system. This is yet another example of a lazy policy that avoids the hard and necessary work of evaluating each individual objectively, based on his or her merits."[19]

Companies utilizing this management philosophy

Enron

Enron traders also commonly were under the threat of being fired if they did not produce the desired results. Though the accounting scandals are most credited with the demise of the company, it has later come out that part of the downfall was attributed to employees inflating results in part to help protect their jobs. More about this can be seen in the movie Enron: The Smartest Guys in the Room.

Motorola

Motorola instituted a Vitality Curve plan in the mid-90's under the name IDE (Individual Dignity Entitlement). First six, then nine metrics questions were used to rank employees' perception at the corporation. In 2000-2002, the plan was changed to the PM (Performance Management) program, which was a direct 10-80-10 philosophy and used to "weed out" the lowest producers and reward the highest producers, while offering little to no rewards compensation to the mid-level producers. Some 50,000 employees globally were cut from the Motorola global workforce between 1995 and 2005, and many of these can be attributed to the Vitality Curve. Economics also played a major role, as the stock suffered major losses in the same period.

Dow Chemical

Dow Chemical uses a Vitality Curve program as part of its Performance Management. The program started in 2005 with mixed results.[citation needed]

IBM

IBM has used a Vitality Curve program (known as "PBC", or Personal Business Commitments) since before 2006. For IBM, the main thrust of this strategy is to reduce workforce and shift personnel to lower-cost geographies using a pseudo-objective rationale. The PBC process starts with a corporate distribution target which is applied at the lowest levels of the hierarchy and then iteratively applied through the higher levels. The process involves meetings where managers compete for a limited number of favorable rankings for their employees. An employee's rating is thus dependent not only on the manager's opinion, but also on the ability of the manager at “selling” and how much influence the 1st line manager has on the 2nd line manager (for example, if the 1st line manager is rated highly, that manager's employees are more likely to be ranked highly).[20][21][22]

LendingTree

The LendingTree company uses a system that assigns every employee a 1, 2 or 3 ranking with the buckets set to 15%, 75% and respectively 10%.[23]

GlaxoSmithKline

GlaxoSmithKline uses a four point system, with 25% getting the top rating, but no fixed quotas for the other buckets.[24]

AIG

Under the leadership of Bob Benmosche, American International Group (AIG) implemented a five point system in 2010, with a split of 10%/20%/50%/10%/10%. The top 10% are deemed "1s," and receive the largest bonuses; the next 20% are "2s," and receive somewhat smaller bonuses; the bulk consists of "3s," which get the smallest bonuses, while the "4s" receive no bonuses, and the "5s" are fired if they don't improve. According to Jeffrey Hurd, AIG's senior vice president of human resources and communications, "Prior to this, everyone was above-average [...] You never really knew where you stood."[25]

Yahoo

Yahoo CEO Marissa Mayer instituted its "QPR" (quarterly performance review) system in 2012, using the rankings: Greatly Exceeds (10 percent) Exceeds (25 percent), Achieves (the largest pool at 50 percent), Occasionally Misses (10 percent) and Misses (five percent).

In a new version for the fourth quarter 2013, sources said, those percentages are changing, but only at the discretion of leadership within the units: Greatly Exceeds (10 percent), Exceeds (35 percent), Achieves (50 percent), Occasionally Misses (five percent) and Misses (zero percent).

This new evaluation system has resulted in 600 layoffs in the fourth quarter of 2013. [26]

Amazon

Excerpt from the New York Times[27]

Amazon holds a yearly Organization Level Review, where managers debate subordinates’ rankings, assigning and reassigning names to boxes in a matrix projected on the wall. In recent years, other large companies, including Microsoft, General Electric and Accenture Consulting, have dropped the practice — often called stack ranking, or “rank and yank” — in part because it can force managers to get rid of valuable talent just to meet quotas.

The review meeting starts with a discussion of the lower-level employees, whose performance is debated in front of higher-level managers. As the hours pass, successive rounds of managers leave the room, knowing that those who remain will determine their fates.

Preparing is like getting ready for a court case, many supervisors say: To avoid losing good members of their teams — which could spell doom — they must come armed with paper trails to defend the wrongfully accused and incriminate members of competing groups. Or they adopt a strategy of choosing sacrificial lambs to protect more essential players. “You learn how to diplomatically throw people under the bus,” said a marketer who spent six years in the retail division. “It’s a horrible feeling.” [...]

Many women at Amazon attribute its gender gap — unlike Facebook, Google or Walmart, it does not currently have a single woman on its top leadership team — to its competition-and-elimination system. [...]

The employees who stream from the Amazon exits are highly desirable because of their work ethic, local recruiters say. In recent years, companies like Facebook have opened large Seattle offices, and they benefit from the Amazon outflow.

Recruiters, though, also say that other businesses are sometimes cautious about bringing in Amazon workers, because they have been trained to be so combative. The derisive local nickname for Amazon employees is “Amholes” — pugnacious and work-obsessed. [28]

Other notable companies

Other notable examples cited in a 2010 paper include Cisco Systems, Hewlett-Packard, Lucent, Intel, Goodyear Tire, Goldman Sachs, J.P. Morgan Chase & Co., American Express, Sun Microsystems and Conoco.[29]

Companies utilizing but later abandoning this technique

Microsoft

Microsoft was involved in lawsuits regarding its forced ranking system as early as 2001. Detractors argued that the use of the system in small groups was inherently unfair and favorized those employees who socialized more heavily over actual technical merit.[30] At the time, Microsoft officially claimed, through Deborah Willingham, Microsoft's senior vice president for human resources, that it had no such "stack rank" system.[31]

Starting in 2006, Microsoft began to use a Vitality Curve despite intense internal criticism.[32] Posts on "the curve" by Who da'Punk, an anonymous blogger internal to the company, on his blog Mini-Microsoft became a hot topic of commentary by other presumed employees.[33][34]

In a memo to all Microsoft employees dated April 21, 2011, chief executive Steve Ballmer announced the company would make explicit the Vitality Curve model of performance evaluation: "We are making this change so all employees see a clear, simple, and predictable link between their performance, their rating, and their compensation." [35] The new model had 5 buckets, each of a predefined size (20%, 20%, 40%, 13%, and 7%), which management used to rank their reports. All compensation adjustments were predefined based on the bucket, and employees in the bottom bucket were ineligible to change positions, since they would have the understanding that they might soon be yanked.[citation needed]

Following Balmer's announced departure, on November 12, 2013, Microsoft's HR chief Lisa Brummel announced they were abandoning the practice.[36][37][38]

Since the 2000s, Microsoft used a stack ranking similar to the vitality curve. Many Microsoft executives noted that company "superstars did everything they could to avoid working alongside other top-notch developers, out of fear that they would be hurt in the rankings". It has been said that this stack ranking stifled innovation, as employees were more concerned about making sure that their peers or rival projects failed instead of proposing new inventions, overall turning the company into a collection of non-cooperating fiefdoms which was unable to catch onto many technology trends.[39] The stack ranking system was relatively secretive for a long time at Microsoft. Non-manager employees were supposed to pretend they didn't know about it.[40]

The practice at Microsoft became a topic of significant media attention following the 2012 "Microsoft’s Lost Decade" article[41] in Vanity Fair written by Kurt Eichenwald.[42][43][44][45] According to a subsequent article by Nick Wingfield in the New York Times Bits blog: "While that story overstated the harmful effects of stack ranking in the view of many Microsoft employees, it clearly represented the views of many others. [...] The negative publicity around Microsoft’s old employee review system reverberated loudly around the company, according to people who work there. [...] The executive who spoke [to Wingfield] on condition of anonymity recalled Ms. Brummel saying: “I hope I never have to read another article about our review system ever again.”"[37]

Adobe

Adobe Systems used the method but abandoned it in 2012.[46][47]

Ford

Around 2001, Ford used a forced ranking system with three grades, labeled A, B and C, with preset quotas set to 10%, 80%, and respectively 10%.[48] Ford stopped using this ranking system for its managers and engineers amid class action lawsuits from employees,[49] which Ford settled for $10.5 million.[50]

General Electric

GE is by far the most famous company to utilize this form of corporate management. However, since Jack Welch's departure from the company, less emphasis has been placed on eliminating the bottom 10% and more emphasis placed on team-building.[51] During Welch's leadership, the system at GE was dubbed "rank and yank".[52] New York Times reported that GE has dropped this evaluation method.[53]

See also

References

  1. ↑ http://www.computerworld.com/article/2486003/it-management/-stack-ranking--employee-eval-practice-falls-out-of-favor.html
  2. ↑ http://blogs.hbr.org/2013/11/dont-rate-your-employees-on-a-curve/
  3. ↑ http://www.washingtonpost.com/blogs/on-leadership/wp/2013/11/20/for-whom-the-bell-curve-tolls/
  4. ↑ http://online.wsj.com/news/articles/SB10001424052970203363504577186970064375222
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ http://www.nceo.org/articles/employee-stock-options-factsheet
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ http://abcnews.go.com/Business/microsoft-abolishes-stack-ranking-employees/story?id=20877556
  15. ↑ http://www.businessweek.com/articles/2013-11-13/microsoft-kills-its-hated-stack-rankings-dot-does-anyone-do-employee-reviews-right citing http://web.mit.edu/chintanv/www/Publications/Chintan%20Vaishnav%20Punishing%20by%20Rewards%20for%20Publication%20Final.pdf
  16. ↑ http://archive.fortune.com/magazines/fortune/fortune_archive/2000/02/21/273841/index.htm also quoted by Stewart, Gruys and Storm (2010)
  17. ↑ http://www.cio.com/article/2394165/careers-staffingorced-rankings-are-institutionaliz/careers-staffing/forced-rankings-are-institutionalized-stupidity-at-its-worst.html
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found. citing Pfeffer, J., & Sutton, R. I. (2006). Evidence-based management. Harvard Business Review, 84, 62–74.
  19. ↑ https://www.linkedin.com/pulse/idiotic-office-rules-drive-everyone-insane-dr-travis-bradberry
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ http://online.wsj.com/news/articles/SB10001424052970203363504577186970064375222
  24. ↑ http://online.wsj.com/news/articles/SB10001424052970203363504577186970064375222
  25. ↑ http://online.wsj.com/news/articles/SB10001424052970203363504577186970064375222
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Stewart, S. M., Gruys, M. L. & Storm, M. (2010). Forced distribution performance evaluation Systems: Advantages, disadvantages, and keys to implementation. Journal of Management and Organization, 16: 168-179.
  30. ↑ http://www.nytimes.com/2001/03/19/business/companies-turn-to-grades-and-employees-go-to-court.html
  31. ↑ http://www.nytimes.com/2001/03/19/business/companies-turn-to-grades-and-employees-go-to-court.html?src=pm&pagewanted=2
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ http://www.businessweek.com/stories/2005-09-25/online-extra-a-rendezvous-with-microsofts-deep-throat
  34. ↑ http://www.networkworld.com/article/2222736/microsoft-subneticrosoft-has-become-everything-it-/microsoft-subnet/microsoft-has-become-everything-it--despised---insiders-tell-vanity-fair.html
  35. ↑ Microsoft increasing employees' pay. Seattle Times, April 21, 2011. Retrieved 2011-04-25
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ http://www.zdnet.com/microsoft-does-away-with-stack-ranking-7000023103
  39. ↑ http://www.vanityfair.com/business/2012/08/microsoft-lost-mojo-steve-ballmer
  40. ↑ http://www.slate.com/articles/business/moneybox/2013/08/microsoft_ceo_steve_ballmer_retires_a_firsthand_account_of_the_company_s.2.html
  41. ↑ http://www.vanityfair.com/news/business/2012/08/microsoft-lost-mojo-steve-ballmer
  42. ↑ http://www.theverge.com/2012/7/3/3134719/microsoft-windows-office-loyalty-lost-decade
  43. ↑ http://abcnews.go.com/Business/microsoft-abolishes-stack-ranking-employees/story?id=20877556
  44. ↑ http://www.slate.com/blogs/future_tense/2013/08/23/stack_ranking_steve_ballmer_s_employee_evaluation_system_and_microsoft_s.html
  45. ↑ http://www.pcmag.com/article2/0,2817,2406673,00.asp
  46. ↑ http://www.hreonline.com/HRE/view/story.jhtml?id=534355695
  47. ↑ http://www.forbes.com/sites/petercohan/2013/11/29/adobes-stock-up-68-since-it-dumped-stack-ranking-will-microsofts-follow/
  48. ↑ http://www.nytimes.com/2001/03/19/business/companies-turn-to-grades-and-employees-go-to-court.html?src=pm&pagewanted=2
  49. ↑ Shirouzu, N. Ford Stops Using Letter Rankings To Rate White-Collar Employees. Wall Street Journal, B.1 (July 11).
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ New rule: Hire passionate people. Old rule: Rank your players; go with the A's. FORTUNE Magazine By Betsy Morris, Fortune senior writer July 11 2006: 10:13 AM EDT CNN Money - July 10, 2006
  52. ↑ http://www.slate.com/blogs/future_tense/2013/08/23/stack_ranking_steve_ballmer_s_employee_evaluation_system_and_microsoft_s.html
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Articles

Retrieved from "https://infogalactic.com/w/index.php?title=Vitality_curve&oldid=3009963"