Wiki Patterns

Maybe a distinction needs to be made

Corporate website - fairly static

Intranet site - changes occasionally

Wiki - very frequent changes

As data matures, maybe as a result of a design process (or a refining process) the data becomes complete and can then be made available on more static sites. The wiki being the tool for creation and frequent modification during the design phase 

While the comment about not understanding the nature of thought may be apt in some circumstances, it's also true that websites don't only represent thought, especially its critical and/or imaginative dimensions.

They also represent policies and decisions, and these generally need to be portrayed as finalised statements, as in the traditional form of publishing embodied in a corporate website or intranet site.

The more common mistake, however, is to assume that ALL information is of this type, when in fact the vast majority is not.

The challenge is changing attitudes sufficiently to have an open discussion about which documents fall into which categories, and how to keep the more static documents in touch with the critical/creative attitude of the wiki through a process like the one metzlert suggests.  

I am running into this for a grassroots organization I am starting at my global software company. One of the main benefits that I see for wikis with my group is a low adoption barrier and easy maintenence. With company intranets especially, very few people have access to contribute or alter content, and they are not usually saavy designers or information delivery people. With a wiki users don't need alot of training to get up and running.