Month: January 2009

Dear Geeks:

·

(Before anyone gets excited, this is not intended for or aimed at any specific geek or non-geek who has ever worked for, around, or with me. It was originally inspired by this and this, although it isn’t the same format. Thank you.)

An open letter to geeks, from a geek leader:

I like you. I like working with geeks. You’re intelligent, have odd senses of humor, are creative, and usually shower. I chose to move into geek-dom, and, once here, decided to stay. Eventually, I became a leader. I know some of you don’t quite understand why I would want to do that, but perhaps you can attribute it to a management gene or being dropped on my head as a child (or maybe hitting a house with my head going 20 mph when I was in 2nd grade, but I digress).

But here’s the thing: I still think you should know some stuff.

  1. I’m human. I make mistakes. Shocker, I know. Do me a favor and tell me, rather than letting me look like an idiot, okay?
  2. I experience political pressure. Which, in turn, sometimes makes me tell you to do things you think are stupid. And sometimes I can’t even explain why. Please ask, though. See #1 for the reason you should ask.
  3. If we don’t work in an IT/software company, please learn how to talk non-geek to the, well, non-geeks. Actually, this applies even if we do work in an IT/software company.
  4. You have this job in order to provide value to the shareholders of the company. Either you make the stuff or do the work that makes money, or you support the people who do. Shockingly, very few companies will pay you to just sit around and be geeky.
  5. My top priority is to run the department according to #4. That’s why I have the job. They don’t pay me to just sit around and be management-y.
  6. I want to have fun. I want to be a team. But #s 4 and 5 have to come first. Doing both at the same time is optimal, but sometimes we won’t have fun. I know it sucks.
  7. I care more about you as a human than as a geek or a cog in some corporate machine. Does this sound counter to #s 4, 5, and 6? Yup. It’s a balancing act. See #1 for why I mess it up sometimes.
  8. My job as a manager is to enable you to do your job. Your job is to accomplish the goals I set as a manager and the goals of the company. In my world, you and I work for each other.
  9. But I’m still a manager. If I excuse myself during off-color conversations, it’s because I’m trying to be appropriate. Especially since we’re probably different genders.
  10. The way this all works is that we all act like adults. You do what I ask you to do without my telling you how to do it, and you ask me for help or push back when it seems odd, strange, or impossible. We communicate. We don’t kvetch about each other without first discussing the problem face-to-face (or at least phone-to-phone if we’re a remote team).

I think we can all figure this out, really. It’s a matter of respect and priorities.

Sincerely,
Jenn

P.S., It’s okay to shoot the flying monkey into my office. Just be warned that I’m easily startled and might shriek…

On Misery

·

Ever notice that a lot of geeks seem pretty miserable? You know, down-in-the dumps, put-upon, generally grouchy? Well, according to this article, 1/4 of geeks in small and mid-size businesses have suffered verbal or physical abuse at work, many work hours outside business hours (uh, duh!), and some are looking to leave the field. While I’ve never seen physical abuse, I’ve heard some pretty impressively horrifying help desk calls, where the geek technician is personally insulted for problems that he or she did nothing to cause.

And while I understand that users are frustrated beyond belief when they can’t do their jobs due to technology, it’s definitely demoralizing to hear someone say, “gee, IT has a problem AGAIN.” Well, yeah. We hate it, too. And none of us wants to have a problem AGAIN. And we’re not perfect. And we’re sorry. AGAIN. (And one or more of us have probably pulled an all-nighter or three to fix it. AGAIN.)

So I don’t wonder that geeks are miserable.

However, I don’t actually think it’s all externally motivated misery. Oh, there’s reason enough to sit around and be miserable, but I think there’s a better way to deal with it.

No, it’s not to drink heavily. Honest!

If you’re a miserable geek, I challenge you to ask yourself the question, “What would it take to make me happy?” And then answer it. Honestly.

I did that myself this past week, and was shocked by my answer. There were really only two things: make one change at work, and see friends more often. That’s it. Oh, sure, I’ll be happier with more stable systems, a laptop that actually works, and all sorts of other things; but really, there were only two things that I could think of that would change my attitude radically.

So I ask you, gentle geek and non-geek readers. What would it take to make you happy?

On Training

·

My first technology job was as a computer training specialist for a health and human services company. I was terrible. I’ve been under the impression for the past decade or so that I was terrible because I dislike telling people how to do something more than once.

Turns out that I was wrong.

I was a terrible trainer because I designed, built, and taught my classes around the way I personally like to learn: If you briefly show me all of the features of something, I’ll figure out the optimal way for me to use it on my own. Don’t tell me how to do every little thing methodically–I’ll get bored and pissy.

Many geeks are exactly like this, making it fairly easy for me to teach fellow geeks (see above about the not like telling folks how to do something more than once). Unfortunately for me as a trainer, this is not exactly like normal human behavior. Normal humans (and I realize I’m wildly over-generalizing) seem to want to actually know the best or recommended way to do things, and they’d like step-by-step instructions.

Woah; shocker.

This is exactly what the all of the wonderful trainers who have worked in my departments have done. They figure out the best way to do a task (or the best way for our users to do a task) and design, built, and teach their classes accordingly. Everyone they have trained has loved them and has gone back for more classes or individual help time and time again.

I have to think more about this. And, when I deal with users, I need to learn NOT to say, “You can do it this way, or this way, or this way, or that way.” Instead, I need to say, “There are many different ways to do this, but the best way is to…” and go through it step-by-step. My favorite way to teach? Heck, no. But I’m a big fan of effective, and I believe that this will help me communicate more effectively with non-geeks.