This blog post echoes a blog post I made in June 2015. The earlier blog was designed to accompany a presentation that I gave to the Computing and IT student support team, who were then based in Birmingham. Since I gave that talk, things have changed: the Birmingham office is just about to close and the functions have relocated to the Open University Manchester Student Recruitment and Support centre.
This post has a similar aim: to accompany a presentation that I gave to my student support colleagues to given them a feel for what Computing and IT staff tutors do. An important point is that every staff tutor has, of course, slightly different roles and responsibilities. Our exact mix of duties and responsibilities depends on our own expertise and interests.
Another point is that every day can be very different. Here’s what I wrote last time: ‘the below narrative is a collage of aspects from different days. I’ve written it this way so give a sense of the diversity of things that we do. It’s not representative, since every day is different, but it does give a taste of what kind of things a staff tutor gets involved with’
Blitz the inbox
I wake up at any time between 7.00 and 8.00am; I often watch the travel reports whilst I eat breakfast. Now that I’m a home worker, I do find the travel reports strangely satisfying; I take a life affirming moment to reflect that I’m not in the middle of one of those huge snarl-ups on the north or south circular roads.
One of the first things I do is triage my inbox to decide what is important. The exciting thing about being a staff tutor is that anything could happen. I look after approximately sixty associate lecturer contracts (or tutor groups) across three different levels of study. To give an impression of scale, a tutor might (of course) have anything between 18 and 20 students.
My key objective is to get to the messages that are important. So, glance through announcements about conferences and drainage issues. I delete messages that offer reminders about events in Milton Keynes, even though I’m not working in Milton Keynes. I shift-delete emails about fire alarms and electrical testing, and start to read messages, dropping updates about new procedures into folders (I don’t read things in depth if I don’t need to).
TM356 tutor telephone call
The first scheduled event was a chat with a TM356 tutor. Our tutor has been raising some really good points about the design of some online sessions; he’s also very experienced too. We shared views about how things are going on the module, and I make a note about some things that I need to bring to the module teams attention.
After our chat, I receive a delivery: it’s my new desk. To make things easier at home I’ve been reconfiguring my study area, and this has meant trying to find a bigger work area. I haul a big new desk into my lounge and start to puzzle about what the next step needs to be: my desk needs varnishing. I make a mental note.
It is a busy morning: I email a tutor about organising an additional support session, and then send off another email, this time to AL services in Manchester about transferring TMAs from one tutor to another due to a tutor being away on sick leave; a few days earlier I had found a tutor who was willing to cover.
A Microsoft Outlook reminder popped up on my screen: it told me that there was an AL CDSA (appraisal) was due in fifteen minutes. I started to get everything sorted out: I opened up the tutor’s draft CDSA form that he had sent to me and the tutor’s ALAR report in a different screen (I have a two screen setup; my new desk will allow me to have three screens!) I familiarised myself with the contents of the ALAR report: turnaround times were very good, and the student surveys were very good (but like with so many student surveys, not many students had responded; this is always a problem that isn’t easily solved).
I get everything sorted out for the CDSA and give the tutor a call. He was great to talk to; he was committed and dedicated. I asked him what kinds of things I might be able to do to help him in his job, and told him to contact me if he has any suggestions about what AL staff development events might be useful.
After a drop of lunch and a bit of TV it was onto the afternoon stint. Now that the key emergencies had been sorted out, it was time to get onto some academic work. For me, the term ‘academic work’ can mean a whole range of different things.
Over the last year and a half (or so, perhaps a bit longer) I have been a deputy editor for a publication called Open Learning: The Journal of Open, Distance and e-Learning (Routledge).
The journal has an interesting history: it began as an internal OU publication that shared information about ‘the OU approach to teaching and learning’ amongst its many staff. As time has moved on the journal’s remit has broadened, adopting a more international focus. It is still an Open University institutional publication but it is one that is more outward looking. It does, however, maintain its core focus, publishing research about distance education, technology and educational practice.
I spend about an hour looking through the status of the submissions. I try to match up newly submitted papers to reviewers. One paper has been reviewed, and there is a positive ‘accept’, which is always good news. I read through the reviewer comments and have another quick read of the paper before making a final decision.
When this is done, I get onto editing a PowerPoint presentation for an online tutorial that is scheduled to take place later on in the day. I send a couple of pictures I have taken from my phone to my laptop, open up the PowerPoint, and then drop them in. I then convert the PowerPoint into the native OU Live format, and upload the new file as an OU Live preload, just to make I’m fully prepared.
I receive an email from an associate lecturer colleague that I’m working with. We’re working on a tutorial observation research project that is funded by something called eSTEeM, which is all about Science Technology Engineering and Mathematics education. My colleague has started work on a literature review and it looks brilliant. I look in my diary and I fix a time to have a chat about how things are going.
One of the things I really enjoy doing is AL development. I enjoy it because it’s great speaking to all the tutors. At the start of the month I ran a TM470 AL development session for purely selfish reasons: I am a tutor on TM470 and I wanted to run some tutorials, but I was also very aware that other TM470 tutors are significantly more experienced than I am. Put simply: I wanted to steal some of their good ideas, and a way to do this is to find a way to get tutors talking to each other. To do this, I ran an online staff development event.
After the event had finished, I had to do a couple of ‘wash up’ tasks. The first one was to send AL services in Manchester a list of associate lecturers who had attended. The second was to write a quick blog post about the key findings, and share that post to all tutors. I spent the next couple of hours going through the recording of the event, making notes, and putting everything into a blog summary of the TM470 AL development event (blog)
I try not to work evenings (or weekends) but sometimes you just can’t avoid it. It was one of those nights.
At the start of TM356 Interaction Design and the User Experience, some tutors were worried about an event called the ‘Hackathon’. The OU group tuition policy stipulates that each face-to-face event must have an online alternative. The thing is, the TM356 face-to-face Hackathon takes an entire day, and you can’t have an online equivalent of an event that starts at 10.30 and ends at 16.30; it just wouldn’t be humane!
With a blessing from the module team, I made the executive decision to create three ‘parts’ to a longer running online equivalent. After making this suggestion, I realised that I was going to making a substantial contribution to the pedagogic design of these ‘parts’.
The tutors were asking, quite rightly: ‘how are these sessions going to work?’
I made a decision: showing and demonstrating a teaching idea would be significantly easier than writing a document that tutors would then have to try to decode. I had prepped a session, uploaded a session, and I worked with a tutor to deliver a session.
My fellow tutor had some brilliant ideas; we tried a ‘dialogic approach’ to teaching, which means: ‘we asked each other questions’. Listening to two voices is always, in my opinion, more fun than listening to one.