Mr. O'HAGAN
  • Home
    • About
    • Contact
  • Blog
  • Other Cool Stuff
    • MA EDL >
      • EDL 680 >
        • 20Time
      • EDL 610 >
        • Habits
        • Culture
        • Platform
      • EDL 600
      • Enterprise Architecture Methodology
      • EDL 655 >
        • Discovery Phase Week 1
        • Week 2 Interpretation Phase
        • Week 3 Ideation Phase
        • Week 4 Reflection
        • Week 5 Reflection
        • EDL 655 Final Project

Module 7

3/6/2016

0 Comments

 
Reflection: Schools are often working against themselves as there are distinct applications for various needs:
  • Teaching and Learning Systems  
  • Administrative Systems  
  • Back Office Systems  
  • Supplemental Systems
Reflect on how you could help to clarify and unify these systems.

In the district that I am evaluating for this class, I see the draw of various departments to have their own systems and processes for their tasks.  Teachers have instructional sheets on the various processes to follow based on the department they need to contact.  This causes confusion and wasted time for the teachers, who have more important things to do, lesson plan, grade, tutor, etc…
Identifying the problem is the easy part.  Solving it is more difficult.  Districts don’t purchase a wide array of counterintuitive systems just for the fun of it.  Most departments have compelling reasons why they need a particular program.  HR, for example, has confidentially (social security numbers, background checks, bank account information, emergency contact information) needs that other departments don’t.  Teaching and learning have specific needs that are integral to the mission of the school district, educating students.  Back office systems and supplemental systems are also specific to their functions.
So again, how do we rectify the problem and make the systems more streamline?  As with any big decision, we need to gather data, and evaluate it.  The systems themselves need to be studied for functionality, purpose, ease of use, security, among others.  Once this evaluation is complete the district should employ an Enterprise Architecture like approach to determine if any uses cross departments.  If they do, then it should be possible to purchase, or create, a system that is multifaceted enough for all stakeholders to use.
Many products currently on the market claim to be a one stop shop for district needs.  As much as I would like to believe that products like this truly do exist, I have to be hesitant until I see them in action.  Pearson makes Power School, which according to them, “technical ecosystem for district and school ... operations.”  This is one system that could be evaluated by the Enterprise Architecture group mentioned above.  If it does provide a complete ecosystem, then this can alleviate many difficulties that districts encounter.
0 Comments



Leave a Reply.

    Author

    Michael A. O'Hagan is currently a middle school teacher and graduate student working on his Masters of Educational Leadership.

    Archives

    April 2016
    March 2016
    February 2016
    January 2016

    Categories

    All

    RSS Feed

Proudly powered by Weebly