|
|
|
|
|
|
Avoid Common Blogging Blunders, Part 1
Go to page: 1 2
Printer Friendly Version
When we look at an organization's Web site, we know that its design and content have been painstakingly thought out, developed, and written. The site is carefully polished to provide users and potential clients with the organization's best face, describing who they are and what they do. Blogs, on the other hand, are a much more personal, informal, and intimate medium. But this doesn't mean that a professional blog doesn't require the same strategic approach. Professional blogs need the same forethought as a conventional Web site -- and you can have a lot more fun with a blog.
If a conventional Web site is an organization's face, then a blog is its voice. And organizations need to use this voice carefully and responsibly by avoiding common blogging mistakes.
Using blogs as substitutes for conventional Web sites
Setting up a blog is so easy. Tools such as Wordpress and Blogger allow you to put a blog together in no time with very little design and development experience. This can be both a good thing and a bad thing. It's good when what you want is actually a blog; it's bad when what you want is actually a conventional Web site.
Conventional business Web sites require you to design something from scratch. Everything from site cosmetics to navigation to content structure must be decided. Blogs, on the other hand, provide you with an established template and tools for content posting, content organization, and calendar-based navigation.
But conventional Web sites and blogs serve different purposes. A blog is used to publish serial content, and it drives my batty when I see businesses use a blog as a substitute for a conventional Web site simply because they want to avoid confronting the issues associated with developing a conventional Web site. They end up putting static information about themselves and their business on
If you want to comment on these or any other articles you see on Intranet Journal, we'd like to hear from you in our IT Management Forum. Thanks for reading.
Not standing behind what you write
Blogs, unlike conventional Web sites, take on the voice, personality, and sometimes the opinion, of its author. It's with these that the overall tone of the blog, and the reputation of the blogger, is set. But bloggers need to understand that anything written in a public forum will be open to criticism. They have to have thick enough skin to handle this criticism and not take negative comments too personally.
If bloggers are timid and don't stand behind their words, allowing critical readers to get under their skin, they will lose their voice and begin to allow others to dictate what they write. Bloggers who back off every time they're confronted and challenged by a reader will lose all credibility and will reveal to the blogosphere that their backbone is softer than a wet noodle.
Posting anonymously
Bloggers who try to give their organization a face by hiding their own seems counterintuitive. Once you find your voice as a writer and a blogger, don't be afraid to let the blogosphere know who you are. A blogger/reader connection can't be formed when the reader doesn't even know who the blogger is. Bloggers should avoid posting as an anonymous entity or under the organization's name... How can an organization write a blog? Is it some giant collective hive mind thinking and speaking in unison? I don't think so.
| ||||||||||||||||||||||||||||||||||||||||||
Intranet Journal's Tutorials |
|
Managing Editor |