7.2. Recognizing and Exploiting Wikipatterns

In his excellent book Wikipatterns[Mader07], leading wiki evangelist and consultant Stewart Mader describes how observed, repeated methods of behavior can be described as wikipatterns. On the Wikipatterns website[Wikipatterns], these behaviors are grouped as either people patterns or adoption patterns (remember what I said about wiki adoption being as much a sociology exercise as a technical one?).

At the time of writing there are over sixty different wikipatterns listed on the website. Each wikipattern has its own wiki page, which includes the following information:

  • A definition
  • A usage example
  • Links to related patterns
  • Suggested further reading
  • A comments thread

It is well worth familiarizing yourself with these wikipatterns so that you will be able to recognize and predict them.

You should also familiarize yourself with wiki anti-patterns, that is, behavior that is detrimental to the usage and growth of the wiki. Examples include Wikiphobia, Over Organizer, Design By Committee, Too Much Structure, etc. Many of these are also listed on wikipatterns.com.

When it comes to landscaping your wiki, focus on the wikipatterns for navigation and organizing content. By observing the way that people place content on the wiki, or navigate around it, you will be able to determine where to locate content, or how to set up navigation techniques that work for your community. You may need to set up a combination of wikipatterns and navigation techniques.

I have seen one software company wiki that successfully combines three different navigation techniques, each designed to meet the needs of one part of the company’s diverse customer base:

  1. A traditional collapsible, tree-structure Table of Contents pane was created at the left-hand side of each wiki page for those users who are more comfortable navigating through a traditional book-based online help model.
  2. A series of category type labels was created for those users who are comfortable with the social network-driven paradigm of tagging pages that interest them. These pages can then be grouped and searched by a category type, even if there is no direct structural relationship between them. Having a pre-defined category list that users can easily see (and add to) reduces the need to accommodate synonyms.

    For instance, users are considerably less likely to create labels such as airplane, aeroplane, plane, planes, etc., if there is already a clearly defined label of aircraft available to use. These category tags can then be used to create visual navigation aids such as tag clouds or to generate a related pages list of all the other pages labeled with the same tag.

  3. A page of wiki permalinks (with its own permanent link from the wiki’s home page) lists and assigns permanent links to the most popular pages. For a corporate internal wiki, that could be links to things like an employee directory, the HR policies & procedures, etc. In a product documentation wiki, that could be links to things like a quick start page. The permalink process is used to create a unique, unchanging reference to a specific version of an article on the wiki.