OU blog

Personal Blogs

Christopher Douce

1st Computing and Communications AL development conference

Visible to anyone in the world
Edited by Christopher Douce, Wednesday, 5 Dec 2018, 12:20

Associate lecturer development events generally take two different forms: they are either large multi-faculty ‘generic tutoring’ events that are run at different venues across the UK, or they are small module specific focussed events. From time to time, the university runs a larger events (I remember running a computing and IT event in the London office a few years ago), but these are the exception rather than the rule.

What follows is a summary of what has been called the 1st Computing and Communications AL development conference, which took place at the university student recruitment and support centre (SRSC) in Manchester. Just as with other blogs, this is a personal summary of the event (different colleagues may, of course, have very different experiences and memories!) I’m sharing this summary just in case it might be useful for someone, and also because it will help me remember what happened when I come to do my annual appraisal...

By way of background, the event was for tutors who teach on Computing and IT modules. One of the reasons for running the event is that the subject of computing can pose some interesting tutoring challenges and it would be helpful to share experiences between tutors who teach on the same undergraduate programme. There’s also the importance of community; in recent years the link between tutors and the university department (school) to which they are related to has become more important.

Manchester was chosen as the location for the conference, since it is also home to the Computing and IT student support team (SST). The conference took place over two days: Friday 30 November 2018 and Saturday 1 December 2018. The agenda for each of these days was roughly the same, and tutors were encouraged to sign up for the day that best suited them.

Looking forward: curriculum and school updates

The conference began with a short keynote and introductory presentation by our head of school Arosha Bandara and David Morse, director of teaching. Arosha mentioned the mission and vision of the school: that it aims to ‘empower our students, industry and society, to leverage digital technologies to address the challenges of the future’ and ‘be a world leader in open, innovative distance teaching of computing and communications, founded on excellent research and scholarship’. I noted that the undergraduate degrees were accredited by the British Computer Society, that the school ran a premier Cisco networking academy, and it is playing an important role in an organisation called the Institute of Coding (IoC website). Arosha also touched on research areas that are important within the school, such as technology enhanced learning, software engineering and human-computer interaction (amongst others).

David presented a summary of the computing curriculum and degree programmes, which ranges from introductory level computing through to postgraduate MSc degrees. In collaboration with Maths and Stats, the university will be introducing a new Data Sciences qualification, and the school of Computing and Communications will be introducing a new level 3 Machine Learning and AI module. Looking further to the future, the school is currently recruiting for Cybersecurity lecturers, which might see the emergence of new modules at levels 2 and 3. 

Spot the difference: sharing your practice 

After a brief break to meet and chat with colleagues, there was a series of short 5 minute presentations by tutors about different aspects of their OU teaching. What follows is a summary of the notes that I made during those sessions. 

Some tricks to establish early contact with students 

Charly Lowndes is a very experienced tutor and former OU student who teaches on a range of different modules. One of his tips was: “send them a 2 line email, and tell them to send you a reply to say that they have got it; when you do that, I’ll send you some useful stuff”. Charly also makes an introductory video that he has recorded and uploaded to YouTube; he said that “it’s nice for them to know what you look like”.

Another tips include: if you don’t hear from a student, send them a SMS; populate the module forum with messages; use email rules to process emails (I do this too, filtering on module code). Charly also said “I don’t get stressed if they never get back to me; I had one student who was on his honeymoon” – the point is that the student support team is able to help. Another comment was: “use a range of methods; everyone is different” and use different bits of information provided by the university to try to create a picture of your student.

A strategy for recording student contacts

The second presentation in this session, given by Helen Jefferis, complemented Charly's presentation really well. Assuming that you had made contact with your student, then what? Helen offers a suggestion: use a spreadsheet. Helen begins by downloading a list of students from her TutorHome website, and then adds a set of headings, which includes a simple notes section. I noted down the sentence: “if they reply, things are ticked off; ticks to show that they’re active”. Other approaches may include using tools such as Microsoft OneNote. Also, further information about student interactivity and engagement if available from the OU Analyse tool (which is entire topic all of its own).

Teaching methods on TM470

Jay Chapman gave a brief summary of what it was liked to be a TM470 project module tutor. I found Jay’s session especially interesting since I’m also a TM470 tutor. Jay began by outlining TM470. The module isn’t about teaching technical stuff, it’s about helping students how to write a technical project, and demonstrating how they can build upon the expertise and skills they already have. An important point is that TM470 students can take on different roles: they may be the project leader, the client and the stakeholder. Also, every project is different, but there are some common challenges: planning is important and students can easily fall behind, and a big challenge is the importance of academic writing and critical reflection.

I noted that Jay sends his students an email, then a SMS (if he hasn’t heard from them), and he runs tutorial sessions using video Skype. During these sessions, Jay mentioned that he uses an agenda, and then sticks to it. An important sentence that I noted down which resonates with me (as a TM470 tutor) is: “you have to show me what you did, and how you thought about it”. 

Approaches to working with under-confident students

Jean Weston shared some tips about working with students who might not have high levels of confidence. One tip was to tell them things that they don’t have to do. One suggestion was that with some modules, students don’t need to go outside the module materials. I noted down some practical tips: read the introductory and summary sections first, and it’s certainly okay to read something several times.

When it comes to exams, Jean shared some really great tips. One tip was: write down the blindingly obvious (since the examiner might well be testing whether a student knows the blindingly obvious). Another tip was: “answer the question, the whole question, and nothing but the question”. Also, successfully completing examinations requires you to balance two resources: your brain (what you know and can apply) with the time that is available, and “and answer is better than no answer”.

