Define use
There certainly can be confusion as to why you are implementing a wiki, what information goes in there, when do we use a wiki over Email?
The best approach is to explain why you are implementing a wiki, and then decide based on that, what information should find its way in there. My approach is that "conversations" need to occur in the wiki, anything where a decision is being sought, or, ideas need to be shared to find an outcome.
So, in defining how you are going to use the wiki, you need to understand why you are using it -
- Visibility, the wiki will allow everyone who has access to the information to be able to see it when they need to. People are not left out of Email lists, and people are not bombarded with Emails that are not relevant to them.
- Version control, the wiki version of a document or conversation is the most recent version. No need to track back through Emails to try and find where something is up to. I often find it difficult to locate the most recent version of a document, or, Email conversation, the wiki removes this issue.
- Everything in one place, supporting documents, attachments, etc can all be attached to the wiki entry. Rather then having this supporting information live on someones local hard drive, or, lost in a corporate server, it is just where it needs to be.
Following these concepts on why you would use a wiki, will assist in defining what you put into the wiki, and this will help everyone in understanding why it is being use, and how they can get value from it.
Next up, the rules of engagement
