Cisco People. Cisco icons, shapes, stencils and symbols

"Subjective performance evaluation allows the use of a subtler, more balanced assessment of employee performance, and is typically used for more complex jobs where comprehensive objective measures are difficult to specify and/ or measure. Whilst often the only feasible method, the attendant problems with subjective performance evaluation have resulted in a variety of incentive structures and supervisory schemes. One problem, for example, is that supervisors may under-report performance in order to save on wages, if they are in some way residual claimants, or perhaps rewarded on the basis of cost savings. This tendency is of course to some extent offset by the danger of retaliation and/ or demotivation of the employee, if the supervisor is responsible for that employee’s output. ...
Another problem relates to what is known as the "compression of ratings". Two related influences—centrality bias, and leniency bias—have been documented ... The former results from supervisors being reluctant to distinguish critically between workers (perhaps for fear of destroying team spirit), while the latter derives from supervisors being averse to offering poor ratings to subordinates, especially where these ratings are used to determine pay, not least because bad evaluations may be demotivating rather than motivating. However, these biases introduce noise into the relationship between pay and effort, reducing the incentive effect of performance-related pay. ... this is the reason for the common separation of evaluations and pay, with evaluations primarily used to allocate training.
Finally, while the problem of compression of ratings originates on the supervisor-side, related effects occur when workers actively attempt to influence the appraisals supervisors give, either by influencing the performance information going to the supervisor: multitasking (focussing on the more visibly productive activities...), or by working “too hard” to signal worker quality or create a good impression...; or by influencing the evaluation of it, e.g., by "currying influence"... or by outright bribery..." [Principal–agent problem. Wikipedia]
The example "Person demotivated by evaluation - Fault tree analysis diagram" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Fault Tree Analysis Diagrams solution from the Engineering area of ConceptDraw Solution Park.

This onion diagram example was designed on the base of figure "Stakeholders for a System" in the slide presentation "A103: Introduction to ITS Standards Requirements Development" from the U.S. Department of Transportation (US DOT) website.
"“Stakeholders for a System.” A graphic of four concentric circles arranged like an archery target. The innermost circle is a reddish tan. The three bands of colors that are further from the center are in lighter shades of tan. This is called an “onion diagram” as onions are made up of multiple layers. The inner circle is labeled “Physical System.” The next layer outward is labeled “Operational System.” The next layer outward is labeled “Containing System.” The outermost layer is labeled “Wider Environment.” There are smaller black graphics of person positioned in the different layers of the diagram. Each person has a project role next to it as follows: 1) Inner Circle has no people – It represents the system; 2) Next Layer Outward has three people labeled TMC Operator, Field Maintenance, and Operational Support respectively; 3) Next Layer Outward has two people labeled Interfacing System Owner and Purchaser respectively; and 4) Outermost Layer has four people labeled Sponsor of the Project, Regulatory Agency, Public, and Politician respectively. The picture demonstrates while they are all stakeholders, different stakeholders have different levels of influence on the physical system to be defined. The most influence coming from those closest to the center."
[pcb.its.dot.gov/ standardstraining/ mod04/ ppt/ m04ppt.htm]
The onion diagram example "System stakeholders diagram" was drawn using the ConceptDraw PRO software extended with the Stakeholder Onion Diagrams solution from the Management area of ConceptDraw Solution Park.