If you’re reading this blog, it’s likely that you are at least interested in the implications of technology on educational practices. Residents of the blogosphere/Twitterverse can quickly become ethnocentric and forget that not everyone is reading the latest copy of Wired on their iPad while they take a break from developing an online learning space. Some colleagues are not interested in digital technology, are intimidated by it, ignorant about its applications, and/or fed up with pressure to adopt quickly-changing practices, tools, and theories. Educational developers should try not to make assumptions about their colleagues’ familiarity or capabilities with any particular tool or anyone’s basic ‘digital literacy’.2. Some staff concerns are valid (but these usually have a solution)
It’s not always fear, laziness, or ignorance that prevents academics from using digital tools in their practice; sometimes teachers have tried new pieces of technology and been disappointed, frustrated, or thwarted by any number of challenges. Health and safety concerns, especially, need to be taken seriously and potential issues and adjustments identified. Educational developers should work carefully to fully understand any reasons behind resistance and act with sensitivity to help break down barriers and provide workable solutions.
3. ‘It’s better for the students’ isn’t a convincing argument for staff
Like us, our colleagues are under tremendous pressure in their myriad professional roles. While evidence may show that a digital tool improves student learning and/or experience, we must also consider the implications on staff time, workload, and health and safety. If some subject teachers already find pedagogical research a drag, then the introduction of an extra layer of tech know-how certainly won’t appeal. Educational developers need to be sensitive to the pressures our colleagues are under and find ways to present digital tools as solutions to problems, not another symptom of micro-management and the dehumanising, corporate educational context.
4. Training and support – on a personal level- is key to success
Providing ongoing training and 1:1 support is one of the best ways to overcome resistance to the adoption of potentially useful tools. Working with HR, IT, and other relevant departments, educational developers should expect to offer friendly, helpful advice about any new technological innovations.
5. Students need help too
Educational developers can also work with learning development teams to provide support for students who may not be ‘digital natives/residents’. Just as staff have a variety of reasons for resisting technological innovations, students can find the adoption of new digital tools and systems overwhelming.
6. Engage students to help develop and implement your project
Don’t stop at simply offering help; get students involved in a substantial part of your development activity – not just as tokenistic questionnaire-fillers, but as researchers, trainers, and consultants. On FASTECH, the Student Fellows are key members of the team and the most successful change agents.
7. Institutional regulations can be a barrier to good practice – or a starting point for change
Using some emotional intelligence and political savvy, educational developers can use quality assurance and other regulations to work for (or at least in tandem), rather than against, positive educational change with technology. Again, students might be able to help effect some ‘top-down’ changes.
8. Students aren’t always keen for technology
We sometimes assume that students want us to use the latest technology in our teaching and assessment, but check first. Have a look at the relevant literature, run pilot interventions, and examine student feedback. Students sometimes prefer the status quo to ill-conceived or hasty implementation of technological interventions.
The FASTECH team is working hard to embed technology that improves staff and students’ experience of technology, but we’re learning the need to proceed slowly and gently with staff and students alike.If you have any questions about the project, please visit our website at www.fastech.ac.uk or email email@example.com.
Joelle Adams and The FASTECH Team