Adopting wiki's - wikipatterns

How do you use wiki's in organisations? How do they fit in your information architecture? Aren't wiki's too loose? In what situation should I use a wiki? What is a good configuration for my project wiki?
An interesting new initiative has been launched to help companies answer these questions. It's called wikipatterns. Go ahead and take a look. Two good posts about wikipatterns can be found here and here. Larry Cannell of Collaboration Loop (first 'good post') asked the following interesting questions after looking at wikipatterns:

• Does WikiPatterns represent a key piece to enabling companies trying to fill the gap between IT and Business and help drive adoption of new technology?
• Can patterns be applied to other technologies like Microsoft SharePoint or eRoom? Are product-specific patterns sustainable or do patterns only apply to a capability (like wikis)?
• Are there, or should there be, patterns for blogs, social networks, or other Web 2.0 technologies?
  
• Can a company harness patterns unique to its cultural norms and behaviors that give it a competitive advantage? Is this an example of how a company might create what McKinsey calls "a formidable competitive capability"?

What do you think?

I'll try to answer the second and third question. The other two require some more thought.
I'd say 'yes' it would be wonderful if we had "blogpatterns", "SharePointpatterns", etc. Due to the different types of information sharing tools, it's hard to decide what fits best when a customer asks for team/project/etc. support. Offering one standard solutions doesn't seem to solve the problem. But letting employees decide for themselves doesn't either. These patterns could be used to help decision makers decide what's best for their company (or am I now answering the first question?). These patterns give us a norm, some general consensus, that this seems to be the best way to go in a certain situation.

Samuel