Decisions I don't want to make as a tech director

While we all crave power and control at some level, there are quite a few policies and procedures I simply do not want to create - or at least create unilaterally - as a tech director. Nor should any tech director working in education. These decisions include:
- What Internet resources to filter
- What devices to use in 1:1 programs
- What e-books, e-texts, databases, adaptive learning programs, and other instructional materials to use
- What (or if) games should be allowed in school
- What learning management system to support
- What computer OS to support
- Whether to use a classroom device monitoring system
- Whether to support interactive white boards
- What metrics are used to determine student/teacher/school success
It's my experience that too many school IT folks forget to discriminate between setting policies and enforcing policies. And while I am more than happy to provide guidance based on my IT knowledge, teaching experience, education, librarianship, and readings, those setting educational goals should have the final say in these decisions. I am happy to share my (often strong) opinions, but I always want to be considered as one voice among many.
Too often instructional leaders are happy to pass all responsibility for technology implementation, including policy-setting, on to the technology department. Bad move. As I've written before, teachers and techs usually have competing priorities.
Teachers are usually about access, effectiveness, and ease of use.
Techs are usually about adequacy, reliability, and security.
All worthy priorities. But competing.
Remember my fellow tech directors, just because you are given the power to make an educational decision, doesn't mean you must do it.
A good policy for good policies
Librarians are from Venus; technologists are from Mars
Problem or dilemma?