Mike Gotta’s 2009: Planning Considerations For Enterprise 2.0 via George Dearing via Twitter
Okay, I learned something useful from Twitter. George Dearing linked to Mike Gotta’s excellent post, 2009: Planning Considerations For Enterprise 2.0. Now you could say if I only looked at my RSS feed which does include Mike’s blog, I would have seen it. However, attention is everything as Tom Davenport used to say. I am giving Twitter a try so it gets more attention at the moment that my RSS feeds.
Back to Mike’s stuff. It is excellent. He covered some topics should be considered when formulating Enterprise 2.0 plans. The first concerns Sharepoint. Mike writes that many people are using Sharepoint for “valid reasons unrelated to E2.0 and are "ok" with undertaking extensive customization or adding specific partners (e.g., NewsGator) to augment what SharePoint has in terms of E2.0 capabilities.” This is move is actually aligned with Sharepoint’s current strategy of linking to best of breed E 2.0 partners as many have written about. Mike appears to feel that they need to move beyond this reliance and writes that the next release will be a tipping point for Microsoft's social computing efforts.
He may likely be right and I look forward to what happens. In the meanwhile, if you want to use Sharepoint, there are many systems integrators thankful for the opportunity to help you and third party vendors ready to supplement Sharepoint. Many of these vendors first saw Sharepoint as a competitor and now see it as a platform to provide more space for their products (e.g. The Sharepoint Sessions Revisited – AIIM Seminar).
I especially like his next planning factor - Think "Adoption", Not "Deployment." It is always 90% people and 10% technology for enterprise 2.0.
The third is interesting. He notes how many point vendors have expanded their products suites (e.g., blog platforms have wikis and visa versa and more). This is smart move on their part but Mike points out that it creates overlap issues. The movement is toward platforms and not point solutions. This will help to reduce content silos but it will also likely reduce the players.
There is much more and I will not repeat everything but recommend that you read the original. Mike closes with enterprise twitter as the space to watch and links to his Enterprise Versions Of Twitter. Here is a post, Enterprise Microblogging or Micromessaging, that links to some of my thoughts on the vendors and issues. I think that twitter functionality will follow the trend described by Mike and become part of a platform, rather than stay a separate function. However, there will remain room for some of the best standalone vendors.