Transformation from within...or from outside?
What we see however (not all the time, but enough times) is that technocracy takes hold in institutions. The process of getting the technology and justifying it is much more important than the need for it. Take for example a technology which we already have access to, but it is not enabled. We don't need more money to access it, the button needs to be pressed for it to be enabled. Even to just press a button, we need to go through the motions of providing justifications, work flows and other rigamerole to gain access to it. Learning management systems (LMS or VLE depending which country you're in) seem to be a sore point in many institutions. These things are expensive so we're in VHS vs. Beta Max debates again and again. Once a technology has been adopted, there is a push to get more people to use it, even if it's not the appropriate technology. I think this just shows how problematic change is within the IT department.
I think that change in the university will occur form within, but it won't come from the IT department. I think that change will come from the faculty and students themselves. In a recent CIT (center for the improvement of teaching) forum I heard a faculty say that they don't count on technology being present because they don't know what the school supports and what they don't. At the same forum another instructor indicated that they don't use Blackboard (our LMS) because it is too complicated. At last year's EdTech conference I saw faculty who were openly flaunting the fact that they don't use any IT supported by the campus and instead opted for free Web 2.0 alternatives for their Web Enhanced classes.
If campus IT is providing tech that is hard to use, or is erecting barriers for their use, the non-tech savvy people are not going to use them and the tech-savvy people are going to find other alternatives. One thing is clear: technology which is paid for won't be used. Wouldn't it be better to return to basics and (1) examine the current pedagogical needs on a class-to-class basis and recommend tech based on those needs, and (2) make ourselves friendlier and more flexible to our users needs...or else we'll go the way of the mainframe and remote terminal.
Image retrieved from: http://www.offthemark.com/cartoons/1995-01-25.gif