In recent posts I have been talking about how companies are effectively using a company blog to reach out to their constituents and receiving comments and feedback as a result. They are building relationships, which is great for a company. In many of the articles I have read on corporate blogs IBM has been mentioned, so I decided to research more about IBM. What I found was somewhat interesting because their blog had a different feel. In the article Corporate Blogging Best Practices the author talks about how IBM encourages their employees to openly blog internally and externally. IBM has a community blog, which is called DeveloperWorks Community. IBM’s community blog consists of thousands of employees, developers, program managers. If you check out the link you can see how it work, its like a aggregation which holds all the new posts from each author listed. However, anyone can search posts by most popular, title, or author. What it seems like is that the employees that blog either do on their personal blogs, but IBM has guidelines to follow. In Corporate Blogging Best Practices and in the book Radically Transparent IBM was mention for their terms and conditions for their bloggers. This video explains more:
One point that was mentioned in two separate case studies 1 and 2 talking about IBM was that their blogs were not getting much feedback and little customer support. Bill Higgins, a system engineer and blogger for IBM, was interviewed in both case studies. He brought up an intriguing point about how IBM is not too concerned with getting feedback, he still feels there is a community, and at least they are getting their information out in a timely fashion to anyone who has an interest.