The Blame Node: Why Every Failure in the Building Still Feels Like Yours to Own
Two weeks ago I introduced the Origin Code - the set of implicit rules your nervous system wrote about safety, worth, and belonging long before you held a job title. Last week we opened the first file in that code: the Over-Functioning Mandate, the rule that ties your worth to your output and convinces you rest has to be earned. This week we open the second file, and it's the one that shows up not when things are going well, but the instant they stop: the Blame Node. The rule, stated simply, usually sounds something like if something in this organisation has broken, I am the reason, whether or not I was in the room when it happened. Its enforcement mechanism is faster than thought - a flash of personal fault that arrives before anyone has established what actually went wrong.
The Reflex That Arrives Before the Facts Do
Accountability, properly understood, is an analytical act. It requires information: what happened, who held the decision, what was reasonably foreseeable, what wasn't. The Blame Node skips all of that. It doesn't wait for the postmortem. It fires the moment a deal collapses, a team member resigns, a launch slips, or a board member asks a pointed question in a meeting you didn't even attend - and it fires as certainty, not hypothesis. You don't think I might have contributed to this. You think this is mine, fully formed, before a single fact has been checked.
This is measurably different from garden-variety conscientiousness. A conscientious leader reviews the facts and then decides how much of an outcome was genuinely theirs to own. The Blame Node inverts the sequence entirely - the verdict arrives first, and the facts, if they're gathered at all, get selectively read to confirm it. That's the signature: if your sense of fault is fully formed before the debrief has even been scheduled, you're not exercising judgement. You're executing an old instruction.
Guilt and shame aren't interchangeable, and the difference explains why this reflex is fast rather than careful. Guilt says I did a bad thing - specific, proportionate, and open to evidence. Shame says I am the bad thing - global, instant, and closed to evidence, because the verdict and your sense of self arrive as the same package. The Blame Node doesn't run on guilt. It runs on shame. That speed gap is architecture, not a personal failing. The threat-reading part of you fires and returns a verdict before the slower, language-based part that would actually weigh the evidence has finished loading the facts - a superb setup for outrunning a predator, a poor one for allocating blame accurately in a board meeting. That's precisely why it never waits for the postmortem: there's nothing to investigate when the conclusion was never really about the event in the first place. It was about a much older, much more totalising question - am I the problem - that got answered a long time before this quarter's numbers came in.
That certainty isn't a character trait. It's a compiled instruction, the same way the Over-Functioning Mandate was. For many executives, the Blame Node was written in a household where someone had to hold responsibility for the emotional weather in the room - where conflict, chaos, or a caregiver's distress needed an explanation, and providing one, even at your own expense, was the fastest route back to stability. Claiming the blame first wasn't submission. It was strategy. It let a child convert an unpredictable situation into a predictable one: if I am the reason, I know what happens next, and I might even be able to fix it. Predictability, to a child with limited power, is its own kind of safety. For others, the code was written slightly differently - not as the child who volunteered responsibility, but as the one who was assigned it, the designated explanation for whatever went wrong in the house, fairly or not. Either route compiles to the same adult instruction: fault defaults to you until proven otherwise, and proving otherwise never quite feels like your job.
The problem, as always with the Origin Code, is that the instruction never checks whether the current environment still needs it. A board isn't your childhood household. A missed quarterly number is not evidence of your fundamental unworthiness. But the Blame Node doesn't run a fresh risk assessment each time. It runs the same subroutine it always has, and it runs it in milliseconds, long before your actual judgment - the thing you're paid for - gets a turn to speak.
Why the Blame Node Compiles Stricter for Queer Leaders
If you're an LGBTQ+ executive, there's frequently an additional layer here, which I want to name directly rather than gesture vaguely towards. For many queer people, especially those who came out into families, schools, or workplaces that weren't ready for it, a specific and painful lesson often got learned early: your existence, or the parts of it you couldn't hide, generated discomfort in other people, and you were, implicitly or explicitly, held responsible for managing that discomfort. Not causing offence. Not creating tension. Being, in effect, accountable for other people's reactions to who you are.
Family isn't the only place this compiles, either. Many queer leaders carry a second, more literal version of the same lesson from school: childhood bullying tied directly to being visibly different, where peers, and sometimes the adults meant to intervene, treated your identity as the provocation. Children who are bullied overwhelmingly reach for the same explanation, because it's the only one that leaves them any sense of control: it must be something about me. If I were different, quieter, smaller, less myself, this wouldn't be happening. That conclusion is rarely accurate, but it is remarkably efficient - it converts a situation with no good options into one with an action plan, however punishing. It's the same trade the Blame Node makes as an adult: certainty over accuracy, control over correctness.
That is an enormous amount of responsibility to hand a child, and it tends to generalise. If you were once made to feel accountable for feelings you didn't create, it becomes a short step to feeling accountable for outcomes you didn't cause. The logic, rarely stated out loud, runs something like: if I take the blame first, at least I control how this lands, instead of waiting to find out how badly I'll be blamed anyway. Pre-emptive self-blame becomes a form of damage control learned in an environment where the actual damage - rejection, ostracism, a relationship withdrawn - was a real and serious risk.
In an executive seat, that same reflex reads, to everyone around you, as extraordinary ownership. You'll likely be praised for it. But underneath the praise is a leader quietly absorbing fault that was never actually theirs to hold, at a cost that compounds every time it happens. That inversion has a real cost in the room, too, and not just to you. A leader who reflexively absorbs blame trains their team, however unintentionally, to let them. Reports stop flagging their own contribution to a miss because the boss will apparently claim it anyway. Peers stop offering the fuller picture because the conversation already feels over before it started. The Blame Node doesn't just misallocate fault internally - it quietly degrades the quality of information reaching you, because nobody feels the need to correct an account that was never going to be examined.
Where the Blame Node Actually Fires
You'll rarely catch this one in the abstract. It shows up in specific, repeatable moments: apologising, unprompted, for a delay a vendor caused. Opening a postmortem with your own failings before a single piece of data has been reviewed. Feeling a genuine, physical drop in your stomach when a peer's project underperforms, even though it was never yours to run. Absorbing a resignation as evidence of your leadership failure before you've had a single conversation about why the person actually left. The instinctive urge to speak first and worst about yourself in a room that hasn't yet formed an opinion, so that whatever criticism might be coming arrives pre-empted by your own. None of these moments look like distress from the outside - they usually look like humility, or maturity, or the kind of leader who takes the hit for the team. That's exactly why the Blame Node is so durable. It gets rewarded, repeatedly, by a culture that mistakes reflexive self-blame for accountability.
Two Ways to Separate the Reflex From the Fact
As with the rest of this work, insight won't move this on its own. You have to catch the Blame Node firing in real time, in your own specific situations, before you can start correcting its output.
The Attribution Audit
Execution: For the next two weeks, every time you feel that flash of personal fault, write down the trigger and the immediate thought that followed it - not the polished version, the raw one.
Action: Once the facts are actually available - after the postmortem, after the real conversation - go back to each entry and write down what was genuinely yours: your decision, your delegation, your blind spot, and what wasn't. Be as specific about the second column as the first.
Target: A running, evidenced record of the gap between what the Blame Node claims instantly and what turns out to be true - the raw material for recalibrating the reflex itself.
The Root-Cause Pause
Execution: The next time something breaks and you feel the urge to claim it publicly before the facts are in, wait. Not indefinitely - until the next relevant conversation or meeting, whichever comes first.
Action: Use that window to gather one piece of actual information about what happened before you say anything about whose fault it was, including your own.
Target: Direct, repeated evidence that a short delay costs you nothing in credibility, and frequently produces a more accurate - and more useful - account of what actually needs to change.
Owning What's Genuinely Yours
None of this is an argument for dodging accountability, and I'd be doing you a disservice if I let it read that way. Real accountability is a genuine strength, and very likely part of why you're in the seat you're in. The work here is precision, not avoidance - separating the failures that are actually yours, which deserve your full and immediate ownership, from the ones the Blame Node has been claiming on reflex, which only ever cost you capacity you needed for the problems that were genuinely yours to solve.
Next week, we open the third file in the code: the Silent Operator, the strategy of staying so competent and so quiet that nobody looks too closely - and the cost of a leadership style built on never being examined at all.
Schedule a confidential consultation to find out how I can help you locate and rewrite the code still running your leadership from the inside.
