Reviews, Appraisals and Incentives

black_green_black_thin_2Author: Gene Gendel

I wanted to start this discussion with Wikipedia definition of Performance Appraisal:

A performance appraisal (PA), also referred to as a performance review, performance evaluation,[1] (career) development discussion,[2] or employee appraisal[3] is a method by which the job performance of an employee is documented and evaluated. Performance appraisals are a part of career development and consist of regular reviews of employee performance within organizations.”

Interestingly enough, while all three terms are being included in the same definition (“review”, “evaluation”, “appraisal”), in practice, companies predominantly use the term “review” to describe PA as it implies less scrutiny and preconception towards an employee. But does this change the essence of the process if a less abrasive term is being used?

Usually, PA process starts with setting individual career goals by an employee. Of course, this is not done in a vacuum of what an employee only chooses for herself. Individual career goals should be in-line with organizational/department career goals, usually set by management. It is expected that throughout a year, an employee has to steer herself towards set goals, while performing her day-to-day job responsibilities.

Every company that supports PA process has a scoring system (variations exist) to rank employees, against other employees, based on score that an employee earns, while performing her yearly accomplishments (goals set vs. goals achieved). Some organizations offer a mid-year (quarterly, at best) check-point to employees, at which an employee reviews with her manager how she is performing with respect to the goals, set originally. Practically, no companies handle PA as an actively managed, iterative agile process.

For most companies the whole PA process, typically serves the following three main purposes:
1. To identify low-performing employees that are potentially a subject to downsizing
2. To identify high-performing employees that are potentially a subject to promotions
3. To decide how discretionary incentives (bonuses) can be distributed among employees
While on the surface PAs still appear as an effective way ensure quality of employees and provide benefits to organizations, under the surface this process presents real challenges. These challenges become more visible at organizations that are in the process of adopting agile culture, since in agile environments systemic organizational dysfunctions get exposed much better.

But before we dive deeper in the discussion, let us first briefly refer to some credible research and studies that exists today:

In his book “Out of the Crisis”, originally published in 1982, Edward Deming discusses Seven Deadly Diseases of Management and refers to individual performance reviews and performance evaluation as Disease # 3. Deming’s philosophy of transformational management is about seriousness of barriers that management faces today, while improving effectiveness and striving for continual improvement. Deming argues that trying to evaluate and measure workers with the same yard stick causes more harm than good to individuals and companies.

Tom Coens and Mary Jenkins offer specific suggestions on how to replace performance appraisals with a more effective system that emphasizes teamwork and empowerment in their book “Abolishing Performance Appraisals: Why They Backfire and What to Do Instead. Coen and Jenkins discuss new alternatives that produce better results for both managers and employees.

In his Forbes article “Eliminating Performance Appraisals”, Edward E. Lawler III, a distinguished professor of Business at the University of Southern California, advocates that organizations stop doing performance appraisals. Professor Lawler states that performance appraisals frequently do more damage than good, with damage levels fluctuating between wasted time (least troublesome) to reasons for alienation of employees and creating conflicts between them and their supervisors (most troublesome).

Garold Markle, an author, executive consultant and speaker, leverages his studies and experience with systems theory to illustrate his points with real-life examples of why employees and managers both have come to believe the “ubiquitous performance evaluation as industry’s poorest performing, most ineffective, and least efficient personnel practice”. In his book “Catalytic Coaching: The End of the Performance Review”. Markle provides an innovative way to measure ineffectiveness and inefficiency of performance evaluations and then introduces his catalytic coaching to replace them. His statement is awakening: “People hate performance reviews”.

In his book “Drive”, Daniel Pink offers a paradigm-shattering view on what truly motivates people in their lives. Pink draws on four decades of scientific research on human motivation, to expose a mismatch “between what science knows and what business does”. Pink challenges the mistaken belief of many that people doing intellectual work, will demonstrate higher performance, when incentivized monetarily. Bas to Pink’s research, it becomes clear that individual performance evaluations and individual appraisals that are linked to monetary rewards, are not an effective way to steer individuals to become more efficient and productive. Therefore, they should be abolished. And the list goes on….

So, now lets take a closer look at the problem, with some specific examples:

 

Fabricating Goals to Game the System

Are goals that employees officially set for themselves (in a system of record) truly reflect their genuine, personal goals?

It is not uncommon that real personal goals are risky and challenging to achieve or may take longer than initially expected. Many other goals can be also situational or opportunistic: they may change as a situation changes or unforeseen opportunity presents itself (job market trends, other job opportunities, personal life). People want to have freedom and flexibility to adjust their goals to optimize their personal benefits; this is a human nature. There is no true personal benefit for an individual to “set in stone” her goals into a personal development plan at year-start and then having to deal with unpleasant consequences at year-end, IF she does not meet her goals. In general, in order to set her real goals, a person needs to know that it is safe to actively manage them along the way and, if needed, safely change and/or fail them, without fearing negative consequences.

