OMDE 603: Learning Technology Units and Faculty Training

Note: This post is an extra one. Stay tuned for my post on Moore's and Kearsley's Chapter 5!

Chapter 5 of Bates and Sangra (2011), "Organizational Structures and Initiatives" addresses the challenges that universities face in managing Technology* writ large. It's a daunting task, to say the least; after reading this, I am far more sympathetic to the tasks that my large research institution faces with regards to IT organization, maintenance, and planning.

*The capital T I'm using for Technology is intentional: it's meant as a reminder that this is a ginormous topic, one that is overwhelming for me to imagine at a systems, or university-wide level.

First, there are (at least) two main branches of Technology to contend with: administrative and teaching and learning. Technology initiatives for administrative purposes came first; teaching and learning have haphazardly followed suit (Bates & Sangra, 2011, pp. 27-30). What this has led to in many institutions is an amorphous central IT division that is "responsible for telecommunications and campus network infrastrtucture and services...administrative software systems support, IT support, network access, and software maintenance of the institutional LMS" (Bates & Sangra, 2011, p. 115). This is fine. This makes sense. This alone is a hefty task, one that requires a healthy, well-funded staff with a "line of governance" that goes straight up to the Provost's office. I know this is the case at my institution; we have a CIO (a new one in the wake of the huge security breach last semester) and I'm sure if I went to our website I'd find the whole organizational structure for IT management.

I'm not going to do that. Instead, I'm going to write what I know based on my five years teaching here as a technology-heavy faculty member. I regularly take workshops facilitated by the Learning Technologies Institute, a wing of the DIT. I know two of the instructional technologists very well. I think there are more. We created our own Office of Instructional Technology in our department a year ago; it's an office of two people: the full-time assistant director, with whom I work closely, and the Director who is also the overall Ops Director in the department. We also have our full-time tech god, who is in charge of the support services described in the quoted material in the above paragraph for our department.

I work for a huge R1 university. We need a lot of tech support. Like, a LOT. And not just support, but long-term planning. Innovation. Maintenance. Training. This requires being able to see into a crystal ball to know what kinds of technologies to pursue and which trends are unsustainable fads.

I'm sure we spend a zillion dollars a year on tech services and support. Here's the thing: If we have security breaches wherein the personal data, including home addresses and SSNs of faculty, students, and staff all the way back to the late 90s were compromised, how can we justifiably move some of the funding for basic security to faculty training and support?

This is making my head spin. It's also making me look at our new Teaching and Learning Technology Center (TLTC. I think that's the acronym.) in a different light. I've been cautiously optimistic about this center since I first heard about it last fall. Cautious, because my work over the last three years is largely the result of a new initiative (blended learning), the enthusiasm for which died sharply after just one year. I'm still around, but the excitement for BL was promptly replaced by the excitement for MOOCs, which are of course much sexier and have mega publicity benefits. BL is local. MOOCs are global.

The TLTC is subsuming the LTI and CTE, the Center for Teaching Excellence. In this way, it's taking the two bodies devoted to teaching and learning and bringing them under one roof, which I heartily support even more so after reading this chapter. Having two centers--one for "teaching excellence" and one for "learning technologies" is archaic and wasteful. They need to be in the same place. Learning technologies should not be seen as separate from teaching excellence--they should be part of it (because they are). At issue, of course, is a small thing called faculty buy-in. According to Bates and Sangra (2011), Virginia Tech and UCT have mandatory (?) faculty training, or "systematic policies and strategies to ensure that all faculty and instructors using technology had training in the use of technology for teaching" (p. 119). Well, that would be everybody, wouldn't it? Yet I can't imagine being the poor soul to announce to the university that all faculty have to do anything. Faculty autonomy is the last thing that we have.

This is running long; in my next post I want to look at faculty autonomy more closely--the phenomenon that students often have to deal with several LMSs or course websites in any given semester, based on faculty preference; the refusal of some faculty to learn how to use simple tools that will make their and their students' lives infinitely easier; the persistent fear that technology somehow threatens the human element of teaching or even that technology will replace teachers, etc. I also want to look at the overall budget of my institution. I know faculty are expensive, but I also know that the number one reason that tuition costs have skyrocketed over the past thirty years is administrative bloat. Yet looking at technology needs alone forces me to realize that the pejorative "administrative bloat" must of course include technology services and support. These jobs are vital. They are hopelessly complex: one tiny, yet critical example of this is that no university can attract students if their wireless access is even remotely problematic, something that is harder and harder to ensure when every person on campus is carrying at least two mobile devices at any given time. These jobs require significant expertise.

Expertise is expensive. Our president is telling universities that we must keep tuition down. Meanwhile, adjuncts like myself make half of what public school teachers make. This whole enterprise is fracked up. Like completely.