Insights into developing TUPs

My first thought after reading a) the guidebook published by the grad students at Mississippi State, b) several of the articles about technology use plans, and c) two of the existing state use plans, was d) "ugh!, this is not what I want to be doing with my life." Nevertheless, here is some of the insight I was able to glean from the articles:

• It seems obvious, but if a school or institution does not have a vision for its technology use that is closely tied with the mission of the institution, then the technology use plan should probably begin with developing a vision statement. That development process should:
• involve all institutional stakeholders - in a school, that would mean students, teachers, administrators, parents, and members of the local community;
• be an extremely collaborative, transparent, and dynamic process;
• produce a succinct and concrete statement that will maximize constituent "buy-in."

• It seems equally obvious, and especially important in today's economic climate, that the parameters of the overall institutional budget are well understood. My school's yearly budget is around $12 million. If I create a technology use plan calling for an additional $500,000  expenditure, then my plan must demonstrate either a) how my school will be deriving $500,000 of value as a result, b) how student learning will be maximized, or c) how this expenditure is likely to save the school money in the long run.

• Focus on a number of constantly revisited and evaluated short-term plans, rather than one comprehensive five or ten-year plan. Technology changes rapidly, so plans should be relatively simple and flexible. Very few stakeholders will be willing to put their time and effort into developing a comprehensive plan that they know will become obsolete in the medium term.

• Ensure that an "evangelized core" of leaders at many, or all, institutional levels is present. These are people who are flexible and open-minded enough to see the plan through and then evaluate the plan, without becoming too territorial or defensive.

• Ensure that the plan is written in user-friendly terms and that the plan involves provisions for the procurement of user-friendly technologies, applications, and development opportunities for the end-users.
  

• Remember that it is not about the technology, it is about learning and development. The bottom line for a school is about improving student learning outcomes. The technology use plan must specifically address those outcomes. The plan cannot simply be about purchasing new, must-have gadgets.

• Provide for a sensible time-line for procurement, staff development, roll-out, and steady implementation.

• Plan for maintenance and for evaluation of the plan. In some of the literature I have read, these two aspects seem to be neglected and often leave end-users (teachers, in my case) feeling that they are left hanging out on a limb.