Late to Meetings, Labeled 'Lazy': How Trait Ascription Undermined a Product Team
A real-world example of Trait ascription bias in action
Context
A mid-size software company was scaling rapidly and introduced quarterly performance reviews to keep up with faster product cycles. Managers were stretched across multiple projects and many decisions about promotions and reassignments were made based on short interactions and anecdotal impressions.
Situation
A product manager, Anika, began arriving late to standing design reviews after taking on a morning caregiving responsibility for a family member. Her manager, Carlos, noticed the lateness but had limited visibility into her schedule and continued to interact with her mostly in spontaneous ad-hoc meetings. Over the course of two quarters, Carlos began to frame Anika as 'disorganized' during calibration conversations about promotions.
The bias in action
Carlos interpreted Anika's tardiness as a stable personality trait — that she was careless and unreliable — rather than considering situational factors that might explain the change. When other team members were late, Carlos often assumed external causes (traffic, emergencies) but treated Anika's behavior as reflective of her character. Because he believed her lateness was a trait, he discounted recent examples of strong deliverables and postponed her promotion. This narrative also spread in calibration meetings where managers preferred simple trait explanations over probing situational details.
Outcome
Anika was passed over for promotion and reassigned to lower-priority projects despite leading two successful feature launches in the prior year. She became disengaged and began looking for other roles, leaving the company three months after the review cycle. The product team lost momentum on a key roadmap item as knowledge transfer was delayed.