At my workplace, I am on a team that provides Voice over Internet Protocol communications support. Our training and knowledge-based documentation are constantly being updated because technology is dynamic. Lately, we have been updating our training documentation and looking for ways to create centralized collaborative knowledge based documentation. I am tasked with sourcing a Web 2.0 tool that may help create centralized collaborative knowledge based documentation.
I am proposing to utilize Wiki’s to create centralized
collaborative knowledge-based documentation. Specifically, I will utilize a
Wiki to provide training to VoIP Coordinators regarding how to enable Microsoft
Lync phone for enterprise users. Utilizing a Wiki for training documentation will
provide learners a central location to access and share the information.
Additionally, when modification to the Wiki occurs all VoIP Coordinators will
be aware of who and when the modification occurred. In addition to having this
Wiki in a central location, access will be strictly controlled by the
administrator; the administrator will only grant access to members of the VoIP
Coordinators team. Moreover, Wiki’s will enable team members to collaborate by
editing, comments, and/or creating sidebars. Collaboration is imperative
because technology is dynamic; it may require new processes to be added in the
future.
Hi Jesse,
ReplyDeleteI like utilizing the wiki because it make it easy for everyone on the "team" to see when others have modified something too. I'm interested in your project. Do you plan on using any video - maybe to actually show the coordinators how to do the steps involved?
I appreciate the feedback Tami; yes collaboration and transparency is a couple of the reasons why I selected Wiki. I have no plans of video; I just want learners to understand the basics.
DeleteThis comment has been removed by the author.
ReplyDeleteA wiki is a great tool for this type of project. Have you selected which wiki? Also, do you know if you need to control access (e.g. passwords)?
ReplyDeleteI will use PBworks since I am familiar with it; I will control access and let users know how to access the website and grant them permissions to write.
DeleteWhat a great idea, many companies are implementing technologies like this now is the time to see which wiki to pick. Western has something similar called Western's Knowledgebase which is powered by RightAnswers, Inc. I think it might be worth checking out.
ReplyDeleteI appreciate the feedback Dane, I will take a look at RightAnswers. Currently we use Sharepoint; however, it does not notify users what was modified; it only has a time stamp of who edited the document last.
Delete