Change management recommendations

For Little SIS adoption to have the greatest impact in your school(s), we recommend the following:

  • Collaborate closely with instructional leadership: A technology team should probably not adopt Little SIS without strong collaboration with an instructional leadership and/or tech integration team.
  • Nail it before you scale it: Little SIS is designed to be “pilot friendly.” By selectively excluding courses, schools, or teachers from your exports, or by imposing inclusion and exclusion rules from within the Little SIS interface, you can start with a smaller group of teachers and work your way up to a full-scale implementation. We recommend this approach!
  • Build change champions: Get your go-getter teachers on board from day one. Classroom should already be in use in some classrooms, and these teachers are your best spokespeople for getting broader buy-in. Ask these teachers to be part of your pilot group. Build their profiles by giving them leadership opportunities in your broader Classroom training plan.
  • Communicate early and often with participating teachers: Let teachers know what Little SIS is, the rationale for its adoption, and how they should expect their Classroom classes to behave differently based on your chosen Little SIS setup.
  • Manual before automated: Job setup errors, data export errors or student scheduling errors could create changes in Classroom that impact many users. Automating too soon could be disruptive if you don’t catch these before they run.
  • Take the time to identify course matches: If teachers have already set up courses prior to Little SIS setup, the tool will try to match them, but this is an imperfect process that requires some manual review. Taking the time to correctly match existing courses with SIS courses will greatly minimize confusion and make sure your Classroom fanatics have a positive experience as their first experience.