Originally published in Intranet Journal (24-May-2006)
We all know what's mightier than the sword, but if Spiderman has taught us anything it's that with great power comes great responsibility.
Blogs have become one of the most popular forms of personal expression to emerge on the Internet in years. They have the ability to turn regular users into writers by providing them with an easy-to-use medium in which to express their opinions. Blogs are easy to create and they're easy to broadcast. They can be part of a Web site and syndicated and delivered to readers as an RSS feed.
But there are so many trivial "hobby blogs" on the Internet that were created on a whim. For instance, when a lack of judgment leads you to believe there are more people out there who share your affinity for cheese sculpturing than there really are. Because of this, it has lead some to perceive blogs as a frivolous tool.
As blogs matured, however, organizations of all sizes saw the advantages in using them for marketing and branding purposes. But do they have any practical internal application on corporate intranets? The answer is yes—but they have to be used properly and responsibly.
The bandwagon is a crowded place. Whenever a new technological trend gains widespread usage and support on the Internet, corporate intranet owners or IT seem to find an excuse to implement the same technology internally regardless of whether it's needed or not. Perhaps it's the little kid in all of us that causes our enthusiasm for novelties to overshadow common sense and necessity.
Whether or not organizations can benefit from integrating internal blogs with an intranet boils down to motivation: Why are you doing it and what's it for? Internal corporate blogs are an excellent way to communicate with an organization's employees but intranet owners must have a clearly defined goal before adopting the tool and including it as part of the officially sanctioned intranet. Will it be used to support official business processes, communicate important organization news to employees, provide lighthearted and casual water cooler content, or a combination of all three?
A blog shouldn't be implemented simply for the sake of having one or because everyone on the Internet seems to have one. Finding a reason to have a tool after it's been implemented is sure to lead to misuse and failure.
There's been an ongoing debate about the true productivity of such user-generated content on intranets, and whether they should really be sharing the same space as engineered content. Unlike the relatively formal tone of engineered content, blogs reflect the personality of the author and are usually more conversational—and that's one of its main appeals.
A blog, like e-mail, is simply another form of communication but with one very noticeable difference: E-mail is targeted to a recipient or a group of recipients; blogs are meant to be published for all to read. They lack the wink-wink, nudge-nudge subtleties afforded to recipients of private e-mail messages. Blogs are very public, and bloggers need to realize this.
A blog can be a great way for:
|Corporate level communication||CEO, CIO, CFO, President||Formal|
|Project or contract level communication||Group/project leaders, department heads||Formal|
|Industry news and discussion||Individual employees||Formal or casual|
|Water cooler content||Individual employees||Informal and casual|
Blogs invite open expression on the part of the blogger; it cries out for it. With that in mind, intranet owners and stakeholders must realize that those expressions might not always have the most productive end result. Bloggers might be tempted to make seemingly innocent remarks about the organization's competitors-especially given the false sense of security that comes from believing what's said inside corporate walls stay inside corporate walls. If a blogger's comments were ever to leak out into the public, they can be considered defamatory and land the organization in some legal hot water.
Even though the statements are made independently by an individual blogger, the medium and technology belong to the company. Anything that's written with company resources, on company time, will be considered company sponsored and result in guilt by association. While blogs promote freedom of expression, it doesn't mean bloggers can act recklessly with little regard to the consequences of what they write. They still need to observe the same corporate etiquette that prevents them from pulling their pants down in the middle of the cafeteria.
Before an internal blog is implemented intranet owners need to understand the nuances of blog use, the various tools for reading and writing blogs, and the possible negative impact they may have on the intranet community and the organization. To maximize chances of successful blog integration with the organization's intranet:
A blog isn't an anything-goes communication medium. The limits of what an internal blogger can write aren't imposed so much by technology, but rather by common sense. Bloggers need to realize that what they post can be read by everyone in the company and even possibly leaked out into the public.
Responsible blogging isn't a restriction on bloggers' freedom of expression. It's about writing something of use to the organization's user community while respecting corporate etiquette and content sensitivity. Like any other mass communication medium, blogs are only beneficial if the blogger has something useful and interesting to say.
Copyright © 2006 Paul Chin. All rights reserved.
Reproduction of this article in whole or part in any form without prior written permission of Paul Chin is prohibited.