360-degree feedback bias

360-degree feedback bias is any systematic tilt in multi-rater feedback that makes ratings not fully reflect an employee’s typical performance. Biases can inflate, deflate, or skew specific skill areas depending on who provides feedback and the context in which they do it.

These biases are not necessarily personal attacks or praise; they are recurring patterns tied to relationships, timing, role expectations, and the feedback process itself. For managers, spotting the pattern is often more useful than debating a single discrepant score.

Common forms include halo effects, leniency or severity trends, central tendency, and source-specific blind spots (e.g., peers underrating leadership presence while direct reports underrate technical skill).

These characteristics help managers interpret a 360 report beyond the headline scores: look for patterns across sources and over time rather than treating single items as definitive.

**Reciprocity:** raters soften criticism or boost colleagues who have helped them or who they expect future favors from

**Reputation bias:** a colleague’s known reputation (positive or negative) influences ratings regardless of recent behaviour

**Salience and recency:** recent incidents or visible behaviour get more weight than routine, consistent performance

**Role visibility:** certain competencies are more observable to specific raters (e.g., peers see collaboration, managers see strategy)

**Social desirability:** raters provide answers they think are acceptable rather than fully candid assessments

**Process design flaws:** unclear scale definitions, insufficient rater training, or anonymous formats that encourage extremes

Large gaps between self-ratings and others’ ratings

Direct reports consistently rate someone higher or lower than peers or managers

Teams where ratings cluster around the midpoint regardless of qualitative differences

Repeated comments that contradict the numerical score (e.g., high score but many negative examples in comments)

One rater group (often peers or manager) driving the overall score because of small sample size

Ratings that swing dramatically after a single visible event (presentation, conflict, win)

Pattern of leniency or severity tied to interpersonal closeness or distance

High agreement on strengths but wide disagreement on developmental areas

Comments that focus on personality traits rather than job-relevant behaviours

Over-reliance on labels ("good communicator") without examples

Recent project failure or success that’s still top of mind

Recent reorg, promotion, or demotion changing relationships

New raters unfamiliar with the role being evaluated

Tight deadlines causing raters to rush through responses

Ambiguous rating scales or poorly worded questions

Anonymity perceived as permission to be blunt or punitive

Recent interpersonal conflict or praise that skews perceptions

Lack of calibration sessions or rater training

Cultural norms that discourage direct criticism

Incentives tied to team harmony or individual ratings

Require rater training that clarifies rating scales, gives behavioral examples, and explains what each competency looks like in practice

Use mixed methods: pair scores with structured comments that require specific examples and context

Compare patterns across rater groups rather than relying on a single aggregate score

Implement calibration sessions where managers review anonymized trends and reconcile outliers with concrete evidence

Set minimum rater counts per group to reduce the influence of single voices

Time feedback collection to avoid proximity to major events (e.g., not immediately after a heated meeting)

Provide raters with short guidance on common biases and encourage evidence-based examples

Weight rater groups appropriately for role visibility (e.g., product managers’ stakeholders vs. direct reports)

Track trends over multiple cycles to distinguish one-off events from persistent patterns

Share and discuss the 360 findings with the individual in a coaching-oriented conversation, focusing on examples and development goals

Use a separate review to validate high-stakes decisions (promotions, pay) rather than relying solely on 360 output

Document decisions and evidence when 360 results contradict other performance data

Performance appraisal: connected to 360 feedback but usually manager-driven; 360 adds multiple perspectives and so introduces multi-source bias dynamics

Halo effect: a single positive trait inflates other ratings; similar mechanism but halo is one of many biases affecting 360s

Rater calibration: a practice to align raters; it reduces 360 bias by creating shared standards and examples

Social desirability bias: raters give favorable answers to conform to norms; explains why some 360s skew positive

Anonymity effects: anonymity can increase candor or reduce accountability; it changes how bias expresses itself in 360s

Leniency/severity bias: consistent tendency to rate high or low; in 360s this can come from group norms or fear of damaging relationships

Central tendency bias: choosing middle options to avoid extremes; leads to flat distributions in multi-source feedback

Source credibility: the perceived expertise of a rater affects how managers interpret 360 input; explains differential weighting of rater groups

Feedback culture: an organizational norm that shapes whether 360s are honest and useful; weak culture amplifies bias