Stewart Mader, Wiki Evangelist
  1. Product documentation — collaboratively write it in-house, then let customers add to it as they use the product.
  2. Collaboratively write news releases — A great way to make sure that a news release has input from product managers, marketing staff, etc. and can be quickly updated as necessary before release.
  3. Knowledge base — Keep common FAQs and support questions on a wiki so they can easily be updated with new information.
  4. Meetings — Instead of emailing agendas that can't be easily and quickly changed, put them on a wiki page. Take meeting minutes on the same page and you'll have everything on one place!
  5. Manage projects — Give each project a page in your wiki, and keep all relevant materials there so it becomes a magnet.
  6. Build a peer-directory — This gives people a reason to come to the wiki in the first place — to put information about themselves in the directory — and then they stay to collaborate.
  7. Keep time-sensitive information up to date — For example, I keep a list of events where I'm speaking on the wiki, and others can add an event they want me to know about.
  8. A space for every group/team/department — Give each group a place to organize their projects and work collaboratively.

Which ones do you want to know more about? Vote in the poll below and I'll write in-depth posts about the four uses that get the most votes:


Tags: wikipatterns

4 Comment(s)

Use a wiki to write that book you've always wanted to write. That I find tends to be the most popular individual use.

A lot of people have that book in their head and it is hard to maintain it over time in paper format.

By Kin Lane at May 12, 2007 10:33 AM

Kin,
Great comment! I did just that with Using Wiki in Education, the wikibook based on my blog: http://www.wikiineducation.com

Stewart

By Stewart Mader at May 12, 2007 2:59 PM

Could be interesting to develop confluence to Rolonic (world) theory.

By Gordan at May 13, 2007 6:42 AM

For any kind of client services company Confluence is a wonderful way to manage instantly create secure collaboration and documentation areas. This serves a vast number of purposes but a few include:
* an area to create and collaborate on specifications and a statement of work
* a place to write documentation for components and services
* A searchable archive to quickly pick projects back up. The majority of my clients come back multiple times though the timeframes can span months or years making it next to impossible to simply remember key system details.

This is actually one of the things that drew me to Confluence.

A wiki is also the easiest way to publish and manage a website. Confluence makes it easy to lock down areas you simply wish to display.

By Brendan Patterson at May 16, 2007 7:35 AM

Post a comment





Remember personal info?

Type the characters you see in the picture above.