- IT Home
- How Tos
- IT Support
- Office Hours for Staff Support
- Office Hours for Student Support
Here is a collection of several quotes and articles each holding interesting ideas and considerations about how to use a Wiki (like this
Once a wiki 'catches fire' within an organization it quickly becomes the key knowledge repository exceeding even email in it's usefulness.
You need to help people understand that they should just add stuff and not be concerned with proper organization. People [...] can quickly become preoccupied with trying to figure out the proper 'placement' and end up withholding their knowledge. The ironic thing about 'placement' or 'organization' is that it is one of the least used ways of finding the information later by others. People use search more than any other way of finding pages [...]
Top 10 Applications for an Enterprise Wiki gives some what to use a wiki for, including project communication,, informal learning, and intranet.
Why might you want to use a wiki for your project? The wiki is:
- Good for writing down quick ideas or longer ones, giving you more time for formal writing and editing.
- Instantly collaborative without emailing documents, keeping the group in sync.
- Accessible from anywhere with a web connection (if you don't mind writing in web-browser text forms).
- Your archive, because every page revision is kept.
- Exciting, immediate, and empowering--everyone has a say.
from What Is a Wiki (and How to Use One for Your Projects), by Tom Stafford and Matt Webb, which also discusses how to best employ a wiki. Also tips for organization of content include:
- Keep it messy: Provisionality is key--don't let perfectionism get in the way of throwing down on the wiki all the half-thoughts, potential seeds, links, and factoids that you'll need later.
- But not too messy: We talked earlier about "wiki gardening," which is the process of wandering around the wiki tidying as you go. The point isn't necessarily tidying, it's seeing pages and ideas with fresh eyes, too. It's a good habit, it's easy, and really shouldn't just be ten minutes a day--it's continual. Try spending your first cup of coffee in the morning on the wiki, picking up loose ends, trimming the index, and so on. Do more whenever you have a spare few minutes. You'll run across late-night ideas from before that might change your day. Be wary of imposing structure too early, however. You'll find you come to an understanding, as you garden, of what needs to be structured and what doesn't. Reorganization (but not too much) keeps things fresh.