Posts Tagged ‘IT Manger’

How IT Leaders Can Grow Good Ideas

Thursday, April 30th, 2009
IT Leaders Need Practical Ways To Grow Innovative Ideas Within Their Departments

IT Leaders Need Practical Ways To Grow Innovative Ideas Within Their Departments

Innovation, innovation, innovation. Everyone seems to be talking about it, but nobody seems to have any clear guidance for IT Leaders when it comes to telling them HOW to grow good ideas within their IT departments. Well we’re going to change that starting right now.

Dr. Jan van den-Ende and Bob Kijuit have spent some time thinking about this problem and they’ve got some suggestions for us. The problem that they’ve been doing research on is just how to come up with systems that will allow IT departments to nurture GOOD ideas while at the same time getting rid of BAD ideas.

In a nutshell, what they have found is that if you can come up with a way to tap into the input of many people early on in the idea process, then you can make sure that the good ideas make it all the way to the top.

In most companies, new ideas are often collected via some form of  the old fashion “suggestion box”. Using this method, literally thousands of ideas can be submitted in a company of medium size if you have an enthusiastic work force. The problem that this causes is that then someone has to review all of those suggestions and identify the worthy ones. Good luck with that!

What the research has found is that if people take the time to discuss their ideas with colleagues then this helps out a lot. These discussions can help further refine the idea in terms of technical issues or market feasibility. If the idea is really a stinker, then it will cause it to be quickly discarded.

The researchers have also discovered two additional things:

  • if ideas are discussed with colleagues who work outside of the submitter’s department instead of colleagues inside his department, then there was a better chance of the idea eventually being accepted.
  • if ideas were discussed with friends and trusted colleagues then once again the idea had a better chance of eventually being accepted.

The reason for these higher acceptance rates is probably because both close friends and outsiders can give the most frank feedback.

IT Leaders can help their departments to generate innovative ideas. They just need to introduce this additional review and discussion step into the process in order to improve the quality of the ideas being submitted.

Does your IT department have a program to collect ideas from department members? Does anyone currently review and take action on these ideas? Do you get too many or too few ideas submitted? Do you think that adding a peer discussion step in the process would help in your department? Leave me a comment and let me know what you are thinking.

IT Leader Book Review: “Lead Well And Prosper”

Thursday, April 16th, 2009
Nick McCormick Wrote The Management Book "Lead Well And Prosper"

Nick McCormick Wrote The Management Book "Lead Well And Prosper"

So how is an IT Leader supposed to keep on top of his / her game? There were very few college courses that we had to take during our undergraduate years that dealt with management (or even better, leadership). Even if you’ve gone on and gotten an MBA, precious little time is devoted to the day-to-day skills that one needs to be a good leader.

That’s where books like Nick McCormick’s Lead Well And Prosper come in to play. Nick reached out to me awhile ago and asked me to take a look at a copy of his book in order to get a bit of publicity for it. I agreed.

I’ve read a lot of management books in my time and I generally come away from them with mixed feelings. Books like Jack Welch’s “Jack: Straight from the Gut” always strike me as a good read, but don’t really provide me with any tools that I can use – Jack got lucky and did a good job.

There are a lot of other management books out there that read like a textbook because, in fact, they are. These always seem to be just a bit too removed from my reality to do much good.

Nick’s book, “Lead Well and Prosper”, attempts to strike a middle ground between these two extremes. By in large, he does a pretty good job. The one thing that struck me when I was reading this book was that Nick’s style of writing is very conversational. This means it feels like you are having a talk with the author when you read the book. This will work for some and won’t work for others who looking for books to be having a one-way dialog with them.

In the 15 chapters that make up the book, Nick starts each chapter off by presenting a fictitious scenario between two workers: Joe Kerr the manager (“Joker” – get it?), and Wanda B. Goode. After this scenario is presented in which Joe almost always makes a management mistake, Nick spends the rest of the chapter dissecting the situation and explaining what SHOULD have been done.

The scenarios are a little contrived, the analysis is a bit on the basic side, but I have to give to Nick – he hits most of bases in regards to what it takes to be a good manager.

