The Process of Blame: Why Fast Thinking Breaks Slow Systems
- Chris Terrell
- Dec 19, 2025
- 3 min read
Every week on the Process Debt Podcast, Toby and I sit down, hit record, and talk about whatever rock we’ve been flipping over lately.
This week, that rock was blame, specifically, why it’s so easy to point fingers and so hard to fix anything. And it hit a little too close to home. Because if you’ve ever worked in an organization (or had a teenager), you know blame shows up fast.
And that’s exactly the problem: blame is a fast-thinking reflex shoved into a world that desperately needs slow-thinking process.
Where Blame Comes From
We have just recently lived through the latest government shutdown — and not a single press conference sounded like, “Here’s how we’ll prevent this next time.” It was all finger-pointing, all day long. No ownership, no curiosity, no slow thinking. Just: They did it to me.
Daniel Kahneman calls this System 1 thinking — the fast, instinctive, jump-to-conclusions brain we inherited from millions of years of trying not to get eaten. It’s useful when a bear is chasing you. It’s terrible when your accounting system is.
Blame becomes the defensive maneuver that protects us from discomfort: the discomfort of uncertainty, the discomfort of being wrong, the discomfort of not knowing the process we’re supposedly responsible for.
And in knowledge work, where so much of what we do is muscle memory, it’s easy to forget the why behind the button we click. When something breaks, we don’t diagnose — we deflect.
The Missing Ingredient: Slow Thinking
A friend of mine, a veteran program manager turned product leader, once said the hardest part of process change is that people don’t know their process. They know their tasks. They know their buttons. But ask where a transaction starts and where it ends? Blank stares.
This is the heart of process debt: we’ve automated so much without ever understanding the sequence underneath it.
So when something goes wrong?
“Oh, that system is broken.”
Cool.
Which part?
Why?
What changed?
What evidence do you have?
Fast thinking gets you to a scapegoat. Slow thinking gets you to the source.
The Real Cost of Blame
Blame spreads because it’s rewarded. Fire starters get attention. The person quietly fixing a root cause? They don’t show up in Slack with a gif of a dumpster fire, so nobody notices.
But here’s the irony: the best managers — the ones people would follow into chaos are the ones who absorb blame rather than weaponize it. They take responsibility so their teams can operate without fear. They slow the thinking down.
Blame flourishes anywhere people lack authority. If I'm responsible for a broken step but not allowed to fix it, what tools do I have left except excuses? Modern software makes this worse — it disenfranchises people from their own work. We’ve become button-pressing tippy birds from The Simpsons, and then we wonder why accountability evaporates.
And because organizations hate ambiguity, people learn to react. “Just give me an answer.” That pressure breeds shortcuts, not clarity.
Fixing Process Means Making Boring Valuable
Here’s the twist: the antidote to blame isn’t discipline — it’s boring.
Slow thinking looks like:
pulling up a “clean your room” dashboard
verifying delivery dates
checking that fields are filled in
confirming that the process is still the process
None of this wins awards. But it’s the social glue that keeps systems from drifting.
One of my favorite examples was a team that celebrated finding bugs by naming them. They turned what could have been blame into a game. Why? Because finding issues early meant customers didn’t feel the pain. Boring is a feature.
Our own team rotates meeting ownership for the same reason. Every time someone else drives, they expose a faster way, a missing detail, or an insight hiding in plain sight. The meta-process gets stronger because the people inside it get smarter.
The Process Debt Truth
Blame is fast. Fixing is slow. And organizations that never slow down stay stuck in the same chaos they keep blaming others for.
Make your meetings a little more boring, a little more consistent, and a lot more grounded and watch how quickly the fires stop needing to be started in the first place.



Comments