Trait Ascription Bias

You're seeing Trait Ascription Bias when a manager labels an employee as "not a team player" based on a few interactions, while explaining their own occasional lack of collaboration as "I was under a lot of pressure that week." The same behaviour gets a fixed label for others and a situational excuse for self.

You're seeing Trait Ascription Bias when a founder writes off a potential partner as "indecisive" after two slow email responses, while attributing their own delayed replies to being busy. They ascribe a trait to the partner and a situation to themselves.

Build performance systems that evaluate behaviour across contexts, not from single data points. When forming opinions about partners, investors, or employees, force yourself to generate a situational explanation before accepting a character-based one. The people you write off as "just like that" often aren't — they're responding to conditions you haven't considered.

Nooyi was known for evaluating her leadership team with unusual contextual depth. Rather than labelling executives as "strong" or "weak," she assessed performance relative to the specific conditions each person faced — market dynamics, team composition, resource constraints. She explicitly resisted fixed-trait judgments, insisting that the same person could perform brilliantly in one context and struggle in another. Founders can apply this by building evaluation systems that account for context, not just outcomes. Before labelling someone's ability, understand their situation. Nooyi proved that the leaders who get the most from their teams are the ones who refuse to reduce people to fixed traits.