It took me a long time to become a Google Docs convert. I played around with the app as a tool for collaboration in an upper-level course one term and it was a total disaster, mainly because students didn’t know how to use it (and neither did I, really) and we often ran into issues when students attempted to access documents that I had shared with them (I think this had much to do with Google Docs’ bugginess at the time). I subsequently used Docs only when needing to access a document that had been shared publicly, and in doing so, began to see the utility in creating certain documents in the app so that I could hyperlink to and even embed them on a class website or whatever social media tool the class happened to be using.
The collaborative magic of Google Docs did not really appeal to me until I was forced to use the app to collaboratively edit an article that I had submitted to Hybrid Pedagogy. After submitting the draft of the article, the editors, Jesse Stommel and Pete Rorabaugh, provided me with feedback via the commenting feature and then Pete and I used the in-document chat feature to discuss how best to integrate their ideas with mine. As I worked to revise the document, Pete (virtually) worked alongside me, serving as both sounding-board and devil’s advocate and providing me with synchronous feedback on my revisions. It was an eye-opening experience, not just because I was unaware of many of the tools available in Google Docs (such as the revision history feature and the chat tool), but because of how powerfully the act of collaboratively revising a piece of writing affected me. I had always wrote alone, in isolation, never with someone looking over my shoulder and certainly never engaging in a dialogue about my rhetorical choices (and possible alternatives) as I was making them.
If writing collaboratively had such an impact on my writing, I began to wonder what kind of impact it could have on my students’ writing. So I began to consider how I could use this powerful tool that I had been poo-pooing for years as a weapon against the isolation, anxiety, and despair that I so often see plaguing my First-Year Composition students.
I know that there’s been a lot written about the value and utility of Google Docs in the classroom, so I won’t bore you with a rehashing of what others have already so effectively said. ProfHacker has written quite a bit about the app and their post “GoogleDocs and Collaboration in the Classroom” is chock-full of links to various tips and useful ideas. Getting Smart’s “6 Powerful Google Docs Features to Support the Collaborative Writing Process” provides an excellent step-by-step guide to using Google Docs especially for collaborative writing. And for a basic overview of Google Docs’ features and potential uses, you can browse through this slideshow:
By no means have I explored the full potential of Google Docs. But I would like to share a few strategies that I’m trying out in my Basic English Skills class this term that seem to be having an especially powerful impact on my students’ writing.
I’ve always used journals in my literature and writing classes, whether they were reading journals, learning journals, or writers’ journals, because I believe that the most powerful thing we can teach our students is how to be more “meta.” But there are several problems with student journals. The main problem is accessibility because I honestly never enjoyed lugging around armfuls of composition books, 3-ring binders, and plastic folders (or whatever else students had handy to stuff their hastily-thrown-together-at-the-last-minute “daily” journal into). Which brings me to the other problem. Since it was logistically impossible to check journals every day, I would usually take them up three or four times a semester, which meant that students could very well wait until the last minute to write all of their journal entries (but ingeniously writing each entry in a different color ink to disguise their act of subterfuge). This also meant that students were without their journals for the few days in which it took me to read and record their entries.
These are the reasons why I became an early adopter of student blogging. By having students blog instead of keeping analog journals, I could monitor their entries (and when they were doing them) without inconvenience to the students or myself. But students are sometimes hesitant about or resistant to making such informal, and often intimately personal, writing public. So, this term I have asked my Basic English Skills students to keep a daily journal (which can be on anything they wish to write about and functions to help them build their writing muscles) in Google Docs, which they’ve only shared with me. Besides alleviating any anxiety students might have felt about making their journals public, Google Docs allows me to easily monitor new entries (whenever a Doc is edited, the title turns bold) and to verify when students are completing their entries (by using the revision history feature). Aside from how much easier it now is to ask students to keep journals, I’m also enjoying reading their journals and learning more about their lives outside of the classroom (many of which are filled with challenges and struggles that often leave me in tears and/or feeling extremely blessed).
Writing in Teams
The sources that I referenced above have already pointed out the benefits of using Google Docs during the brainstorming and peer review processes. But I wanted to attempt to channel some of the power of those collaborative writing sessions that I shared with Pete Rorabaugh to help alleviate some of the angst that many of the students in a remedial writing class experience as they work their way through the entire writing process. So, I decided to have the students write in teams of three, with one team member serving as lead editor each week. The lead editor is in charge of each week’s blog post, which includes coming up with a focus question and locating 2-3 sources to help them answer their question, which they share with their team before the week’s first class meeting (I have had the teams indicate each week’s lead editor in a spreadsheet in Google Docs so that I am aware of which students are in charge each week).
But it gets really interesting when the teams come together in the week’s first class meeting. The lead editor creates a Google Doc, which they share with their team and me, and type in their focus question and a brief summary of how they plan to answer it. What follows is a 30-40 minute session in which the team discusses the question, the lead editor’s sources, and their plan for answering the question completely in writing in the Google Doc, observing a strict rule of silence (I adapted this activity from Lawrence Weinstein’s “Silent Dialogue” activity in Writing Doesn’t Have to Be Lonely). The purpose of this activity is to force the team to flesh out the lead editor’s ideas and to communicate all of their ideas in written form. This is beneficial for the lead editor because it provides them with sounding-boards and devil’s advocates and by the time they leave class, they have a much better grasp on what it is they want to say and how best to say it. It also benefits the other team members because it gives them more practice in expressing their ideas in writing. And it allows me to monitor the team’s work and provide my own feedback early in the writing process before the lead editor begins writing a draft that might be too ambitious in scope.
Aside from the pedagogical functions of the collaborate brainstorming session, the human factor becomes more obvious and explicit (a factor that, unfortunately, we as teachers often forget about). The docs lay bare the students’ hesitancies, their false starts, their doubts, their over-shootings, their assumptions, their candor, their egos, their camaraderie, and their humor. Here’s an example of one team’s silent dialogue session:
The next step in the process is for the lead editor to come to the next class meeting with a rough draft that they share with their team and me. The team then begins the process of revising, proofreading and editing, and designing the blog post. Again, I can use the revision history feature to monitor the transformation of the draft, verify that all team members are contributing, and provide feedback on the effectiveness of their work. All in all, this aspect of the collaborative writing model has been successful because of the synchronous access that Google Docs allows me to have to the students’ writing process, and I’m not sure that it would be as successful without it.
What I think I see as I read through the teams’ weekly brainstorming and collaborative writing sessions is a sense that they are not alone, that they have peers who are capable of helping them and who are invested in their writing as much as they are their own.
What a powerful thing for students to feel.
And while I can’t say with 100% certainty that the writing that is being produced would not have been as good if the students were not using Google Docs, I’m so confident that it is that I’ll be putting it to the test in my regular FYC classes next term.