When 'Keeping Up' Costs the Team: A Startup Engineering Review
A real-world example of Social comparison bias in action
Context
A mid-stage SaaS startup was scaling its engineering team rapidly while preparing for a major product launch in six months. Leadership emphasized qualitative performance narratives over standardized metrics during reviews to preserve team autonomy and speed up promotions.
Situation
During quarterly reviews, an engineering manager informally compared a competent mid-level engineer, Sam, against a standout peer, Alice, who had previously shipped several high-visibility features. The manager, worried about maintaining their own reputation for hiring and team quality, started treating Sam as "less promotable" despite similar objective metrics.
The bias in action
The manager's judgments were driven by social comparison: Sam was assessed relative to Alice's perceived status rather than on Sam's actual contributions and growth trajectory. As a result, Sam received fewer stretch assignments and less public recognition, which limited opportunities to build the same reputation. Team members picked up on the differential treatment and began to self-sort into perceived 'high status' and 'others' groups. Over time the manager reinforced their own status by allocating prominent work to those already seen as top performers, creating a feedback loop.
Outcome
Sam's engagement and motivation declined, leading to a drop in personal productivity and the decision to accept an outside offer two months later. The team lost institutional knowledge on a critical module and sprint velocity dropped while a replacement was recruited and onboarded. Morale among remaining mid-level engineers fell, and several began looking externally.