Archive for the ‘soft skills’ Category

IT Leaders Have Two Of These But Do They Use Them?

Wednesday, October 1st, 2008
You Should Be Listening Twice As Much As You Talk!

You Should Be Listening Twice As Much As You Talk!

About a year ago I had a chance to sit down with a member of an IT team that was working for me in order to have a heart-to-heart with him. We’ll call him Tim. Tim was a project manager on one of my teams and so far he had been a steady performer. I’d say that he was strong on the analytical side and soft on the interpersonal side; however, he was doing a good job and I had really had no complaints on his performance. Recently, things had changed with Tim. His whole demeanor had been transformed as a deep depression seemed to both surround him and flow off of him and onto anyone that he interacted with. It had gotten so bad that nobody really wanted to have anything to do with him. Clearly this was having an impact on his ability to do his job. It was time for me to step in and see what I could do.

I took Tim with me down to the cafeteria in order to get him into a neutral location. I started my conversation with him by explaining that I had been pleased with his work up until recently. I told him that it sure seemed like something had changed and I needed to find out what it was because things couldn’t continue like they were. Tim initially said exactly what you’d expect a guy to say: “Nothing’s wrong.” I thought about opening up on him with both barrels – look, he was doing a lousy job and he was going to be out the door if he didn’t shape up. However, I knew better and so I kept gently probing. Finally, Tim got around to saying “I hate my Director.” Once again, my gut reaction was to tell him “Too bad, he’s not leaving so you had better make some changes.” However, somehow I was able to hold my tongue and instead said the three most important words that an IT Leader can say “Tell Me More…”

Tim started telling me the standard things that everyone says about their boss behind their backs “He doesn’t give clear instructions, he changes his mind too often, he’s never around when I need to talk to him, etc.” This is regular stuff – not enough to cause such a change in personality. So I went on and said “What else has happened lately?” This finally got Tim to confess everything. In a staff meeting, his boss had found some errors in some slides that Tim had prepared showing the status of the project and had called him out on it in front of the rest of the department. Given Tim’s personality, this was just about the worst thing that anyone could do to him. He was wounded and still sulking several weeks after the event. Bingo! We had our smoking gun.

This was a problem that I could (and did) fix rather easily. That’s not the point of this posting. Rather, my first reactions as Tim’s story unfolded would have been the wrong ones to act on and if I had, then I would have ended up doing a great deal of damage and not fixing the problem. I guess that’s why we all have two ears and just one mouth.

David Benzel is an author and a speaker and he points out that as IT Leaders we all have four main responsibilities when it comes to communicating with our IT teams:

  1. To listen
  2. To get the facts
  3. To determine the problem
  4. To help resolve the situation

As hard as it is to do, listening is both an art and a science that all of us IT Leaders need to get better at doing. Listening is hard to do because it requires you to focus your attention and use your full brain to process what is being said – no multi-tasking allowed! By keeping your mouth shut and your ears open, you allow your staff to do the talking and when they do that, you will learn amazing things.

Have you ever been in a situation in which you spoke too soon without doing enough listening? What happened when you did this? Have you ever seen someone who was a good listener at work? How did people respond to them? Were they more or less effective at their jobs than their peers? Leave a comment and let me know what you are thinking.

Pimp My IT Job!

Tuesday, June 3rd, 2008

How To Improve My IT Job
What to do when you are stuck working on a program/project that is not the executives’ current favorite? Do you feel as though you are stuck in your company’s technical back waters and that your skills are growing older, staler, and more out-of-date each and every work day? Do you look enviously at your coworkers who are working on more glamorous projects and using cool new tools like Ruby or various Web 2.0 toolkits to create shiny new beasts?

Well fear not, amazingly enough you are not alone. Most of the IT community is in your shoes — we work to keep the critical systems up and running and try to make them just a bit better each and every release. “Project Envy” is a fact of life that we all live with. What to do about it?

There is no single magic cure for this affliction; however, here are three ways that I have dealt with this in both my own career and in trying to keep folks on my team motivated:

  1. I.N.T.L.S: “It’s Not The Language, Stupid” Lots of times our jealousy of other workers and projects stems from the fact that they get to use a neat new toy that we don’t get to use. Get over it — good design is good design, no matter what language or tool you have to work with. Back in the day, folks were able to get Fortran to do some pretty amazing things that it had never been originally designed to do. Think about it this way: how boring must it be if the language / tool that you are using to solve a design problem does too much of the work for you. Instead, focus on creating the tightest, clearest code that is humanly possible. We all like a challenge and this will help you to overcome language envy.
  2. Can Anyone Say “Soft Skills?”: If you find yourself trapped on a back waters project, instead of spending your days surfing dice.com, how about if you spend some time working on those skills that you are going to need in order to make it through your entire 45 year career? Skills like communication, delegation, negotiation, etc. If your career eventually takes off, you will desperately need these skills so use this “pitstop project” as an opportunity to bone up on what you’ll need.
  3. Play the Metrics Game: Most IT departments have fallen in love with metrics and this offers you a great way to get some department wide recognition no matter what project you find yourself stuck on. Back water projects are generally in charge of older, stable applications or systems. You can use this to your advantage. Study what metrics your department is tracking and determine which of them are most important to upper level management. Then take a look at your project and ask yourself how you can make this project #1 in terms of department metrics. By doing so you’ll rise to the top and will get noticed. This just might be enough to get you moved to another more popular project.

There are many more things that you can do should you find yourself stuck on a project that turns out to not be the flavor-of-the-week. Complaining, sulking, and surfing for a new job are always options, but there are much better ways to spend your time!