With our start of year enrolment period drawing to a close, staff from various UC departments were keen to catch up with the Student First Programme (SFP) team at the March community update.
Hot topics included the programme’s focus for 2019, how the course creation work stream might be approached and some of the issues implementing change in large organisations.
Process Manager, Tim Hatherley-Green highlighted SFP’s key projects in 2019 and was quick to acknowledge that what the team were able to complete this year would not have been possible without the work staff have done in the last 18-24 months.
“Last year a lot of our work was student facing, this year it’s all about improving the processes and systems [staff] interact with to get a student from the moment they register an account on myUC until they pick up their Canterbury Card.”
Student First Programme’s focus for 2019 includes:
- Better application administration – improving the application and enrolment process for students and staff, introducing new ourUC staff portal and pipeline view of student’s enrolment process.
- Academic Model – making course creation easier, a strategy for migrating our academic model out of Jade
- Finance Phase – still in discovery phase
- Support & Maintenance – will continue for myUC and connectUC
- Strategy & Leadership – driving strategic decision making at a senior level
- Transition – transitioning improvements back into business-as-usual
Project Manager – Academic, Rachel Motejo, gave the audience an overview of Course Creation Utopia versus Course Creation Reality, highlighting the scope of work involved navigating this large piece of work.
To keep the momentum of the SFP moving forward, Business Change Manager, Marcus Cullen emphasised the importance of communication cascading up and down the layers of UC’s hierarchy. It’s this action that will instil effective change into UC.
Watch the highlights of the March community update here.
If you have any questions or feedback, please contact the team at firstname.lastname@example.org.