I recently talked to a friend whose company is considering converting their current intranet over to a wiki. I loved the idea. What's great about his situation is that the technical folks are on board as well. When I show people how a wiki works one of the things I always talk about is the internal uses for wikis and blogs.

There is a great article over at Gilbane about Blogs & Wikis in enterprise applications. One of the many key quotes:

This is a major issue I see quite a bit. A PR or marketing person I talk to goes back to IT and asks about the utilization of a blog or a wiki and they get the cold shoulder.

This is also true in the web development world. If a web firm or IT person does not understand a technology or a tool they dismiss it or try to convince the client to use another solution. That is when I usually step in for the client and ask, "Is your reluctance to use this solution based upon some sort of research or experience, or do you just not know how to do it?" Almost every time, it is becuase the IT department/developer knows nothing about it, and does not want to take the time to investigate it.

The ability to easily create/edit content with blogs and wikis is the real draw. From an end-user perspective I have not heard many great comments about solutions such as Sharepoint. It's just too difficult to use. Wikis to the rescue!

Cutting Through also has a post about using blogs for project management.