Warwick university campus (which I discovered was, actually, in Coventry). It was a busy weekend: I helped to co-facilitate two sessions (the STEM faculty session and a session that had been organised by the school of computing); I also ran a session that was entitled: delivering excellent correspondence tuition quickly – is it possible and how do we do it?
I’m very aware that I don’t have all the answers to how to do excellent correspondence quickly; modules, tutors and students are all different. In true workshop fashion, there was a flip chart and each table was given a set of post it notes. What follows is a summary of notes that were generated by tutors who attended the event.
Tips from the whole group
The comments below have been gathered from group discussions. They are a mix of tips from tutors about how to do things quickly, and how to offer excellent feedback.
Make sure that feedback is personalised
Focus on 2 or 3 areas that need improvement (as otherwise our students might be overwhelmed)
Link the ETMA (PT3) comments to the on script comments
Use comments to build a relationship: be positive and be clear
Be positive, formal, factual, clear, unambiguous and approachable.
Provide comments that are appropriate to the level; consider comments that stretch students
When marking, know when it is a good idea to stop and take a break
Consider using speech recognition software as a way to provide feedback
If you have a mentor (as a new tutor), do make good use of that mentor
As a tutor, know and understand the course calendar
Consider editing or adding to the tutor notes as a way to collect your own practice
Consider marking TMAs in batches
Use the tutor forums that the module team has provided
Comments gathered from individual tables
The following comments were from post it notes that were gathered from workshop tables. I’ve tried to group them into clusters and have excluded post it notes that are really similar to each other to avoid repetition:
Important: building a relationship (through feedback), timeliness (be prompt with everything)
What should be included: what done well, what needs improvement, student’s name, continuity from previous feedback
Rapport with students; take an interest and encourage
Tone: personal, supportive, warm, friendly by clear, supportive but firm
Include: opportunities to improve, access to support, suggestions about what to extend and improve.
Comments: forward looking on the ETMA summary, backward looking on the script
What matters in your subject? Science: more prescriptive, arts: more flexible
Provide: accuracy and precision, application of [module] concepts, approach to study
Feedback and comments varies according to students, but includes: accuracy, relevance and learning skills.
Reflections
I’ve run this session a few times now, and I always really enjoy them. A discovery is that every session is slightly different; this could be down to the mix of tutors from different faculties, the type of the room that we used, or the number of tutors coming along to the event. This session was the biggest and most popular yet.
Correspondence tuition remains to be an important topic within AL development sessions because it is such an important part of the tutor’s work. I received one bit of feedback that was interesting, and this reflected an earlier comment that I received after delivering the first version of this session (which, I think, took place in Leeds): that there should be more focus on ‘speed’ rather than ‘excellence’. It is a fair criticism, and I’m thinking (on one level) that I might be trying to do too much, but I’m aware that, as tutors, we should never cut corners; there is no question that our feedback should be as good as it could be.
From memory, we did share some really useful speed up tips, such as: use more than one screen, don’t agonise over individual marks, edit your version of your own tutor notes. I feel it very much depends on figuring out what works for each individual tutor. As I mentioned above: modules, tutors and students are all different.
Warwick AL Development Conference 2018
Warwick university campus (which I discovered was, actually, in Coventry). It was a busy weekend: I helped to co-facilitate two sessions (the STEM faculty session and a session that had been organised by the school of computing); I also ran a session that was entitled: delivering excellent correspondence tuition quickly – is it possible and how do we do it?
I’m very aware that I don’t have all the answers to how to do excellent correspondence quickly; modules, tutors and students are all different. In true workshop fashion, there was a flip chart and each table was given a set of post it notes. What follows is a summary of notes that were generated by tutors who attended the event.
Tips from the whole group
The comments below have been gathered from group discussions. They are a mix of tips from tutors about how to do things quickly, and how to offer excellent feedback.
Comments gathered from individual tables
The following comments were from post it notes that were gathered from workshop tables. I’ve tried to group them into clusters and have excluded post it notes that are really similar to each other to avoid repetition:
Reflections
I’ve run this session a few times now, and I always really enjoy them. A discovery is that every session is slightly different; this could be down to the mix of tutors from different faculties, the type of the room that we used, or the number of tutors coming along to the event. This session was the biggest and most popular yet.
Correspondence tuition remains to be an important topic within AL development sessions because it is such an important part of the tutor’s work. I received one bit of feedback that was interesting, and this reflected an earlier comment that I received after delivering the first version of this session (which, I think, took place in Leeds): that there should be more focus on ‘speed’ rather than ‘excellence’. It is a fair criticism, and I’m thinking (on one level) that I might be trying to do too much, but I’m aware that, as tutors, we should never cut corners; there is no question that our feedback should be as good as it could be.
From memory, we did share some really useful speed up tips, such as: use more than one screen, don’t agonise over individual marks, edit your version of your own tutor notes. I feel it very much depends on figuring out what works for each individual tutor. As I mentioned above: modules, tutors and students are all different.