Wikiquette

some useful wiki etiquette tips from the Businessweek CEO guide

DO

Be bold: Go ahead and create content or edit someone else’s work. Wikis develop faster when people fix problems, correct grammar, add facts, etc. This is a collaborative tool, after all.
Make notes: If you make changes, explain why you made those changes in the discussion or notes pages that are generally attached to wikis.
Give praise: Has someone added useful content to the page or spent a great deal of time cleaning up the page so it’s easier to read? Praise helps let people know their contributions are valued—and makes them want to contribute again.
Build structure: Wikis need people to synthesize and structure content so it’s easy to read. Even if you’re not creating content, you can still help by shaping what’s already there.
Be polite: As with e-mail and instant messaging, it’s often easy to misinterpret the tone of a comment. Disagreements over content or edits can become heated. If that’s the case, it’s a good idea to take a break for a day or two and come back to it later.

  

DON’T

Take it personally: Yes, colleagues will edit your work and you might not agree with every change, but that’s the nature of collaboration. It doesn’t mean that your co-workers dislike you or think you’re stupid.
Ignore questions: Colleagues may disagree with your changes and ask why you made them. If so, be prepared to give concrete reasons for your edits.
Delete useful content: Many times a posting can be improved by amending or editing it, but deleting content upsets people, and they may feel they’ve wasted their time.
Be chatty: A wiki shouldn’t be used as a chat room. Any discussions related to a wiki subject should take place on the discussion or talk page, not on the actual content page.
Keep it secret: If you find valuable content on your company’s wiki, tell others about it. Wikis benefit from a wide range of contributors.
Be Sociable, Share!

Related Post

Comments

comments

One thought on “Wikiquette

Leave a Reply

Your email address will not be published. Required fields are marked *