Leading Geeks

Can they actually be led?

Category Archives: about

Managing stupid(ly)

Astronomical Clock

Astronomical Clock (Photo credit: simpologist)

A few years back, I realized I was killing my staff.

I thought I had found the ultimate in productivity. In order to manage my completely ridiculous inbox, I found a system.  Each night, I’d leave the office late and go wait for the bus. While I was waiting, I would use my trusty Blackberry to clear out my inbox. I would merrily send emails as follow-ups, delete things, and set myself up for a pretty darn productive next day. Hey – I’ve always loved the concept of Inbox Zero (even though practicing it in Outlook is pretty much impossible). This made me, well, happy.

I’d go home, make (well, order) dinner, and relax, knowing that I was prepared for the next day.

And then something really annoying would start happening – my Blackberry would start going off. My team, fresh from their own dinners, would start replying to my email. Being a rather Type A personality, I’d then feel the need to read the email, which kind-of messed with my evening, but I got enough email from others that it didn’t mess it up that much. I’d ignore the email until the next day (except for urgent ones), and go to bed.

The next morning, I’d walk into the office, perfectly chipper because I knew what my day entailed. On my way to my office, I’d do my usual check-ins with my team (my office was at the end of the hall, so I did morning drive-bys).

Oddly, I found exhausted people who would immediately ask me if their response was OK, or expect me to have responded to their responses.

Sometimes I can be a bit slow, but after a few weeks (months?), I realized that my team was stressed and becoming less productive.  I eventually even realized it was my fault. When I was replying to email after hours, they assumed I expected them to do the same. Sadly, they were already working enough, and I wasn’t expecting it. But I was the manager, and that’s what I was doing.

So I stopped. It was downright painful to have to come in each morning with a full inbox and deal with things I could have dealt with the night before, but the change in my staff was worth it. Their stress levels went down, they eased into their mornings, and they became more productive because they stopped working stupidly.

Here’s the thing with being a manager – YOU are the mold. You are what your team attempts to replicate. If you work stupidly, they work stupidly. If you work late, they work late. If you answer email at all hours, they answer email at all hours.If you manage stupidly, you’ll eventually kill them with stress. Or at least lose them to your competitors.

It’s easy to manage stupidly. Are you managing stupidly without realizing it?

Working stupid(ly)

burning a candle at both ends

burning a candle at both ends (Photo credit: Mayaevening)

I have a confession to make: I’ve been working stupidly. For a while now, I’ve been working all hours. Sometimes I start at 5am and end at 7pm. Sometimes I put in 60 hours and then work another 10 on the weekend. Sometimes I get up in the middle of the night and check my email.

Quite frankly, this is DUMB.  I realized how dumb when I started at 9am and left at 6pm a couple of days last week and then did NOT work more at home.  You know what happened when I did that? I was more productive.  Yup. I got more work done at a higher quality when I cut time OFF my day. I spent last week producing a kick-butt set of graphs and various other analyses that are going to make up a foundational document for my role.

At the same time, however, I felt horrendously guilty. There I was, waltzing out of the office at 6 to go home, read a book, and recharge, and there my co-workers were, still in the office. Still toiling away at their desks.  Even knowing that I’m a better asset when I restrict my hours, I felt awful leaving.

I know that restricting my hours makes sense.  When I restrict my hours, all sorts of things happen:

  • I am able to work crazy hours and get crazy things done during emergencies, because my tank isn’t empty.
  • I am a much smarter person! My insights are brilliant, my documents beautifully written, and my analyses are razor-sharp. (Well, smarter, better, and sharper, anyhow.)
  • I am easier to get along with. I don’t snap at folks as often.
  • I understand what my co-workers are saying much faster.
  • I have a better attention span.
  • I have time to geek out reading all the new leadership books and resources. :)

I’m hoping that, by writing this post, I can stop being dumb. I can stop buying into the cult of overwork and be more valuable to my company, my co-workers, and my spouse. I also secretly (well, not secretly any more) hope that my co-workers read this and start leaving the office at sane hours, but I need to realize that I am responsible for my own actions. Therefore, I need to leave the office at a reasonable hour, limit working from home, and STOP BEING STUPID.

2012 in review

The WordPress.com stats helper monkeys prepared a 2012 annual report for this blog.

Here’s an excerpt:

600 people reached the top of Mt. Everest in 2012. This blog got about 2,400 views in 2012. If every person who reached the top of Mt. Everest viewed this blog, it would have taken 4 years to get that many views.

Click here to see the complete report.

My main takeaway?  Get off my butt and BLOG in 2013!

Getting better at being wrong

WRONG WAY

WRONG WAY (Photo credit: CarbonNYC)

A few days ago, someone corrected a mistake that I made. I nodded and said, “Now I know.”

