by Jon Mell
This is a Headshift blog post by Jon Mell, written on March 12, 2009 in Corporate . It has (2) comments, the latest of which was on March 17, 2009. You can find more posts like this here.
Sharepoint as an Enterprise 2.0 platform
2 Comments
I think, for the most part, your post is correct. A company's SharePoint architecture requires lots of user input and clever structuring to avoid creating lots of silos. Social software extensions can add-on functionality that resembles what we envision as Enterprise 2.0 best practices. But, by adding metadata, defining content types, and engineering the search solution there is no excuse for not being able to find content or for not being able to share content easily with others. Even in SharePoint content can be aggregated via the search engine and made visible to those that are interested in it. Out of the box, SharePoint is limited, but it can, with careful design improve sharing, reuse and process performance.
I would venture to say that an immediate creation of hundreds of silos is a worst demonstrated practice and could be avoided by understanding user requirements, prototyping solutions, training and change management initiatives!

I think you hit the nail on the head. Smart enterprises will find a way to integrate the various tools into a complete information management solution. Some organizations will be able to create value from Sharepoint as a Collaborative Tool and as a Social Software solution. Other’s will add tools such as the ones you mention to the mix to improve the business value. Those that choose Sharepoint for Enterprise 2.0 should be demonized but welcomed into the fold. The world is a lonely place, we can use all the friends we can find.