The Impact Cycle Specifically Includes All Except The Following Steps

Okay, let's talk about the Impact Cycle. Sounds important, right? Like some serious business mumbo-jumbo that's going to change the world. And maybe it is! But let’s be honest, sometimes these “cycles” feel more like going around in circles. Anyone else?

The Steps We Know and (Kind Of) Love

So, the Impact Cycle. Apparently, it's got all these crucial steps. Things like identifying a problem, planning a solution, actually doing the thing, and then reflecting on how it went. Makes sense, on paper anyway. They even throw in words like implementation and assessment to make it sound extra official.

We nod along in meetings. We pretend to understand flowcharts. We maybe even take notes that we’ll never look at again. We’re good at this, aren't we?

The Missing Step (According to Me, Anyway)

But here’s my unpopular opinion: there’s a step missing. A vital, crucial, absolutely-essential-for-sanity step that nobody ever mentions. And that step is…

…Blaming Someone Else.

Okay, okay, hear me out! I know, I know, it sounds terrible. We’re all supposed to be accountable and take responsibility. And of course, we should! In theory.

But seriously, after all that hard work? After all that planning and implementing and reflecting? Sometimes you just need to vent. You need someone to agree with you that it wasn’t your fault the project went sideways. Maybe the budget was too small. Maybe the instructions were unclear. Maybe a rogue squirrel chewed through the internet cable at the exact moment you were trying to upload the final presentation.

These things happen!

And let’s be real: isn’t a little bit of blame-shifting inherent in the "reflection" phase? Like, “Well, I thought it was a great idea, but the team just didn’t quite grasp the concept.” Subtle, I know. But it’s there. Lurking.

The Guilt-Free Blame Zone

I’m not advocating for a full-blown blame-fest. We’re not trying to start a revolution here. Just a little acknowledgment that sometimes, things go wrong for reasons beyond our control. And sometimes, it’s really nice to have someone to blame for it. Ideally, someone who isn't present. And preferably a hypothetical someone.

Think of it as a pressure valve. A safety release. A momentary lapse in professional judgment that allows us to move forward with renewed vigor and absolutely zero personal responsibility for past failures. (I’m kidding! Mostly.)

Of course, the Impact Cycle gurus will tell you to focus on solutions, not problems. To learn from your mistakes. To grow and evolve and become a better version of yourself. Blah, blah, blah.

And sure, that’s all well and good. But sometimes, you just need to say, “This wouldn’t have happened if Brenda had just sent that email on time!” And then maybe Brenda will feel bad, or maybe she'll have a perfectly legitimate excuse (rogue squirrel?), but either way, you’ll feel a tiny bit better.

So, the Impact Cycle might include identifying, planning, implementing, and reflecting. But in my slightly-unhinged, definitely-not-professional opinion, it should also include a healthy dose of completely guilt-free, utterly cathartic, entirely-between-friends blame-shifting. Don't tell Stephen Covey I said that.

The Moral of the Story (Sort Of)

Look, I’m not saying we should all become professional blamers. The world doesn’t need more negativity. But a little bit of lighthearted finger-pointing? A little bit of "it wasn't my fault" camaraderie? I think it could actually make the Impact Cycle a whole lot more impactful. Or, at the very least, more bearable.

So, next time you're going through the Impact Cycle, remember to add that extra step. You know, the one where you privately (or maybe not so privately) decide whose fault it really was. You’ll thank me later. And so will your therapist. You're welcome.

Just kidding! (Mostly.)