Directory · B
Not sure this is the right entry? Run the check · New here? Start with the premise
Blame
1 min read · 293 words
Blame is the search for a cause being quietly redirected away from you. It protects the story you hold about yourself, and it costs you the actual explanation.
Is this you?
Check whatever lands. Nothing is sent anywhere.
Blame is the identity defense system redirecting the source of a problem from inside the control room to outside it.
Something went wrong. The system needs to locate the cause — this is how the software processes negative events, by identifying what produced them so the pattern can be avoided. But locating the cause inside the control room — my decision, my error, my pattern — activates the identity defense protocol. The file on who I am resists the entry. If the cause is mine, the story takes damage.
Blame routes around this by locating the cause in someone else’s machinery. They caused this. Their failure produced the outcome. The system’s internal model remains undamaged. The identity file is intact. The cost is that the actual cause — which may be partially or entirely internal — goes unaddressed.
This doesn’t mean all blame is deflection. Sometimes the cause genuinely is external. Another system’s behavior genuinely produced the outcome. The distinction is whether the assignment is accurate or protective.
The diagnostic: does the blame resolve when examined, or does it intensify? Accurate blame — the identification of an actual external cause — tends to produce clarity. The problem is located. The response can be calculated. The one at the controls has data to work with. Protective blame — the deflection of internal cause to external target — tends to produce escalation. The more the blame is examined, the louder it gets, because the escalation is serving the defense rather than the analysis.
If the blame is running hot and getting louder, check what it’s protecting. What internal cause is the identity defense system trying to route around? The answer is often more useful than the target the blame selected.
A defence wearing the costume of analysis
Something goes wrong and your system needs to locate the cause — that's a reasonable process, and it's how patterns get avoided in future. The problem arrives when the cause sits inside: my decision, my error, my pattern. That entry activates the identity defence, because if the cause is yours, the story takes damage.
Blame routes around it by locating the cause in someone else's machinery. They caused this. Their failure produced the outcome. Your internal model stays undamaged, the file stays intact — and the actual cause, which may be partly or entirely yours, goes unexamined.
What makes it hard to catch is that it doesn't feel like a defence. It feels like analysis, and it often has real evidence attached, because other people usually did contribute something. The tell isn't whether the blame is accurate; it's that the analysis only ever runs in one direction.
There's a cost beyond the unexamined cause. Blame produces relief, which reinforces it — identifying a culprit closes the question and the discomfort stops. So the habit strengthens with use, while the pattern that actually produced the outcome keeps running.
Run the analysis in the other direction
For something recent you've already assigned a cause to.
Real questions
What's wrong with blaming someone who actually is at fault?
Nothing, if the analysis continues afterwards. The problem isn't accuracy — other people frequently do contribute — it's that blame tends to terminate the investigation the moment a culprit is found. You get relief, the question closes, and your own contribution goes unexamined. Someone can be genuinely at fault and you can still be the only person positioned to change what happens next.
Why does blaming someone feel so good?
Because it closes an open question and protects the story you hold about yourself in one move. Locating the cause outside means the identity file takes no damage, and the discomfort of an unresolved negative event stops. That relief is reinforcing, which is why the habit strengthens with use — and why the strongest blamers are often people who'd find the alternative most costly.
How do I tell blame from accurate analysis?
Check whether the analysis ever runs in the other direction. Accurate analysis finds causes wherever they are, including inside. Blame reliably terminates at your edge, and it does so while feeling like reasoning and often while carrying real evidence. The asymmetry is the signal, not the content — if your account of problems consistently ends outside you, that's a pattern about the method rather than about the world.
What about self-blame — is that better?
It's usually the same mechanism running inward, and it's no more accurate. Global self-blame produces a verdict rather than an explanation, and it's equally resistant to correction — people who do it will argue against evidence that something wasn't their fault. What's useful is neither direction but specificity: what actually caused this, in what proportions, and which part can be changed.
Why do couples and teams get stuck in blame?
Because each side is running the same protective mechanism, and each has real evidence. Both accounts are partly accurate, both terminate at their own edge, and the argument becomes about whose story survives rather than what produced the outcome. The thing that breaks it is unusual and effective: one person naming their own contribution first, without conditions attached to the other doing the same.
How do I stop blaming people?
Not by trying to stop the impulse, which fires before you've decided anything. Add a step instead: after you've located the external cause, write what you contributed, assuming the other person behaved exactly as they did. It's a small discipline and it's uncomfortable in a specific way — the discomfort is the identity defence, and noticing it is most of what makes the habit visible.