Most conflicts in organizations aren’t actually about the problem.
They’re about who caused it.
The moment something goes wrong, a familiar sequence begins. People start positioning. Protecting. Explaining why the thing that happened wasn’t their fault, or at least wasn’t only their fault, or at least wasn’t as much their fault as someone else’s. The conversation that should be about moving forward gets consumed by a debate about the past.
And the problem doesn’t get solved because everyone’s too busy making sure they’re not the one who gets blamed.
Here’s a distinction that I think changes everything in these moments: fault and responsibility are not the same thing.
Fault looks backward. It assigns causation. Its purpose is to answer the question: who did this? And while there are absolutely situations where that question matters — genuine misconduct, serious ethical violations, situations that require accountability with real consequences — fault is a remarkably poor tool for most of the conflicts that actually show up in organizational life.
Responsibility, on the other hand, looks forward. It answers a different question entirely: what do we do now, and who owns what part of that? Mistakes happen; who makes them matters far less than understanding how the mistake happened in the first place — and what needs to happen next.
When you take fault off the table and replace it with responsibility, something interesting happens. The energy in the room shifts. People stop defending themselves and start engaging with the actual problem. The conversation that felt like a courtroom starts to feel like a collaboration.
This doesn’t mean you can’t examine what went wrong. You absolutely can — and should — look at what decisions were made, how they were made, and what could be done differently. But there’s a meaningful difference between asking, “What decision led to this outcome?” and saying, “You made the wrong decision, and this is your fault.” One opens a conversation. The other closes it.
I think about a sequence from The Big Bang Theory — Season 2, Episode 14, “The Financial Permeability” — that captures the opposite of this beautifully. Sheldon loans Penny a sum of money — completely matter-of-factly, with no strings attached, no expectation of a timeline, and no emotional weight whatsoever. For Sheldon, it was simple: she needed money, he had money, the transaction made sense.
For Penny, it was anything but simple.
She couldn’t stop thinking about it. Couldn’t stop judging every decision she made in light of it. The debt sat on her like a weight, coloring every interaction, making her feel like she was constantly falling short — even though Sheldon hadn’t said a single word to make her feel that way. The judgment was entirely her own.
This is one of the most underappreciated dynamics in conflict: the person who seems most resistant, most defensive, most difficult to reach — is often in the middle of a conversation with themselves that the leader can’t even see.
They’re not fighting you. They’re fighting their own self-judgment. And the harder you push on fault, the more ammunition you give that internal critic.
Which means one of the most powerful things a leader can do in a conflict isn’t to assign blame more precisely. It’s to remove the conditions that make self-protection necessary in the first place. To make it safe enough for someone to say: yes, I was part of this, and here’s what I’m going to do about it.
That’s the shift from fault to responsibility. And it changes not just how conflicts get resolved, but whether they get resolved at all.
Not everything is your fault. But if you’re the leader in the room, the path forward is almost always your responsibility.
If you’re navigating a conflict — on your team or within yourself — and you’d like a thought partner, I’d love to connect.
Photo by Pavitra Baxi on Unsplash
