browser icon
You are using an insecure version of your web browser. Please update your browser!
Using an outdated browser makes your computer unsafe. For a safer, faster, more enjoyable user experience, please update your browser today or try a newer browser.

11 Things I wish I’d Known Before Becoming a Tech Teacher

Posted by on October 2, 2013

tech teacherMost of the teachers I know didn’t set out to be a tech teachers. They got here via the PE department or the 4th grade classroom or when laid off as an IT manager at some small company. Few took college classes to teach K-12 technology, nor did they say, “Gee, I have all the skills to be a top-notch tech teacher at my son/daughter’s elementary school. I think I’ll apply.” Most of us got here because 1) our current job disappeared (the Brits call it ‘made redundant’–isn’t that cool?) and this was the better alternative to unemployment, 2) our Principal offered us what Oprah calls a ‘life-defining moment’.

So here we are, doing our best, minute to minute hoping we can solve whatever catastrophe the Universe throws our way, usually with a solution that has something to do with servers and permissions. Fifteen years into it and still flummoxed on a daily basis, there are a few details someone should have told me when I first crossed the tech lab threshold. I mean, who forgot to mention these:

  1. You don’t need to know everything. Do what you can and the rest gets kicked upstairs. That’s right. You are human. You don’t wear a cape and you can’t leap tall buildings.
  2. You can make mistakes in front of the students. Really. Common Core is about problem solving–show how you work through a problem like sound doesn’t work or website won’t load. They’ll see your calm approach and emulate it when solving their own problems
  3. Tech isn’t a digital puzzlebox, the end of a Mobius strip, or the solution to an irrational number. There are only about twenty problems that occur 80% of the time. Know them and know how to solve them. I’d include them here, but that would make this a massive article. I’ll cover it in my next series (stay tuned)
  4. Common sense isn’t common. Don’t expect it to be. When a teacher frantically tells you their Smartscreen doesn’t work, start at the beginning: “Is it plugged in?” Every techie I know starts there and after fifteen years, I know why: It works.
  5. When you wake up in the morning, remind yourself that no one can scare you–you’re the tech teacher. You do know more than the teachers. Don’t start by apologizing because you don’t know what you’re doing or telling her/him how you’ve never seen this problem before. Take a deep breath, think about it, consider the options, and start. Chances are, you’ll figure it out.
  6. Tech works better integrated into classroom inquiry. Sure, you can create fun projects that use cool tech tools, but learning will be more authentic and scalable if students see you working with the classroom teacher. I use that term loosely–‘working with’. Sometimes, grade level teachers barely have time to breathe, much less meet to discuss tech tie-ins. I’ve been known to chat up parents about what’s happening in class, wander through and read room walls, ask students. I’m not above interrupting a teacher’s lunch with ‘just a few questions’.
  7. Don’t jump in to solve student computer problems. If they’ve already seen a solution, let them work it out on their own. I have three extra computers in my lab and parent helpers always want to move students to a new computer when their usual seat is ‘broken’. I don’t let them. I have the student explain what the problem is and think through solutions. Only if none of them work do I allow switches.
  8. There are days when coffee and aspirin count as two of the four food groups. Don’t let it bother it. It will pass. Your job as Go-to Geek requires you are always available. Tech teachers don’t get lunch hours or set breaks. When someone has a computer emergency, they need it taken care of NOW. Respect that. They’ve tried to make a tech lesson and now something doesn’t work and they’re frantic. Take care of them. It doesn’t happen that often. I promise.
  9. Let students redo and make up work. Without taking points off. Wait, you say–I’ll have double the work! Truth, I’ve been doing this since I started and get only a handful of redos for each project. Sometimes I grade it with students and use the opportunity for teaching. The students who really care will really benefit. The others won’t take you up on it.
  10. There will be days when you and Anything Tech are barely on speaking terms, when you wouldn’t fix another broken digital device if it came with a free puppy. When that happens, talk to other tech teachers. Online is a great way to do that. Join tech teacher groups, share problems, offer suggestions. You will feel brilliant and thankful for the kindness of others.
  11. A feature is not a bug. The computer or the iPad or laptops aren’t broken when doing what they’re supposed to do, even if the user doesn’t like it. Gently point that out.

Now go get ’em–you’re ready!


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 six 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.

updated 5-20-16

Leave a Reply