"It's Not Your Fault" Is Half a Sentence

November 06, 2026

Watch the video version:

Decisions are piling up on your desk again. The week went to meetings. The team waited on you for things they could have settled without you. So you read something about it, or someone you trust tells you, and the message is kind: it's not your fault. You are carrying too much. The organization is under-resourced, the system is broken, and you are doing your best inside it.

When I was learning to lead, I came up against that message constantly. It is the industry default, and it is half a sentence. Every time, I ran into the same wall. If it's not my fault, it's not mine to change; it's not within my control. If it is my fault, and it is what I am doing, then I can change what I am doing in pursuit of different results.

If you lead a technical team, you have heard the default in two versions. The first is "give yourself grace": you are carrying too much, none of this is you, be kinder to yourself. The second is "fix your mindset": reframe the story, quiet the inner critic, choose a different response. The first puts the cause in your environment. The second puts it in your head. Neither one points at what you do on Monday morning. You leave calmer, with no lever, and the problem is still there on Monday.

Here is how it runs. A problem keeps coming back: decisions pile up, meetings eat the week, the team waits on you. The reassurance arrives and says the cause is anywhere except what you do. The relief is real. Guilt drops, and with it goes the only reason you had to look at what you do. So the system runs unchanged. Decisions nobody assigned still route up to you. That is The Escalation Default: the structure never said where they belong, so they go to the safest place, which is you. The standing meeting stays on the calendar. The boundary stays unwritten.

Then the problem comes back. "Not you" has already been spent, so the old explanation returns in its place: I am not good enough for this. Guilt comes back, and so does the next reassurance. Each round costs you twice. First, it costs you now: the constraint sits on you. Every unassigned decision, unwritten boundary, and meeting nothing replaced runs through one person's week, and the reassurance changes only how carrying it feels. You stay the bottleneck, a comfortable one. Then it costs you later: it sits on your belief in your own capability. By the third time the problem returns, the most capable person in the room concludes they are the problem, and either grinds harder at the wrong thing or leaves.

This is not an argument for blaming yourself. Self-blame and absolution make the same mistake: both ask about character, and fault is the wrong question in both directions. Some of what you face really is outside your control. The reorg, the budget, and the headcount are real. The default takes that true sentence and stretches it over things that are inside your control: the decisions you take, the meetings you run, and the boundaries you leave unwritten. Owning those is not a heavier load. It is how the load comes off.

Getting out of this loop does not mean being harder on yourself. It means dropping the question of whose fault it is for a smaller one.

What am I doing that keeps producing this? Answer it in three places, because that is where a leader's own work turns into the system. The decisions you keep taking that nobody assigned to you. The meetings you run that exist only because nothing replaced them. The boundaries you never wrote down. Each answer is an action, never a verdict on who you are. Those actions are the system your team runs on, so each one is a lever you hold today.

Split the problem in two. One column is what happened to you: the reorg, the budget, the headcount. The other is what you are doing. Call that one the Second Column. The first column is real, and it is not where your attention goes next. The second column is. Then pick one move, not a program. The reassurance sells you a program of becoming a better person. The second column asks for one change you can see.

This week has been four answers to that question, one a day. Monday's Exit Line puts an owner and a review date on any system that runs only because nobody decided to end it. Tuesday's Trigger Rule sends news straight to the person it affects, so you hear about it only when two people need a decision they cannot make. Wednesday's Author Test judges a proposal by whether its author can defend it, not by its polish or by how it reads to the most senior person in the room. Thursday's Owner Line gives each recurring decision one written owner, so it stops going to whoever reaches you first. Each one replaces something you were doing with something written down, because whatever isn't written decides anyway.

Take the problem you have been reassured about most often, the one that keeps coming back. Write it at the top of a page and draw two columns: what happened to me, and what I am doing. Be strict: "I don't have enough people" goes in the first column; "I review every pull request myself" goes in the second. Then read your honest answer to "why does this keep happening?" If every reason sits in the first column, you were reassured, not helped. Over the next week, ask your team one question: "What am I doing that makes you bring this to me?" Do not explain, and do not defend. Write their answers in the second column. Pick one, and change it before next Friday.

Before you pick your one move, take the LeadershipOS™ Scorecard. It is free, with no obligation: twelve questions across Decision Load, Escalation Patterns, Cadence and Meetings, and Role and Ownership Clarity that show which part of your second column to move first: https://theleadershiposbook.com/scorecard

Anthony S. Jackson

Anthony S. Jackson

Anthony S. Jackson has spent 30 years inside technical organizations. He is the author of the Architecture Protocol Series: three books on the structural problems technical leaders were never told they would face. He writes the LeadershipOS™ Inner Circle, a monthly printed newsletter for CTOs and engineering managers who design teams that hold under pressure.

LinkedIn logo icon
Back to Blog