Denham has written about Connecting Wikis. He refers to FluWiki that is a domain specific wiki that focusses on managing a influenza pandemic. He speaks about a dedicated group of bloggers who contribtue to this wiki. He says “…practices and solutions bubble upwards from bloggers to domain wiki to Wikipedia”. This approach could have implications on the quality/reliability of content that goes into Wikipedia.(or will it not?)
From an organizational perspective this seems to be analogous to moving content from the personal workspace(could be file folders on your PC) to the community workspace,where peers may review and rate the content and then this peer-reviewed content is moved on to the enterprise repository for use. However,here the content is still static.
If we were to extend the Blog->Domain Specific Wiki->Wikipedia idea onto the enterprise this would roughly translate into a zoo of blogs at the bottom of the pyramid that would focus on stirring conversations and probably bringing out different opinions . There would then be a group of domain specific Wikis on the next layer which essentially would be the first layer of consolidation-the key challenge here being negotiating a neutral view of the issue at hand.The top most layer would be the master repository(analogous to wikipedia) which would have the content that you may reuse.
Does the “blog->domain specific wiki->master wiki repository” flow preserve context better than the “Personal Workspace->Community Workspace->Master repository” flow? If I were to use a metaphor,the blogs at the bottom of the pyramid would be involved in “environmental sensemaking” which in turn is channeled into Wikis upstream(These would essentially be “living documents” as they call it). Any major change would happen at the bottom of the pyramid in blogs where intense conversations will happen followed by a negotiation phase. The changes that happen upstream would essentially be fine tuning content.