In response to my last (substantive) post, What Now? asks how I structure workshops. (No, I didn't plant her, really.) I've been doing draft workshops in writing classes routinely since 2001; at this point, they're such an ingrained part of my pedagogy that I can't imagine life without them. I think that students learn an enormous amount about diagnosing and revising their own work by reading the work of others, and I also think that group workshops teach them that papers aren't love letters to the professor (as one illustrious colleague puts it). I also think that draft workshops are invaluable in modeling how to give feedback.
Since workshops are essential to my first-year seminar, I tell students at the outset 1) that we will workshop a draft or part of a draft from everyone over the course of the semester; 2) that they will have the opportunity to volunteer, but that in some cases I will choose the workshoppees; and 3) that their names will be on the papers when they're circulated.
(I now also tell them to let me know if they think that this will be really painful for them; this lets me avoid the disaster I wrote about earlier. I let those students know that they should be on the look-out for a good opportunity to volunteer.)
The first workshop comes in the second or early in the third week of class. I structure it pretty heavily, because I want them to learn how to do this. As a result of being heavy-handed early on, I can scale things back later in the semester. What I'm going to describe here are our most formal workshops, which I call "Draft Workshops" on the syllabus. We spend about 60 minutes talking about two students' drafts. I distribute the drafts in advance of class, and all students have to read the drafts, write marginal comments, and a letter to the author. And I give them instructions about the letters. (See, I told you I was heavy-handed.) It should start out by describing what you think the paper is arguing; what you think is the best thing about the paper; and finally what kinds of things the author should do to revise.
(For these formal Draft Workshops, I choose the workshoppees and email them a heads-up before I circulate the papers. I choose papers from the middle of the range, that exhibit with particular clarity issues that I think all the students can usefully think about. I tell students in advance that these are my criteria.)
Only I'm a lot more specific about what I ask students to think about for the first workshop than I am later in the semester, because I want the students to learn that "revise" means something more than "tweak." For the first workshop, we typically focus on thesis, motive*, and structure. We've done some work with the first two concepts already, so my instructions ask students to "identify and evaluate" both of those elements of the drafts they're reading. They should then map the structure of the draft by identifying the main point of each paragraph, and make a few recommendations on the basis of all these observations.
This is basically what we do in class, as well. I lay down the following ground rules (which I've poached from Kerry Walk):
- The author doesn't speak for the first 5-10 minutes.
- We start out by saying what we like about the paper.
- We then identify its thesis and motive.
- We then identify issues that confuse us, or that we feel get in the way of the complete development of the paper's argument.
- We then brainstorm a revision.
Often, in this first workshop, we reinvent the thesis ("look, there's this super-cool argument that emerges on page 4!") and then map out a new structure for the essay. That's a pretty significant lesson in what revision can entail, all by itself. My task in the workshop after I get the ball rolling is usually to make general points that extend the students' local observations, and to push students to brainstorm ideas for revision.
I don't do very much reflective or personal writing in my courses. This is a bit heretical in my field -- at least in some sectors of it. But I do ask students, at the end of the first draft workshop, to reflect in writing on what they learned that will help them in revising their papers. I want them to make the connection as quickly as possible that they can get something for themselves out of thinking about how to kick someone else's paper up a notch. I don't collect these writings; it's something that they do for themselves.
While I do peer review in pairs or small groups as well, and I generally find that I like the ways these work best when they're pretty well structured** and in class, or towards the end of the semester with a group of students who've really "gotten" the point of peer review. Sometimes you have a group that's so focused on professorial feedback that it's really hard to get them to realize that they can get something from one another . . . although even then I make them do it, and just structure it more.
* "motive" and lots of other concepts that I use come from Gordon Harvey's "Elements of the Essay." How those concepts organize my teaching will how to wait for another post.
**I don't like doing "worksheets" for peer review, although I know a lot of people who swear by it. Instead, I give instructions about issues to focus on while reading and to include in the letters they write to one another -- writing a letter is a really important part of it, to my mind, since that dramatizes the experience of a reader.
Recent Comments