EDUCATION BLOG

This summer I’m teaching a technical writing class and as I’ve done in previous semesters with this online class, I’m using a wiki. One of the collaborative writing assignments is an FAQ and although I don’t require them to use the class wiki for this particular assignment, I encourage them to do so (and for any other similar sort of group work).

In order to get some sense of the collaborative dynamics, I ask them to write a reflection memo that they usually submit a day or two after they’ve submitted the assignment. Today while I was reading their reflection memos I noticed an interesting pattern: heavy reliance on email. They describe how they used email to exchange drafts, delegate responsibilities, and coordinate other related project management details. Now on its face, this doesn’t seem all that remarkable, but rather entirely predictable; however, with this particular class, I aim to make the wiki a more central feature. And even though I’ve posted various materials that describe the ways in which wikis typically work better than email for group projects, their memos document a gravitation towards that ol’ stand-by.

In mulling over this hesitation to adopt the wiki as their workspace, a couple of thoughts come to mind. Maybe it’s not just out of habit, but also an anxiety of working on projects in a more public space. Working in the wiki not only makes their group processes available to the members, but the other students in the class as well. Another speculation is that they perceive it as another kind of LMS or stratified space that should be managed and maintained by me, the instructor. Or maybe it’s just inertia: email works well enough and the evidence for migrating to a wiki needs to be more dramatically displayed when they’ve got busy schedules and a myriad of responsibilities.