Perhaps this doesn’t seem like a strange situation to you, but it represents a lot of personal growth for me.

I have spent most of my life sucking at being wrong. I don’t think that this is unusual for many geeks – we build our self-esteem on our brains, and our brains are rarely wrong. Therefore, we seriously lack practice. It can be embarrassing to be wrong as well. When I was in elementary school, my friends would giggle with glee if I was wrong about something, and they’d tease me about it for days.

I got to the point that I would be defensive about being wrong. It was never that I was actually wrong, but that there were circumstances beyond my control. Like aliens stole my brain, or this other person was wrong and told me the wrong things. In retrospect, I’m sure I looked even more ridiculous by being defensive, but I would do just about anything to avoid admitting that I made a mistake.

I was in a singing group in college (with a bunch of other geeks – our name was a calculus term), and we used to always tell each other to sing more loudly by saying, “If you’re going to be wrong, be wrong loud enough that you can tell and fix it!” This was hard for me, as my mistakes would be (gasp) heard! Before I could fix them! But I eventually realized it was better to be wrong in practice and corrected than to carry the mistake over to our performance.

While I would love to say that I got better immediately after this experience, that wouldn’t be honest. I’m sure I could tell you lots of stories of my being in denial about being wrong over the years, but I’ve apparently blocked them out.

Eventually, however, I made another step. I realized that if I didn’t know that I was doing something wrong, I couldn’t fix it. I would just continue to do the wrong thing, and the consequences could be rough. Folks could quit if they disliked how I treated them, or I could really blow a budget or project based on an incorrect assumption. I developed a pretty strict policy of, “If I don’t know about it, I can’t fix it.”

By developing this policy and treating being wrong (and finding out about it) as a learning experience, I eventually came to value being corrected. I’ve also worked at a few non-law firm companies now, where being wrong is treated as more of a learning experience than an exercise in shifting blame, which has helped me a lot. I can’t say that it doesn’t still embarrass me – I did blush when I was corrected earlier this week – but I have finally learned to accept it and move on.

Making people successful

Perhaps I’m a bit optimistic, but I am inherently convinced that anyone can be successful given the right attitude and circumstances.

Two small test tubes held in spring clamps

Photo credit: Wikipedia

I think I came to this conclusion in college.  During my junior and senior years, I was a lab TA for the intro biology lab at MIT (7.02). This class had four major experiments (that I’ll call units), and the TAs would rotate between groups of students for each unit.  During my junior year’s class, one group of students had a 3-person team (all others were 2) that was known as being a complete disaster.  They had no idea what they were doing, and the other TAs would be constantly frustrated by getting them to work successfully on their experiments.

I’ve always been a bit rebellious, so when I rotated to this group on the third rotation, I decided that I wasn’t going to let the other TAs’ frustrations influence me.  I spent the first day of that rotation watching and listening to them.  I discovered that they were struggling to take the protocols designed for two people and expand them to three without being confused.  I started working with them to try to more effectively divide and conquer each day’s tasks (and I had the advantage of having the best teacher for this myself – my lab partner the previous year had been SO GOOD at strategizing in the lab that I had learned some amazing ways to do it).  At the end of that unit, when it came time to grade them, I was able to grade each of them a full letter grade higher than anyone had been able to during the first two units.

My experience with the “disaster” team convinced me that setting up the right circumstances could help pretty much anyone be successful. It (along with my experiences later) taught me that, to make people successful, I needed to:

  1. Watch and learn. Had I not taken the time to watch the “disaster” team to find out what was going wrong, I never would have been able to figure out how to fix it.
  2. Identify the real problem or challenge. And I don’t mean identify the problem that I thought existed before going into the situation . With the “disaster” team, we honestly just assumed they weren’t very good at biology lab. It turned out that their real problem was struggling with logistics.
  3. Communicate. Quite frankly, the “disaster” team knew that they were pretty disastrous.  By talking to them about what I’d observed and the problems I’d identified, I got their buy-in to try to fix the problem together.
  4. Change the circumstances. Once we decided to try to fix the problem together , the “disaster” team and I talked every day about ways to solve it. As time went by, they felt more comfortable proposing their own solutions and asking me questions.

I’m not saying that my “disaster” team all pulled their grades up to As.  But they definitely improved because we were working together to create successful circumstances for them.

In the business world, I’ve learned that successful circumstances don’t always include the current role for someone. The strategies I’ve used to address that (after I’ve exhausted the above) include giving negative feedback and, eventually, terminating the person. Luckily, however, I’ve found that more often I can (with the help of the person) create an environment that helps make him or her successful.

I am a stealth geek

Jenn Steele: Stealth GeekIt’s been a while since I posted, so I figured I’d introduce myself:

