“The Explanation Sounds Like an Excuse” — Facts, Accountability and Trust

Project status after a delay. Anna asks Olek why the work is one day late.

— Why is this a day late?
— First the API changed its response, then it turned out the library…
— First tell me the impact and what you’re doing about it.

Olek starts with causes because he wants to explain the situation honestly. Before hearing the story, Anna needs to know the impact and the recovery plan.

What really happened

Anna asks why the work is a day late. Olek begins with the story: first the API changed, then there was a library issue, then he tried several solutions. To him, that sequence is honest because it explains how the delay happened. Anna is listening from a different need. First she wants to know the impact, what Olek is doing now, and when the issue will be closed. Before he gets there, the first several sentences already sound like an attempt to push responsibility away. Olek notices her reaction and begins explaining himself even more, which only strengthens the impression of an excuse. The same facts take on a different meaning because of the order in which they are presented.

What the research says

When something goes wrong, people do not listen to an explanation only to learn the sequence of events. They also judge responsibility, intent, and what will happen next. Research on managerial reactions suggests that the way poor performance is explained can influence how a manager assigns responsibility and responds to the employee (accounts after failure; Mitchell & Wood, 1981). There is no strong scientific law saying everyone should always speak in the precise order “impact, plan, cause.” That is a practical way to reduce ambiguity, not a universal formula demonstrated for every conversation. In this scene it works because it answers the questions Anna needs for managing the situation before supplying the background.

How to handle it

When reporting a delay or error, start with what the other person needs in order to act: “It will be one day late. I’m fixing X today and will send it by noon tomorrow. The cause was the API change.” That does not hide the cause; it places it after the impact and next step. A manager can also avoid assuming bad intent and simply ask: “Give me the impact and plan first, then we’ll go through the cause.” The general rule is: an explanation sounds most accountable when it answers not only “why?” but quickly shows “what does this mean?” and “what are we doing now?”

How Empatyzer and Em can help

Empatyzer can help Anna and Olek see that their conflict is not really about accountability itself but about the order in which they need information after a problem. Olek wants to reconstruct the causes honestly; Anna first needs the impact, plan, and recovery time. Profile comparison may show that one person naturally explains from the beginning of the story while the other filters information quickly for decisions and risk. Before the status update, Em can give Olek a simple structure: “impact → plan → deadline → cause,” without taking away his ability to explain fully. Em can also remind Anna not to equate lengthy context automatically with avoiding responsibility. Micro-lessons reinforce the structure in errors and delays, so over time an explanation stops sounding like an excuse and starts functioning as information for a decision.