Ensight – Jeremy Wright

I’ve been mulling over what my recent firing means to me. I’m not really angry at my previous employer. And I know there are lessons to be learned here.

However the lessons aren’t as simple as some people might think. It’s not enough to simply say “don’t post about work”. Because people have been fired for blogging about personal things as well.

And it’s not enough to say “don’t blog about anything controversial”, as others have said. I’m not going to cheapify this issue by saying “what about Freedom of Speech?!” Because it doesn’t matter. Whether you’re right or wrong fired is fired. And it’s generally not worth fighting the issue after the fact.

The recent release of the Blogger’s Bill of Rights has had me thinking even more.

Is it a good idea? Sure, it’s a great idea for advancing the discussion. But, I don’t feel that it really gets to the core of the issue. The Blogger’s Bill of Rights is too defensive. Too “save us from thy wrath”. Here’s an example:

1.) If an employer wishes to discipline an employee because of his/her blog, it must first establish clear-cut blogging policies and distribute these to all of its employees.
2.) Blogging employees shall be given warning before being disciplined because of their blogs.
3.) NO ONE shall be fired because of his/her blog, unless the employer can prove that the blogger did intentional damage to said employer through the blog.

All of these make sense in and of themselves. But, really, it’s an employer’s job to look out for their best interests – both as a company and as individuals. If you were to say something over the phone to someone which caused your boss offense you could quite easily be fired. Even if it did no damage to your company. And even if you hadn’t been warned before about the costs of saying stupid things on the phone.

Really, this all comes down to discretion and risk. Opening your mouth carries a risk. Whether you’re talking to a friend, writing an article or blogging. Everything you do carries a risk that someone will be offended. So, you have to use discretion and common sense.

In my case, I wrote a post, weighed the costs and posted it. There were a few laughs around the office (because everyone had been there) and we moved on. But, a year later the post bit me in the ass.

The reality is that everything you say could offend someone. The fact that I just said ass could have gotten me fired by a different boss.

Part of blogging is knowing you’ll be read, knowing you are going to offend people and knowing there will be consequences.

But part of blogging is also knowing that you are exposing yourself to a vast network of new friends, contacts and opportunities. And you have to decide for yourself which is more important. Will you reign back your controversial stuff for a personal and private blog which nobody but your friends can read? Will you let loose anonymously? Will you attach your name to everything and let the chips fall where they may?

This is a personal decision. And, to me, not one that anyone can judge as stupid or whatnot. Stupidity is not considering the issue. Disagreement and healthy discussion comes when people simply don’t agree and can work through things to grow.

And that, really, is what blogging is about. Lots of people disagreeing. Lots of people talking. And, hopefully, lots of people learning.

My lesson learned? When I talk, people listen. And some of those people will get upset. I need to learn to either engage them in healthy discussion or (if that isn’t possible) to ignore them and move on. Because I’m not going to stop blogging and I’m not going to stop being myself. So I need to learn to deal with the consequences as they come and enjoy the massive benefits that blogging brings.