So who should read this book? It’s a quick read at 75 pages and so it won’t take anyone too long to get through it. As I was reading it, I tried to think about who I would give it to. I came away with the impression that it would make an excellent gift for anyone who has been newly promoted. Yes, they probably already know many of the things that the book covers. However, when you are going into a new job is just the time to be reminded about what it takes to be a true leader.

Go out and pick up a copy of Nick McCormick’s book Lead Well and Prosper and when you are done reading it, pass it on to your next friend who finds themselves in a new position where they need to be reminded of what a leader really is.

What’s An IT Manger To Do When You Screw-Up BIG TIME?

Wednesday, February 4th, 2009
We All Make Mistakes At Work, It's What We Do Next That Matters Most...

We All Make Mistakes At Work, It's What We Do Next That Matters Most...

So I’ll be the first one to admit it – I’ve screwed up big time at work. It was awhile back, but as I remember it I was responsible for crunching some numbers that were going into a report that was being used to plan what the company was going to be working on for the next year. Somehow I forgot to include some critical numbers. I discovered my mistake. What should I have done next?

As IT Leaders, we’d like to appear as though we never make mistakes to both our superiors as well as to our teams. However, the sad reality is that we do screw-up and sometimes in a big way. What hurts the most about doing things like this is that it flies in the face of how we view ourselves (as perfect). The fancy name for what this creates is called “cognitive dissonance“.

Phyllis Korkki has looked into this situation in a piece that she wrote for the  New York Times and to get to the heart of the matter she talked with the social psychologist Carol Travis (author of Mistakes Were Made (But Not by Me): Why We Justify Foolish Beliefs, Bad Decisions, and Hurtful Acts).
What Travis says is that internally we look at what we’ve done and we say to ourselves “There is no way that I could have screwed-up on something that I view myself as being good at.” Once we have this thought, then our mind moves on and starts to come up with various forms of self-justification for what we’ve gone and done. How do we do this? You pick: lies, blame, defensiveness, etc.

So this might be a bad situation to find yourself in, but what can you possibly do to make it worse? Simple – don’t tell anyone and try to cover it up. Just in case you haven’t learned your lesson from Enron, Worldcom, or most recently Satyam over in India then listen and understand. Covering up your error will lead to bigger and bigger problems that will eventually entangle you so securely that you can’t get free. Talk about stress!

So once you’ve made the mistake, what SHOULD you do? First off, realize that this mistake is not necessarily a reflection of either your intelligence or your talents. If you can realize this, then you should be able to mentally separate who you are as a person from this event.

What next? Ok – so this is the tough part. You need to point out your error sooner than later. The first step in doing this is to go to the people whom your error has affected and do that most painful of all actions, apologize.

Your next step has to be to get to work undoing the damage that you’ve done and fixing the situation that you’ve caused. This is not easy to do either, but you should realize that it’s the right thing to do. It turns out that keeping the knowledge that you’ve screwed something up inside will be a bigger burden than just getting it out into the open.

What if I get fired? Well that’s always a possibility; however, wouldn’t you rather go out because you pointed out something that you did instead of being found out by someone else? It’s all a matter of who you want to be in control of your life.

A lot rests on how your boss deals with your slip up. If he / she is going to get ticked off, then you are going to be a lot less likely to point it out. As an IT Leader you need to realize that how your team views you will also determine if they feel comfortable coming to you when they screw up (and they will).

Hopefully your boss will realize that having you point out your mistake earlier rather than later  is a good thing. Hey, if you’ve got a worker who is pointing out their mistakes to you then that’s a very good thing. If it keeps happening over and over again, then you need to move the person to a different postion.

In my case, my boss turned out to be incredibly cool. He sighed because he realized that his management was not going to be happy about the correction that was going to be required and then he went and “fell on the sword” – he accepted blame for my mistake. Talk about building loyalty! Man, I double and triple checked everything that I gave him after that and I would have gladly fallen on the sword for him…

Have you ever screwed up big time at work? Did you discover your mistake or did someone else? What did you do when you found out that you had made an error? What happened because of it? Leave me a comment and let me know what you are thinking.