Rants
Questions
Soapbox
Best Practices
Apply today for a FREE subscription to CIO Magazine!
Mon, Feb 4, 2008 17:06 EST

|
Posted by: Meridith Levinson in Questions Topic: IT Organization ManagementBlog: Movers and Shakers
Current Rating: |
Is it easy or hard? What behaviors or actions demonstrate that a CIO is a stinker?
The Wall Street Journal has a great article—Keys to Spotting a Flawed CEO Before It's Too Late (registration required)—that got me considering the same question for CIOs: How do you identify a bad CIO? What are the tell-tale signs? Is it possible for recruiters and hiring managers to read the writing on the wall before they hire the stinker CIO?
Terry Leap, a management professor with Clemson University, notes in the December 1, 2007 issue of The Wall Street Journal that it's easy to identify a bad CEO "once the damage is done"—profits drop, strategies fail, the company comes under the scrutiny of regulators.
Leap provides an extensive list of red flags that search committees can use to smell trouble in CEO candidates. The list includes power-hungriness, shameless publicity seeking and a unilateral approach to management. The warning signs Leap offers easily apply to CIOs.
I want to ask all IT professionals who work for CIOs—from user support specialists all the way up to the CIOs' chiefs of staff—how you determine whether a new CIO is good or a bad. What behaviors or actions demonstrate to you that the new CIO is no good?
I came up with a few ideas, but I want you to add to my list:
I'd also like executive recruiters and executives on search committees in charge of hiring CIOs to weigh in: When you're screening candidates for a CIO job, how do you know when you've got a bad CIO on your hands?
Update 2/22/08: I finished my feature story based on this blog entry about bad CIOs. You can find it here. I hope you find it entertaning *and* useful. Thanks to everyone who left comments on this blog entry. We sparked a heated, energetic debate, and I was glad to see two individuals who thought they had different views on the topic come to consensus. Let the discussion continue!
Update 2/28/08: Beth Israel Deaconess Medical Center CIO John Halamka offers his perspective on what makes a bad CIO on his blog, GeekDoctor.
1 - CIO gives someone responsibility for a project or role, gives them limited direction, doesn't communicate the assignment properly (or at all) to other mgrs, then slap the mgr around mercilessly when they don't do it the way he/she wants.
2 - Ask mgrs to perform a detailed evaluation of high dollar hw or sw and ask them to re-evaluate until they choose the vendor/solution that the CIO wants.
3 - Agree to speak at conferences about things that we are planning to do, as if they are already completed, and extoll the virtues of the vendor/solution. (see # 2 above)
4 - Spend money or direct others to spend unbudgeted money, then rail against subordinates about being over budget, and not controlling the expenses.
5 - Promote those who always agree, or choose not to disagree with the CIO, regardless of their productivity. Then pass over those mgrs who ask questions, or offer alternatives.
6 - Add responsibilities to mgrs that are on the "good" list without providing sufficient resources, until they fail. Then put them on the "bad" list, so someone else can be on the good list for a while.
I could go on, but you get the idea... We actually have a successful IT Team with very low turnover, but this is in spite of the CIO, not because of him. The IT mgrs below him are good enough to compensate, but it could be so much better!
Well, I could see your good business knowledge in your points. Point #5 stopped me and made me think… In a perfect world, I would agree with you...
Take this example. A CIO in a 'C' level meetings with one of his/her managers proving him wrong multiple times... how would CIO feel, and what that make the CIO look in front of other top heads.
As a respect, I tell my CIO when he is wrong behind close doors and in a polite way with something like "I think there is a better way...”
If I feel that he crossed the line, I will softly cut in and say something like "what xxxxxx is trying to say..." or “to xxxxx’s point…”
It may even come to as your conclusion, if you have a good managers WITH WISDOM, point #5 shouldn't rise.
I agree with your point. (I wrote the original post you replied to.)
If we have good managers that respond similarly, and/or the CIO is NOT a bad CIO, it should not be an issue.
However, if you have a "bad" CIO, who is likely to go off on seemingly benign comments, some managers tend to keep their head down. I am admittedly not the most diplomatic manager, but knowing that the CIO has certain tendencies, I try to keep a low profile as well. Although, I am not the type of person that will go along with something that may need further discussion. I have come to the defense of other managers as diplomaticlly as possible with comments such as you suggested - "What I think he intended to say..." or "I don't think he was suggesting...".
I have learned, and have counseled some of our other managers, that when he is in his "attack mode" to not try to argue the point in the staff meeting, but get with him later for a one on one.
Thanks for your input.
You stated: "Take this example. A CIO in a 'C' level meetings with one of his/her managers proving him wrong multiple times... how would CIO feel, and what that make the CIO look in front of other top heads".
My reply to that is - just because he is the CIO, does that always make him right? I think not. If he is wrong, he is wrong. Why should he be treated with more respect than any other employee? What makes him special, besides his title or paycheck? Just because someone is in a management position does not make them more knowledgeable than others.
If someone is "bashing" or disagreeing with the CIO in public, that's disrespect. I believe what #5 is referring to is practice of the CIO surrounding him/herself with "Yes people", never wanting to appear wrong, likes to be the center of intelligence and never needs to justify their opinion or decisions.
Many of us have lived in that world and your experience or intelligence is not appreciated. Time to move on.