Bootstrapping a Wiki in an Enterprise

Here’s my lazyweb wish list for the wiki implementors:

1. Build a virtual image for VMWare or VirtualPC so that there is absolutely nothing to configure
2. The OS should be automatically patched by default
3. When the OS boots, it should show the VM’s IP Address on the logon prompt.
4. Provide easy instructions so that System administrators can do E-mail integration for Exchange, or Lotus systems.
5. Make it easy to import E-mail Distribution Lists into the Wiki. This forms the basic strategy for spreading Wiki-use
6. Provide in built DynDNS so that a readable URL is available instead of an IP Address
7. Provide templates which encourage users to explore and alter pages
8. The home page of a Wiki should be more like Google News, showing screenshots of pages inside the Wiki, and also encourage people to use it as a whiteboard

The main aim of this exercise is to lower the barriers for Wikis to be adopted.
Under this configuration, there is no server to purchase, and it doubles up as a mailing list-manager.
If you want to persuade people to use a Wiki, you need to wean them off using e-mails as a medium for communication.
You also need to make it easy for the key influencers to use the wiki as an e-mail device. For instance, CC e-mail conversations to the Wiki. The other option is for the key sneezers to e-mail the wiki, which subsequently broadcasts it to the people in a group.