The Blame Reflex
Why the search for accountability often prevents real accountability from taking hold
It usually starts with a simple question.
The words sound reasonable. A request for clarity. An attempt to understand what happened.
Yet the tone and the timing communicate something else entirely.
Someone is about to be held responsible.
You can feel the shift in the room almost immediately. Shoulders tighten, language becomes more careful, and the conversation narrows. Attention moves away from understanding the problem and toward protecting positions.
I see this pattern across organizations more often than people realize. It tends to appear quickly under pressure and feels productive in the moment, yet over time it quietly erodes trust, slows progress, and limits what teams are capable of achieving.
This is edition 3 in an 11 part series exploring the most common forms of organizational friction I encounter when working with leadership teams. Each edition focuses on one pattern that appears consistently under pressure.
In this edition, the focus is on the instinct to assign blame.
I saw a very different version of this pattern play out at home.
Our daughter had just reached the stage where she could move more quickly than we expected. In a brief moment, she launched herself off the bed and hit her eyebrow on the corner of the nightstand. It happened instantly, one of those moments where everything shifts before you have time to react.
My wife’s response was immediate. She was shaken and clearly upset, but what stood out was not just the concern for our daughter. It was how quickly she turned inward. She began to blame herself, and you could see it in how she spoke and how she carried herself.
There was also something else underneath it.
An expectation that I might blame her too.
Nothing had been said. There was no accusation. Yet the anticipation was there, as if the next step in the sequence was already known.
That is what struck me.
The instinct to assign blame is so deeply wired that it does not need to be spoken. It can be felt, anticipated, and internalized.
In that moment, the priority was not to determine what had gone wrong or who was responsible. The priority was to care for our daughter and steady the situation. Once things settled, the cause became clear. She was developing quickly, her movement had changed, and our environment had not yet caught up.
It was not a failure of attention. It was a normal transition that required an adjustment.
The visible event drew immediate focus, but the underlying cause sat somewhere else entirely.
This same pattern becomes far more consequential inside organizations.
In one project I worked on, tensions escalated after a series of missed expectations. A senior leader became convinced that the issue was obvious. In his view, the project manager had failed to build a proper work plan, and the solution seemed straightforward. Create a detailed plan and the project would get back on track.
He expressed that view with certainty and frustration, directing his attention toward the individual he believed was responsible.
When I examined the situation more closely, a different picture emerged. The team already had a detailed plan. It existed in multiple formats and had been in place for some time. The issue was not the absence of a plan. The issue was that a new lead had not taken ownership of it and was not using it to guide the work.
What appeared to be a clear failure in planning was, in reality, a gap in ownership.
That moment created tension because the original explanation was simple and provided a sense of control. Letting go of it required sitting with a more complex and less comfortable truth. Once the focus shifted away from blaming the individual and toward understanding what was actually happening, the conversation changed. Energy moved from criticism to alignment and from reaction to support.
This is the nature of the blame reflex. It offers a fast and satisfying explanation, particularly under pressure, and creates the impression that the problem has been identified and action is being taken.
In practice, it often does the opposite.
It redirects attention away from the system that produced the outcome and toward a single point of failure, whether real or perceived.
When blame enters the conversation, behavior changes immediately. People begin to protect themselves. Information becomes filtered. Risks are surfaced later rather than sooner. Problems grow quietly until they can no longer be ignored. Over time, the organization loses its ability to see clearly and respond early.
Boards often sense this dynamic without always naming it directly. Reports appear structured and complete, and explanations are delivered with confidence, yet the discussion rarely reaches the conditions that produced the result. The focus remains on outcomes and responsibility rather than understanding.
Strong leaders approach these moments differently. They recognize that accountability is not created through blame, but through clarity.
Instead of beginning with the question of who is responsible, they begin with a different question.
What led to this outcome?
That shift changes the nature of the conversation. It opens the door to examining decisions, assumptions, incentives, communication patterns, and context. It allows people to speak more openly about what actually happened and creates the conditions for meaningful learning.
Accountability does not disappear in this approach. It becomes more precise because it is grounded in understanding rather than reaction.
When leaders consistently resist the blame reflex, something important changes. Problems surface earlier, conversations become more honest, and ownership becomes clearer because it is no longer tied to fear.
Many of these patterns are not isolated moments. They are deeply embedded behaviors that shape how teams think, decide, and perform. I explore these dynamics in more depth in my book The Hidden Project Drivers, which officially launches in print this week.
The discipline is simple to describe and difficult to practice.
Resist the urge to assign blame too quickly. Stay with the problem long enough to understand it.
That is where real leadership begins.
Until next time,
Kursten