Mission Is Possible

  Often when I think of educational initiatives, I often think of Ethan Hunt in Mission Impossible. He is given a monumental task and it takes a heroic effort to accomplish the intended mission. Educators are often given a task but we don't display the same heroics that Ethan Hunt does and it falls by the wayside. Educational technology is a version of Mission Impossible in that trying to meet the needs of everyone can be an extremely arduous task that requires heroic efforts to consolidate support. 

As a technology coordinator, you are responsible to be the lead learner for the technology needs of a district. Every building principal and central office figure all have their own needs and wants for their respective school or department. This mission, should you choose to accept it, is to convince an administrator of not going rogue on a device purchase. How can you accomplish this mission?

Return to the Vision

As a technology coordinator, you have played a major role in the development of the vision as it relates to educational technology. Of course, it is a team effort but when purchasing hardware or software, it is important that the purchase lines up with the vision that has been set. Herrington and Frazier (2017) state that a technology coordinator develops a plan for carrying out the vision and to communicate and work with various groups. The district in which I serve, Jefferson County, states its technology vision as follows: The JEFCOED Technology Department strives to support the success of our schools and to ensure that learning is a student-driven process of exploration, creativity, and discovery. If an administrator is coming to purchase hardware or software, I would first ask if their goals fit within the overall vision of the district.  

Is It compatible? 

Most, if not all, districts unify themselves with software that can be used within the entire district. This uniformity allows for consistency as well as training and support that can be universal. If an administrator is coming for a purchase and the software is not compatible with what the district supports, it would require a conversation that would let them know that it would need to be changed. Returning to my own district, Jefferson County is a Google district. Our purchases support the fact that we are a Google district. If an administrator wanted to make a large purchase of devices or software that was Apple based or iOS based, I would take great pause due the lack of compatibility to what we as a district can support. 

There is an Option

Rarely if ever is one device or piece of software the end all and be all. As a technology coordinator, it is on you to know the ins and outs of all the hardware and software that exists and guide an administrator through the weeds to find one that works for the district AND for them. It is important to have a conversation and work with them through this process. Yes, it may be easier to just say No to their request and move on, but that isn't building bridges and relationships. 

Mission Accomplished!

Following these steps can lead to a positive outcome. It is a difficult road at times, but one that can be achieved with hard work and dedication. 

References

Frazier, M., & Hearrington, D. (2017). The Technology Coordinator’s Handbook.

Technology / JEFCOED Technology. (n.d.). Retrieved April 11, 2022, from https://www.jefcoed.com/domain/1154: