This is a helpful question to ponder at this point. I think I am beginning to see what some of the priorities have to be for the tech director at this point. On the other hand, I am sure my perspective will change as I learn more about the position.
One thing that strikes me about the tech director position is that one has to learn to ask for help from others and, hopefully, have a few colleagues to work with. The tech director, for instance, will not be a full-blown network administrator; that’s really another position, by definition, requiring substantial and specific training. However, the tech director needs to know some basics about how networks work, since the director is involved in purchasing a network infrastructure, assisting end users one-on-one with concepts like saving files on network shares, setting up their email or a network printer, or simply understanding the importance of changing their password(s). The rapport one gains with the network staff by knowing something about their field will benefit the cohesion of the whole tech department.
It goes without saying that a tech director has to wear many hats, even in larger organizations. That actually may be the thing that makes the job more stimulating—you get to do various things in your day. The need to be organized will also have to be one of the top priorities. One needs to plan one’s day/week for getting things done in the most efficient way possible and yet be able to respond immediately to the most pressing things that come up in the course of a day. Restructuring one’s schedule for the subsequent days will then need to take place. Areas that I would think require the greatest organizational skills would be purchasing (including researching vendors and bidding), and then keeping track of inventory, including creating databases that store info about hardware specs and software licenses attached to those pieces of hardware. Good reporting functions also need to be built into those databases. These would probably be the most time consuming responsibilities. If one is involved in raising money for the institution (for instance, writing grants), that, I would think, would be quite time consuming also, though it may only be a concern at certain times of the year. Areas I would think would be the greatest joys (as least for this trainee), would be conducting training (on email and networking principles, for example) with teachers and students and putting together a tech plan that integrates technology into the curriculum. The latter would involve things like researching and testing educational (and administrative) software, and setting up and leading mini research and testing on software use in actual classrooms.
From the perspective of what would be the most difficult to do for a beginning or first year tech director, I would say that would have to do with where that person is best prepared from his/her past training. I do not believe any one area is inherently more difficult than any other, but some areas probably are more time consuming. Personally, this trainee finds desktop support and network support easier because I have worked with those kinds of things, whereas working through the purchasing and bidding process, including writing grants evokes the greatest anxiety. My advice to beginning tech directors would be to get some kind of a cheat sheet for the budgeting codes as well as secure some solid examples and “templates” for the bidding process and grant writing process, from either the previous tech director or someone in the business department. Thus, in putting together a preparation course for a tech director, I would emphasize the purchasing and bidding processes. Although it is one thing that I personally enjoy, putting together a tech plan can be a difficult task, mainly because it involves getting on board with the vision of others in the school. In previous positions, I have learned, sometimes through a painful process, that my vision for what children need to learn and what software best assists with that is not always shared (in any significant way) with others who have greater tenure at that school or institution. As the Bailey/Frazier text says, as well as our instructor in TLT 474, another key skill one has to learn is the ability to swallow one’s ego (not to mention having a sense of humor).
2 comments:
Technology directors definitely do have to wear many hats. You're right I don't think one area is especially more difficult then others. It really depends on the person's experience coming into the job. If I become a technology director my most enjoyable aspect of the job would be working with the teachers and students observing how technology makes a difference in their learning and teaching. I definitely agree with you that a technology director needs to be organized otherwise they are going to become quite overwhelmed. A sense of humor is definitely needed in any job, it makes the job much more enjoyable if you can have fun!
I agree with you that a technology director should be part of a team and not hesitate to ask for help. Many times I run in to various dilemmas that require a third person perspective on the subject. Even though one may think this might be a proper solution to the problem, there might be a better one.
I would not prioritize purchasing as much as the research that goes into purchasing the equipment. Normally the purchasing part is taken care of by accounting department. You as a technology director needs to establish clearly what is being purchased, in what quantities and from where(which bid).
Post a Comment