But is there any safety with PA processes if job security, career advancement ability and ability to collect fair compensation are at risk? If there is no personal safety, the exercise of setting personal goals becomes nothing but a routine of faking objectives that are “definitively achievable”. People are forced to do it, to minimize the risk of being scrutinized by their management for not meeting their goals. Setting individual goals becomes just a formality that brings no true value to an employee.
The process of individual performance reviews becomes even less meaningful if people work in small teams, where swarming and collective ownership is important, and joint delivery is expected. In cases such as these, people are forced into unhealthy competition with each other over goals, trying to privatize what should be owned and claimed collectively.
Another challenge with evaluating employees’ individual career goals is that in pursuit of personal goals, people frequently “drop the ball” and de-prioritize common goals. Again, this dysfunction becomes much more vivid in going-agile environments, where agile frameworks (e.g. Scrum, Kanban) de-emphasize individual ownership and reinforce the importance of collective ownership. Often, close to mid-year and end-year performance reviews, collaboration and mutual support of team members worsens, as silos get created and everyone begins to think about their own goals, at expense of shared goals. This translates into inefficiency and productivity drop: swarming, velocity and throughput go down; cycle time and queues grow; handovers take longer.

 

Example:

Jane is an employee of a large insurance company. She is being requested to enter in a company’s system of record her personal goals – things that she intends to achieve throughout a year.   Jane is smart and in order to avoid any unwarranted risk, where her personal success depends on success of others, she creates goals that are free of dependencies. Jane creates a set of personal goals that other group members do not know and don’t care about. Her line manager John, also discourages Jane from sharing such information.

However, Jane does not work alone. Her day-to-day work is tightly coupled with work of other individuals in her group: Jim, Jeff, Jill, Joe and Julie.

Jane really values team work. She also feels that by closely working with her group members, by swarming and sharing day-to-day activities she can earn a lot more than if she worked by herself.   This is where Jane decides to put her full focus: on team work. She does not feel that creating an additional set of personal goals can add real value to her professional growth. But Jane needs to “feed the beast”: she needs to provide her line manager with a list of “achievable” bullets that the latter can measure. At the same time, Jane does not want to create a conflicting situation with her colleagues, by diluting her focus on shared goals by shifting it personal goals. Therefore, she fabricates her personal goals: “quick kills” and “low hanging fruits” – something that she can easily claim as her “achievement”, without jeopardizing common interests of her team. Jane is forced to “game” the system to minimize harm to herself and her team.
In his book “Tribal Leadership”, David Logan describes five tribal stages of societal evolution. According to his research, corporate cultures typically oscillate between Stage 3 (“I am great and you are not”) and Stage 4 (“We are great and they are not”), with agile organizations trending more towards Stage 4. When individuals are motivated (a.k.a. “manipulated”) to think more about individual performance than about collective performance, they mentally descend to Tribal Stage 3 and, as a result, drag along their organization to this lower stage. It is very important for organizations and their senior leaders to understand that motivation is one of the most important factors that drive evolution of corporate culture.

Note: To understand how Motivation Evolution (defined by Daniel Pink in “Drive”) relates to Tribal Evolution (defined by David Logan in “Tribal Leadership”), please refer to this tool.

 

Unhealthy Competition, Rivalry and Jealousy

Let’s face it, overemphasizing individual performance evaluations and allowing them affect job security, promotions and compensation of individuals does not come free to organizations. It comes at high expense of lowered collaboration, unwillingness to share knowledge and provide peer-to-peer support, increased selfishness and self-centric behaviors. For individuals that are encouraged to work and produce collectively (e.g. Scrum or Kanban teams) uneven performance evaluations frequently result in jealousy and feelings of unfair treatment. These dysfunctions become more frequent around times when employees are due to mid-year and end-year reviews. PAs have adverse effects on individuals’ ability to focus on work and, as a result, produce high quality products and think of customer satisfaction.

It is worth mentioning, ironically, when dysfunctions are uncovered, it is agile that becomes the target for blaming.

But agile is hardly at fault here as it only provides transparency and reflection of already existing dysfunction.
Example:

Jane works alongside Jim, Jeff, Jill, Joe and Julie. All of them are smart, self-motivated and talented technical experts that cumulatively have more than 70 years of software development experience. Their work is intense: there are lot of deliverables and their timeframes are rigid. The group serves the same client for a number of few years and, so far, a client is happy. The work that this team performs, requires a lot of collaboration, collective thinking and brainstorming, teaching/learning from each other and, of course, collective delivery.

But then comes a mid-year review period and Jill notices that Jeff is not as supportive of her as he was at the beginning of the year. Jeff becomes less responsive to Jill’s requests, he does not share his knowledge as readily as he used to; he does not give advice. Tasks that used to be handled collectively by Jill and Jeff are now illogically split by Jeff as he tries to focus only on what he assigns to himself.

