Now that many companies have adopted wikis internally and are beginning to understand their power, why should education institutes be left behind. After all, the knowledge density in education institutes is bound to be as high as, if not higher, than in most companies. Moreover, content creation is part of any education process, and a wiki is an ideal medium for refining the content and making it available to a wide audience. So, what are the stumbling blocks in the widespread adoption of wiki or any knowledge/content management system for that matter?

Challenges

IBM has WikiCentral, an internal deployment of the Confluence wiki, and I was one of its 125,000+ users. We had wikis for our project, our team and various initiatives. In fact most of the documentation, FAQs etc of our project were on the wiki. So, we could easily refer to them and keep them up to date at the same time.

However, I have found a couple of limitations in wikis during my stint with IBM. Firstly, a wiki (barring wikipedia) is not the reference source (no prizes for guess the first) which means that even if we manage to aggregate a wealth of information, not too many people are going to actually refer to it. This can be tackled in some ways through publicity, which is precisely what was done in IBM. The second and biggest problem is the content creation part which is due to the lack sufficient contributors. Even wikipedia faces this problem (different scales though). I have ended up being one of the handful of contributors to quite a few wikis.

Wiki for SJMSOM

Finding the critical mass of contributors to sustain a wiki is the toughest challenge, and it gets even tougher with a tiny user base. However, I have not yet given up on wikis :-), and now that I am back to being a student, I find that a wiki is an ideal fit for this environment. There is a lot of information that is exchanged among students, and most of this would be of value in the future too. However, this information in the form of emails and verbal communication which makes the persistence quite low. So, a wiki with its persistence and ease of editing is an ideal medium to store all this information.

I did some exploration of different wiki options on the internet, and found two that were well suited: Wikia and Zoho. In fact, Wikia already has a section for students. However, Zoho has better access control (supports domain level access control), and I chose it as the platform for my b-school wiki. Of course an internal wiki deployment would have been ideal, but I’m just doing this as an experiment to see if it works out.

I have been doing some work on it, and the support for HTML embeds is quite handy for adding different widgets on pages. I have currently kept the wiki visible to the public with the ability to add comments. However, editing is restricted to students from SJMSOM (my b-school). It is currently a work in progress, and I am still trying to find the tipping point of contributors 🙂 . So, if you have any comments or suggestions, do share them with me.

P.S. My father has blogged on a similar topic “How Important Is Technology For Knowledge Management?”, and it doesn’t seem to be very encouraging for my experiment 🙂