Other tips are worth remembering, such as: “learn to pick the low fruit, and apply that throughout your study” (or, in other words, ‘it’s okay to be strategic if you need to be’). Also: do get help if you need it, do take the time to talk to somebody if you need to, and take time to understand the vocabulary and complete the activities (since these can directly relate to the assessment questions).

PG teaching: what's the difference?

Joan Jackson gave the first short presentation on the morning of the 1 December. Joan is a tutor on a number of modules, such as M815 Project Management, T847 The MSc Professional Project and T802 Research Project.

One of the big differences that Joan emphasised was the level of skills that can be applied. From her slides, Joan reported that “undergraduate study provides the ‘grounding’ within a field or subject and academic skills” whereas “postgraduate study allows the subject to be explored further to attain a higher level of proficiency through independent study, scholarship, research and professional practice, emphasising critical thinking, synthesis, reflection and effective academic writing”.

An important question is: how do you learn to do all these things? Thankfully, the university has some resources that can be used. I’ll highlight two free OpenLearn courses that may be useful: OpenLearn course: Succeeding in postgraduate study and OpenLearn course: Are you ready for postgraduate study

A further question is: how can tutors develop postgrad skills once the module begins? I made some notes that suggested that there are opportunities: forums can be used to run activities. Students can explore the library to uncover research or discussion papers, than sets of papers can be compared and contrasted. Also, as a brief aside, there are also some resources on the OU Skills for Study pages, such as a resource about Critical Reading.

Cisco accreditation and teaching on Cisco modules

Phil Irving tutors on a number of Cisco modules, such as TM257 Cisco networking (CCNA) part 1, an undergraduate module, and T828 Network Security a postgraduate module.

Phil gave us a bit of history about the OU Cisco Academy (and Cisco as a company) before beginning to talk about the link between Cisco material and the OU approach to study. One of the benefits of the joint approach is that students have the potential to gain an industrial qualification whilst also learning important academic skills, such as academic writing. Students are also incentivised to pass the industrial qualifications. I didn’t know this, but if students pass their Cisco exam, they get back some of their test fees.

Practice tutors: a new approach for apprentices

The final short presentation of the conference was by Christine Gardner and Alexis Lansbury who spoke about the university’s involvement in degree apprenticeships and the role of a practice tutor. Since apprentices have a lot of study to do over quite a short period of time, practice tutors can offer some advice about how to manage their workload. Practice tutors are just one of many people involved with apprentices: there are also module tutors, and functional skills tutors, and the student support team. Practice tutors visit apprentices four times in a year, typically at a student’s workplace, and they will be a consistent contact across four years of study.

An important thing to remember is that degree apprenticeships differ across the UK. There are different programmes in England, Wales and Scotland. There is also something called higher apprenticeships, which can be linked and connected to postgraduate study.

What makes a good online session?

The first of two longer presentations was given by Shena Deuchars. Shena’s presentation was all about the use of breakout rooms in Adobe Connect. A personal confession is that I’ve only ever used breakout rooms twice. The first time was using Blackboard Elluminate (or, OU Live, as the university called it), which seemed to go very well. The second time was using Adobe Connect, and didn’t go well at all (I remember a few voices in my headset saying the words: “what’s going on?!”) and feeling quite embarrassed!

Shena gave us some tips about creating some layouts that we could use to manage breakout rooms. A sequence of actions were suggested: (1) create a new layout, (2) add content to pods, and (3) create rooms. Then to get things going, (4) tutors need to click on the ‘start breakout’ button. Finally, there is the step at the end to end the breakout rooms and to bring everyone back to the plenary space.

Some of the tips were very helpful, such as: try to get people who are willing to use microphones in the same room as each other (you can do this by asking everyone to give you a green tick). Also, in anticipation of a session, a thought is to email everyone to tell everyone that they will get more about of the session if they are prepared to speak (and have a headset).

I found Shena’s session useful, and it was great that she managed to encourage everyone to login to the shared room that she had prepared so everyone could get a feel for how things work. 

During her session I thought about my own recent experience as a current OU student who was recently put into a breakout room. Initially, I wasn’t happy, especially when all of my fellow students volunteered me to summarise all of our discussions during the plenary session. This said, it was really helpful to hear how other students were getting along with their reading. One fellow student made me realise that I hadn’t read some aspects of the module materials as thoroughly as I ought to have done.

One thought I will add about breakout rooms is they take time. I’ve heard it said that a breakout room activity can or should take at least 20 minutes. This means that if you’re doing a number of things in a tutorial, it’s important to pay close attention to timing. In the case of the tutorial that I attended, I found the breakout rooms so useful, and I became so engaged, I was surprised that the tutorial was over so quickly. In retrospect, a thorough debrief or summary after my time in the breakout room would have been useful to help me return to the physical world!

Teaching of problem solving and algorithmic thinking

I’m not going to summarise Friday Jones’s presentation on algorithmic thinking directly, partly because I don’t think I can do it justice. Friday’s talk was one that encouraged us tutors to think about what it means to teach algorithmic thinking and also how we should (or could) respond to students. From my perspective, it contained a number of themes, such as whether we should teach top-down or bottom up, and how students might understand the notion of abstraction.

Some interesting phrases I noted down was: “I teach by epiphany…”, “I taught them that they could solve the problem” and “I don’t want to make tea anymore; I want to question why we do this”; ‘this’ means “they need to ‘get’ why we do what we’re doing”.

Friday’s talk reminded me of another talk that I went to that I saw at the Psychology of Programming Interest group back in September 2018. Friday said that she learnt to program ‘bottom-up’, as did Felienne. Some thought provoking words from her presentation were: “sensimotor level is syntax”, and “motivation leads to skills”. And skills, of course, can be linked to the ability to develop (and implement) abstractions.

