Wednesday, November 16, 2011

tech no faculty

I just read two more articles bemoaning the challenges of getting faculty to use instructional technology in ways that benefit students. Both articles offer the same staid suggestions for technology adoption, as well as the standard 5-step approach for implementing technology -- any technology -- to address a specific problem.

These regurgitated suggestions always fail to recognize the audience -- the faculty we are asking to rethink and retool. Beyond the anecdotal generational differences among faculty, there are a few other "conditions" that cause faculty to not fully accept our best efforts and good intentions in regard to instructional technology. For starters, faculty will not read anything that is not specific to their discipline, area or research, or something they've written themselves. Countless hours have we scribed workbooks, templates, tools, and guides to assist faculty in preparing to use instructional technology, only to find the wealth of knowledge therein committed only to the ether. Instead, faculty prefer to learn about instructional technologies by simply calling the help desk and asking, "How do I use [mention technology here] for my class that starts tomorrow?
 
To compensate for the lack of engagement with our written materials, we've fallen back on face-to-face training sessions scheduled around proven and well-designed project plans. Yet when provided a chance to sit and work hands-on with a new technology, faculty disregard the schedules, project plans, and other activities associated with having a course structured and complete prior to the start of the semester. They prefer, instead, to not interact with others -- particularly when with their peers -- nor to engage with support staff when in group training settings. Maybe it's an ego thing. Most likely, it's an ego thing.
 
So what are we left with? Beyond the old 5-step solutions, here's what seems to be working in places that have the balls to do it: First, link faculty training directly to an incentive -- pay them or reward them in some other way to learn and adopt instructional technologies for their courses. As with any effort involving faculty, get to know the culture in which you're working. Find out what motivates faculty and leverage those motivations in the cultural contexts of your school, college or university. Money and release time seem to be the most popular motivators. Second, teach faculty as they go -- don't jam them up with the traditional show-and-tell type training. Let them move through the technology in ways that scaffolds their use and competency -- make the technology seamless to their instructional objectives. This is the ego rub -- it's where you can make them think it's their idea. It works really well when done tactfully.

Two things to consider. Lots of issues associated with both. Of course, nothing is as easy it should be. All we can do is to keep chopping. Chop, chop, chop.

No comments: