Uses for a Wiki

De Assothink Wiki
Aller à la navigation Aller à la recherche

Top 10 Uses for a Wiki


Wikis are a great way to quickly build and share knowledge within an organization. The ability to conform to a rapidly changing work environment by providing a secured medium for sharing information is what makes wikis a “Web 2.0” application and what advances them beyond traditional mediums for informal learning and knowledge sharing.

10 Ways to Make Effective Use of a Wiki:

  1. Disseminate information quickly; roll out a new process, update documentation, change a current procedure.
  2. Create a Resource Center for on-boarding new employees; reduce and support on-boarding efforts.
  3. Help experts make better use of their time and knowledge by helping them avoid answering the same question over and over. Capture that valuable intellectual capital within the wiki and allow your employees to work on more valuable activities.
  4. Deliver a Frequently Asked Questions (FAQ) Center; create and publish FAQs in minutes to assist with training and as support to formal training.
  5. Search for information and find your answer immediately.
  6. Provide a Self-service channel for employees, partners, constituents, or even customers; 24 hours a day, 7 days a week.
  7. Gather valuable feedback in line with the content; allows for versioning of a document, instead of passing back and forth in email, etc.
  8. Roll-out a new product to your entire team and sales team immediately; including marketing pieces, sales guides, procedures and more.
  9. Enhance your customer service by answering the calls consistently and quickly; deliver up to date information to the desktop of your service group immediately.
  10. Create a corporate knowledge repository that’s as easy to use as email.

The additional benefit is that it does not require the need for IT resources to get started, simply assign a business project manager and get started using a wiki today.


Other uses for a Wiki

Operations Guides- As fast as you can put down information on what to do in a certain situation at work, it changes. Right? “If the A server goes down, reboot the router.” No… scribble, scribble… Manuals are dead. If I owned a wiki company, I’d sell tee shirts that said “paper is dead.” Wiki-fy your operations manuals (and sure, print them once a month to keep an offline copy, should power go out).
Dashboard- There are better calendering options out there, especially for group projects, but a wiki can be a great FOCUS TOOL for upcoming events. If you’ve got the kind of business that works on deadlines, and on projects, it’s a great way to put a kind of “dashboard” that shows deadlines, things to focus on, and maybe key contacts/resources for that time frame.

Water Cooler- In the world of telecommuting, there becomes a need for telecommunity. Throw up an employee-driven wiki page for stuff for sale, outside-of-work events, and other items. It becomes a great way to keep people connected outside of the email stream. (Which is kind of the point of wikis).

Fact and FAQ Lists- I find wikis are a great way to share all the easy things you need over and over again. For instance, what’s that command that lets you pipe the output of a query right into a MySQL database? Put a line in the wiki showing that info. Did you switch suppliers? Put a reminder on the fact sheet. Want to gather up product resources quickly with links? Wikis are great for it.

Making Plans- Wikis are excellent ways to build up a project for either inside or outside of work. In the workplace, wikis can be a great place to get the brainstorming down, and then maybe to a second edit before committing the information to a more formal project plan. Wiki as whiteboard, I’m suggesting. I think this makes for a quick way to get lots of ideas thrown together. Imagine gathering around a conference call with everyone working on the same wiki. It’s like getting the whiteboard notes without that extra step of copying. Maybe not as easy as a mind-map, but definitely another way to capture points for planning.


More Uses

  1. Creating a knowledge base on a specific topic (examples: Creatures, Wikimac)
  2. Writing documentation or a FAQ (see Category:Documentation)
  3. Brainstorming (example: Scratchpad)
  4. Collaborative writing (examples: fiction, comedy, poetry, Storypedia)
  5. Learning writing through online collaboration (example: schools)
  6. Product reviews and comparisons (examples: beer, Cafe Review, Facial Cleansing Products, shopping, TechCompare)
  7. Creating specifications and architecture documents for software or other projects (example: Scoop)
  8. Creating how-tos (example: How To)
  9. Creating promotional material (example: Mozilla Community)
  10. Developing new languages (example: Baby Sign Language Dictionary, conlang)
  11. Sharing tips and advice (example: quit smoking, Answers)
  12. Translating documents together (example: Translation)
  13. Coordinate and help fill needs of charities, for donations and services or volunteers (example: fundraising)
  14. Sharing tips with gaming communities (see Category:Gaming)
  15. Discussion of theories (examples: Abaeté)
  16. Publishing (examples: academia, Metodologia Científica)
  17. Bringing together a community for activism (example: activism)
  18. Consumption guides (example: Altereco)
  19. Exploring fictional worlds (examples: Alternative History, Conworld)
  20. Fan sites or fan clubs (examples: Ashlee Simpson, CamarilaRequiem)
  21. Developing patterns or best practices (Best Practices, engineering)
  22. Support groups (examples: Cancer Help, Celiac Resources, Quit smoking)
  23. Parody (examples: Désencyclopédie, Homestar Runner Wooky)
  24. Planning and documenting events, maintaining a calendar of local events, or real-time reports on conferences (examples: events, conferences)
  25. Developing software features and other inventions (examples: FeatureGarden, inventions, Software testing and development)
  26. A meeting place for language communities (examples: Ladino, Ido Korea, Cantonese, Translation)
  27. Political campaigns (examples: VoteRice, Eagle Party)
  28. Communication between and within communities
  29. Creating an easily searchable, linkable, and editable website
  30. Community news and group announcements
  31. Information and policies about a project
  32. Easy refactoring of communication on forums and mailing lists (by turning the thread mode of these discussions into a more useful document mode).
  33. Meeting agendas and notes for organizations
  34. Project collaboration
  35. Enriching existing text documents by editing them collaboratively and adding multimedia
  36. Solidifying an existing community through collaboration and increased connections
  37. Supporting a shared community goal
  38. And even for playing games (example: games)