• Front Page
    • Digital Education
    • Terry Freedman's Books Bulletin
  • RSS
  • Search
    • Welcome
    • The "About" Page
    • Testimonials
    • CV/Resumé
    • My Writing
    • Published articles
  • Corrections Policy
Menu

ICT & Computing in Education

Articles on education technology and related topics
  • Front Page
  • Newsletters
    • Digital Education
    • Terry Freedman's Books Bulletin
  • RSS
  • Search
  • Info
    • Welcome
    • The "About" Page
    • Testimonials
    • CV/Resumé
    • My Writing
    • Published articles
  • Corrections Policy
You could put this up on the doors of your computer labs! Photo by Terry Freedman 2017

You could put this up on the doors of your computer labs! Photo by Terry Freedman 2017

11 ways to deter colleagues from using education technology

March 22, 2017

It can be so annoying when colleagues wish to use education technology. Here's how to minimise the likelihood that they would want to.

  • Make it hard to access, eg keep computer labs locked, don’t make the rooms easily bookable from anywhere, give the responsibility for equipment loans to someone who works part-time. 
  • Make the tech hard to use, eg make sure there are no instructions, manuals or quick-start guides.
  • As an extension to the preceding point, offer no training sessions whatsoever. 
  • Make it hard to report faulty equipment. For instance, don't have any reporting 'system' at all: ask people to catch you or the technician at random, in corridors. If you must have a more formal system than that, make sure that reporting has to be done on paper, using long forms that take at least ten minutes to fill out, with questions that are hard to answer, and put a batch of these forms in the least accessible part of the school (a 'temporary' hut is quite useful here, especially if it's kept locked most of the time).
  • Take a long time to respond to fault reports. If the headteacher or principal insists that you respond within, say, 24 hours, ask for faults to be reported by email, and create an autoresponse system so that people receive a response within a few seconds. You can then safely ignore the message altogether.
  • Do not replace faulty equipment immediately with something that works, but take it away for repair. This approach works very well when the item is a printer.
  • Take a long time to have it repaired. If you take long enough, people will forget that it ever existed.
  • Make the equipment uninviting to use, eg filthy keyboards, digital cameras not fully charged, computers taking several minutes to start up, tablets taking half an hour to connect to the wi-fi.
  • Only allow access if the intended use meets with your approval. As it happens, this is a very good approach if staff are allowing kids to do what they like on computers as a way of keeping them quiet. But you can extend the principle by asking every teacher to justify every intended use, in advance. Ask for at least a week's notice, and for a long form to be filled out.
  • Make the rooms uninviting, eg untidy, printer paper all over the floor.
  • Do not keep equipment maintained, including keeping antivirus software up to date. In fact, that second one is very good, as it should cause everyone with a computer at home to not wish to risk sending or taking home infected files.

Needless to say, I hope, this article is tongue-in-cheek, and if you take any notice of it at all it should be with a view to doing the exact opposite of what I've recommended.

Sadly, all of these suggestions have been made on the basis of practice I've seen.

I hope you have found this article interesting and useful. If so, you may wish to subscribe to my newsletter, Digital Education:

In Leading & Managing Computing & ICT, News & views, On the lighter side, Unintended consequences Tags access, computer suite, ICT Co-ordinator, Technology Co-ordinator
← National Backup Day: points for discussion, and 8 potential elements of a Computing projectDigital Education: what's in the latest issue? →
Recent book reviews
power up.jpg
Review: Power Up, by Matthew Lane

This book looks at the maths concepts — and, to some extent, the physics concepts — hidden in popular video games.

Read more →
Shortest History of AI.jpg
Review: The Shortest History of AI

How is it that ChatGPT, Claude and other Al models appear to perform so well at certain complex tasks that some people become convinced that they're sentient — only for them to then promptly fail at simple tasks that even a child could handle?

Read more →
teacher geek.jpg
Review: Teacher Geek

Every so often I like to take a look, or another look, at a book published a while ago, and today I’ve been looking at Teacher Geek, by Rachel Jones.

Read more →
Teach Fast.jpg
Review: Teach Fast

The book contains some interesting ideas.

Read more →
profits, prophets.jpg
A question of leadership

I have somewhat dichotomous views of this question of whether leaders make a difference, or much of a difference. I think my views can be classified as macro and micro.

Read more →
Making good progress.jpg
Review: Making Good Progress?

Daisy Christodoulou carefully picks apart the pitfalls of various kinds of assessment, drawing on different subject areas to do so.

Read more →
principles and practice of assessment.jpg
Review: Principles and Practices of Assessment

There is plenty in this book to like.

Read more →
effective teaching.jpg
Review: Effective Teaching: Evidence and Practice

Although this is a few years old now (2018), it has stood the test of time.

Read more →
maths library.jpg
Review: One for maths teachers

This wide-ranging book takes in probability, fractals, astronomy, Babbage, Lovelace and a host of other areas and people.

Read more →
Weimar.jpg
Reviews: Two for History teachers

Two books on the Nazi era.

Read more →
Dig+Ed+Banner.jpg

Contact us

Privacy

Cookies

Terms and conditions

This website is powered by Squarespace

(c) Terry Freedman All Rights Reserved