“He’s Unreliable” — When an Outcome Turns Into a Label

A review of a delayed task. Anna looks at the deadline Olek missed. Nia checks the project history.

— Late again. He’s just unreliable — Anna says.
— He waited three days for client access — Nia replies.
— He could have anticipated that.

Anna sees the person’s trait first. Nia sees the conditions the person was working in first.

What really happened

Anna sees the outcome: the task is late again. Because something similar has happened before, she quickly reaches a simple diagnosis — Olek is unreliable. Nia looks at how the work unfolded and sees three concrete blockers: missing access, changed requirements, and dependency on another team. Olek is not entirely without responsibility either; he admits that he could have escalated earlier. The real picture is mixed. Part of the cause lies in Olek’s behavior and part in conditions outside his control. The problem begins when either perspective tries to explain everything.

What the research says

People often overestimate the influence of personal traits on behavior while underestimating the influence of the situation — the fundamental attribution error (Ross, 1977). The opposite extreme is also possible: people can point to the system and circumstances until personal responsibility disappears. Good analysis therefore does not choose “person or situation.” It separates the levels. In organizations, it is especially useful to ask what information and resources the person had, which obstacles were foreseeable, and what they could reasonably have done once those obstacles appeared. Attribution research is useful here mainly as a brake on fast judgment: an outcome does not, by itself, tell you why the outcome occurred.

How to handle it

Instead of the label “unreliable,” work through three questions: what was under Olek’s control, what was outside it, and what should he have done earlier once the blocker was visible? If the same problem repeats under comparable conditions and expectations are clear, then it becomes reasonable to discuss a stable behavioral pattern. If the blockers are systemic, the system needs changing. The general rule is: judge the person only after separating their decisions from the conditions in which those decisions were made.

How Empatyzer and Em can help

Empatyzer can help Anna pause the automatic move from “the task is late” to “Olek is unreliable.” Olek’s profile can add context, but it should not be used either to excuse him or to produce a verdict. Em can do something more useful: separate the person’s decisions from the conditions by asking three questions — what was under his control, what was not, and what could he have communicated earlier? Anna can still hold Olek accountable, but she evaluates specific behavior rather than the whole person. Team data can also show whether delays cluster around one individual or around shared process blockers. Micro-lessons practice this distinction in everyday situations. Over time, Empatyzer helps leaders spend less time guessing what a person “is like” and more time identifying what actually needs to change.