You did a very good job at describing the tension between what employees are expecting from using wikis, and what an organization needs to do to keep people and knowledge on track. Thanks for sharing, I have forwarded this article to decision-makers at my workplace.

BTW, if you’re interested, I wrote a report on using wikis in education last year. It touches some of the same issues, from a different perspective. Here’s the URL: http://udel.edu/~mathieu

Mathieu Plourde

I think we will eventually clarify the marketplace and use cases to rationalize:
1. enterprise-wide transparency
2. departmental-wide unity
3. team-wide coordination
4. project-wide activity (which may or may not be the same as team)
5. individual productivity enhancement tools (profile, streams, bookmarks, etc.)

Do you think these are right?

Rocket appears to have the capability to turn the sometimes tired approach to Wikis, or prescibed blogging, inside out.
Why not automate the posting to the Wiki and remove the people?
While this may seem silly as it removes the ‘collaborative’ component, it saves time and stress and you will be able to add virtually all of the value after the posting with a tag or meta data or sticky note approach.

Then you put the values in a datacube and allow users to navigate in multi-dimensional space.
Simple enough, I’ve been prescribing this approach for two years.

Just a thought.

Cheers,
Nick
http://www.neuropersona.com