Has this happened to you? You spend hours rewriting an old lesson plan, incorporating rich, adventurous tools available on the internet. You test it the evening before, several times, just to be sure. It’s a fun lesson with lots of activities and meandering paths students undoubtedly will adore. And it’s student-centered, self-paced. Technology enables it to differentiate authentically for the diverse group of learners that walk across your threshold daily.
Everyone who previewed it is wowed. You are ready.
Until the day of, the technology that is its foundation fails. Hours of preparation wasted because no one could get far enough to learn a d*** thing. You blame yourself–why didn’t you stick with what you’d always done? Now, everyone is disappointed.
Implosions like this happen every day in tech-centric classrooms. Sometimes it’s because the network can’t handle the increased traffic, or students can’t log in due to a glitch, or the website server goes upside down–nothing a teacher can do about that. Really, the reason doesn’t matter. All that matters is an effort to use technology to add rigor and excitement to an old and tired lesson plan fails, leaving the teacher more technophobic than ever. With the pride of place iPads and Chromebooks and 1:1 programs are getting in curriculum decisions, tech problems will be common, varied, frustrating, show-stopping, and nauseating. They will be wide-ranging, everything from a student’s device not having required software to the classroom systems not hooking up to the school’s network or wifi. Students will look to their teacher for solutions and the teacher will become best friends with a colleague in thick glasses and the pasty tan of someone rarely away from their computer, whose conversation includes domain-specific words like gig, server, and modem rather than the score of the weekend football games.
Because to many, ‘tech problem’ equates to the mind-numbing, bone-chilling feeling of ‘I have no idea what to do’.
In a word: Failure. Not a feeling veteran teachers like. As a culture, we eulogize those who go bravely through gates of fire, can think under pressure, are never beaten down, who can connect the dots even when they’re bouncing all over the landscape:
No problem can stand the assault of sustained thinking. (—Voltaire)
Success consists of going from failure to failure without loss of enthusiasm. (—Winston Churchill)
I’ve learned you can tell a lot about a teacher by the way s/he handles three things: a rainy day, parents who drop in unexpectedly, and a lesson plan that explodes.
It doesn’t stop with the teacher, either. What about when we ask our students to use one of the gazillion available internet tools to communicate-collaborate-share-publish–those exciting Common Core words that are code for ‘technology-rich’. Now, when students don’t turn in homework, their entirely believable excuse is ‘the computer ate my homework’ because most everyone has had it happen to them. When I attempt to unravel what happened with questions like ‘Where did you save it?’, I get the deer-in-the-headlights-look that says, How am I supposed to know the answer to THAT question?
Having said all this, I am willing to stipulate: Tech failure is inevitable. There are too many moving parts. Too many circuits and algorithms and scripts and wires shoved under a desk to expect it to go right all the time or even most of the time. Exorcise any thought of perfection in the same sentence as tech from your syntax. But if fear of failure is a reason NOT to use technology, no one would ever cross that digital threshold. So let’s ignore the absolute inevitability of failure, and address the question: What do I do when it happens?
I have three ideas:
Prepare for it
I’m not fatalistic. I’m realistic. Technology–be it phones, scanners, your house’s water meter, your child’s online report cards, the Smart TV you just purchased–fails often and will continue to do so into the foreseeable future. In that way, it is very human. Perfection is well outside of its programming.
Knowing that, bone up on the Law of Technology Failures: The reliability of technology is directly proportional to your needs. To decode that: Tech fails most often where it is needed most. Prevent failures by having back-ups–not just of data, but devices, hardware, systems. For example, if you’re trying to get to Disneyland from Arkansas with three friends, each with Google Maps (or my new favorite Waze) on their phones, said phones will never run out of battery power. Ever. Redundancy. Install three browsers on your computer so if Firefox won’t work, Chrome will. Build in time for system reboots (because that solves at least half the tech problems that plague a classroom). Pre-test relevant systems to become familiar with glitches. Sure, tech will still fail, but not in areas in which you are prepared.
Having said that, keep in mind the corollary to the Law of Technology Failures: The better technology works, the safer you’ll feel with it, the less redundancy you will activate.
Be a problem solver
Dylan Thomas said this as well as anyone in history: Do not go gentle into that good night. Rage rage against the dying of the light. Embrace problems. Own them.
Here are three basics that will get you through many a stressful tech day:
- Know the basics. My job requires tech every day so I’ve solved a lot of problems. I’ve found there are only about twenty that account for 80% of the downtime. The top two: If the computer won’t start, check to see if it’s plugged in. If power isn’t the problem, reboot. Those two solve about half of the tech traumas I face in the classroom. There are eighteen more I’m equally prepared for. Track yours by writing each down as it happens. Soon, you’ll find it’s the same ones over and over. The tech version of Groundhog Day.
- Google the problem. Lest you think that’s too geeky and shouldn’t you call an expert first, it’s not and you shouldn’t. But I understand your fear. It’s such a common fear, it has a name and its own website call LMGTFY.com. That’s an acronym for ‘Let Me Google That For You’. Before you become that LMGTFY (pronounced lemjetfy) person, grab your keyboard, slam those words into the Google search bar, and see if there’s a solution. There will be about 70% of the time. BTW, LMGTFY is a noun, an adjective, and a verb, depending upon how you use it. It can even be used as an expletive.
- Be a risk-taker. Sure we mouth that to our students and Common Core expects it in college- and career-ready students, but does that mean teachers too? Well, yes. Make that who you are. Grin in the face of problems. Model solutions. As Edwin Cole famously said, You don’t drown by falling in the water; you drown by staying there. Don’t drown. Don’t stay there. Stand up and you may discover it’s only an inch deep.
Build in alternatives
Many times this year during the nation’s premiere tech-in-ed conference–ISTE–the internet didn’t work. Lots of reasons why–all that mattered was that presenters couldn’t access their presentations. Most handled this with aplomb either with screenshots or animated descriptions of what might have been. No one quit and walked off the stage.
Let’s face it, if you’re over the age of ten, you know life runs off of Plan B.
What else can you do?
- Don’t expect technology to remain unchanged–Links die, by some counts, about 4% a year. The website you used last week can be 404–not working today (for example: Nimble Fingers for keyboarding). The favorite software you’ve used for years could be incompatible with system updates (i.e., Oregon Trail). Your new computer with Win 8 (probably) won’t run a handful of the programs you use regularly. Prior to presenting, go through the tool you’re going to use or the process you’re teaching–see if it actually works as it used to.
- Use it as a teachable moment--show students how you handle stress, problems, frustration. It’s a learning experience. It’s an opportunity to stretch that magnificent big brain and devise a solution. It’s a chance to ask students, What would you do?
- Don’t apologize–save apologies for something you caused. Tech failures are the cause of the Universe.
- Michael Hyatt who writes for business magazines like Forbes and Business Week has several suggestions I haven’t mentioned. You might want to check out his post.
- Shaina over at Women 24 has a great article which itemizes the five stages we go through when our digital device self-destructs.
Tech is the third leg to the ‘inevitable experiences’ stool, along with death and taxes. Personally, I don’t know anyone who hasn’t had a major tech failure. You know it’s coming. That’s out of your control. The only thing you can control is how you react to it.
What was your last tech failure and how did you handle it?
More on problem solving:
20 Techie Problems Every Student Can Fix
How to Teach Students to Solve Problems
5 Ways to Cure Technophobia in the Classroom
Don’t Be Afraid of Mulligans
Jacqui Murray has been teaching K-8 technology for 15 years. She is the editor/author of dozens of tech ed resources including a K-8 technology curriculum, K-8 keyboard curriculum, K-8 Digital Citizenship curriculum, and dozens of books on how to integrate technology into education. She is webmaster for six blogs, CSG Master Teacher, an Amazon Vine Voice book reviewer, Editorial Review Board member for Journal for Computing Teachers, CAEP reviewer, CSTA presentation reviewer, freelance journalist on tech ed topics, a tech ed columnist for Examiner.com, and a weekly contributor to TeachHUB. You can find her resources at Structured Learning.
Jacqui Murray is the author of the popular Building a Midshipman, the story of her daughter’s journey from high school to United States Naval Academy, and the thriller, To Hunt a Sub. She is also the author/editor of over a hundred books on integrating tech into education, adjunct professor of technology in education, webmaster for four blogs, an Amazon Vine Voice book reviewer, a columnist for TeachHUB, monthly contributor to Today’s Author and a freelance journalist on tech ed topics. You can find her books at her publisher’s website, Structured Learning. The sequel to To Hunt a Sub, Twenty-four Days, will be out this summer. Jacqui Murray has been teaching K-8 technology for 15 years. She is the editor/author of over a hundred tech ed resources including a K-8 technology curriculum, K-8 keyboard curriculum, K-8 Digital Citizenship curriculum. She is an adjunct professor in tech ed, CSG Master Teacher, webmaster for four blogs, an Amazon Vine Voice book reviewer, Editorial Review Board member for Journal for Computing Teachers, CAEP reviewer, CSTA presentation reviewer, freelance journalist on tech ed topics, and a weekly contributor to TeachHUB. You can find her resources at Structured Learning.