Hi. I’m Jenn, and I am a stealth geek.

I would think that, by now, I would be accustomed to the surprised looks I get when I join in a conversation about Star Trek captains (Picard was the best. Stop arguing.) or Wheel of Time characters, but I still occasionally get puzzled by the surprise.  I think it’s because I truly believe that I’m a total geek.  (Well, okay. The nerd/geek/dork test says I’m pure nerd, but I’m going to own geek culture anyhow.)

Here’s why I believe in my heart of hearts that I’m a geek:

  • I LOVE reading epic fantasy (my username at MIT was arwen. Do I really need to say more?).
  • I hate not having admin rights on a computer.
  • I have a slashdot login.
  • I lived on the “geeky” side of campus when I went to MIT.
  • Speaking of which, I did go to one of the geekiest schools in the country.
  • When I was in IT, when a new server came I would immediately want to open it up to see the components.
  • My favorite TV shows and movies usually have to do with magic, dragons, superheroes, sci fi, aliens, or whatnot.  I am a HUGE Joss Whedon fan.
  • I play video games for fun.
  • I deeply love intellectual debates.
  • I WILL correct you if you’re wrong.

Despite being a bit geeky deep down (a bit – who am I kidding?), I don’t necessarily come across as one.  I have some theories as to this as well:

  • I am an extrovert. Quite massively so.
  • I love talking to people.
  • I currently work in marketing.
  • I wear make-up.
  • I smell kinda good. (I wear perfume.  “Good” is subjective.)
  • I don’t wear glasses (during the day).
  • I dress somewhat stylishly (yay Nordstrom stylists).
  • I have a Nordstrom stylist.
  • I’m really into exercise and physical fitness.
  • I once played a ditz in drama club and high school and I have NEVER gotten rid of some of those mannerisms.  Sigh.

All that said, I could be completely wrong.  What do you guys think?  (I will return to less narcissistic posts in the future, I swear.)

My job as a manager

Thor, the god of Norse mythology. "Thor's...

Image via Wikipedia

When you think about it, management is really a necessary evil.  Oh, sure, I happen to weirdly like it and have been accused of having a talent for it, but it’s really unfortunate that we need as much management as we do.

Just think about it.  When your team or company is small enough, you don’t really need managers.  Each person in the room knows that they need to simply get “stuff” done in order to make the team or company work.  If they’re good enough at that, your company grows, and that’s when you need managers.

Why do you need managers? Coordination and resources.  My job as a manager isn’t to be the almighty powerful lord of my domain (even though sometimes it’s just fun to act like that to see how quickly my team calls me on it.  The best teams take less than 10 seconds.).  My job as a manager is to be a resource and the coordinator  for my team so that they can get the real “stuff” done.  In other words, the power is actually theirs, not mine.

What does this look like (you KNOW I’m going to do a bulleted list, don’t you?)?  So glad you asked! :)

  • Understand what they do. It’s pretty darn tough to act as a coordinator and resource when you haven’t the foggiest notion what they do all day.  I’m not saying you need to be a pain and look over their shoulders constantly, but you need to have a grasp of what their day-to-day jobs look like and what short-term (and long-term) goals they’re working towards.
  • Get out of the way. In trying to get things coordinated and achieve your mandates, it’s very easy to get in your own way (and in the way of your team).  When push comes to shove, you have to chat with them and then, well, trust them to do their jobs. Yes, your butt is on the line for their work, but that’s why you get paid the big bucks, right?  If you put yourself in the way by demanding constant meetings, updates, etc. (basically, being a micromanage-y PITA), “stuff” just won’t get done.
  • Give them what they need. One of your most important jobs as a manager is to give your team the resources that they need.  Basically, your job is to smooth the path in order to make their jobs as easy as possible.  Sometimes that takes the form of covering for one of them during a family emergency, or dealing with political BS, or bringing in caffeine or a V8 after a late night. Basically, you’re never, ever “too good” to do something that helps one of them get their job done.
    • “But Jenn,” you whine, “I’m not a secretary.”  No, you’re not.  And if you’re blessed enough to have the god or goddess that an admin is, maybe your job will look less “menial” because you don’t have to do as much detailed coordination. But if you don’t have one, suck it up and do the work.
  • Show appreciation publicly.  If you want to make sure your team is demoralized, go ahead and do a private, “Good girl, now get back in your box,” when one of them truly goes above and beyond.  Send an email to your VP, or announce it on the wiki, or use a formal feedback channel to let your company know just how amazing she was.  She might act embarrassed (and there are those employees who don’t want public kudos, so get to know her or check with her first before your stand on the rooftops and shout, but note that “Oh no, you don’t have to do that,” isn’t a refusal), but there is a very wide chasm between public appreciation and private, and employees are aware of that.
  • Show appreciation and disappointment privately. Standing on the rooftops isn’t appropriate for every employee action, so giving a constant stream of feedback is incredibly important.  Don’t ever wait for review time to tell him that he has done well or poorly.  Each day is an opportunity to say, “Nice one with the foo case,” or “In the future, can you make sure that you say goodbye before you hang up the phone?”

