Last weekend’s BESIG workshop, facilitated by David Petrie, was titled Personalised learning programmes – a pick and choose approach. David touched on issues such as personalised learning, differentiated instruction and teaching the student instead of the lesson. Towards the end of the webinar, he shared three activities for using students as resources and offering personalised learning:
1. Office modals
Ask Ss to make three lists:
- Things my boss makes me do
- Things I think it’s important to do
- Things it would be a good idea to do around here.
Ss explore the items in these lists by reframing them using some suggested modals.
2. Office gossip
Ask Ss to work in pairs to share some hopefully innocuous gossip. Then put Ss into new pairs and have them share the gossip they heard using reported speech.
3. The meatloaf game
Ask Ss to write down ten things that are a part of their job role that they like doing and ten things that they hate. They should write each item on separate piece of paper. I think ten’s a bit much for even a medium sized class – five might be more manageable.
Have Ss crumple the chits and play snowball fight with each other. Call time after a minute and have them collect chits so they are all equally distributed. Ss spend a couple of minutes reading through the chits – there’ll probably be some items that they dislike doing. They should negotiate with other Ss to trade job responsibilities so they have a list of things that they more or less like doing.
David, like many of us, uses Google Forms to collect data during the needs analysis phase. He suggests distributing the form through a web app so it can be accessed easily on mobiles using a tool called Appgeyser which reformulates your web-content for the mobile device (Here’s an example he’s created). I’m not sure I see the point of doing this. Google Forms accessed via a normal mobile browser seems to display content fairly well and it makes sense to pin a web-app to the user’s mobile screen only if you want her to repeatedly access the link. David uses QR codes to share the Appgeyser URL (but you could do this with a normal URL as well) and Appgeyser offers a short URL. I see two issues with this: QR codes cause more problems than they solve especially when Ss are expected to use their own devices (and they’ve really not taken off in India); and the Appgeyser short URL is really not very short and would benefit from additional shortening using Goo.gl. Appgeyser is worth exploring but I think there are far simpler and more efficient ways of distributing surveys created in Google Forms.
- Petrie, D. (2015) Personalised Learning IATEFL BESIG workshop slides