Shiv Singh from Razorfish announces that the Razorfish report on intranets has been wikified and is available at The Intranet Maturity Framework.
Nice idea, we'll see how it plays out, and whether a better report comes out of it.
I'm also interested to see how the rights (and credit) issue gets played out. I've suggested they clarify terms by adding a Creative Commons license - which in itself might be an internally controversial idea.
Haven't really read the report, but I did notice that it looks as if Razorfish have got a big downer on internal blogging:
Some employee blogs will last, but, unfortunately, most won't. Many companies that enthusiastically set up employee blogs ignored the two most important ingredients for blogging success. The first is that the blogger needs to have something important and unique to say. According to a recent survey by America Online, the most popular blogs are the most personal and opinionated ones. Most organizations have cultures that subconsciously encourage information hoarding and group think. These organizations will find that their employees are reluctant to share their knowledge and personal insights unless they see tangible benefits to doing so. As a result, most employee blogs will be superficial and boring unless, of course, they are anonymous.The AOL survey was about external blogs. We're discussing internal use here. Apples vs Oranges ? I think so. I agree there will be many cultural issues (and frankly, the companies with those sorts of cultures probably won't even green light a company wide blogging infrastructure), but a blanket prediction of most internal blogs failing is, I think, a pretty big leap. And finally - could I have chosen a worse title for this post ? [tags]internal, corporate, razorfish, wiki, blogs, intranet[/tags]
I love the first bit: "For best results, please view on Internet Explorer"
I guess that's what corporates use mostly. As someone who struggles hard to make his sites acceptable to multiple browsers, I find it fairly offensive.
Yeah - it is disappointing isn't it - especially for externally facing sites.
Seems to work just fine in Firefox though - that's what I was using yesterday - I didn't even notice the IE line until you pointed it out !
There are some really good thoughts that have been shared here. As the one who actually wrote that line about using IE, I think you're absolutely right, it was an unfortunate inclusion. It has since been removed.