Collaborynth

In the first article in this series we had a look at email as a collaborative tool. This time round we're going to be looking at Wikis.

Wikis - A Brief History

"A Wiki is a collection of web pages designed to enable anyone who accesses it to contribute or modify content, using a simplified mark-up language. Wikis are often used to create collaborative websites and to power community websites. "

That's the official explanation from the worlds best known Wiki, Wikipedia.org. Essentially, a Wiki is a tool, that allows people to work together using a common interface to build and share ideas and knowledge.

The first "true" Wiki to be released was the WikiWikiweb project. Originally launched in 1995 and still operating today, it sits at http://c2.com/. Wade Cunningham - the developer of WikiWikiweb - was still looking for a name for his project when he travelled through Hawaii and used the "Wiki Wiki" shuttle buses that run between the various terminals.

Since then, the Wiki has grown from a tool mainly used by software developers and enthusiasts to a concept that has allowed for one of the most innovative knowledge projects in the world. It has branched out into the enterprise and has firmly established itself as a core tool in any on-line collaboration project.

Wikis - As A Collaboration Tool

There are a huge number of different Wiki systems available to your collaborative project. Below are listed what could be called the "core components" of an effective Wiki system.

• Formatting Language: Each Wiki system has it's own language for formatting entries. These range from quite simple to quite complex. This can cause issues with users who are not used to these sort of systems, however there are Wiki projects that include WYSIWYG (What You See Is What You Get) interfaces which allow users who are more familiar with products such as MS Word or Open Office Writer to interact efficiently with the system.
• Change Tracking: Every change made to an entry is tracked and logged. This allows for a complete history of the entry to be retained and examined at any future point. This allows for project users to have a complete understanding of the development of the entries.
• Discussion Area: Most Wiki systems have a discussion area for each entry. This allows users to discuss the entry and create an ongoing dialogue that allows for continuing improvement of the entry.

Many packages go beyond the above and add features such as user management, support for importing different file types so they can be managed and changed by the Wiki and so on.

Best Use In A Collaborative Project

The best place for a Wiki in any collaborative project is at the centre. By creating a core place for your users to gather and develop their knowledge you create the potential for great things to happen.

However, a Wiki will only work well if there is the right culture within the project. Your users need to feel comfortable both with the system itself and the idea of sharing information and knowledge for the betterment of the project. If there is a culture of knowledge retention and "organisational feudalism" a Wiki can only go so far in breaking down those barriers.