CAIeRO workshops are a time-intensive activity, requiring two full days from every member of the team to be most effective. With this in mind, it’s really worth taking the time in advance to agree what the team wants to achieve in that time. The person running the CAIeRO will be a trained facilitator or Learning Designer, and they will always request a pre-CAIeRO meeting, with at least the programme and module leaders but ideally with the whole team.

In the pre-CAIeRO meeting we will cover a range of topics including:

• Background to the programme. We’ll need an idea of what the course is about, who the tutors are, who the learners are, mode of delivery etc.
  
• Why do you need a CAIeRO? We’ll discuss any goals or challenges identified by the programme team that need to be addressed, and also any upcoming QA processes (validation, PSR) that need to be considered.
• What do you know about CAIeRO? We’ll give you an overview of what you can expect, what’s expected of you, and the deliverables.
• What skills and resources do we have available? We’ll review what experience the team has of course design, of teaching on the course, of delivering in the chosen mode, of using NILE etc.
• Who (else) needs to be there? We need at least all the staff on the teaching team. This means those who lead and teach on the modules under review, and ideally also those who teach the other modules in that year or programme. This helps promote a consistent experience from the student perspective, and also allows the shared vision and skills developed to be disseminated to other modules where appropriate. We will also need at least one ‘reality checker’ from outside the team (more on that later). But in order to get the design right, we might also want input from other stakeholders… Students? Academic Librarian? Learning Technologist? Embedded Quality Officer? CfAP? Critical friend? External Examiner? Employer?
• Logistics. When* and where? You’ll need a room with a screen, and with tables for laying out flip chart paper. And although fun, CAIeRO can also be hard work, so don’t forget the coffee and biscuits!

Once we have all the details worked out, your Learning Designer will create a CAIeRO planner document and send out the link to it. This is a working document that we will be using throughout the process. Before the CAIeRO itself, the team can use this document to record their aims for the module, reflections on student feedback, and any ideas or resources they want to include on the day.

*Note: the two days that make up a CAIeRO do not need to be consecutive. There are benefits to keeping the two days together to maintain momentum, but it can also be helpful to leave time in between for reflection, depending on how the team works best. It is important though to put both days in the diary at the beginning. Leaving the second day to be arranged later risks leaving the work half done, despite the best of intentions…

This is one in a series of posts about the CAIeRO process. To see the full list, go the original post: De-mystifying the CAIeRO.
Need a CAIeRO? Email the Learning Design team at LD@northampton.ac.uk.

“I keep hearing about this CAIeRO thing, but I don’t really know what it is…”

CAIeRO stands for “Creating Aligned Interactive educational Resource Opportunities”. If you’re wondering, yes, there is a theme here. The acronym was chosen (although not by me) to align with the Northampton Integrated Learning Environment (NILE).

So what does it actually mean? Think of it as a Course Design Retreat – a full module CAIeRO is two days away from the phone and the email, to build or re-design taught modules, with support from a range of specialist staff. Every CAIeRO will be different, but broadly speaking the workshop has two aims – to develop the modules themselves, and to help the teaching team to develop their course design skills.

This is the first in a series of blog posts examining the different elements of the CAIeRO course design process. The series will cover all of the key interactions, from the pre-CAIeRO meeting through to follow up activities. It will discuss the tools and techniques used in CAIeRO, and their role in course design.

I hope these posts will provide an insight into the process for those that are new to CAIeRO, as well as a reminder for those who have participated in or facilitated sessions. CAIeRO is a work in progress, and we’d love to hear about your experiences, so please feel free to add your own comments, insights and suggestions.

Links to the posts will be added below as they are published. You can also click on the image to see a visual overview of the CAIeRO process.

De-mystifying the CAIeRO:

1. The pre-CAIeRO meeting
2. Programme level CAIeRO
3. CAIeRO Stage 1: The blueprint
4. CAIeRO Stage 2: The storyboard
5. CAIeRO Stages 3-5, let’s get building!
6. CAIeRO Stages 6 and 7, planning and reflecting

Need a CAIeRO? Email the Learning Design team at LD@northampton.ac.uk.

For more information about the development of the CAIeRO methodology, research into the use of CAIeRO, and guidance on how to become a facilitator, see the Introduction to CAIeRO page on our ILT website.

