\n
![](\"http:\/\/static.arstechnica.com\/assets\/2010\/01\/wiki_barriers_list-thumb-230x130-11765-f.jpg\")
\n <\/a>
\n <\/p>\n
As I continue to research and write my upcoming book on wikis, I keep hearing one word over and over again. That word is “BUT” (complete with all-caps), as in, “I would like to use a wiki, BUT…” or “We tried using a wiki, BUT…”<\/p>\n
What follows is usually an excuse for why the speaker feels that a wiki isn’t a worthwhile tool for collaboration in his or her environment. I use the word “excuse” deliberately, because rarely does anyone articulate an actual business reason, such as a lack of need. When I ask deeper questions, I invariably find that the objection isn’t to the wiki technology itself, but instead to the concept of collaborative authoring and a perceived loss of control over the content.<\/p>\n
The true business benefits of collaborative knowledge sharing, such as improved productivity, greater efficiencies, removing cross-functional boundaries, enabling customer feedback etc., are often lost to a perceived, and understandable, fear. In the modern workplace, we have traditionally been defined, both in terms of success and hierarchy, based on what we know. <\/p>\n
![\"Read](\"http:\/\/static.arstechnica.com\/mt-static\/plugins\/ArsTheme\/images\/read-more.jpg\")
<\/a><\/p>\n