I think wikis have their place. For example, in a situation where the members of a group who will be editing/contributing to the wiki trust each other, wikis can work well. This could happen in an intranet (say, an intranet for Newton Reference librarians ... we trust each other, right?), or for helping conference-goers connect to others/contribute pertinent information. Wikis have to be structured well, so that the information is well-organized and relevant. I look at wikis more as "architecture" (or scaffolding); and like a building or other structure, a wiki can be really well done/'beautiful'.... or something to be 'torn down'/done away with. Take a look at this website, Wikipatterns:
http://www.wikipatterns.com/display/wikipatterns/Wikipatterns
Wikipatterns has this to say about itself:
"There is no 'right' way to use a wiki. The fantastic thing about wikis, and the reason they have been so successful, is that they are built from the ground up by the people who use them. That way, the structure of a wiki, and how it is used, comes to mirror how the people using the wiki want to structure it, how they want to use it.
One of the most common misconceptions about patterns are that they are somehow recipes. With that misunderstanding, you would read this site as a list of instructions: how to set up initial content, how to encourage people to contribute, how to deal with disruptive elements. Wikipatterns is not an instruction manual, it's a set of tools. It's examples of techniques that have helped people, and of situations that people have found themselves in that they wished they hadn't. We want to help to identify a nail, and know you might want to hit it with a hammer. We recommend against grabbing a bag of nails and hammering them into every wall just in case it turns out to be a good idea."
I will try to find examples of wikis that I think are successful in a future post.