There is also a noticeable change in Julie’s behavior. Julie becomes very eager to be the one who stands in front of a client and presents deliverables of the whole team. This responsibility used to be rotated from one person to another, with no one caring too much about being a “spokesman”. But as mid-review came, Julie clearly stepped up to be the main, customer-facing presenter. Julie also tries to make it very obvious to John (the group’s manager) that it is her – Julie, who presents to a customer. Julie wants to be viewed as a “centerpiece” and gain most of spot light.

Jim’s contribution to the group’s efforts have also subsided. Early in the year, Jim used to be a very active participant at the team’s brainstorming meetings and workshops. As mid-year arrived, Jim started spending a significant portion of his time working on items that are not related to the team’s shared work; his focus has noticeably shifted to personal work that he does not even discuss with others.

Since the beginning of the year, it has been customary for the group to go out for drinks to a local bar, every Friday. But this tradition is now barely followed, at mid-year period. There seems to be less desire for the group to socialize outside work settings. Everyone finds an excuse not to make it. The group’s synergy has gone down noticeably. What used to be a well jelled team of great collective performers has turned into a group of self-centered individual achievers that want to be acknowledged for their heroics.
“Scripted” Ranking to Force-Fit into Bell-Shaped Curve
Typically, when an organization ranks its employees based on individual performance, a bell-shaped curve is produced, where samples (ranked employees) are binomially distributed around the median: majority of samples are centered (“center mass”), representing average performing employees, left tail – representing low performing, and right tail – representing high performing (over-achievers). Statistically, a bell-shaped curve is a normal distribution of any large sample. The symmetrical shape of a curve (“bell”), however, can be influenced by additional three main factors (forces):

  • Platykurtic distribution – it lowers amount of samples around the median (average performers) and increases amount of outliers (under-performers and over-achievers), equally on both sides. A curve remains symmetrical.
  • Leptokurtic distribution – it increases amount of samples around the median (average performers) and lowers amount of outliers (under-performers and over-achievers). A curve remains symmetrical.
  • Uneven distribution of samples on left and right sides from median – Typically, this increases amount of samples on left (under-performers) or right (over-achievers) tails of a curve, while also disturbing symmetry of a curve and evenness of sample distribution around median (average performers). A curve loses its symmetry

 

This statistical distribution is tightly coupled to actions that management takes towards its employees at year-end. However, the shape of bell curve, does not “drive” (as it might be expected) managerial year-end decisions; it is rather driven by them.

Managerial decisions are driven by financial conditions of an organization as well as other strategic organizational plans. When managers review their employees, they have to account for such factors to make sure that a bell-shaped curve does not exceed organizational capabilities of promoting too many employees and giving out too much money. Effectively, the entire process of performance assessments becomes a retro-fitting exercise that shapes a bell curve, basing it on organizational capabilities. This makes the process, practically, staged or “scripted”. What further ads to the irony of this situation is that at times an employee may report into a manager that does not even have sufficient skills for perform an objective assessment of an employee’s performance. For example, an architect or a software engineer that reports into a non-technical manager (e.g. PMO) has a much lower chance to objectively discuss her work accomplishments and receive an objective feedback during PA.

There is a need for an alternative approach that will help dealing with overly complex, over-staffed organizations that spend so much time and energy trying price-tag its employees.

Here is an idea: how about more thorough checks of background and references, more rigorous interviewing processes that involve practical (hands-on) skills assessments, try & buy periods, before hiring an individual full time or some other, more objective methods?

Instead of attracting cohorts of workers of questionable quality and then dealing with inevitable force reduction or worrying (or pretending to worry!) about employees maintaining and/or improving their quality, hiring managers should be striving to acquire and retain lower quantities of higher quality workers: self-motivated, enthusiastic professionals, with a proven track record and clearly defined career goals…AND be willing to pay them higher compensations. This may require offering more competitive base salaries, and abolishing manipulative discretionary incentives: removing money from the table makes intellectual workers think more about work, and less about getting paid. This approach would also ensure that quantity of employees is kept at a minimum (this also ensures lowering overhead, complexity reduction, organizational descaling), while maximizing quality. Such alternative should render performance reviews much less important or even obsolete as there will be no need to reduce employees at year-end or thin-slice discretionary incentives among too many candidates.

 

Example:

John is a line manager for the development group. John has great organizational skills, he is well spoken and can greatly articulate his thoughts. But John, has never developed software products; he is not technical. John knows that all of his team members are “good guys”: knowledgeable, enthusiastic, and mutually supportive. But when the team works together, John really cannot validate quality of work that they produce. (Luckily, there is one reliable measurement of the team’s success – it is customer satisfaction). The only thing that John can validate is the team’s vibe and spirit. But even when John notices disagreements or temporary misalignment among the team members, it is impossible for him to offer a c