Working with the Computing and IT student support team

This second half of the conference was opened by John Woodthorpe, our school student support team lead. In addition to a series of short presentations, tutors were able to have a tour of the SST to learn more about what happens within the Manchester office.

The first presentation was about the Careers and Employability Service (OU website). Next up was a presentation by the colleagues from the Student Recruitment and Fees team. This was then followed by another talk by the SRSC continual improvement and change acceptance team, who look at how to enhance existing student support processes. During the first day of the conference, Claire Blanchard concluded by speaking about the role of the SST from the associate lecturer perspective. Claire also emphasised the role that ALs can play in the school by applying to sit on the computing board of studies.

One thing I got from this session was an understanding of something called the Information Advice and Guidance model (which is referred to by the abbreviation IAG). Although I had heard of this before, I hadn’t really grasped its significance. 

In some senses, IAG can be understood as three progressive stages. Whenever a student calls up the SST, they may first speak with a front line advisor, who may be able to provide some general information. If the query is more complex, such as the need for study advice, the student will then be passed onto a senior advisor (the ‘A’, or ‘advice’ part of the model), who will be able to answer more specific queries. Finally, if the query is one that is both detailed and complex, the student might then begin to receive ongoing detailed guidance from an educational advisor.

Simply put: there are a lot of calls about information, and not so many calls that are about guidance (and some guidance calls can take a lot of time to resolve). 

Activity: Working through student support scenarios

For the penultimate part of the conference, Alexis Lansbury, Computing and IT staff tutor, divided the room up into tables, and gave us a series of student support case studies. Each table had a combination of associate lecturers, staff tutors, and advisors. 

For each case study, we were asked to “discuss how you would respond, what actions you would take, what you are aiming to do to help the student, and whether you would involve other people (ALs, Student Support, Employability Specialists, Staff Tutors) in both the decisions you take, and, the help that you offer”. The case studies covered all levels of study (first year through to final year equivalents), and issues ranging from requests for very long extensions through to catastrophic technical problems. This activity emphasised the importance of taking time to gather information and the need to thoroughly understand different perspectives.

AL development in the school: priorities, needs and opportunities

During the final session, I asked everyone the question: “what would associate lecturer development activities or events would help you to do your job?” Some points that I noted on a whiteboard were: 

  • How to best maintain the student-tutor link
  • Understanding, mitigating and influencing the impact of the group tuition policy (GTP) and learning event management (LEM) system
  • How to best work together in cluster groups
  • How to tailor a session to suit a module and also take account of local geography
  • More discussion and less presentation during AL development events
  • More information and further discussion about the new tutor contract
  • Information about the ‘bigger picture’ (either in terms of the university or the discipline)
  • Discussions and information about how programming is addressed across and between study levels
  • Degree apprenticeships and the potential impact on the tutor role and tutor practice

Reflections

Over two days, over 90 colleagues attended the conference: associate lecturers, staff tutors, central academics, and members of the student support team. A colleague said to me: “it’s a sign of a good conference if you come away learning something new”. I certainly agree! One of the things that I’ve gained from the event is a more detailed understanding of what the SST advisors do, and how important and essential their work is, and what IAG means. I felt that it was a thought provoking and useful event, and I hope that everyone else found it useful too. Fingers crossed we’ll be able to run another one soon.

Acknowledgements

This conference was very much a team effort (with multiple teams)! The main organising and planning group included: Frances Chetwynd, Christine Gardner, Alexis Lansbury, John Woodthorpe and Ann Walshe. Many thanks to Saul Young (and colleagues) and Jana Dobiasova (from ALSPD). Thanks are extended to all presenters, and to Shena Deuchars and Friday Jones who ran the longer sessions, and to Arosha Bandara and David Morse from the school. Thanks are also extended to Stephen Rice, Claire Blanchard, Vic Nicholas, Dawn Johnson and everyone in the student support team who were able to spare their time to come and speak to us; we really appreciate your time!

Permalink Add your comment
Share post
Christopher Douce

Day in the life of a STEM staff tutor (reprised)

Visible to anyone in the world
Edited by Christopher Douce, Wednesday, 15 Feb 2017, 21:14

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.

AL CDSA

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.

Academic work

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)

Evening

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.

Permalink Add your comment
Share post
Christopher Douce

Scholarship, CALRG and SST

Visible to anyone in the world

Going to three events in two days, between 15 and 16 June, was pretty intense but also pretty good fun.  The first event was all about the scholarship of teaching and learning.  A different way of understanding this is: how to go about figuring out how to best do teaching and learning?  It's important to do research into this area not because 'learning' has changed, but the ways in we learn (and the technologies we use) continually changes and evolves: we want to know that we're doing the right thing.

The second event had a similar theme.  It was the Computers And Learning Research Group (or CALRG, for short) conference.  CALRG is a long-running research group in the university's Institute of Educational Technology.

