As the technology department of a higher education institution, it is our responsibility to lead and set examples of how technology can help all areas of the college do business better. And this no longer is just about new hardware and software – it’s now about how we work together.
And sometimes this is about how we don't work together. We are constantly challenged to determine where the line is drawn regarding tools and policy. The email policy has changed: does Technology deliver the message or does Academics?
Our notion of training has changed (with help from our trainer who accepted a two year job with the Peace Corps in Africa --- go Rick!): do we fill jobs because they are vacant; or stop to determine if the jobs we define meet our needs?
Do we dare to take the time to discuss whether the needs are legitimate or hold-overs from a different point in time?
In short do the risks we take pay off? How do we help our community understand that change is a good thing? And how do we help our technology staff understand that being challenged is one of the most thrilling aspects of
