Unit II — Individual Behaviour
12. Perception, Attribution and Bias
Perception is the process by which individuals select, organize and interpret information to make sense of their environment, and it strongly shapes managerial judgments about performance and blame. Attribution theory explains how people assign causes to behaviour (internal/dispositional vs external/situational), while biases such as the fundamental attribution error, halo effect and stereotyping can systematically distort these judgments, especially under time pressure or ambiguity.
- Selection: filtering which cues receive attention
- Organization: grouping and categorizing information
- Interpretation: assigning meaning based on schemas and prior experience
- Attribution: internal vs external causal explanation
- Common distortions: halo effect, stereotyping, fundamental attribution error, selective perception
- Ratio of internal vs external causes cited in incident reports written by supervisors
- Consistency, distinctiveness and consensus information actually checked before blame is assigned (Kelley's model cues)
- Frequency of generalized language ('workers are careless') vs specific incident description in appraisal notes
- Time-stamped correlation between downtime events and actual maintenance logs versus supervisor's verbal explanation
- 360-degree perception gap between self-rating and peer/subordinate rating on the same incident
At Bharat Precision Forgings' Faridabad unit, machine downtime on the CNC line rose from 6% to 14% of shift hours over two months. Shift supervisor Mahesh has repeatedly told the plant manager that 'the operators are careless and don't follow SOPs,' recommending disciplinary warnings for three senior operators. However, maintenance logs show that a batch of replacement bearings installed eight weeks ago has a higher failure rate, and unresolved ambient temperature issues in the bay have also been flagged twice by the same operators in complaint logs that went unactioned. The plant manager must decide how to interpret Mahesh's attribution before approving any disciplinary action.
Downtime rise
6% to 14% of shift hours over 8 weeks
Bearing batch failure rate (new vs old)
New: 9% failure vs old: 2% failure
Operator complaint logs about bay temperature
2 logged complaints, unactioned
Consistency of downtime across shifts/operators
Occurs across all 3 shifts, not one operator
Mahesh's incident reports citing operator fault
9 of 10 reports cite operator error
AApprove disciplinary warnings as recommended by Mahesh
Accept the supervisor's attribution at face value and issue warnings to the three operators.
BInvestigate using Kelley's covariation cues before deciding
Check consistency (does it happen across shifts), distinctiveness (does it happen only with certain tasks) and consensus (do other operators show the same pattern) before attributing cause.
CAddress the bearing and temperature issues directly, bypassing disciplinary action
Replace the faulty bearing batch and fix the ambient temperature issue immediately without formal investigation of Mahesh's claims.
AApprove disciplinary warnings as recommended by Mahesh
Strengths
- Quick, decisive action
- Signals accountability expectations
Risks
- High risk of fundamental attribution error given documented situational causes
- May damage trust and morale if operators are unfairly blamed
BInvestigate using Kelley's covariation cues before deciding
Strengths
- Reduces attribution bias by using structured evidence
- Leads to fairer, more accurate root-cause identification
Risks
- Takes more time before any corrective action
- Requires supervisor training to change habitual attribution style
CAddress the bearing and temperature issues directly, bypassing disciplinary action
Strengths
- Directly targets a likely root cause fast
- Avoids unjust punishment of operators
Risks
- Does not address why the supervisor is prone to dispositional blame
- May leave a genuine SOP compliance gap unexamined if one exists
As the plant manager, which course of action would you take regarding the downtime issue and Mahesh's attribution, and why?
Accept the supervisor's attribution at face value and issue warnings to the three operators.
Strengths: Quick, decisive action; Signals accountability expectations. Risks: High risk of fundamental attribution error given documented situational causes; May damage trust and morale if operators are unfairly blamed.
Check consistency (does it happen across shifts), distinctiveness (does it happen only with certain tasks) and consensus (do other operators show the same pattern) before attributing cause.
Strengths: Reduces attribution bias by using structured evidence; Leads to fairer, more accurate root-cause identification. Risks: Takes more time before any corrective action; Requires supervisor training to change habitual attribution style.
Replace the faulty bearing batch and fix the ambient temperature issue immediately without formal investigation of Mahesh's claims.
Strengths: Directly targets a likely root cause fast; Avoids unjust punishment of operators. Risks: Does not address why the supervisor is prone to dispositional blame; May leave a genuine SOP compliance gap unexamined if one exists.
Set the weight of each criterion (1–5), then score every alternative (1–5). The matrix is a thinking aid, not a verdict.
| Criterion | Weight | A | B | C |
|---|---|---|---|---|
| Behavioural impact | ||||
| Employee acceptance | ||||
| Feasibility | ||||
| Cost (higher = more affordable) | ||||
| Risk containment | ||||
| Long-term sustainability |
With your current weights, alternative A scores highest. A matrix only reflects the weights you chose. Evidence, ethics, feasibility and the people affected still belong in your judgement — you decide.
Attribution theory, and specifically the fundamental attribution error, cautions that observers (like Mahesh) tend to overweight dispositional explanations for others' behaviour while underweighting situational factors, which is consistent with his pattern of blaming operators despite consistent, cross-shift downtime. Kelley's covariation model offers a structured way to test this: high consistency across shifts and low distinctiveness point toward a situational (equipment/environment) cause rather than an individual one, supporting Option B or C. Halo/horn effects may also be at play if Mahesh has a fixed negative impression of these operators that colors his interpretation of ambiguous evidence.
- Short-term: disciplining operators without full investigation (Option A) risks grievance escalation and morale damage
- Short-term: fixing equipment first (Option C) may quickly reduce downtime but leaves attribution bias unaddressed
- Long-term: structured investigation (Option B) builds a more accurate diagnostic culture and reduces recurrence
- Long-term: unresolved perceptual bias in supervisors can erode trust and increase turnover among wrongly blamed staff
- Long-term: training supervisors in attribution awareness improves the quality of future incident reports plant-wide
- What cues in this scenario suggest a fundamental attribution error by Mahesh?
- How might Mahesh's own halo/horn impressions of specific operators be shaping his reports?
- What organizational habits (e.g., unactioned complaint logs) enable perceptual bias to persist unchecked?
The fundamental attribution error refers to the tendency to:
Which evidence in the scenario most strongly challenges Mahesh's 'careless operators' attribution?
What is the most defensible next step before approving disciplinary action?