While I work at a small district that is comprise of only two schools decisions are still difficult to make. From curriculum decisions, to vendors for our meal programs, decisions are made with the final goal of increased student achievement. Technology is no different, every decision that is made needs to be made with that in mind, while also understanding that decision need to be made based on data, system and application integration and student privacy in mind. This is the reason why it is important educational programs need to have a systematic process when making these decisions. It is too easy to make decisions based on a gut feeling or a need at that moment but those types of decisions usually lead to redundancy, waste or even issues such as data breaches or privacy issues.
Based on this last module I have begun to look at my district decision-making progress in a different way. While in the past I saw decisions as systematic I was never fully aware of how time and priority aspect of it. By this I mean that in the past, I would see every decision as immediate (within the academic year) and did not look two or three years into the future, which as a leader I believe it is important to do. Additionally, when making decisions I would also want to cover everything within that window of a year. Now as I look at the different business units, systems, application and personnel we have I have begun to priorities decisions based on which ones will be the most important to implement but also which will take the longest in order to begin the planning process of implementation.
Education does not operate in a bubble and the work done in module 7 and 8 allows for stakeholders to have data available to them that will provide information to them to become part of the discussion as well as the solutions to the decisions needed to increase student achievement.