I’ve struggled to come up with something interesting to write this week, although I’ve been doing some reasonably interesting things.
Over the past 8 weeks of so I have been conducting the wonderfully fun task of evaluating wiki platforms for implementation in our organisation. It turns out that the bulk of them are more or less the same, the main difference seems to be in the text editor but even then I reckon that most of them share the same DNA.
In the end I chose a platform based on ability to grow with us, price and most important ability to integrate with our unique environment. We want to implement a Single Sign On function using an encrypted HTML string rather than an LDAP integation. It seems most of the major ‘Enterprise 2.0’ vendors are ready to hook up inside your building but can’t quite handle a smooth integreation with a website. Anyhue we found someone who is very keen and hopefully will provide us with a solid product!
It seems that we’re going to be able to make pretty broad use of the system, we’ve gone with a platform that can accomodate a range of spaces. This should allow us to use it in our customer facing environment and internally, either way the more successful uses we find the easier it’ll be to justify the expense for 2009!!
The next trick will be to get people into it. We’ve gone after a wiki to create our own knowledge base, we already have quite a lot of content to go in but due to a range of existing copyright agreements we are not going to be able to make it editable. I actually don’t think this is going to be a problem as we’re going to have to go through a fairly hefty education process on two fronts:
- Many internal stakeholders are terrified of allowing anyone outside the building to contribute to something that has our logo on it. We need to show them that with appropriate guidelines and access levels this will not be a problem and will in fact open many doors to us.
- Many of out target audience probably have not had a lot of exposure to the ‘2.0 revolution’. We are going to have to build a level of comfort in the audience to contribute. I get the feeling that in a knowledge base situation the ‘fear’ factor may be larger than in some other work-based wiki applications. The risk of being labelled as wrong (particularly in our system which will not allow anonymous posting) is much greater than if you are using a wiki in an enterprise environment to host meeting minutes and spreadsheets.
Starting with locked content then slowly opening areas of the wiki up will allow us to gradully build interest and confidence, without the worry of conducting a grand opening only to find it left to crickets and tumbleweeds two months later.
In any case, the boring software selection stuff is done, so now I’m going to start planing for the people. I’ve had Stuart Mader’s Wikipatterns sitting on my desk for about 6 weeks now. I might bring it along for the tram ride tonight!
…well it was a big long rambling mess but turns out I can think of something to write….