Last week I spoke about a little thing called confluence and how awesome it is not only as a blogging tool but as a web based wiki. And this week I’m going to talk about some of the ways to influence the adoption of these technologies not only at Airservices Australia but in any organisation.
Enterprise Wiki – A tool, not an encyclopaedia. – Mike Cannon-Brookes Co-Founder Atlassian
The first thing that you’ve got to realise is that it’s NOT Wikipedia, and cannot be treated as such. What I mean by that is that for it to be successful you don’t want it to follow the 1% rule (where 90% of visitors are lurkers, 9% contribute and only 1% create), nor do you want it to be as difficult to find content in and least of all do you want it to be as difficult to generate content for. The Enterprise Wiki is a place where employees don’t just come to for information. It is a place where they should come to collaborate and to share their knowledge.
So as Sherif mentions in his blog post you can’t really define the exact steps to Wiki adoption but I think there’s a handful that will certainly get the ball rolling. My top three, in particular reference to Airservices Australia but which can certainly be utilised by any organisation are:
Choose a good Wiki.
This is soooo important! The best way to put anyone off using a software tool is by making it intimidating. Figure out who your users are going to be (are they techy or are they arty?) and what are they going to use it for (meeting minutes and action items or code snippets or both?). The answers to just these two questions will give you a massive insight into what kind of tool is right for your organisation. <cough> Confluence <cough>. Claire points to an awesome tool in her post this week called WikiMatrix who have a tool called the ChoiceWizard
which is just perfect for getting started on choosing what’s best for you. Check it out!
Lead by Example.
Ok so if you want to spread the word and you want to encourage the use of a wiki, you need to migrate the ways you work into the wiki as much as possible. Instead of emailing attachments, link to them in the wiki, instead of sending meeting agendas via email, create them in the wiki and invite your attendees to add their agenda items there too. Only by leading horses to water will you have any hope of getting them to drink.
Seek out your Champions.
Pretty much whenever you bring in new software into an organisation, you’re gonna get your haters. And to combat these little tumorous individuals you need people to not only spruik the benefits of the wiki but also who can offer sage advice. Those that create the most content, those that find inventive ways of creating content, they’re your champions. Seek them out.
Here’s a few more links that I used to create this week’s post but I’d be well keen to hear if you have any tips or tricks to help aid the adoption of Enterprise Wikis. Laters.