fundamental attribution error
Also called: attribution error, correspondence bias
The tendency to explain other people's behavior by their character ("careless", "lazy") while underrating the situation they were in, such as an unclear process, a broken tool or an overloaded week. For a lead, it means checking the setup before judging the person.
The fundamental attribution error is the tendency to explain other people's behavior by who they are ("careless", "lazy", "not a team player") and to underrate the situation they were in: an unclear rule, a broken tool, a workload that doubled, a family emergency. When we explain our own behavior we tend to do the opposite and point to circumstances. The effect is well documented, although its size varies with culture and with how much people know about the other person's situation.
For a lead the cost is a wrong fix. If the cause is the setup (overlapping roles, a metric that rewards the wrong thing, overload, missing training) and you treat it as a character problem, you give feedback or pressure to the person, the problem stays, and the person learns that explaining doesn't help. The same error drives many conflicts: two reports who fight over ticket ownership look "difficult" until you notice their roles overlap.
A simple order of checks helps. Before judging the person, ask: Do they know what is expected? Can they do it (skills, tools, time)? What changed in their situation? Look at the pattern over time, compare with colleagues under the same conditions, and ask the person what is getting in the way. This doesn't excuse everything: sometimes the cause really is a habit, and then it gets direct feedback on the behavior. The point is to check the situation first.
Example
June 2027, the end of the spring peak at Klasna. The lead notices that Maryna, usually the team's quality anchor, is getting through tickets more slowly. The first, character-based reading: "she's losing interest". The situation, from the workload data:
She isn't doing less; she is working longer and more tired. The team average hid it: the coordinators' mean overtime was only 1.79 hours per person-week (86 hours over 48). Part of the setup is the lead's own: the lead sent 108 of the team's 234 out-of-hours messages (46.15%). The right response is about workload and norms, not a performance talk.
The opposite check matters too. Of Taras's 36 reopened tickets in January, 9 (25%) were a new question from the family or a platform fault, not his doing; 27 came from three repeatable shortcuts. Those 27 are a behavior to give feedback on, and the 9 are not.
Common mistakes
- Writing labels in your notes. "Careless" or "lazy" closes the question before the facts are in.
- Comparing people under different conditions. Check that workload, ticket mix and tools were the same.
- Leaving your own part out. The lead's habits and rules are part of everyone's situation.
- Swinging to excuse everything. When the cause is a repeatable habit, it still needs direct feedback.
- Deciding before asking. Ask the person what got in the way before you settle on an explanation.