Some Question The Value Of State Worker Blogs
from the build-it-and-they-won't-come dept
I'm very interested in the use of blogs within business settings, partly because that's (in some ways) the business Techdirt is in. However, for all the hype, most organizations experimenting with enterprise blogs are going about it the wrong way. They seem to think that all you need to do is give all your employees a blog, and watch the revolution begin. As state IT employees in Utah are discovering, it's not quite so easy. If you just want to give people blogs to write about whatever they want, why not just point them towards any of the free (or cheap) blogging systems out there, and let them go wild? If you're really talking about using a blog to increase worker productivity, better share knowledge, or better connect with partners/customers/co-workers, you need a bit more thinking involved. So many of the blog-boosters seem to believe that everyone wants to blog, and if given the opportunity to do so at work, they will blog useful work-related items. However, the example in Utah suggests the opposite (as does our own experience at Techdirt). Many people out there don't like to write. Many workers out there don't have time to input information. This is why knowledge management systems have a strong history of failing over and over again. It's not easy to get people to input knowledge. People who think that the world is going to change just by giving their employees some blogs are probably going to be very disappointed. Without some guidance, process, or plan the whole thing has a good chance of backfiring completely - leading people to wonder why they're letting their employees post images of themselves picking their noses. Blogs can be useful for personal uses and for work uses - but people need to understand their limitations as well. Here, we believe that there are a lot more readers out there than there are writers, and so our solution is to build internal corporate intelligence blogs for our customers. We fill it with the news and analysis, so they don't have to worry about the "knowledge" part of knowledge management. That doesn't mean I don't see solutions that involve giving employees blogs, but clearly, expectations need to be managed. While the case discussed in the article seems to be a bit misleading (some of the blogs in question appear to be quite good), even they admit that not many are jumping on the blog bandwagon. Blogging for the sake of blogging may be great for personal uses, but when it comes time to bring the blogs into a company, a better set of goals and plans are needed.Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Reader Comments
Subscribe: RSS
View by: Time | Thread
Jumping to Conclusions
I think maybe you're jumping to conclusions about the Utah experience because you're hoping for a good example of how not to do it so that you can sell some more consulting.
In fact, the blogging experiment was to be evolutionary. We never anticipated that most people would blog. We expected that most would participate through reading rather than writing. There were all sorts of plans for things as it unfolded, but it never happened. I left and blogging really lost its momentum at that point. There are less than a dozen blogs at this point and those people would probably be blogging whether they worked for Utah or not.
I conducted a panel at the Jupiter Media Weblog Business Strategy conference in Bostson earlier this month. Here are some links that are relevant:
[ link to this | view in chronology ]
Re: Jumping to Conclusions
Thanks for the added information. That's good to know. It's too bad that blogging has lost the momentum there since you left. As I mentioned in my post, it looks like some of the blogs there are very good. If anything, I'd blame the writer of the article (who, I see from your blog, you do).
My question, then, is why did these blogs need to be officially supported by the state of Utah? Why not just encourage the individual employees to blog on their own? Also, who owns their data should they switch jobs? Since you still have your blog, I'm assuming the answer is that it's the individuals - which raises even more questions about who should have set up the blog.
[ link to this | view in chronology ]
Re: Jumping to Conclusions
[ link to this | view in chronology ]