Enterprise 2.0: Wiki adoption

November 23, 2009 (one comment)

Starting from today, every week we’ll be writing a series of posts focussed on Enterprise 2.0 culture. In this post, we talk about the adoption challenges faced by Enterprise Wikis.

Wiki” (pronounced [ˈwiki] or [ˈviki]), meaning “fast“ in Hawaiian is a collaboration platform enabling users to write, share, edit, exchange content collectively with ease. In the enterprise/organizational context ‘Wiki’ is primarily used for knowledge sharing.

On the cultural side, Wiki has shaped up as one of the best platforms for knowledge sharing across & within teams. Talking about technology, we have many content management systems (mediawiki, wetpaint, atlassian) which can be used for implementing a Wiki.

Amidst all this success, several challenges need to be overcome to ensure a successful implementation of a Wiki:

  • Technology or Culture?
    What kind of benefit does a Wiki provide? Is it purely technological or it is cultural benefit?
  • People – Who will drive Wiki?
    A common exercise during rollout is to identify a champion who will drive the tool. A consultant does his job by giving the advice about using a wiki, taking you through the numerous case-studies. But when it comes to implementing they are not the experts. During situations like these, you are not sure about who the project coordinator is.
  • People – Low participation
    Evaluating the success of a new change can be monitored by the user-participation graph. Post rollout, all your statistics (no. of page views, no. of user-created pages, discussions) reveal extremely low participation.
  • Technology – Do I need another tool?
    If the employees & their peers have been using different mechanisms for exchanging information their first question would be why do I need to install a new tool? I have been already using the file-sharing drives and other protocols like instant messaging system for knowledge sharing.
  • Technology – Security
    There is a paradoxical relationship between ‘openness’ & ‘data-security’. While Web2.0 is about principles of sharing, openness on the flip-side data security is one-aspect you cannot ignore. Moving beyond the trust layers for your employees how can you control unethical practices like copying of wiki data by disgruntled employees? Are features like access-control & user-privileges part of the Wiki philosophy?
  • Cost & ROI – People/Time
    Since there are people from multiple disciplines involved in Wiki, how do you justify their involvement (time/money). What are the benchmarks for evaluating the success of Wiki?

Thinking about the answers to these questions? Next week, we will talk about how to overcome these challenges.

—————————————————————————————————————————————————————-

About Iffort

Iffort is an India based web strategy & social media consulting firm that plans, creates and executes a thorough roadmap to deliver tangible value for its clients and their stakeholders.  For more information about our Enterprise 2.0 offerings, please visit our services page.

Iffort

Iffort

Iffort is a high performance social media and digital consulting firm helping entrepreneurs & business units to create successful online experiences.

More Posts - Twitter - Facebook - Google Plus

Tags: , , , , , , , , ,

One Response to Enterprise 2.0: Wiki adoption

  1. Donald Driver Jersey on January 10, 2012 at 6:59 am

    Im truly enjoying the design and layout of your blog. Its a very easy on the eyes which makes it much more enjoyable for me to come here and visit more often. Did you hire out a designer to create your theme? Great work!

Leave a Reply

Your email address will not be published. Required fields are marked *