-
About
Our Story
back- Our Mission
- Our Leadership
- Accessibility
- Careers
- Diversity, Equity, Inclusion
- Learning Science
- Sustainability
Our Solutions
back
-
Community
Community
back- Newsroom
- Discussions
- Webinars on Demand
- Digital Community
- The Institute at Macmillan Learning
- English Community
- Psychology Community
- History Community
- Communication Community
- College Success Community
- Economics Community
- Institutional Solutions Community
- Nutrition Community
- Lab Solutions Community
- STEM Community
- Newsroom
- Macmillan Community
- :
- English Community
- :
- Bits Blog
- :
- A Feedback Policy with Unintended Positive Results
A Feedback Policy with Unintended Positive Results
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Earlier this year, I shared my strategy to bribe students by offering extra points for those who turned in their work before Spring Break. I had some success, but there is still room for improvement. I am currently teaching a six-week summer session class, and I’ve accidentally found a strategy that encourages students to turn in work sooner, rather than later.
The challenge of a summer class is jamming fifteen weeks of work into six weeks. Every day in the summer needs to cover as much material and work as two and a half days in the fall or spring classes. My normal routine is to have a rough draft due one week and the final draft due the next week. That schedule allows me to provide feedback on the rough drafts so that students can use the information as they revise.
As I set up the schedule for the course, I realized I would be unable to keep that set-up in place. Realistically, I have to cover a new project every week, assigning the project on Monday and then asking for a rough draft due on Wednesday and a final draft due on Friday. My late policy gives students a three-day grace period, during which they can still turn in their work without any penalty.
I bet you can see the problem. I cannot push the rough draft any earlier in the week if I want to allow students time to process and work on their projects. I decided to tell students that I could not give them feedback on rough drafts that were turned in after Wednesday. Even with the small class size during the summer, it isn’t realistic to think students can turn in drafts later and still get feedback before the final draft is due. I added this paragraph to the assignment:
I will not provide individualized editing or revision feedback on rough drafts submitted after 11:59 PM on Wednesday, July 17. I will provide everyone with collective feedback that goes over the issues that I see in the drafts all members of the course submit. I may use excerpts from your draft to provide collective feedback to the class, based on the Anonymous Use of Student Texts policy.
There is no grade penalty involved. Students earn the same number of points no matter when they turn in their drafts. The firm deadline only relates to the individualized feedback involved.
The surprise for me came that first Wednesday night when I checked to see how many drafts had been submitted. Eleven of my fifteen students had turned in a draft! That’s an amazing 73% of the class, far outweighing the 31% who turned work in early during the spring term. Amazing!
I feel a little selfish about the policy. After all, my job is to give students feedback. Within the time constraints however, it was the only option that seemed reasonable. I never expected the policy to entice so many students to stay on track and turn work in on time.
It seems as though I have found a bribery strategy that is working. Will it last through the entire term? I’ll have to let you know after a few more assignments. I am certainly wondering whether I should try it in the fall as well. What do you think? Do you limit the feedback that students can receive from you? I would appreciate hearing from you. Just leave me a comment below.
Photo credit: wocintech (microsoft) - 114 by WOCinTech Chat on Flickr, used under a CC-BY 2.0 license.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.