The final event was at the Birmingham regional office, where the MCT learner support staff are based.  During this event, I learnt about a range of different things - but more about this later.  Actually, there was a forth event, an associate lecturer staff development conference, which was organised by the Oxford regional centre (but there isn't the time to write about this!)

Scholarship event

Linda Price opened the event by presenting a definition of scholarship: it is a term that describes research and research action.  Scholarship regarding teaching and learning is activity that uses information relevant to our learning and teaching to inform and enhance our practice.  She also went on to emphasise the importance of evidence.  Linda told us that scholarship was a strategic priority to the university.  She spoke of an internal university project called SHARE, which is intended to help regional staff with the research activities.  An interesting and thought provoking line that Linda gave us was: 'doctors save lives, but we can change them'.

The next part of the event was a series of twelve five minute 'lightening talks' about different research project (I think there were around twelve!)  First up was my colleague Ann from Manchester who talked about 'perceptions, expectations and experience of group tuition'.  Her project was to explore different perceptions and opinions about tutorials.  This research then has the potential to inform a new Group Tuition Policy.   

Next up was a talk that had the title 'What drives scholarship?' I seem to recall that the research was looking at the use of language in assignments, tutor guidance and feedback.  A really important subject is, of course, retention.  I also remember references to Y031 Arts and Languages, Y032 People Work and Society, and Y033 Science Technology and Maths access modules (which help to prepare students for undergraduate level study).

This was followed by: 'A levels based approach to referencing and information management'.  Apparently, some students may drop out, or become demotivated due to the challenge of appropriate referencing.  The national student survey apparently said that different students are given different advice.  The following talk was all about investigating engagement with on-line library services.

An interesting question, from a colleague in the business school was: 'why do we keep failing our Japanese students?'  One of the reasons could be attributed to differences between HE in the UK and Japan.  Understanding and being aware of cultural differences can allow us to gain an understanding of how to support different groups.

Rob Parsons, an associate lecturer colleague from the South East region spoke about peer assessment.  He argued that the student-tutor relationship can be improved.  Themes that Rob's short talk addressed included active learning, learning communities and engagement and retention.

The university is, of course, a big consumer of technology, and there is a perpetual need to figure out how to use new technologies and whether a technology is appropriate for students.  One talk that explicitly explored this issue had the title: Going Live with Google hangouts.

It was then my turn.  I talked about a project that was about the gathering of tutor experiences of tutoring on a second level computing module, TT284 Web Technologies (I horrified to discover that, in front of over sixty people, all of my PowerPoint animations were messed up!)

The talk that went after mine had the title: 'how to get students to do your iCMA and why that is good' (An iCMA is an interactive computer marked assignment).  This was followed by 'investigating one to one tuition: initial findings'.  This project was from the faculty of health and social care.  The research involved interviewing students and carrying out focus groups with associate lecturers.

Sometimes low technology solutions and approaches can be really useful.  An interesting talk was 'an evaluation of the effectiveness of student buddies', which I think focussed on languages and business modules, specifically L185 English for academic purposes and LB160 Professional communication skills for business studies.  The presentation told us about student buddy training through OU Live and a shared 'student buddy forum' on L192 Bon départ: beginners' French.  This reminds me that some of the materials for these modules are available for free through the Open Learn website.

The final 'lightening' presentation of the morning had a slightly different flavour; it was entitled, 'smarter than the average ebook'.  It was given by a colleague from Learning and Teaching Solutions, part of the university that provides some of the technical infrastructure.  We were taken on a journey through different digital formats, ranging from PDFs, epub (Wikipedia) and epub2 files, and then onto OU anywhere.  Some experiments have been performed with ePub3.  These are becoming 'websites wrapped as an off-line experience'.

An interesting point was that 'students are frustrated about being sent away from the text'.  This is a comment that resonates strongly with me.  I found it difficult to study 'off line' even though I wanted to: I printed off lots of on-line materials, but I found myself being directed to various websites and on-line resources.  This is also a comment that arose during my own TT284 research.

One comment I noted was: 'ebook readers are tricky things'.  Different readers do different things.  To close this presentation, we were shown a demonstration entitled 'how to build a methane molecule'.

After a lunch, it was time for the keynote speech.  The keynote was given by our PVC in learning and teaching, Belinda Tynan.  It began with a question: what does scholarship look like across the university.  There are, apparently 15 groups that 'play in the space' that is called scholarship, and that's just the research groups that belong to faculties (not to mention the research that takes place in the library, student services and other departments).  An important question is: 'how is the scholarship impacting the university, and how is it being focussed and directed?'

Moved on to talking about the different methods that can be used in education research. A related question is: how do we learn from each other, how do we share with each other, and how do we cross boundaries and disciplines?  Another really important question, from an institutional perspective is whether we are getting value for the effort that we institutionally put into scholarship.  It was a thought provoking keynote and it really set the scene for the afternoon session (but this was a session I had to duck out of because I had another commitment: to attend one of those fifteen scholarship groups that were mentioned about).

CALRG event

The CALRG conference is a three day conference, which means that I've missed loads of talks.  In case you're interested, the organisers have published a conference programme (CALRG website).

The first talk I attended was entitled: Building understanding of open education: an overview of OER on teaching and learning.  OER is an abbreviation for open educational resources.  The institute of educational technology hosts a research group that is known as an OER hub (website).

The second talk was all about mobility technology and had the title: Conducting a field trial in Milton Keynes: Lessons from the MApp.  I originally thought that MApp was some kind of mapping device, but it seemed to be something rather different.  It seemed to be about helping different people from different cultural backgrounds (or languages) to connect to each other.  I have to confess to being a bit lost at the start of the talk, but then I discovered that the research was using some really interesting methods to gather up some qualitative research.  (This reminded me about a 'diary study project' that I've been mulling over for quite some time, but I haven't managed to get around to doing anything about it yet!)

The third talk was a longer version of the same 'lightening' talk that I gave earlier in the day.  Talking at CALRG allowed me to talk a bit more about the methodology, and some really tentative findings since the analysis is still on-going!  (This, I think, is one the challenges of qualitative research: when do you stop!  One answer is: when you see the similar findings and themes emerging time and time again).

The next talk had the title: Improving language learning and transition into second language learning, through the language learning support dimensions (LLSD).  This talk used an instrument (also known as a survey) to help learners understand more about how they carry out language learning.  Since this wasn't my subject, I struggled to connect with this research, but I appreciated the idea of using a self-directed too to help learners to reflect on how they approach a problem.

The final talk of the CALRG session was 'diverse approaches to using online 'studio' based learning in Open University modules'.  In some respects, the 'studio' can be considered to be an in-house version of the photo sharing website Flickr.  I seem to have a memory that it was used with a digital photography module, to allow students to share examples of their work.  It was interesting to hear that this module was going to be re-launched as a non-credit bearing module (which will have the module code TG189).  Modules such as U101 use a version of this tool called Open Studio.  I learnt that it has now found its way into a total of thirteen different modules, and the Open Studio tool now goes by different names and has a range of different uses. There is also a blog about OpenStudio that is hosted by the university.

The talk led onto an interesting discussion about accessibility.  Whilst an on-line environment might itself be technically accessible, the materials that are transferred to an environment might be fundamentally inaccessible.  One thought about how to remedy this is to try to facilitate collaborations between students.

SST event

The final event I'll mention was held in Birmingham, which is the home of the Computing and IT student support team.  The SST comprises of associate lecturers, learner support staff, advisors and academics.  The purpose of the meeting was to allow the learner support people to meet academic colleagues (and visa-versa) to learn about how we can work more closely with teach other.

There were three rough parts of the day.  The first enabled staff tutors (the academic staff) to learn more about what was going on from the learner support perspective.  The second was a short talk about 'the day in the life' of a staff tutor.  The final section was an update from the faculty Media Fellow.

During this final session I learnt about a project called JIFL, also known as Journeys from Informal to Formal Learning (which remains a bit of a mystery).  There are also a number of FutureLearn MOOCs (Massively Open On-line Courses) that are either currently being delivered, or are in the process of being developed.  These have the titles: 'Introduction of Cybersecurity' and 'Programming one line at a time', which uses the Python programming language (which is used in M269 Algorithms Data Structures and Computability).  Other MOOCs will include one about smart cities and another about renewable energy.

In other news, there is going to be an update to the OpenLearn site, where potential students can gain access to samples of OU materials.  There is also going to be a new programming module, which is intended to help students transition from the first level modules, such as TU100 My Digital Life and TM129 Technologies in practice, to the second level modules, such as M250 Object-oriented Java programming and M269.  This transition module will draw upon materials from an earlier module, M150 Data Computing and Information, and have a focus on problem solving.

In terms of forthcoming media productions, there was a lot of exciting news: there is going to be a programme about Algorithms (and how they relate to our lives), a programme about the life of Ada Lovelace (which contains a bit about gambling), and a documentary called Game Changer, which is about the developers of the Playstation game, Grand Theft Auto.

Permalink Add your comment
Share post
Christopher Douce

Day in the life of a MCT staff tutor

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 17 Mar 2020, 08:26

I’ve written this blog post to complement a presentation that I have given (or are just about to give!) at a faculty student support team meeting on 17 June. The aim of the presentation was to share something about what staff tutors do on a day to day basis. Since I thought that other people within the university might find the presentation (and this summary) of interest, I’ve decided to share it more widely.

I’ve written this summary from my own perspective; other staff tutors within the Open University (and in other faculties) are likely to have very different days simply because of how their role might be split between central academic work and regional academic work.  There will be, of course, common themes: working with module teams, working with student support teams and working with tutors (and doing research, when time permits!)  We also, of course, can and do speak with students.

If you’ve accidentally discovered this post, you might not know what a ‘staff tutor’ is.  It’s a job that is half academic, and half management.  The management bit means we manage tutors.  This management bit can and does directly feeds into the academic bit: we represent the interests of the tutors during module team discussions.  A staff tutor is what is known as a ‘regional academic’. We are currently spread across the whole of the UK, and we might do a whole bunch of different things, ranging from outreach, working with local industries (if time and opportunity permits), and playing a role in marketing events.  I’m based in the London region, and work for the MCT faculty (which is the faculty of Mathematics Computing and Technology).

Before I go on and describe ‘a day’, I should perhaps make a quite note on how I wrote this somewhat eclectic summary.  I began by writing what I got up to during an entire day.  I then thought about other important tasks that hadn't cropped up during the day that I sampled.  In fact, 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 usually get up between 7 and 8 in the morning, depending on what I’ve got on.  If I’ve got to travel to Milton Keynes (the head office) I usually set my alarm clock for 6.30pm so I can comfortably catch a couple of trains.  Most of the time, however, I tend to work either at home, or in the Camden regional centre. On this day, I was up at around half seven, had some breakfast, and was in my study around three quarters of an hour later after quite a bit of early morning faffing about. 

When I boot up my laptop in the morning I usually have a single objective: to get though as many inbox messages as I can, as quickly as I can; this way I can figure out what is important and what is not.  I delete unnecessary calls for papers and scan through a ‘geek newsletter’ looking at new tech headlines.  I then delete a load of messages from Milton Keynes.  This might be: fire alarm notifications, messages about cakes and something about a pathway diversion. There is some stuff that I just don’t need to know about.

It’s important to keep everyone in the loop about what you’re doing, so one of the first things I did was to email our London faculty assistant to tell him what I’m doing.

I have a load of folders to manage my email load.  I see one email that corresponds to an on-going issue (a complaint).  I open up a folder that corresponds to the presentation of a module that I’m looking after, and I drag it in, to create a ‘virtual paper trail’ of an issue.

I see a university conference announcement that relates to an eSTEeM project.  This is a university scholarship initiative; I’m becoming increasingly interested in the scholarship of teaching and learning and I received a bit of funding to run my own project.  I read the conference call and wondered: could this conference be useful for dissemination?  Perhaps it might, but I then decided the timing didn’t work: I needed to concentrate on finishing the project which is about understanding the tutor experience of TT284.  I’ve got loads of other ideas; the challenge, of course, is trying to find the time.

One message reminds me that I need to send a message to all TU100 14J students.  One of my roles is to support the level 1 computing undergraduate tutors.  One thing that I’ve been doing is trying to encourage as many students to come along to the face to face tutorial sessions.  To do this I send them neat, concise messages about their day schools – this means they have all the information they need: information about the venue, information about travel information, and information about the room that they need to go to.  I compose a message to our faculty assistant, asking him to send it out later that day.

One email is interesting: can I help out with postgraduate events (because apparently I was some kind of IT curriculum programme lead?)  This was news to me!  I used to be a postgraduate computing student, but I’m certainly not a curriculum lead.  I sent an email to the regional marketing contact (who is always lovely) agreeing to run a ‘demo tutorial’ for any prospective students who might be interested, suggesting that we had a face to face chat when I’m next in the London office.

A colleague sent me a message that demands a response: Could I contribute to an associate lecturer’s CDSA (or, appraisal)?  Yes, I can!  He’s great!  But there isn’t much to say at the moment since he’s currently on a year out, but I’ll happily write a couple of paragraphs that might be useful.

One thing that I do in the region is help out with the associate lecturer development conferences which offer all tutors on-going professional development and training.  These events are very important: they give tutors an opportunity to meet each other, help tutors become familiar with new educational tools and approaches, and help the regional academics to more readily appreciate any of their worries and concerns. I’ve been helping to organise a session where the tutors would work with two actors who are running a session on dealing with difficult telephone calls.  After sending and receiving a couple of messages, it has been decided: the actors are going to invoice the region.

Releasing monitoring reports

It doesn’t seem like there are any really urgent crises to deal with this morning, so I decide to set another objective: to sign off all off on ALL the associate lecturer monitoring reports that have arrived into a faculty inbox over the last week or two. 

I’ve always held the view that signing off on monitoring reports is an important job.  I hold this view for two reasons: firstly, it’s a really useful way to get an understanding of the correspondence tuition that is delivered to students and secondly, as a tutor, I really welcomed the personal comments that used to come from my line manager.  Here’s what I do: I look at the comments of the monitor, and then the PT3, and then the script, and then add some ‘mediation’ comments.  Some monitoring for other staff tutors who are located in another part of the country has ended up in the London inbox, so I emailed it them a colleague who looks after those.

After a couple of hours of work, I decide it’s time for a well-earned cup of tea.

Academic stuff

During my break I idly browsed the BBC technology pages and discovered an article about a new computing initiative that uses something called the ‘Microbit’.  This takes me down the path of looking at (briefly) some of the history about the BBC’s computer literacy project that ran in the 1980s.  I start to read about someone (who is now a fellow of the royal society) who had helped design the ARM chip instruction set.  Since I often help at the London degree ceremonies in the Barbican I started to idly wonder whether this could be someone to put forward for an honorary degree. From my perspective, their contribution to computing is pretty clear.

I decide to park this, since I’ve already said I would recommend someone else to the honorary degree committee, but haven’t (yet) managed to find the time to write a biography of the candidate that I was thinking about.

A few weeks earlier I had attended an event that was run by the Higher Education Academy (HEA website).  The event was all about teaching introductory computing (personal blog), which is an interest of mine.  I also have an awareness that the faculty will soon start to consider how to replace TU100 My Digital Life (which will take a couple of years).  I’ve got this habit of writing ‘blog summaries’ so I can keep notes of interesting events and share these notes with colleagues.  I finally find the time to finish writing my summary, and I upload it to my personal OU blog after a bit of editing.

Dealing with a module issue

I receive a call from a fellow staff tutor about a student who is persistently unhappy with aspects of a module. We swap student ID numbers, and I look up the student record.  We have a chat about the student, and by looking at the student record, we figure out a way forward.  We both manage the tutors who are delivering the module in question, and between each of us we figure out what needs to be done: my colleague agrees to speak with the student to try to offer some further guidance and explanations.

I send my colleague copies of some emails that I had safely filed away.  I remember that after starting as a staff tutor, I soon realised that effective record keeping is really important.

Working with the student support team

The computing and IT student support team is located in Birmingham.  The members of the Birmingham team respond to student’s learner support queries and help students choose their next module on a programme of study.  When it comes to helping students with certain issues, we sometimes ask students to ring the SST, or we create what is known as a ‘service request’, asking the SST to give students a call: there are things that they can do that us staff tutors can’t do.

I receive a call from a colleague in Birmingham about a particular module, TT284 Web Technologies. My colleague has a very precise question about the module, and it’s a question that I can easily answer (since I work with the tutors who deliver that module, and have worked with the module team).  From my own perspective, it’s great to have that contact with someone who is offering advice to the students.  Also, I feel that due to changes in the way that tutors are managed (staff tutors are now managing smaller number of numbers), we’re able to specialise a bit more, and this will help us to more easily respond to detailed academic queries.

Towards the end of the day

As well as being a staff tutor, I’m also a tutor.  In MCT I tutor on M364 Fundamentals of Interaction Design.  In the previous presentation of M364, I ran a module wide revision tutorial.  I didn’t have to do this (this isn’t something that the M364 module team explicitly ask tutors to do), but I thought it would be a good thing to do; plus, it would help me to get more OU Live experience.  I decided to do the same for the current presentation. 

When I announced that I was running a session, another tutor said that she would come along and help out, which was great news. After quite a few email messages, we chose a date and time. There will be two sessions, and we agreed that we would work together on both of them. Our two sessions will tackle the subject of revision in different ways.

After a bit of a delay, the first stage of the Locations Analysis is out. I discover there are a huge number of documents to read through.  I skim through the main document, which seems to be over eighty pages in length. I quickly become tired.

When I get back I check my email again. There an extension request from a fabulous T320 tutor. I’m very happy to accept their judgement, and I appreciated that they asked me about it.  I offered a couple of suggestions about what to say to our student.

It’s the end of the day.  It has been a busy one. I make something to eat, and then caught a train to the middle of London to meet up with some friends.

On the way back, at Charing Cross train station, I noticed that I had missed a call.  There was a voicemail.  It was from a student of mine. I called the student back and we had a chat.  The student was asking for an extension. I agreed to the extension, and highlighted some sections of the assignment so our student could just focus on completing what he needed to do. I also emphasised a really important point: that there are no extensions to the final TMA. 

Permalink 4 comments (latest comment by Emma lawrence, Saturday, 13 Mar 2021, 08:57)
Share post
Christopher Douce

First MCT Student Support Team Conference

Visible to anyone in the world

I drafted this blog post some time ago, but it got temporarily shelved due to the reality of day to day work.  I never forgot about it, though!  I still feel it’s important to share, since it relates to an important (and on-going) change within the university: the development and implementation of the Faculty of Mathematics Computing and Technology (MCT) Student Support Team (SST).

Introductory bit

Nineteenth of July 2014 was the date of the first ever Faculty of Mathematics Computing and Technology (MCT) Student Support Team (SST) conference that was held at The Open University campus in Milton Keynes.  Although this blog is written primarily for my colleagues, fellow tutors and students might find this summary useful since everyone has been subject to different amounts of change within the university.

The SST comprises of learning support staff (who are based in Birmingham and Nottingham), associate lecturers and central academics.  The idea behind an SST is to create a grouping of people who have more detailed knowledge of how to support students who are studying a particular subject, so we can improve the way that students are supported.  The ideas behind SSTs predate the increased focus on programmes of study due to the availability of student loans for part time students.

Although the SST staff for MCT are based in two regions, all the other Open University regions remain fundamentally important to the operation of the university: they remain centres from where tutorials and day schools are run, outreach events are facilitated, and students can have additional support sessions with tutors (and students can drop in to look at module materials).  They are also essential places from where continued AL development and training occurs.  Without these centres, tutors would not have sufficient training to allow them to offer excellent teaching and learning experiences to their students.

This blog starts with a summary of the plenary or introduction session, and is then followed by a session about retention.  There is then a brief description of session that was specific to the department of Computing and Communications.  This is then followed by an AL development session about disabled student services (this might be of interest to some students who study H810).  The day ends with a session about ‘tutor staff development’.

Introduction plenary

Our former Associate dean for regions and nations introduced the conference and welcomed us all to the SST.  We were shown a bunch of graphs that gave us a bit of context.  I remember that one of the graphs was about the number of students who are studying at a study intensity that is equivalent to full time students (which is a way to allow the OU to be compared to other institution).  In terms of full time equivalent (FTE) students, the number of students in MCT is broadly similar to the number of students in the Faculty of Art and the Faculty of Social Sciences.

An important point is that undergraduate computing and IT modules currently represent the biggest group in the faculty with 60% students registering for a BSc in Computing and IT.  By way of perspective, there are 13K FTE students in the whole of MCT, whereas Birkbeck (as a whole institution) has a total of 17K students.  We were given even more mind blowing stats: there are 1,200 associate lecturers in MCT, who teach a total of 2,900 contracts.

Retention and progression (of students between different modules) is considered to be an important strategy.  One figure that I made a note of was that there was a target of 75% of all students moving to the next module (unfortunately, I didn’t note whether this was related to level one modules only).

Our associate dean also spoke about other university priorities, such as helping to design student interventions (to make study easier), the student induction process (to help students become more familiar with the process of studying) and the development of the OU virtual learning environment (to make smart use of data).  On the subject of interventions, one great intervention that I heard was the SST proactively calling students discuss their study intentions if they have registered for an excessive number of modules.

One of the most important elements of OU study is the relationship between a student and their tutor.  The situation used to be that a student was left to their own devices at the end of a module.  The SST can now talk to a student between modules.

We heard about future plans.  Apparently there is some work afoot to improve the induction process.  For quite a while, I’ve heard about a new induction website, but I really do think there’s an opportunity to do more to help students become familiar with how to ‘survive’ when being a distance learning student. 

Future university activities include an attempt to diversity income, and continuing alignment of associate lecturer services to student services.  Also, quite recently, there has been internal debate regarding a new group tuition policy (which I hope to share some information about to ALs as soon as the details have been defined).

MCT Level 1 retention review

The next part of the day was by a colleague who spoke about a retention review project.  A really interesting fact I learnt was that module presentations that start in October have slightly higher retention figures than modules that begin in February.  I have no idea why!

I’ll do my best to summarise some of the key points that were made.  A really important concern was how well students are prepared for study.  If a student comes to the university without have any prior qualifications, this means that they less likely to complete.  There might be a range of different factors that influence this, such as available study time, workload, and other points, such as a lack of confidence (writing from experience as a former OU student, it takes time to ‘figure out’ how to consume the learning resources that we get from the university.

The one really important point that that has made the difference is: our tutors.  Proactive contact with an associate lecturer can really help to improve retention.

I’ve made a note of some recommendations: it’s important to have consistent module advice, we need to have effective subject specific advice, and have a solid induction programme to incorporate the development of on-line study skills.  The characteristics of a module and its design can make a different too: module teams to consider workload, to carefully consider assessment, and study events should be designed in to the module structure.

According to my notes, the review also offered some really practical suggestions, such as the SSTs could explicitly contact students without previous qualifications (but there’s also a tension between balancing the need to answer the phone in response to incoming student queries, and the willingness to initiate positive interventions: everything has a cost, and everything takes time).

I also made a note of the importance of student support:  AL development is to prioritise soft skills training for ALs (and perhaps points such as using the phone).

Over the last year, the university has made available something called a ‘student support tool’, which brings the associate lecturer closer to the systems that the university uses.  Whilst such tools are great, there is a question which needs to be asked, which is: how can any tool be used effectively.  Again, it’s back to the importance of helping to train and develop our brilliant associate lecturers to make sure that they are as well-equipped as they can ever be to support their students.

Computing and IT session

The next session in the day was by John Woodthorpe, academic lead for Computing and IT.  John opened the question by asking us a question:  ‘Put up your hands if you’re a member of the SST!’  His point was simple: we’re all members! We all have an important role to play.

John asked a rhetorical question about what the members of the SST in Birmingham and Nottingham are doing.  He answered this by providing a long list of activities.  The helped to book and organise exams at different venues, offered study and course choice advice, wrote disability profiles, and were always developing relationships with different members of the faculty.

During the session I made note of the phrase: ‘pre-emption, proactivity, prevention’, which seems like a good way to encapsulate different important aspects of study support.

One gap that has been identified is the need to develop a more comprehensive and structured approach to resubmission support, i.e. what happens if a student doesn’t pass an exam.  At the moment, students could call the SST and request a special session, but not all students know that they may be entitled to this support.  The SST is trying to tighten up resubmission support, aiming to offer more support for students beyond the boundaries of individual modules.

Disabled Student Services

After the faculty session, we were offered a number of different session choices.  I chose a session which was all about disabled student services.  I was interested to hear how the new SST would help MCT students who have disabilities.

We were introduced to different models of disability: the medical model and the social model.  A really interesting point was that people who have disabilities can have a ‘fluid sense of identity’.  What I think this means is that some disabilities may be transitory (such as a physical injury, such as a broken leg), and others may be episodic (such as ME).

We were also introduced to the Equality act 2010, which identifies a number of protected groups.  We were also told about different types of discrimination.  These are direct and indirect discrimination (which I had heard of), but there is also discrimination by association, i.e. discrimination might arise against someone if they have significant caring responsibilities.

We had a discussion about on-line tutorial materials, reasonable adjustments, and the provision of advice and guidance (of which, module accessibility guides play an important role).  We also spoke about the importance of contacting students directly to enquire about the extent of any adjustments that might be necessary, and also the role of examination boards.

Another area that was covered was the Disabled students allowance (DSA).  The DSA covers three areas: ergonomic furniture, personal support (such as non-medical helpers), and travel.  The DSA no longer funds standard electronic devices such as computers since they are now deemed to be an essential part of academic life, but funding for upgrades are permissible.  One really important point is that DSA is only available for students who are studying 30 points and a registered for a qualification (in Scotland this is 60 points).

Non-medical helpers can be really helpful for some students; they can make the difference between a module being accessible and a module being inaccessible.  A non-medical helper always works on behalf of the student: there is a contact between the student and the helper; tutors (or the university) are not able to speak directly to a helper – this relationship is fully controlled by the student.

AL Staff Development: The art of the possible

This final session of the day was all about how we should collectively think about associate lecturer development now that we’re in the new world of the student support team.  This session was facilitated by fellow staff tutor and tutor, Frances Chetwynd.

Associate lecturer broadly takes on two types: generic development (which is about how to perform teaching and learning, to make use of technology, and to be aware of university initiatives and developments), and module specific (sharing good practice about teaching certain subjects).  Now that we’re moving into broad teams, there are opportunities in terms of large subject (or, even programme) specific events.

Like all good tutorials, Frances’s session was very interactive.  We were given sets of post it notes to propose new ideas.  Pink post-it notes were about face-to-face AL development ideas, orange post it notes were about on-line (or other) types of development sessions.  When we had written down our ideas, we stuck them on different sheets of paper that had broad different category headings.

Frances also gave us ten stickers (which were in the form of ‘gold stars’), allowing us to collectively vote for the ideas that we liked best. 

The ones that I’ve noted down are: a session about ‘coding at different levels’ (which could be like some kind of internal symposium), Teaching Sense on TU100 (apparently there is a 10% tutor churn on TU100), making sure that we Record module briefings, and sessions about qualification overviews (or, future plans for modules).  There were loads more ideas, but I haven’t noted them all down.

Reflections

It was a busy day!  One thing that was really good about the conference was that it put the work of the SST and the MCT faculty in context (I had not heard of some of the numbers that our associate dean mentioned) and also helped to emphasise how much change has been going on within the university in the last few years.  It almost allowed us to ‘take stock’ of where we were. 

The session on AL staff development really got me thinking.  I came up with a number of ideas about different types of events that might potentially help tutors from across the UK who tutor on specific modules.  One thing that keeps coming to mind is that there is also more potential in terms of how the student support team members can feed directly into module teams.  I can’t help but feel that these new structures can help different bits of the university to work closer together, and that can only be a good thing.

All this said, it’s still very early days for the student support team and I guess I’m one of many who are still finding their feel in terms of what we do, how we work, and how we communicate with each other.  It also strikes me that although the university has been reorganised along slightly different lines, the notion of a geographic region or ‘place’ remains very important.  The development sessions that are run within our regional centres for our associate lecturers are invaluable.  Developments in information and communication technology has made the SST possible, which means now it’s up to us to figure out how to best take advantages of the opportunities it offers us.

Permalink Add your comment
Share post

This blog might contain posts that are only visible to logged-in users, or where only logged-in users can comment. If you have an account on the system, please log in for full access.

Total visits to this blog: 2273129