Dr. Jeff Borden. Speaker, Educator, Stand-Up Comedian, Innovator, and all around nice guy…
Welcome to Jeff Presents…
“As a teacher, if I don’t know the answer, I’ll tell you I do. Then I will inform you that it’s much more important for you to find the answer yourself so as to learn it. Finally, once you find the answer, I’ll have you email me so I can tell you if it’s right…” Dr. Jeff Borden delivers keynote addresses and workshops in an unconventional manner. He actually uses what we know to be effective practices when speaking, teaching, facilitating, or consulting. What does that mean? We know that lecture is likely the single-worst form of communication available if the desired outcome is to remember and also an impetus for change. We know from brain research that PowerPoint stinks. We know from hundreds of years of learning experiments that listeners who “do” are far more impacted than listeners who solely listen. Jeff not only speaks about this very research, but actually models it in his presentations, ensuring audiences will laugh, possibly cry, but engage with ideas meaningfully and transformationally throughout.
Overcoming Staff and Faculty Resistance to New Technologies
Technology upgrades are becoming critical to universities that want to survive the digital age. New systems are replacing antiquated software that was introduced years ago when they were bricks and mortar, and the concept of a ‘digital campus’ didn’t exist. Decision makers are in a delicate position as they face pressure to innovate while knowing that staff and faculty are likely to push back against change. Staff and faculty value the stability of their existing routine, so the reticence to adopt new systems is understandable. The resistance of faculty to changes in utilizing technology and managing that resistance may be among the most pressing challenges for leaders in academia (Berge & Muilenburg, 2001; Moerschell, 2009). To overcome the objection to new technologies and ensure a smooth transition, start with these key strategies. Choose platforms that are easier to learn Whenever evaluating a new platform, one of the primary factors should be the ease at which students and staff can learn how to use it effectively. A lot of technology companies try to reinvent the wheel when developing their user experience which is a very insular approach that causes more problems than it solves. Designing new systems should be done in a way that makes user onboarding easy. By replicating the look and feel of existing systems and making incremental improvements, software providers are putting their users first. A primary example is Yammer, a business communication tool, which adopted a very similar look to Facebook. The result? Extensive user adoption in the early years after release. Explain the reasoning To build interest in technology before it is released, it is important to provide staff with precise reasons for the decision. Be open about why the new platform is essential. Make sure that the logic is linked directly to relevant and personal outcomes. For example “We’re introducing this technology to build student community,” Should be replaced with: “We’re introducing this technology because our students continue to report that they feel unsupported and the ongoing dropout rate is unsustainable. We’re making this change to avoid potential job cuts in future.” It is also valuable for staff to see examples of other colleges that have successfully implemented the technology. Use a case study to show how another university has changed for the better. Showing how issues will be solved will also help convince staff that the initial pain is worth it for the long-term gain. Find a champion Your internal champion is your quarterback. They coordinate, control and take responsibility for delivering a successful rollout. They can’t do it all on their own, but they’re calling the shots and making sure everyone else plays their role. The internal champion should be a respected leader within the university with a track record for getting things done. They should be afforded autonomy to make decisions about implementation as they arise. Internal back and forth is certain to hurt adoption. Having an internal champion keeping everyone moving in the same direction increases the likelihood of… Read More