6
min read

Responsibility is not the blame game

Blame is just responsibility’s awkward cousin who always shows up uninvited. Though mistake is not the issue - not learning from it is.

Responsibility is misunderstood

Let’s get one thing straight: responsibility is not the same as blame.

In too many workplaces, responsibility has been reduced to a game of hot potato — whoever’s holding the issue when it explodes gets blamed. No wonder many want to avoid it.

But here’s the thing — responsibility isn’t about fault. It’s about response. It’s the ability to respond. Response-ability.

In basketball terms, it’s not about who missed the shot or who turned the ball over. It’s about who recovers fast, adapts, and makes the next smart play. The team doesn’t freeze the game and start pointing fingers. They’re moving forward, not stuck in post-mortem mode.

Responsibility is forward-looking.
Blame is backward-looking.

In business, we often confuse the two. We hold "accountability meetings" that are really just retroactive blame sessions. But in reality, the person who takes responsibility isn’t the one who caused the problem — it’s the one who responds to it with action, clarity, and ownership. It’s about influencing the team’s future plays. Stop treating responsibility like a punishment, and start treating it as the willingness to move forward.

Missing personal responsibility

One of the most common ways teams break down is when people wait for someone else to make the next move. That’s what it looks like when personal responsibility is missing — players standing still, looking around, hoping the coach calls a timeout or someone else takes the shot.

In real life, it sounds like:

  • “Can someone make a rule that no one sends emails after 6 PM? It’s too stressful.”
  • “Let’s block everyone from booking meetings during our agile ceremonies.”

In basketball terms, that’s like saying, “When we play defense, the referee cannot blow their whistle.”

Instead of adjusting how we engage — turning off notifications, owning our calendar, protecting our time — we try to redesign the game around our discomfort.

The difference between great players and the rest? Great players don’t wait for perfect conditions. They work their position, manage their space, and stay in the play. They understand what’s in their circle of influence (how they defend, pass, show up) versus what’s just in their circle of concern (the crowd noise, the ref’s calls, the time left in the game).

Personal responsibility means taking the initiative to change what you can — not lobbying for new rules every time things get uncomfortable.

The blame game at the organisational level

At some point, every team drops the ball. Deadlines slip. Features break. Customers get frustrated. That’s just part of the game.

But here’s where things often go sideways: instead of responding, organisations start pointing fingers. They turn postmortems into witch hunts. Suddenly, it’s less about fixing the playbook and more about finding the “culprit.” This is the corporate version of a bench full of players arguing over whose fault the last turnover was — while the other team runs a fast break.

Blame is easy. It’s emotionally satisfying. It gives the illusion of control. But it kills team chemistry. It shifts the focus from learning and adapting to covering your back.

And worse — it teaches people to play it safe. If every mistake gets punished, no one takes bold shots. No one experiments. Everyone just tries not to mess up.

Healthy teams do it differently. They treat mistakes like game film: What did we miss? Where can we adjust? What do we try next? Responsibility becomes collective, forward-looking, and focused on improvement — not retribution. It’s about “what now?” not “who’s fault?”.

When organizations confuse responsibility with blame, they stop playing to win. They start playing not to lose.

The psychology behind avoiding responsibility

If responsibility is so essential, why do smart, capable people avoid it?

Because under the surface, responsibility brings up fear — fear of judgment, failure, being exposed. And when that fear kicks in, it shows up in subtle but powerful ways.

Impostor syndrome

“I shouldn’t even be on the court.”

You’ve made some good plays. People trust you with the ball. But deep down, you feel like you’ve tricked everyone — and any minute now, they’ll figure it out. So instead of stepping up, you hesitate. You second-guess.

Even top performers feel this way. But here’s the truth: you’re already in the game. Earning the opportunity to make it to the team and the game is already a sign of performance not everyone can achieve. The uniform’s on. The ball’s live. You don’t need permission to play — you need belief to keep going.

Procrastination

“What if I take the shot and miss?”

It’s not laziness. Most procrastination is just fear in disguise. Fear of getting it wrong. Fear of not being perfect. So we stall — rewrite the strategy deck five more times, tinker endlessly, or just avoid the task altogether.

In basketball, this is the player holding the ball, looking for the perfect pass, and missing the window. Sometimes, the responsible move is just to take the shot, live with the outcome, and learn.

Locus of control

“The coach, the ref, the clock — they’re in charge.”

Some players believe the game happens to them. Others believe they shape the game by how they play. The second group has an internal locus of control — and they tend to take more responsibility, show more resilience, and grow faster.

It doesn’t mean they control everything. It just means they believe their actions make a difference. And that belief changes how they show up — on the court and in the office.

Knowing that these psychological patterns — impostor syndrome, fear, externalisation — play a real part in avoiding responsibility, we can start showing more empathy. Instead of judging teammates for hesitating, we can recognise the internal battles they might be facing and offer a hand. Sometimes, the most responsible move is helping someone else take their shot.

Cultivating response-ability

Responsibility isn’t a fixed trait — it’s a skill. A mindset. A muscle you build by choosing to stay in the game, even when it’s uncomfortable.

It starts with a simple question:  “What’s the next smart play I can make?”

A former CIA agent explains how to manage the tasks that piled up against you:

  • However many tasks you think you can confidently carry out simultaneously, subtract two
  • Focus on the next simplest task
  • Focus on the task that you can carry out in the shortest amount of time

By following these rules, you’ll accomplish some focused tasks, which help you regain control and confidence that you’re making progress.

You can also search for something that is in the intersection of

  • what needs to be done
  • what you are capable of doing
  • what you will (want to) do

You don’t need to be the team captain or have the perfect plan. You just need to move. Communicate. Adjust. Help your teammates. Protect your time. Own your decisions. That’s response-ability in action.

Here are a few ways to build it, day by day:

  • Watch your zone. Focus on what’s in your control — your attitude, your actions, your next step — not the scoreboard or the drama in the stands.
  • Claim your space. Block your calendar for what matters. Mute the notifications. Speak up when something’s off. If it’s important, protect it like it’s game time.
  • Own your energy. Notice when fear is driving your decisions — and don’t let it. Take the shot even if it’s not perfect.
  • Help others step up. Responsibility isn’t solo. It’s contagious. When you show up, you make it easier for others to do the same.

Because here’s the real game-changer: responsibility doesn’t mean doing it all yourself — it means showing up like it depends on you. And when that mindset spreads across a team, that’s when things really start to flow.

Do you want to subscribe?
Or would you like to discuss the topic?
Get in touch
ARE YOU INTERESTED IN SIMILAR ARTICLES?
TAKE A LOOK HERE:

Send us a message

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Follow us