This blog post is an example of how a blog can be used for reflective practice. I am going to reflect on a training session that I recently ran, and use this reflective practice to help me improve the session for the future and help with my planning of other similar sessions.
On Friday 28th March 2014 I ran the first FE/HE session for The Tablet Academy at Lougborough University. The session was designed to look at the use of tablet devices in assessment, and attracted 8 people from across the country.
There are lots of different people, companies and organisations offering tablet training at the moment, of varying quality and varying price (and no direct correlation between the two), so I was keen that I offered something different, something more than the very easy “look at me and how clever I am with an iPad” type session, that yes can be inspiring, but often doesn’t give people a chance to unpick bigger issues.
Therefore the main focus of the day, was to try to get the attendees to think openly about the use of tablet devices in assessment, including the issues that may arise, and not just the positives that can be brought. We also made the decision to focus on BYOD (Bring Your Own Device) rather than specifying a particular platform (e.g. iPads).
The structure of the day was:
- Introduction presentation.
- Exploring options of how tablets can be used in education.
- Designing, completing, then assessing an assessed activity with tablets.
- Bringing it all together.
Here is my reflection on each part:
I created a short presentation that was designed to set the scene, and to try to create the mindset of not using tablets to replace laptops, but to look at what tablets do that laptops cannot, and how this can be used beneficially in assessment. On reflection, I should have spent less time on this point and more time demonstrating options of what is possible with tablets. I didn’t want to spoil the next activity by giving the attendees the answers to the tasks I was about to set them, but some of the the attendees would have benefited from such examples to help make the rest of the day less abstract.
Exploring options of how tablets can be used in education
We had allocated a significant amount of time (over 2 hours) to this part of the day, which was an opportunity for attendees to explore different options of how tablet devices can be used in assessment. Because each person would have different organisational needs, roles and devices, I created 7 separate tasks (challenges) for them to look at. Each task had some background information, then a set of questions/activities for them to work through which would hopefully guide them through an exploration of that topic, with me facilitating them to unpick some of the issues. I estimated each topic to take about 30 minutes so hoped that people could explore 4 or 5 of the options in the allotted time. As it turned out the tasks took longer than I anticipated, so they only managed to cover 2 of the tasks, which was a shame. For future events, there are various options:
- I could shorten each topic, but then have a section for each topic which is titled “further exploration” or similar – so they could continue exploring at a later day.
- I could have sent attendees some pre course information so they could look at the options and possibly start some of the tasks (even if they only downloaded any required apps, and created accounts where required on them – which would have saved time).
- I could have been more draconian with the time keeping, forcing them to change topics if they spent more than say 40 minutes on any topic. I am not a big fan of this idea, as I need attendees to be comfortable with their explorations, and it is more beneficial for them to unpick a smaller number of options well, rather than more options badly.
- If I increased the time of the introduction, to include a quick demo of each idea, this would then have saved attendees time when exploring these options.
Having jotted down these possible options, I think points 1,2 and 4 above could be used together to improve this part of the session, and is what I will do next time.
Designing, completing, then assessing an assessed activity with tablets
This part of the day worked really well. Working in pairs, each pair had 30 minutes to design a tablet enabled assessable activity. They would then share this with a different pair. Each pair then had 30 minutes to complete the task set by someone else, after which they returned the work to the original pair, who had a further 30 minutes to assess and give feedback.
For this activity I was very strict with the timings, using a countdown timer on an iPad to keep me and the group focused. By setting a very specific and challenging time helped to keep people on task, and stopped the afternoon from ‘drifting’. Attendees very much got into the spirit of this activity, they had a lot of fun (which is good), they were imaginative (which was the intention) and they uncovered a few problems with the logistics of actually getting the task to the other people. The main reflection (which was also echoed by the participants feedback) was they didn’t need 30 minutes to assess the work, so could shorten this easily to 15 or even 10 minutes, apart from that I would keep this part of her he day the same.
Bringing it all together
As with any good training session, it is important that there is a chance to reflect and regroup at the end, and some form of identified action for people to do next. For this I set the task of asking people to identify the 5 Ws – Why, What, When, How, and Who for them to identify a small step that they were going to take to move their organisation forward in using tablet devices in the process of assessment. After the slightly pressurised previous 90 minutes as they raced against the clock, this made for a useful reflecting and refocusing activity. We then had some general discussions and used Socrative as a tool to reflect on the day in general.
Looking at the feedback provided by the attendees all bar one were very satisfied with the day, with some highlighting a few of the points I have made above. A few said they would have preferred the day to be platform specific (e.g. Just iPad, or just Microsoft) rather than BYOD, and a few wanted to see more examples of good practice.
From my perspective, I wanted the day to be a chance for people to unpick the real issues around using tablets for assessment, and as such I knew that people would encounter certain problems during the day, which was good, as better for them to encounter them here rather than with real assessments, however these few problems may have been perceived as outweighing the benefits of using tablet devices, which wasn’t my intention. The biggest problem that people encountered was the BYOD issue – of working with ideas that work across all platforms. Many thought Google Docs would be a good option, but discovered that these didn’t work well on iPads and sharing them was more complicated than expected. I tried to reinforce the point that in reality you use the tablet devices when they are most appropriate and use something else when not appropriate, e.g. It is perfectly acceptable for a member of staff to use a computer to create the assessment, the student to use and tablet to complete it and the tutor to use a computer to mark it.
My thanks go to the staff at Loughborough University for their support, in particular Charles Shields and Farzana Khandia.