A typical module CAIeRO will often start with programme level exercises, such as agreeing or reviewing the mission, ‘look and feel’, and learning outcomes for the programme as a whole. It’s in the interests of the teaching team – and the students – to (re-)use these elements of the programme’s blueprint when designing at module level – it helps to promote coherence and consistency, and to minimise unintentional duplication. But focusing on the module level, while necessary for planning and supporting good learning, can sometimes lead to a fragmented approach over time. Sometimes you need to take a step back to see the bigger picture.

The Learning Design team are often asked to support teams who need to review and make changes at the programme level. As with module CAIeROs, the reasons for this can be many and varied: maybe it’s a new programme or pathway; maybe there have been significant changes in staffing or in the subject area; maybe the team want to respond to specific institutional agendas or to challenges identified in student feedback or grades; maybe it’s just been a long time since the programme was reviewed as a whole and the team want to ensure that iterative changes at the module level haven’t affected the coherence of the award map. Programme level CAIeROs can be as diverse and bespoke as module level ones, but there are some common goals, and as a team we are always refining our toolkit to support them. You may find you use some of the steps below more or less depending on your needs, but this post, along with the Programme Planner developed by our very own Rob Farmer, will give you an idea of some of the approaches available to you.

Before you start: (Re)establishing consensus

If the programme team haven’t worked together before, or it’s been a while since you’ve had chance to get together for a review, it can be helpful to start by taking the time to share your values, and your views about what the programme should be. This process can help you to agree on what’s really important, and ensure that the programme design will reflect this. It’s also an opportunity for members of the team to share a little about their own perspectives on, and specialisms in, the subject area, so that you can decide as a team how these should be presented to the students.

The programme ‘blueprint’
As always we suggest you start by defining the intended outcomes, if you don’t have these already. Although programme outcomes are slightly different to module outcomes, because they are not directly assessed, many of the same principles still apply. They need to be aligned with national quality standards (e.g. the FHEQ and Subject Benchmark Statements), and with any relevant Professional, Statutory and Regulatory Body (PSRB) requirements if the programme is accredited – and of course they have to make sense to non-experts, including students and employers. Once you have your programme outcomes, you can start thinking about breaking them down into chunks of learning that will form your taught modules – or, for existing programmes, reviewing how well they map to the modules you already have in place. Do you need to add, remove, combine or split anything?

Sequencing learning
Taking a programme level perspective allows you to plan the development of understanding and skills across a larger timeframe, to make sure that the scaffold is sound and your students aren’t missing a foundation piece when they reach the higher levels. To get the sequence right, you can storyboard your programme using a range of tools, from paper and post-its to Powerpoint or Popplet. Move the pieces around until the order seems logical, and think about whether each piece needs to be ‘short and fat’ (intensive) or ‘long and thin’. At this stage you might want to consider the placement of elements that are more complicated to schedule, like placements and trips, as well as those over which you have no control, like holidays and closed days.

Mapping assessment and feedback
It can be really useful to overlay your assessments on to your programme storyboard, to give you an idea of the mix of assessment activity and also to identify any deadline and marking ‘bottlenecks’. Programme leaders will usually collate details of the summative assessments across a programme, because this information is required for processes like validation, but we would encourage you to do this for your formative assessment opportunities too. This will allow you to easily see the turnaround time and where students will receive their feedback – and to identify whether it is timely enough to be useful for the next summative task! If you don’t know yet how your modules will be assessed, make a note to come back to this step, or keep a ‘work in progress’ version that you can update with more detail as you go on.

Key skills and ChANGE skills

It’s often relatively straightforward to ‘chunk’ a programme into modules focusing on particular aspects of a subject, for example by taking a topical or a chronological approach. It can sometimes be more challenging to think about where the transferable skills should be developed – and how often. Complex skills like problem solving and group work often need to be developed in more than one module over the course of a programme, and taking the time to map this explicitly can help you to ensure consistency and progression, as well as making the development of these skills more visible to the students themselves.

Programme design can be a complex business – and this is before you even get in to the details of the individual modules! We recommend that teams who have a lot to do at the programme level leave at least a full day for this type of work, before moving on to the module level CAIeROs.

This is one in a series of posts about the CAIeRO process. To see the full list, go the original post: De-mystifying the CAIeRO.
Need a CAIeRO? Email the Learning Design team at LD@northampton.ac.uk.