IME it is also important for management to officially recognize the need for a Wiki and provide some minimal resources and time to manage it. Otherwise it beco

IME it is also important for management to officially recognize the need for a Wiki and provide some minimal resources and time to manage it. Otherwise it becomes just another thing for people to add to their ever growing list of things to do. I'm in a team now with a brilliant but highly overambitious manager, and we've got lots of great knowledge locked in people's heads. So three years ago we created a nice wiki and started adding stuff into it. One year later the company reorganized and the group that owned the company wiki master site said they wouldn't pay for it anymore, and that we had to move to a new system. So we did after a lot of work. And guess what happened a year later after another reorg? Putting something in a Wiki also requires you to put in a lot of thought so you properly address the audience that will try to make use of it. And that can range from people who are lazy and need to have their hands held through everything, to people who just needed a nudge in the right direction. With meetings you don't have to be so mindful, apart from knowing which people need to just go away. If there is some recognition from management that a Wiki is required and it officially needs time from people, then there is consistency about what goes in there, the time required, and some escalation process if the Wiki is wrong or outdated. Otherwise it's just another thing you do that gets no recognition that could easily lead to more work.