When wikis have been mentioned on IT Business Edge, the coverage generally has been of the "this is an incredible way to get employees collaborating" variety. In Carl Weinschenk's interview with Patrick Tam, Cisco's senior manager of operations, for example, Tam described how wikis geared toward process innovation, project management and other areas are helping the company move from an environment in "which people work in individual silos to using individual technologies to create more of a collaborative environment."
It's worth noting, however, that even at Cisco, users didn't jump right in and begin using the wikis. Cisco did some upfront "hand-holding," Tam said, providing training to user groups and getting top executives to promote wikis and explain the need for them to their teams.
User reticence to wikis (and other Web 2.0 tools) is not uncommon. In a post on MediaShift, Roland Legrand wrote about challenges encountered by his company, Mediafin, in introducing both internal wikis for employees and external ones for readers of the company's financial markets blog. Based on the tepid response to all the wikis, with all participants appearing reluctant to actually add or modify content, Legrand had a number of suggestions:
A J. Boye analyst reached a similar conclusion and shared her thoughts in a Computerworld article. She faults undue hype with many of the problems associated with wikis and breaks problems down into three "myths:"
The good news is, the analyst provides some ideas for addressing these issues. Among them: