David has an interesting, multi-post series going over at his blog about his experiences blogging. These are part of an ongoing case study that I hope will become an argument for why all product teams should blog.
It’s unlikely that there will ever be an end to this collection, unless he shutters the blog, so rather than wait, I figured I’d point the posts out and encourage a little peer participation. So, bounce over and check out Why Product Development Should Blog – Part 1 and Part 2.
Update: David just posted Part 3 in his opus.
Since the inception of the ‘Lab, we’ve spent a lot of time preaching New Web, and the hardest part is always showing concrete value. I can talk about the uses for social bookmarking, social networking, RSS, wikis, collaboration, whatever until I’m blue in the face, but it won’t mean squat if my audience doesn’t give them a try. Mandating usage sometimes works, but it’s always nice to have an example to entice people.
That’s the first step, but even after that, which is tough enough, the tools needs to show value. This is where the case study is gold because it provides tried and (somewhat) true ways to get similar results, a formula if you will. We all know attention is highly subjective, but it’s reasonable to assume that a case study based on David’s blog could be a primer for other teams.
I’m curious to see how David’s blogging adventure goes. His experiences along with other product teams we’ve pushed into the blogosphere (Armchair Architect, Human Strategies, Oracle Financials Strategy, Project Directions, TalentedApps) should make for a nice case study. I hope it’s a case study for blogging, not one against it.
Do you agree that product teams should blog? Why or why not?