Personally, I’m a big fan of Wikis (when used in the right circumstances). Coming from a consulting background, I like to collaborate on web documents with my teams and customers. It is a great tool that saves significant time and produces high quality results. HOWEVER, wikis are not great for everything. I run into customers every day who have published external Wikis for their customers to distribute information on their company and/or product. This is a big problem for the following reasons:
- Most wikis require familiarity or training to use them effectively, especially when contributing. They are not for the faint of heart and require effort to learn.
- Wikis are challenging to search and find information. They typically create silos of information that can confuse or frustrate a customer.
- Wikis are not good for ill defined or generic collaboration.
- They take significant effort to monitor. I would love to see an analysis on how much time the Wiki Editors spend managing Wikipedia. I suspect the answer would be stunning. Most companies couldn’t afford the proportional time and effort necessary to keep up with an evolving wiki.
Many of these customers are now dropping their external-facing wikis, or at the very least, augmenting them with other tools to address customer needs.
There are cases where wikis work well. Customers are:
- Extremely engaged with you and each other
- Work well together as a team
- Focus on specific topics
If a situation meets the criteria above, wikis are fantastic.
I think many companies rolled out Wikis for their customers and incorrectly assumed they were ideal because they give the company one place to go to maintain information. As usual, this is right and wrong. For the company, it might appear to be low maintenance. However, this is a fallacy because the maintenance load grows substantially as the Wiki grows. For the customers, it is not ideal and leads to frustration and antipathy. My advice is to use a Wiki selectively, but don’t make it the central tool to collaborate with your customers.
Tags: collaboration, customer, wiki
May 13, 2008 at 11:12 am |
Enterprise Collaboration and Virtual Teams Report (May 13, 2008)…
The People Part of Enterprise Collaboration and Virtual Teams One vendor argues that wikis are bad for external customer collaboration, due to four reasons. “I think many companies rolled out Wikis for their customers and incorrectly assumed they were…
May 14, 2008 at 4:51 am |
I would use a wiki ONLY for the collaborative editing (group editing) of documents or web pages (manuals, agenda meetings, brain storm lists, …). Not ‘… to distribute information on their company and/or product …’
March 9, 2009 at 2:09 pm |
[...] retrieved date: 02/28/09 [11] “Wikis not ideal for external customer collaboration”, http://blog.groupswim.com/2008/05/12/wikis-not-ideal-for-external-customer-collaboration/, retrieved date: 03/03/09 page_revision: 3, last_edited: 1236632336|%e %b %Y, %H:%M %Z (%O ago) [...]