This is the second in a series on wiki adoption, based on my visits with organizations in the midst of wiki adoption. Part 1 is here.
Once your group starts using the wiki, be firm about making sure people use it and don’t drift back to earlier means of collaboration. For example, if you used to send out meeting agendas by email, and now you put them on the wiki and email a link to the appropriate page, you may get someone who protests and asks for the agenda by email. They may argue that it’s more work to get an email and have to link to a wiki page, instead of just having the agenda right in the email.
If this happens, I’d suggest responding that although it seems like an inconvenience now, it’s really only a temporary inconvenience that paves the way for several improvements. First is a reduction in email when people are using to going to the wiki and an email with a link to the meeting agenda wiki page is no longer necessary. The second is a further reduction in email when people need to edit the agenda and can do so directly on the wiki instead of emailing the person who sent the agenda.
The third improvement is that now information is stored in a more archival, accessible, and secure format than email: if you were to lose your laptop or it’s stolen, email is lost along with it and this can compromise the security of sensitive information. However, if you’re using a wiki, that information is stored on a secure server and won’t be lost or compromised as easily.
The fourth improvement is that once you start using the wiki for meeting agendas, it lays the foundation for further wiki use, like managing the tasks and projects that arise from the agenda. It’s this organic use that makes the wiki quickly become an indispensable tool for information and collaboration.

Fresh ideas, announcements, and inspiration for your team, delivered weekly.

Subscribe now