Strand 1: Giving feedback from tasks
You arrived here because you agreed or fully agreed with this statement:
At the end of tasks, I always go through all the items with the whole class so people can check how they did
There are, naturally, times when it is important to do this. There are other times when this is not an appropriate procedure because it slows the lesson, becomes dull and predictable and takes the responsibility away from the learners.
Why is this important? |
Try to think of some reasons and then click here.
- Taking unnecessary feedback:
- Can be boring
- Slows the class down unnecessarily
- Makes people listen to others when they don't want to
- Results in a loss of pace and focus
- Is predictable and routine
- Not taking necessary feedback
- Means you can't judge what has (and has not) been learnt
- Devalues the learners' efforts
- Means that the learners can't see their own progress
- Results in your not knowing whether it's safe to go on
- Means that you can't amend your plan to take account of issues which have arisen
So how do we decide?
Two sorts of tasks |
The first step in deciding how to take feedback is to be clear about what kind of task you have set. If you have done the development guide to monitoring, you'll know this so you can skip through quickly.
- Are you really interested in the product from
the task?
Do the learners need to get the task right before you can go on?
Yes to both questions:- Then this is a product task so you need some way to check if people have produced the right product. This may mean going around the class hearing what people came up with but there are, as we shall see, other ways.
- Is this task simply one to raise awareness or get the learners
thinking about the topic?
Does it actually matter to the rest of the lesson what they come up with?
Is this the final task in the lesson in which the learners are using the targets to do something personal in the language?
Yes to the first question, no to the second question or yes to the third question:- This is a process task:
- What is produced matters a lot less than doing the task itself.
- If you have monitored the task, you already know if there are any problems that need your attention. See the development guide to monitoring in this strand for more.
- This is a process task:
Here's a graphical representation.
Process tasks |
Because feedback doesn't have to be explicit, try some of these ideas
- Change the groupings and get the students to feedback their ideas to each other while you wander around, listen and take some notes (see point 3)
- Appoint a representative from each group or pair and give the 5 seconds only to tell the rest of the class something interesting
- Monitor the task and then pick on two or three interesting things that were said and focus all the feedback on the people who said them
- Thank the students for their efforts and explain that the task was only to get them thinking and you don't need feedback
- Tell the learners to keep any notes they have made for later reference but take no feedback now
Product tasks |
From product tasks, you do need feedback but there is a range of ways to get it. What you choose will depend a bit on the nature of the task
- Get feedback from all the groups or pairs but limit the amount of time they have so they prioritise the difficult issues. For a language form task, for example, this might mean that the groups/pairs themselves choose which items to focus on. Take groups in random order so they never know who's next and stay alert. Starting on the left and going around allows people at the end of the queue to doze off
- If you had 12 items, for example, divide the labour and apportion 3 to each of 4 groups. That way, you cut down on repetition and people stay alert
- Get written feedback by getting the learners to produce a poster presentation rather than talk to people who may not be very good at listening (teenagers, for example)
- Provide the right answers in some form (on paper, via a transparency, on a projector etc.) and let people see what they got right and wrong and ask you questions
- Get the learners to write their responses to the tasks on the whiteboard or via a computer projection
- Mix up the groups to compare their answers and monitor very carefully so you know, for example, that everyone got numbers 5 to 8 right that you only need to focus on the rest of the items
Gauging progress
There's a guide to gauging progress for any development process in this section for some general ideas about how to gather data on your classroom behaviour. In the case of feedback routines, however, here are some suggestions:
- Start at the planning stages and institute a habit of marking all your tasks as Product or Process (some may be both) and then make sure that the feedback routine you have planned matches the task type.
- While you are giving feedback, keep asking yourself: "Do I need to tell them this or do they already know?"
- Make sure you accustom your learners to taking the initiative and asking for feedback on what they found difficult.
- Make notes on your plan recording how long your feedback routines took and whether you think it was time well spent.