Do Work & Blogging Mix?
Via Boing Boing.
This list of people who got fired for blogging, and companies that have fired employees for bloging it pretty interesting. The first story I saw about someone getting fired for blogging was Michael’s post about his termination after his employer read a particular post on his blog. Michael has also posted about other people getting fired for blogging. Of course, there was also, Jessica Cutler (a/k/a Washingtonienne), who’s blogging about her sexual exploits with politically powerful, married men got her fired from her Capitol Hill job. And let’s not forget one of the latest, Queen of Sky, the flight attendant who got fired for blogging. Most recently (another one from Boing Boing that apparently came up while I was writing this) a major British bookstore chain fired an employee of 11 years for remarks made about his workplace on his blog.
The blog post in which this list appears also features the following declaration:
International Bloggers’ Bill of Rights
We, the inhabitants of the Blogosphere, do hereby proclaim that bloggers everywhere are entitled to the following basic rights:
FREEDOM TO BLOG.
FREEDOM FROM PERSECUTION AND RETALIATION BECAUSE OF OUR BLOGS:
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.Blogophobic companies, who violate the Bloggers’ Bill of Rights, will be blacklisted by millions of bloggers the world over.
And so an interesting new term enters our lexicon: blogophoic.
I never got fired for blogging, myself, though I did get a stern talking-to about it at my previous job. And I actually fall into what is, as far as a I can tell, the much rarer category of people whose blogging helps get them jobs.
It’s all got me wondering about something. More people are blogging and more people are reading blogs. It’s one of those things that’s still new enough that the lines are somewhat blurred, and one has to guess what crosses them and what doesn’t. It’s also one of those things that has been around long enough now for people to start figuring this stuff out.
A while back, I wrote this:
Businesses need to realize that their employees are going to blog whether they want them to or not. Just like employees are going to send personal emails and make personal phone calls from time to time on the job. Companies should come up with policies on blogging, make them known company-wide, and spell them out for every new employee. In fact, giving employees blogs through the company might be a good idea, and might generate some inexpensive PR.
But what should a corporate policy on blogging look like? That’s something I never quite got back to wrapping my brain around but seeing this list of people who were fired for blogging got me thinking about it again.
Well, it depends a lot on the employer. Some employers might opt for a “no blogging at all, business or personal, etc.” It would be laughable at best, because it would have the same effect as “no personal phonecalls” and “no personal emails.” Everyone knows these things are going to happen in the workplace. It’s inevitable. It’s a matter of degrees, and shouldn’t be an issue unless it reaches a point at which it impedes performance. The same should apply to blogging, in some fasion. If an employee spends all day on his/her blog, and neglects his/her work, then it’s obviously a problem. If an employee blogs and manages to do his/her job, then all that might be necessary is to warn against “excessive” blogging, as is often done with personal emails and phone calls.
A “no blogging” policy all but ensures that down the line an employee will blog and will—if the policy is to have any meaning at all—will have to be fired. And it’s just possible that the circumstances will not necessarily show the employer in the best light, though they may be entirely justified. As I said earlier, more people are blogging and more people are reading blogs. An employee fired for blogging will more than likely blog about his/her termination, and that story will make its way around the internet from blog to blog, until employer establishes a reputation and winds up on a list of “blogophobic” companies. As blogging becomes more common and more popular, such a list might not be the most desireable place for a company’s name to appear.
Then there’s the matter of content. It probably doesn’t need to be said that employees should be very selective when it comes to blogging about things related to their employers, if they blog about such things at all. That it probably doesn’t need to be said means that it actually must be said, because if it isn’t the day will come when an employee called on the carpet because of something on his/her blog points out that it wasn’t said. And though we live in the era of at-will-employment, it’s can still get messier than anyone wants to have to deal with. Spell it out, and invite your employees to come to you with questions if they’re not sure. Of course they can only do this if you have a blogging policy and you’re open about it.
It’s easy to think that what you write on your blog is fairly anonymous. But the truth is, unless you blog anonymously, then it isn’t. Blog about your employer, or people that you work with, and I promise you the hairdresser of the sister of the best friend of the woman who’s in the bookgroup of your boss’s wife’s next door neighbor will read it, and it will find it’s way back to the original subject. It’s best to assume that there are no degrees of separation if you put your name and your face on your blog. And even if you blog under a pseudonym, enough identifiable details can still land you in an uncomfortable meeting that involves a lot of squirming on your part. If you should come out of it with you’re job intact, don’t breath a sigh of relief because you are still being watched and peoplewill be waiting for the other shoe to drop. And you’ll have to be careful not to slip-up drop it.
From an employee’s point of view, no matter what the case, these days it’s better to be circumspect about what one blogs, and to assume that whatever you blog about will eventually be read by someone you know, or someone who knows you.
For employers, assume that your employees are going to blog, and establish clear guidelines to guide them should they choose to do so. Make the penalties for not abiding by the policy clear, such as under what circumstances an employee will be warned and under what circumstances an employee will be terminated where blogging is concerned. And, of course, one of the best things to do is to set an example by starting a company blog if appropriate.
All of the above would seem to be common sense. But the reality is that much of what we consider common sense today wasn’t always such. It had to be invented as circumstances and developments required, and then spread around to the point of becoming common. Consider this my humble contribution to furthering that process.


January 10th, 2005 at 9:47 pm
This is a tough one for me because I blog and for many years I ran a restaurant and I know how I would feel if one of my employees blogged about me. But the fact is you’re at work to work. Yes we all take personal phone calls and we all send emails that we shouldn’t but in the end blogging is so much different. When you bitch to your friend on the phone about your asshole boss you’re venting to a friendly ear but when you blog about your asshole boss you’re sharing your personal garbage with the world. Its out in the public for all to see and will be there for years to come and for all to write about it.
Work is work and your personal live is just that personal. Yes I know work is part of who you are but some things are best not talked about publicly. Should I blog about the fact that Ed our IT guy is banging the red head in accounting? No… Should I mention my boss keeps a bottle of scotch in his lower left hand desk drawer? No… Its ok to share these with you other half or even whisper to another coworker but publishing them in an open forum is too much and anyone that does so is asking to be fired. (Or worse)
Michael is a friend of mine, and the second I saw “those pictures” I knew, I KNEW the shit would hit the fan. I have on several occasions sent him a personal, email and said stop and think about what you’re doing, you’re going too far.
We bloggers, all of us, need to stop and think about the power we have in our hands. How quickly our words can travel around the world and back again. And with that power come responsibility. Any well read blog (like this one) has as much, if not more power than most daily papers. The WORLD is watching. How many people in Europe read the Seattle times every day? How many people in Europe read this blog everyday? I venture to guess whatever the number it’s greater than the Seattle times.
I once told an assistant manager of mine that liked to write ranting emails to employees. Never write anything you wouldn’t be prepared to read out loud in a court of law in front of a jury. And I stand by those words for bloggers. Its not the fear of being sued it’s the law of common sense. If twelve average people are offended by what you wrote than you’ve overstepped the line. And I can assure you. Regardless of how funny you thought it was. Large companies and Corporations do NOT have a sense of humor.
Keep work at work. It’s not the right topic for an open public forum. Or if you must write about work speak in general terms. I work in Insurance is fine. I work for a slave driving motherfucker at State Farm in is not.
For me the line isn’t blurry at all.
When your at work, your employer is paying you to work, and expects a standard of behavior. You agreed to it when you were hired. So turn off the net surfing and stop the commenting because you have work to do.
You can play when you get home. And play nice.
Everybody is watching.