A blog about management. code and thoughts about random stuff

Blaming culture

Blaming people is always easy. Either for letting the Amazon forest burn or in a small workplace for doing a little too much of something. In this post I'll touch on how these are related and what to watch out for.

The Amazon rainforest is burning right now as of this writing for over 3 weeks. That's not great. After all, it's often referred to as the "Green Lung" of our Planet. But what's interesting to me is who gets the blame for that. When talking to various people; reading comments on news posts; asking friends — the people that seem to get a lot of blame initially are the farmers who probably laid the fires.

"Don't they know how important the rainforest is for our planet? How could they not care?"

Another example just happened last week at my wife's workplace. Something got messed up in production (it's producing goods, nothing to do with the web), and they produced too much of something. Because of time constraints, they fell behind on something that could have been produced in the meantime. What was scary to me was that from exec level the question that got asked multiple times that day:

"Who did that? Who produced more that there should have been?"

Both examples are very different and have effects on very different scales. But the common theme here can not be overlooked – the theme of how important it is to blame someone. In either case, the blame seems to fall on the easiest target, without questioning what lead to that action in the first place.

For the Amazon forest, the reason lies deeply nested in the political situation they have right now, with a leader who's very willing to burn down the forest for profit. He could care less about the meaning of the forest for the world climate. The people who actually lay these fires often see it as the only way to feed their families and make a living wage. They can turn it into farmland, raise cattle, plant bananas, or other things to have something to sell and don't get crushed by the challenges of capitalism. We often end up buying these things and are complicit, but of course, it's cozier to not think about that. Eventually, the blame, can and should not be put on the farmers alone, as it's a result of a wider system.

At my wife's workplace, it's similar. The issue happened not because someone made a mistake, but the system at that company is incredibly unorganized and somehow this extra order ended up in the production list as it always would, and the whole team worked through it as always. The main issue could potentially be boiled down to the exec level and their unwillingness to put better processes into place and tackle the root cause of the behaviour. Instead they tried to find an individual who's responsible for it, so that in future people always have to question their next actions and confirm if it should actually be done.

What does this all have to do with engineering, as this is mostly a blog about these topics? Let me explain...

The Engineers Perspective

Let's get this whole topic into the perspective of software development and engineering teams. Another field I discover blame regularly. From various friends at companies, to my own experiences, I know how fast this can happen.

I remember personally when I blamed someone for a mistake they've made that basically impacted production. A feature I lead was rolled out in an not ideal fashion, and eventually we had to extinguish a few fires as a rollback wasn't an option. The whole team pulled together and we managed to fix everything in a few hours. Eventually the impact for customers was not as bad as felt initially, but when something goes wrong there's a lot of stress and everything feels horrible and you act under pressure. When talking to my manager back then I blamed one person for kicking it all off and causing all this stress.

Luckily I had good managers throughout my career. In this moment she listened, but also ended up helping me to uncover the real reason for the situation. The engineer did handle with best intent. It was the lack of information about deeper implications of a merge. I as the feature lead just worked under certain assumptions that others knew as much as I did. So if someone was to blame, it was actually me.

I was very happy and appreciative of my manager not blaming me for everything, but helping me to become better at communicating and to avoid working under wrong assumptions again.

Sadly, I've seen the companies that actually have this culture of constant blame, and only the worst people stayed at these places.

Final words

Okay... this post was way more political than originally anticipated, but never the less, I felt good about writing this down. The takeaway should be that blame shouldn't be thrown light-heartedly. Try to understand what's going on, what's the root cause and then maybe try to solve the problem without blame at all. Unless the root cause is the president of Brazil. It's totally fine to blame asshats!

Subscribe to Codebryo.com

Sign up now to get access to the library of members-only issues.
Jamie Larson