BFTB: The Tech Nazi
Saturday, August 28, 2010 at 06:00AM A new Saturday Blue Skunk "feature" will be a revision of an old post. I'm calling this BFTP: Blast from the Past. Original post, Sept 1, 2005
I was visiting a small school district not long ago and had a chance to visit with its curriculum director. In passing, she referred to their technology director as the “Tech-Nazi” - a title borrowed from Seinfeld’s character the Soup-Nazi.
This is not the first time I’ve heard people in other districts who have a position like mine described in less than endearing terms. One librarian refers to her tech director as “Bob God.” I heard a teacher refer to her district’s technology department as the “Prevention of Education Department.” And of course there are those other names that shouldn’t appear in a blog my mom reads.
Tech directors have two strikes against them coming out of the box. First, technology itself is not always been warmly embraced by educators (not to state the obvious or anything). Its complex and often unreliable nature makes it a source of irritation more than delight. Second, techs have an appreciation of the vulnerability of the equipment they are charged with maintaining that normal people simply don’t. We see those viruses, hackers, software conflicts, power-surges, and SUDs (stupid user dysfunctions) that are always surrounding our little fort, waiting for the smallest breach, and then sneaking in and wreaking havoc.
I, for one, would be heart-broken if I thought my nickname was Tech-Nazi or Doug God. Good working relations with people are as important to me as the good working order of computers. And I think it is possible to have both if:
- You listen to and heed both educators’ and technicians’ views before making a technology policy decision.
- You establish a formal collaborative decision-making body that meets on a regular basis and includes as many types of stakeholders as possible.
- You take the time to communicate in understandable terms why a technology decision has been made (and have a damn good reason for making it).
- You support the goals of teachers and students, not separate technology “goals.”
- You leave the office and visit teachers and librarians to find out how they are really doing with technology. (I call this being a complaint magnet.)
- You tend to err on the side of convenience and accessibility rather than on the side of security (and pray it doesn't come back to bite you).
- You always give other people the benefit of the doubt, recognize accidents happen, and truly believe equipment is better worn out than rusted out.
- Never, ever lie, especially if it is just a CYA move. You get caught once and there will be no trust left.
- You comply with the law but you don't hyper-comply, always taking the least restrictive path.
Most people - most - are pretty reasonable. If a decision, procedure or requirement they don't like is explained to them respectfully, clearly and honestly, they don't hold it against you. You can shake your head together in synchronicity, both of you victims of technology design and the world.
I’d love to hear other ideas about improving one’s reputation as well as one’s effectiveness.
And other nasty names for tech directors you’d care to share.
Reader Comments (14)
Eat lunch with the faculty. Go to the games, etc.. Play in the staff volleyball tourney.
Most of all--sit in the classroom as much as possible.
Bringing staff together and asking, "What do you want to do?" rather than saying "Here's the stuff I bought for you. Figure out how to use it." id the first and best strategy they can use. Actively listening to staff requests would also help. Maybe that is beaten out of them during courses on network management and server setup. :)
When you implement something new and make it mandatory for all students K- 12 don't test drive it on some high school kids or your own (most likely very tech savvy) kids. Find the the school with the largest number of ESL / Title 1 kindergarten age students and test drive on THEM. If they can manage it anyone can.
Case in point - my district who on the first day of school implemented a sweeping new student password involving 8 letters and 3 numbers. And we found out that 7 year olds have trouble differentiating between the Letter o and number zero on a keyboard. And that it's not uncommon for a 6 year old not to know that their name isn't really "Junior" or "Miha"
I really like this post.
As a weird librarian/tech hybrid, though, I have to say that some days I don't much care what they are calling me because it could not possibly be worse than what I am calling THEM!
Hi Brandt,
Good suggestions. It's easy to get trapped behind a desk and a computer screen as a tech director (I know!) But have to say that my best days are those in the buildings seeing all the planning and training being put to use by teachers!
All the best,
Doug
Hi Rick,
I think for a lot of tech directors that they are encouraged to be "visionary" and push change. There is a fine balance between doing that only listening to staff. Oh, and it's good remember that there are always competing visions for what tech should be doing in schools.
Good suggestions,
Thanks,
Doug
Hi Guusje,
The conflict between "best practices" in computer use and security and children's abilities are certainly at odds at times. I wonder if too many tech directors have never worked directly with children. But your ideas to field test it is great!
Doug
Hi Martha,
I appreciate you honesty. I think we all have days like that?
You might learn a few new terms here:
http://doug-johnson.squarespace.com/blue-skunk-blog/2005/10/10/suds-buas-id-10t-errors-and-ids.html
All the best,
Doug
When I do workshops on Web 2.0 tools for teachers, one of the first things I always tell them is to establish a relationship with the technology coordinator. Obviously, it is never a good idea to start such a relationship with a lot of negative name-calling, particularly any names related to the Third Reich or suggestions that said individual was a member of the Hitler Youth. This is not likely to get you off on the right foot, unless of course that particular individual is flattered by such references. If that is the case you most likely have a bigger problem on your hands than whether the technology director will let you use a blog or not and you may need to contact the FBI.
Anyway, I always tell teachers to plan out what they would like to do. Then go to the technology director with some definite information on what kind of tool they have in mind, and a project strategy for why they want to use it. Also it's not a bad idea to bring the tech people gifts of food or other small tokens of esteem when you initiate these conversations. I also remind the teachers that when there is a security breach, and Johnny's mommy finds out Johnny somehow found a way to respond to the Playmate of the Month blog, whose neck will the superintendent be squeezing tightly with his/her bare hands? The technology directors/technicians have good reasons for the things they do.
It's all about relationships people. Talk to each other. Chances are, maybe the tech director has a better recommendation for your class project than just opening up a Facebook page or whatever. Or maybe they have software on the server that will do the same thing and be more secure. Or, wonder of wonders, maybe if you have a good idea, they might even agree with you, if they are approached ahead of time and not five minutes before the class starts.
Hi Mary,
I would hold the line at offering the tech director burnt offerings.
Your advice as always is very sensible. How did you ever wind up in a position of responsibility?
Doug
Doug, for a long time the leaders of our tech department were referred to as the "Digital Taliban" Luckily our Media Specialist "freedom fighters" have dispatched from our schools.
Always be kind, positive, supportive. Never be nasty, even if you are in a bad mood. Answer emails within 2 days (never more!). Make everyone feel that they are important and heard. Try to answer all questions. If you cannot, find the answer later. Most importantly, feed them! :)
Hi Drew,
I love it!
Doug
HI, Doug--thanks for this post as I begin a new gig in my "retirement," that of covering a maternity leave for a middle school librarian. The school tech person's office is in the library. I like that.
But...proof reader and editor that I am, don't you mean in # 9 taking the LEAST restrictive path? Bet you do; I've heard you saw that and know you do that with your filters.
Thanks for this post, Sara
PS--did you see that this post is included in this week's ALA American Libraries Direct?
Doug,
Great article! Funny how your name keeps popping up, I had our instructional coach share your article "Choices, Choices in Reading Formats" with me last week. Our special educaion teacher has ordered 10 Kindles for her class. I’d been trying to decide for myself which format I wanted to try next. I choose a Kindle, I’m waiting on it as I type. Which format did you choose?
Hi Sara,
Thanks for the sharp editing eye. Yes, I meant the other thing!
Doug
Hi Lisa,
I read on both the Kindle (old one with new one on order) and the iPad. Both have advantages and disadvantages. I also read on this new thing called paper, but don't tell anybody - you'll ruin my reputation.
Doug