I’m sure I’ve missed what a lot of you do, but this is how I see my job?  What have I missed?  What can you add that will make me (and others) a better manager?

Moving to Seattle!

Downtown Seattle, Washington and the Bainbridg...

Image via Wikipedia

What?  You’re moving to Seattle?  When?  What happened?

Yes; my husband and I are moving to Seattle.  We’re flying out late on the 26th of July.  Amazon made him an offer we couldn’t refuse.

What’s happening to you?  Your job?

I’ll be looking for a job in Seattle.  And friends.

Where will you be living?

We’ll be in corporate housing near downtown for a few months while we attempt to sell our house & look for another apartment.

Why didn’t you tell me before now?

I’m telling you now, aren’t I?  :)  I wanted to wait for the big announcement at my department’s meeting at work.

Can I see you before you leave?

Probably, but get in touch with me soon!

I live in Seattle!  When can we get together?

I’d love to see you!  (Assuming you aren’t an ax murderer.)  Drop me an email at jennsteele (at) gmail (dot) com, and we’ll get together sometime after August 1st (since I’ll be a crazy person before then).

My completely nitpicky pet peeves (humor)

Quotes. Made in notepad

Image via Wikipedia

Dear fellow geeks, geek leaders, and other random people who read this blog:

This is not a useful post.  This post, in fact, will show you how the inside of my brain works.  It can be a scary, scary place sometimes.  Also?  This isn’t a rant.  This is just nitpicky.  Also probably brought on by lack of sleep.  And it’s supposed to be funny, not cranky.  So if you read it as cranky, oops.

Here goes.  I hate it when you…

  • Change the subject line of the email.  I have multiple reasons for this:
    1. I don’t read subject lines.  I also don’t read chapter titles, article titles, etc.  I don’t know why.  It’s weird.  My husband makes fun of me for it.  So I’m not actually going to SEE what you put in there for my cute little eyes to see.
    2. It breaks my email threading.  I have a strange obsessive behavior that makes me adore my threaded email conversations.  I cuddle up with them at night (no, not really.  If you’re like me and don’t read titles, please go back and note the “humor” thing up top.).
  • Make plurals with apostrophes.  Just please don’t do it.  Unless you like watching me twitch.  In which case you should go ahead and do it, but don’t expect me to buy you a beer.  Ever.
  • Misspell Latin phrases.  If you can’t spell it, don’t use it.  You don’t sound erudite, you just make me twitch.  See previous bullet point about twitching.
  • Hug me.  There are a few non-family members who I don’t mind hugs from (Whose first names pretty much always start with “J”.  No, I don’t know why.), but otherwise, there will be twitching.  But this one doesn’t get you exempted from the beer buying, so this one is a lesser evil in the Jenn hierarchy.
  • Correct my order of punctuation and quotation marks.  Yes, I know I do it “wrong” for American English.  No, I don’t care.  Pthththt.
So, gentle readers, what are your completely ridiculous pet peeves?  (Other than being called “gentle readers”, that is.  I think that one’s weird, but I’m still leaving it in there.)

Customer Service vs. Accuracy

Customer service vs. accuracyI recently had two customer service experiences with a company that sent me a defective DVD and then sent me the wrong disk as replacement.  The discussions were nearly identical (both took place via online chat), but they left me feeling very different.  During the first discussion, I was confident that I had done everything I needed to do.  During the second one, I was unsure.

That uncertainty led me to examine the conversations in order to see the differences.  Interestingly, there was no real difference in what the service rep said would happen next.  Instead, what I found was that the first rep put it this way:

We will absolutely take care of that for you.  I’ll escalate it now, and you’ll get the replacement DVD.

But the second rep put it this way:

I don’t have the authority to replace DVDs.  I’ll escalate this to support and they will be in touch with you.

Which one was more accurate?  Probably the second.  Which one made me feel better?  The first.

I personally have the tendency to be overly accurate and not reassuring enough–something that I’ll now be working on.  And as I think about it, the geeks I’ve worked with who excel at customer service tend to leave some of the exact details out (like the first rep above did) in the interest of making the user/customer/client feel like they have been both heard and taken care of.

So what do you think?  Which do you value more–customer service or accuracy?

Photo courtesy of Roman Pinzon-Soto.

Follow

Get every new post delivered to your Inbox.

Join 1,701 other followers