11. Ease of Use

11.5. Reliability

The reliability and robustness of the technology are also critical. Most of us will have had the frustration of losing work when our word programming software crashes or working ‘in the cloud’ and being logged off in the middle of a piece of writing. The last thing you want as a teacher or instructor is lots of calls from students saying they cannot get online access, or that their computer keeps crashing. (If the software locks up one machine, it will probably lock up all the others!) Technical support can be a huge cost, not just in paying technical staff to deal with service calls, but also in lost time of students and teachers.

‘Innovation in teaching’ will certainly bring rewards these days as institutions jostle for position as innovative institutions. It is often easier to get funding for new uses of technology than funding to sustain older but successful technologies. Although podcasts combined with a learning management system can be a very low-cost but highly effective teaching medium if good design is used, they are not sexy. It will usually be easier to get support for much more costly and spectacular technologies such as xMOOCs or virtual reality.

On the other hand, there is much risk in being too early into new technology. The software may not be fully tested and reliable, or the company supporting the new technology may go out of business. Students are not guinea pigs, and reliable and sustainable service is more important to them than the glitz and glamour of untried technology. It is best to wait for at least a year for new apps or software to be fully tested in general applications before adopting them for teaching. It is wise then not to rush in and buy the latest software update or new product – wait for the bugs to be ironed out.  Also if you plan to use a new app or technology that is not generally supported by the institution, check first with IT services to ensure there are not security, privacy or institutional bandwidth issues. Thus it is better to be at the leading edge, just behind the first wave of innovation, rather than at the bleeding edge.

A feature of online learning is that peak use tends to fall outside normal office hours. Thus it is really important that your course materials sit on a reliable server with high-speed access and 24 hours, seven days week reliability, with automatic back-up on a separate, independent server located in a different building. Ideally, the servers should be in a secure area (with for instance emergency electricity supply) with 24-hour technical support, which probably means locating your servers with a central IT service or ‘in the cloud’, which means it is all the more important to ensure that materials are safely and independently backed up.

However, the good news is that most commercial educational software products such as learning management systems and lecture capture, as well as servers, are very reliable. Open-source software to is usually reliable but probably slightly more at risk of technical failure or security breaches. If you have good IT support, you should receive very few calls from students on technical matters. The main technical issue that faculty face these days appears to be software up-grades to learning management systems. This often means moving course materials from one version of the software to the new version. This can be costly and time-consuming, particularly if the new version is substantially different from the previous version. Overall, though, reliability should not be an issue.

In summary, ease of use requires professionally designed commercial or open-source course software, specialized help in graphics, navigation and screen design for your course materials, and strong technical support for server and software management and maintenance. Certainly in North America, most institutions now provide IT and other services focused specifically on supporting technology-based teaching. However, without such professional support, a great deal of your time as a teacher will be spent on technical issues, and to be blunt, if you do not have easy and convenient access to such support, you would be wise not to get heavily committed to technology-based teaching until that support is available.