# A step-by-step guide to technology change As we have seen, there are various models to support different approaches to technology change, but the goal is ultimately the same: to provide a better learning outcome for students. Indeed, Manako’s [hierarchy of technology in schools](http://doug-johnson.squarespace.com/blue-skunk-blog/2014/8/23/a-hierarchy-of-technology-in-schools.html) has infrastructure at the base of the pyramid, working up through effective administration, extensive resources and enhanced teaching to achieve the pinnacle of empowered students. So, practically speaking, how can your school reach the summit of this pyramid? The Knoster model proposes that there are several elements required for successful change, with different negative outcomes if any of these elements are missing. These are:

Elements for Successful Change	Guiding Questions	Without It
Vision	What is the purpose of the initiative? Why?	Confusion
Skills	What experience is needed to realise your vision?	Anxiety
Incentives	What motivation or encouragement does your team need to buy in?	Resistance
Resources	What tools and structures are needed to achieve your vision?	Frustration
Action Plan	What steps will you take to succeed? What is the timeline?	False Starts

Source: Managing Complex Change and the Human Element of Customer Experience. ORI

{% hint style="info" %} When implementing technology change in your school, this provides a useful framework for making sure your project has all the elements required for success. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guide.fariaedu.com/leading-technology-change/a-step-by-step-guide-to-technology-change.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.