On 24/11/06, Gunter News2006@freenet.de wrote:
Well, that is a bit off track. Why should people spent their time on an experiment? Rather: Use the wiki to solve a problem. If the employees share the problem, they have an interest in solving it.
Yep! Things we use it for:
* Meeting agendas * Lists of ongoing issues for said meetings * Change requests - the canonical CR is a particular version from the history, but those working on a complicated CR can edit it as they go documenting what actually happened, which is very useful for the next similar CR * Local jargon file
The big use we put ours to was training new starters very quickly. A local jargon file was a particularly good use.
Also: one place I worked, I got them to do a radical thing ... make a documentation tree - folders on a shared drive, vendor and program, with a text file of notes on installation and maintenance issues. I would have suggested a wiki, but a mere doc tree was a head-exploding revelation for them ... a wiki is a natural for that sort of thing.
- d.