Last week in my Corporate 2.0 post I found myself questioning whether Sharepoint is really a collaboration platform. The more I work with the product the more I keep asking this question. May be it is down to how Sharepoint is being implemented. It could be that traditional IT departments are implementing Sharepoint with old style governance and control structures, pre-defined site templates and controlled access. In this environment it is hard for Sharepoint to demonstrate an emergent structure - something that Andrew McAfee points to as a critical trends in Enterprise 2.0.
When Sharepoint's structure gets pre-defined along traditional lines. The result is one step up from a shared file server. A platform offering lightweight document management capabilities and list management functions.
So, if you are looking to implement a wiki as a means to compile a knowledge base follow these tips:
- Keep security simple
- Fight to keep the wiki open to all
- Provide some signposts but let the structure and content emerge
- Moderate - not for censorship purposes but instead to organize and make information easier to find - just like a good gardener
I was also reading Michael Idinopulos's Transparent Office blog. His advice should be taken very seriously. It is so "spot on." His three best practices in creating a knowledge base are:
- Structure by topic, not by organization
- Lead with what you want, not what you have
- Link, link, link
Do you have other best practices that are worth sharing? Let me know!