Wiki Patterns
grow your wiki
EditYour wiki isn't Wikipedia
Since Wikipedia is the most well known example of a wiki, people new to the idea of using a wiki in an organization or enterprise can be highly influenced by Wikipedia's pattern of use.
Unless an organization intends to replicate Wikipedia's application in their organization -- building a corporate encyclopedia that is entirely open -- it is helpful for new users to understand the difference between using wiki technology for their specific need and using Wikipedia, which is but one application of a wiki.
Adoption issues include:
- Application or Use -- The wiki can be applied to a wide variety of specific uses that are fundamentally different from an encyclopedia. New users benefit from seeing a variety of applications -- sales processes, technical documentation, work group collaboration, event planning, etc. -- so that they can visualize how they might use the wiki. One of the first steps is to show new users these possibilities. A picture is worth a thousand words.
- Open versus Secure -- The openness of Wikipedia can actually frighten some new users when they envision using a wiki in a large organization where sharing information is based on more traditional mechanisms -- conversations, meetings, email -- which they have some control over. Although less control and security can make a wiki a more powerful social network (reference/link to Key Success Factors or Tips for Making Wikis Spread), new users need to know that security can control access at several levels, depending on their requirements. Vandalism, for example, which is a quite common problem for Wikipedia (in terms of people intentionally deleting content or damaging it), is more unlikely to happen in an intranet environment, since users there all should be registered (and ideally working for the sake of their company).
- Quality, Accuracy, and Moderators -- Many new users question the accuracy of Wikipedia and then extrapolate that perception to the creation of a wiki in a corporation or traditional organization. For starters, new users can benefit from Nature's comparison of Wikipedia and Brittannica
to debunk some of the myth of Wikipedia's overall accuracy. More important, new users need to understand that the wiki is merely a tool, as is their email, their word processor, or anything they use to do their work. The wiki is no more or less accurate than these other tools. It is simply a new mechanism. The social nature of the wiki actually offers the opportunity to have higher accuracy. Last, wikis can include a feature such as 'mark for review', or have moderators to monitor quality.
Take a tour
Adoption Patterns
Adoption Anti-Patterns
Wikipatterns.com is sponsored by Atlassian Software, creators of JIRA, Confluence, Bamboo and Crowd
Designed by Headshift Ltd
This is a good point. The wikipedia motto "the free encyclopedia anyone can edit" tends to scare a lot of people in enterprise who don't really understand what a wiki is. I don't think open access is a primary feature of wikis; it's an optional feature but a very useful one. The 'anyone can edit' bit is especially hard to swallow for organisations that have dedicated communications departments that are responsible for websites and intranets. The misperception is that because a wiki is html then it must be a sanctioned, vetted and authorised website.
Very good point. Most people I tell about wikis know only wikipedia. So that think it's for building encyclopedia indeed
The link Nature's comparison of Wikipedia and Brittannica
seems to be dead. 
Link fixed via Internet Archive.
We've had modest success introducing a wiki to our enterprise, but only on the basis that we create secure spaces for teams, project groups, existing communities, etc. We did find that the idea of an open-to-all wiki was too big a hurdle to adoption. Unfortunately we've found that maintaining these secure spaces with our wiki tool is onerous and brings problems of its own, namely:-
I'm not a technical guy but I'm coming at this from more of an adoption angle. To me, wikis in the enterprise need better support for secure spaces so that the trust factor can be used to sell the wiki; but the tools don't seem to support this. Is this because wikis are intended to be open to all, even in the enterprise?
In the beginning, we are building an encyclopedia for our field. While on that journey, someone gave me a copy of wikipatterns and my mind has been Blown! However, we do want that encyclopedia and FAQ format first
Our Company is looking to use a wiki to support the customer service frontline. The concept of wiki is intriging, however, am a bit skeptical on how the knowledge is managed and consistent. Does anyone have any experience on the knowledge management side of a wiki?