10 Wiki Strategies for Educators

(This is a copy of a recent post I wrote to my blog http://itcboisestate.wordpress.com about increasing your success with students using wikis.)

Just because you build a wiki, doesn’t mean they will come. This has been my and other faculty members’ experiences in using wikis in the classroom. We all know the feeling . . . the excitement of seeing and then using a type of software that should be just perfect to engage students and to enable community-building. We work during our break time to incorporate this learning technology in our course only to find out that students aren’t that excited about it. I think one of the reasons for the lackluster student enthusiasm toward any type of new technology tool is that they need to learn it. I’m not saying that students are lazy . . . it’s just that the internal question, “what’s in it for me?” probably needs to be answered.

Also, I think that students really have not had (a) that much experience with collaborative projects and/or (b) the collaborative projects they have been involved in left them with negative memories. One person maybe did all the work and there might not have been a justifiable reason for the collaboration in the first place. It’s difficult to design a great collaborative project.

However, teachers are pretty tough creatures, not discouraged by setbacks, rather viewing them as learning experiences and the opportunity to do it better the next time. One of the strongest reasons for using a wiki is to enable collaboration. If any part of your class involves collaboration or a collaborative project, a wiki can be a valuable tool. But students won’t naturally use a wiki without some planning on your part. As I said, if you build it, they may not come.

How can you increase your chances of improving student acceptance of and contribution to a class/group/project wiki? Here are 10 suggestions:

  1. Include detailed wiki instructions or a link on the home page and provide time for practice
    • Most students have never used a wiki before and will need instructions and practice on how to actually use the software. By providing time and instructions for how to use the wiki, students will feel more comfortable in this environment and be more willing to contribute. Make sure you stress that they can’t mess anything up . . . wikis have page versions that save everything! You might provide a sandbox or a practice wiki before your students actually use the real wiki. You might create individual student pages and ask them to answer 5 questions about themselves and insert a picture. The main point here is: Have them practice and get good at using a wiki. Then, they will be ready to work on the collaborative project without stressing over learning the technology!
  2. Post wiki conventions and require participants to abide by them
    • Conventions are a huge part of a wiki’s success. If all students abide by the rules, the wiki community is strong and vibrant. If some are not abiding by the rules, it can become a disruptive and less attractive learning environment. Tell students up front what the expectations are for the wiki and put it on the home page. You may want them to acknowledge and sign a web form, for instance. Here is an example of what you might post for Wiki Etiquette.
  3. Be patient with students and realize they may require technical assistance as they learn how to participate in a wiki environment
    • Remember, not all students are technologically savvy and may need some initial help with the wiki. However, once they get going and see how easy and quick a wiki is, they should start feeling more comfortable and eager to use the wiki for its powerful collaborative features.
  4. Create a culture of trust within the wiki
    • You will need to help your students feel comfortable within the wiki, by creating a culture of trust among all participants. You may want to include some icebreaker activities, to get students to know each other better before they start their “real” activities. You may want to more closely monitor activity at first to engage shy students and to intervene when needed if potentially explosive or harmful interactions occur. In other words, you need to set up and continue to maintain a culture of trust so that students feel safe in the environment while also encouraging them to experiment and take risks. This is not entirely easy to do, but your attitude and leadership can play a huge role in how students perceive their roles and responsibilities toward each other.
    • You might look at some of the People Anti-Patterns on the wikipatterns.com site (http://wikipatterns.com) to see if any of your contributors fit these patterns and think of ways you might resolve these anti-patterns.
  5. Provide clear and explicit course expectations
    • Again, this is an essential part of good pedagogy, but is an important part of working within a wiki. Students should have a clear understanding of course expectations and how they are to use the wiki to achieve the course goals.
  6. Assign meaningful, authentic activities
    • Again, this relates to problem-based learning and should really be a part of any learning experience. Through a wiki, you can facilitate and drive authentic, relevant learning
  7. Include a common goal for collaborative activities
    • Usually wikis work best in a problem-solving environment or something that requires common goals and collaboration. This will help motivate students to work together on completing the goal/tasks/project.
  8. Define and identify student roles, activities, and assessments
    • This is important for any collaborative activity. Defining roles and clearly defining the activity, along with assessments are crucial to the success of collaborative learning.
  9. Remind students of course deadlines and schedules
    • The very nature of a wiki allows and encourages a lot of freedom and self-direction. However, sometimes students need to be reminded of course requirements and deadlines.
  10. Model examples of collaborative activities
    • Since many students have never worked in a collaborative environment before, you will need to model these behaviors and show them what they look like.
Comments