Navigating Curriculum Technology and Management Systems ​

Navigating Curriculum Technology and Management Systems

Presenters Lesley Agostino 5C/4CS - Diablo Valley College Nili Kirschner Woodland Community College Marwin Luminarias 4CS – Fullerton College 2

Session Goals Share experiences with purchase, transition, and implementation Discuss importance of local and state processes in curriculum management Share tips and tricks for developing productive relationships while navigating curriculum technology 3

Fullerton Experience CurricUNET Multi-college district 2 credit, 1 non-credit CourseLeaf vs. eLumen Waiting for Chancellor's office to choose vendor? 4

Diablo Valley College Experience Background Multi-college district, all on different systems DVC Curriculum, SLOs, and program review on three separate systems Web Curriculum System (WCS) Student Learning Outcomes (WebSLOs) Program Review (WEPR) District Wide Selection Only one?! Design/migration phase Training from eLumen Moving from WCS to eLumen Implementation phase Use test environment 5

Yuba Community College District (pt. 1) Background: Multi-college district transitions Paper Curricunet CurrIQunet Meta eLumen Things to consider in the selection phase: Start process of getting buy-in early, and keep it up. Involve both behind-the-scenes stakeholders and faculty users. Do the standard user roles/permissions and reports work for your institution? Can you customize? Find out in advance if there are service charges for additional reports or customizations In a multi-college district, what must be the same and what can differ? Who needs to be involved in next stage? 6

Yuba Community College District (pt. 2) Things to consider in the design/migration phase: Avoid unnecessary customizations, but don't be shy to ask for changes to meet regulatory needs Cross functional teams to ensure data integrity during migration Be as flexible as possible on data continuity Things to consider in the implementation phase: Scaffolded implementation – "baby steps" to ensure buy-in Don't rely on vendor to provide training; tailor it to your needs Expect more changes in the first year and beyond! 7

What drives curriculum processes? Curriculum processes need to follow state regulations and guidelines as well as local policies and procedures. What happens when technology affects your processes? Suggestions for a Smooth(er) Transition Standard reports may not work for CCC reporting needs Try to identify pain points in advance and choose the system with the fewest Standard roles/permissions may not work well with your org structure or local processes Work proactively with vendor during implementation to find solutions Systems may not "talk" or may store info differently Approval/publishing/deactivation workflows in system may not align with local approval timelines Communicate differences between old and new systems clearly to stakeholders and users 8

Working Relationships During Transition Who does what? Roles/permissions in the software that do not match your process When technology dictates job descriptions Don't forget to keep your bargaining units informed Special challenges in multi-college districts 9

Stages of Tech Transition Grief 10

Questions? Lesley Agostino, Curriculum Specialist, Diablo Valley College [email protected] Marwin Luminarias, Curriculum Specialist, Fullerton College [email protected] Nili Kirschner, Curriculum Chair, Woodland Community College [email protected] 11