The CIO in general question the need to install a
blog- or
wiki tool. Why? We already have
SharePoint installed - it supports this, right?
Yes – skimming through the feature list gives us that answer. The problem with SharePoint is not the technology.
It's the culture.
For me SharePoint is an administrative tool. What do I mean by that? SharePoint's strengths, if any, are document management, support for processes, permission management, and so on. Nothing wrong with that.
On the other hand - blogs and wikis are not considered administrative tools at all. There is simply a different culture around them - and they are on a head-on collision course with SharePoint. Blogs and wikis are grassroot forces where rules are defined by the creative people using them - not the administrator.
The difference is huge and is reflected in the result. Where native tools enhances all the benefits with wikis and blogs, implementing blog and wiki alike features in SharePoint puts more burden on the information department stressed to "align it", triggering the built-in resistance.
You might find this absurd and don't agree with me at all.
But the culture surrounding a tool does matter.
I'm still waiting for a success story implementing native wikis and blogs in an organization with SharePoint - it has full support for it, at-least according to the feature list – and have had it for some time now.