A wiki is best known as a Web 2.0 tool. Although at times criticized because the information in them is not always valid, the premise behind why wikis work has much to do with how the collective wisdom, opinion, and judgment of the masses can outweigh the same characteristics of any one individual. Groups with a common purpose and even totally unrelated contributors can centralize information, participate in wiki development, and update it in a collective, self-paced, and or synchronous manner. Wikis operate on the concept of wabi-sabi, where contributions that are incomplete or unfinished are encouraged as it is expected that others in the community will add-to and perpetually complete the document. If one person creates a wiki item, another can add more content, edit what exists, or augment it with supporting links and references. Because most wikis by nature are versioned, anyone can easily review its change log for editing history and revert back to a previous version as applicable. Reviewers might even openly debate a wiki’s validity in an attached discussion thread. Including open discussions as an attached feature of the wiki facilitates a method of judges through peer reviews and ultimately results in highly valid and relevant content. At the end of the day, it is the community of authors who ensures the accuracy and importance of the wiki as it is consumed and critiqued by its readers.
From a learning perspective (Learning 2.0 tool), a wiki allows its contributors and readers to review, add, and update useful information so they can collaborate and share at a peer level, while learning about topics of interest through projects and group assignments as they are relate to other learning events, resources, and job demands. Some examples follow:
HOWTO-type Wikis:
Wikis are great places to display and collaborate on task-based HOWTO-type documentation such as manuals or guidelines on the use of a tool, method, or process. Sure you could post the actual manual or training guide, but wiki items can address the most important and frequently used tasks as well as the contexts in which those tasks will be applied. Additionally, they can be updated in real-time as the subject matter changes. Depending upon the situation, this type of wiki may only be editable by a group of subject matter experts (SMEs as opposed to all). At the same time, if the tool method or process is new, all who are diving in can be publishing and updating HOWTOs to be shared by all. None-the-less, HOWTO-type wikis are a great way to teach and train others either on a stand-alone basis or as a wrapped follow-up to other learning objects or events.
Best Practice Wikis:
Let’s say you have a new tool or method and need to get beyond the task-based HOWTO-type material because the technology is multi-faceted, complex, or just plain real important. A best practice wiki is a great repository for collecting and documenting information for this set of needs. Again depending upon the situation, this type of wiki may only be editable by a group of SMEs as opposed to all, but because such material tends to be more suited for a globally dispersed audience, keeping it open to all increases the likelihood that unknown experts will contribute. Like with the HOWTO-type wiki, if the technology itself is so spankin’ new you have no experts, you will want to give everyone a place to document best practices so as to capture the collective discovery-process and subsequent experiences. Sure, in this type of scenario, not everything captured may yet be a best practice, but what a convenient way to document those lessons in real time so the community can glean out what is truly best or not while applying them. This way, others can learn about and later avoid the mistakes made by others while openly taking advantage of lessons learned. Depending upon the learning need, best practice wikis can be referred-to asynchronously or on a pre-work, mid-curriculum, or post-work basis.
Wikis as Knowledge Bases:
At a consumer level, knowledge bases allow users to collect, organize and retrieve information. They are either part of an automated system, like with helpdesk applications, or are readable, reference-able, and searchable by users. By design, most wikis bake-in this capability. Thusly, using a collection of wikis combined with full text and or federated search engines can emulate a knowledge base. From a pulled learning perspective, they provide an almost database-like experience for learners who need just-in-time information on the job or while participating in a tandem learning activity. From a training delivery perspective, a wiki knowledge bases allows users and SMEs to collaborate on real time updates. This particular usage will become more prolific as baby boomers retire out of the workforce and millennials (Generation Y) onboard into organizations. Based learning needs and opportunities, this type of wiki works well as an asynchronous learning object or as a follow-up reference to a preceding learning activity.
FAQ Wikis:
If you know what questions or issues your participants will ask, or have advanced notice regarding the issues and problems they will experience, FAQ (Frequently Asked Question) wikis can ease the burden for both the instructor and the learner. These are especially useful when rolling out new programs and assigning homework or group-projects. As such, FAQ wikis work well when presented just prior-to and during program roll-out, and just after assigning homework or group-related projects.
Process Wikis:
If your objective is to teach about a new or updated process, a process wiki allows instructors and process owners to collaborate with new learners of the process. Such a wiki combined with discussion threading could support Q&A regarding policies, procedures, and even graphic of the workflow (a picture is worth a thousand words). A process wiki works well as an asynchronous learning object or when paired as a follow-up reference to a preceding lesson on the process.
Learning Path Wikis:
So the instructional design team has created their blended learning masterpiece and your instructors and facilitators need a place to post the curriculum’s learning path and learning objectives… Hey, your learners need a place where they know to find these things. Because the components of blended curricula now go beyond the conventional first module or lesson in a classroom based student guide or self-paced eLearning course, the learning path wiki can be an excellent focal point for converging the various mediums the curriculum is delivered in. It is especially powerful when the wiki function is part of a larger collaboration suite supporting the blended delivery of the curriculum. Naturally, the learning path wiki is best when made available just before delivery or just as participants are beginning their learning experience.
Assignment Wikis:
Let’s say you are mid-session for a virtual class and you were given a group-assignment or your team was given ‘homework’ instructions through a discussion thread. An assignment wiki is a convenient location for collaborating on the assignment. The versioning features allow the group to track progress and to revert to previous iterations while discussing threading allows the group to discuss, debate, and collaborate while drafting the assignment. While they are doing this, the instructor or facilitator can monitor progress and see who is contributing by reviewing the saved versions. Useful, no? Obviously, an assignment wiki is best delivered as a breakout during mid-session, between sessions, or as part of an overall collaborative experience.
So, what’s a wiki? Set up and positioned correctly, it’s a pretty cool learning medium.
No comments:
Post a Comment
Tell me what you think.