Wikis as intranet

I was excited to learn in yesterday's All-Staff meeting that our IT department is planning on doing away with our sorry old Intranet and replacing it with a brand spankin' new wiki. Using wikis as internal document management tools is a great idea.  Our web development team has been using a wiki to store meeting minutes, agendas, comments, resource links and other documents for almost two years now and it works fabulous.   A couple of things I have learned from that experience is to make sure that everyone gets the training they need to use the darn thing.  IT seems to think everyone should be born with technology savvy capabilities, but most people aren't inclined that way, or at least not without a bit of practice first.  Second, make sure everyone understands the concept of wikis: all participants can collaborate -- that means you can edit and you can add and you can delete.  Unless you want everyone to participate with full rights, that means thinking through who has what rights to what content.  On an intranet, that can be sensitive, so its wise to think through all the possibilities.  I'm working out the details for a collection development/acquisitions wiki and need to figure out logistics: 

• Who needs access to what content and at what level? 
• What documentation do I want on the wiki?
• Will there be sensitive information on the CD wiki?
• What kinds of CD resources do I need to include for the liaisons?
• What kinds of forms would be helpful?
• Should I supply a vendor page? What information would be useful?
• Should it be available to faculty?
• Will policy information go here?
• Should I have links to reports or statistic pages?
• What about budget information?

At least I have a start.  Work begins this summer.  We shall see how fast it progresses...