Slashdot Mirror


Hunting Bad CIOs In Their Natural Environment

onehitwonder writes "Bad CIOs are a blight on the IT profession, the organizations that employ them and the IT staff who toil under them (usually cleaning up their messes). Yet bad CIOs manage to migrate largely undetected — like the mythic Big Foot — from company to company. In the process, these bad CIOs lay waste to businesses and information systems, destroy staff morale, pillage budgets and imperil shareholder value. To help rid the world of this scourge, CIO.com has compiled a list of behaviors common among bad CIOs that recruiters, hiring managers and IT staff can use to identify them during the recruiting process."

28 of 112 comments (clear)

  1. Bad Sign #1 by Middle+-+Adopter · · Score: 5, Funny

    Pointy hair

    1. Re:Bad Sign #1 by Pointy_Hair · · Score: 4, Funny

      +1 Informative

  2. Re:A point of disagreement with TFA by jellomizer · · Score: 5, Insightful

    No, you missed the point. Improving security is a primary goal of the CIO. But the way he approaches it the sign. The example in TFA has the CIO fear mongering to get a larger budget then he actually needs. Most companies today don't need new firewalls to improve security, they need to rethink the process. Putting security in the hands of software and hardware alone is a path to disaster. The CIO should be able to itemize what he really for security explain the tradeoffs to management, and tell the shortterm and long term effort it will require.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  3. hey... by Anonymous Coward · · Score: 3, Insightful

    MORE SIGNS OF BAD CIOS

    They overpromise and underdeliver.
    They can't sum up their IT strategy into an elevator speech, nor can they articulate the company's vision.
    They don't take ownership of critical issues, nor do they demonstrate accountability for problems, but they're quick to take credit for successes.
    They can't motivate their staff and don't pay attention to building teams inside the IT group. They can't attract and retain IT staff.
    Instead of working on projects that make meaningful contributions to the company's bottom line, they focus either on projects that will look good on their résumés or on sucking up to executives by giving them Blackberrys and new laptops with wireless Internet connections.
    They overemphasize project management to the point where 90 percent of the timeline for projects is given over to planning and only 10 percent to implementation.
    They view project management as a waste of time.
    They can't prioritize projects.
    They give staff responsibility for projects but no authority, direction or support. When the individual and the project fail, they publicly berate the individual.
    They espouse a different management practice every month.

    Hey, I think I work for this guy!

    [anonymous for job security reasons]
  4. Bad category? by JamesTRexx · · Score: 4, Funny

    It may be tagged humour, but I see too many signs pointing at our CIO... -.-

    Is it for sure that we can't shoot them?

    --
    home
    1. Re:Bad category? by kryten_nl · · Score: 5, Funny

      They're certainly not an endangered species. So I would guess you _can_ shoot them. Inquire with your local LUG about the start and end dates of hunting season.

      --
      For the perfect anti-Unix, write an OS that thinks it knows what you're doing better than you do and let it be wrong.
  5. Two points stand out on the top-10 list... by sticks_us · · Score: 4, Insightful
    FTA:

    They migrate quickly from habitat to habitat. A sign that a CIO is of the nocens executor species is a pattern of rapid job transitions on his résumé This happens a LOT. I'm not sure why, but these people settle in, take on a few token projects (never finishing, or else FUBAR'ing them), then leave just as they're being "exposed." I won't name names.

    FTA:

    Young and old flee the CIO's flock. Unusually high levels of staff turnover in the IT department after the new CIO has joined... Ya think? Some departments empty out like rich people leaving the Titanic once you bring in someone new, which is usually a bad sign. A good, sensible leader will often spend the first part of his/her tenure just watching and learning, before making any huge changes (unless they're hatchet men, in which case I'll be the one wearing a dress floating off in the lifeboat)
    --
    "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth
  6. Article in a nutshell by bennini · · Score: 5, Informative
    Another one of those top-10 articles broken up into 7 web pages with 3 paragraphs each and flooded with useless advertisements & buzzwords like SOA on demand, Oracle Fusion Middleware and "Storage Utopias"...heres the summary:
    1. They migrate quickly from habitat to habitat.
    2. Selective amnesia
    3. Excessive preening
    4. A pugilistic stance
    5. Sketchy evolution.
    6. Dropping names.
    7. Bad references.

    then a sublist....
    Behaviors observers should note when the CIO has settled in his new habitat.
    1. They eat their young.
    2. Young and old flee the CIO's flock.
    3. They use the same hunting and gathering strategies regardless of their environment.
    4. Brown-nosing.
    5. Excessive hibernation.
    6. Intimidation
    7. They play favorites with vendors.
    8. They act like a wolf in sheep's clothing.
    9. They show their teeth and their claws.
    10. hey don't finish what they start.

    and then there is a sublist within that second main list (in case you werent confused yet):
    MORE SIGNS OF BAD CIOS
    1. They overpromise and underdeliver.
    2. They can't sum up their IT strategy into an elevator speech, nor can they articulate the company's vision.
    3. They don't take ownership of critical issues, nor do they demonstrate accountability for problems, but they're quick to take credit for successes.
    4. They can't motivate their staff and don't pay attention to building teams inside the IT group. They can't attract and retain IT staff.
    5. Instead of working on projects that make meaningful contributions to the company's bottom line, they focus either on projects that will look good on their résumés or on sucking up to executives by giving them Blackberrys and new laptops with wireless Internet connections.
    6. They overemphasize project management to the point where 90 percent of the timeline for projects is given over to planning and only 10 percent to implementation.
    7. They view project management as a waste of time.
    8. They can't prioritize projects.
    9. They give staff responsibility for projects but no authority, direction or support. When the individual and the project fail, they publicly berate the individual.
    10. They espouse a different management practice every month.
    1. Re:Article in a nutshell by teslar · · Score: 3, Insightful

      Another one of those top-10 articles broken up into 7 web pages with 3 paragraphs each and flooded with useless advertisements & buzzwords like SOA on demand, Oracle Fusion Middleware and "Storage Utopias"
      Printer friendly view is your friend too, even if you're not a printer. It's certainly more informative than just throwing section titles at me (which is not a summary, it's a TOC). How should I guess what e.g. "excessive hibernation" means in this context until I read TFA, at which point I find out that it's spending more time in the office than talking to IT people.
  7. Bad CIOs do not understand the Tao by sticks_us · · Score: 5, Insightful

    Why are programmers non-productive?
    Because their time is wasted in meetings.

    Why are programmers rebellious?
    Because the management interferes too much.

    Why are the programmers resigning one by one?
    Because they are burnt out.

    Having worked for poor management, they no longer value their jobs.

    --
    "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth
    1. Re:Bad CIOs do not understand the Tao by ukyoCE · · Score: 3, Insightful

      >> Why are programmers non-productive?
      >> Because their time is wasted in meetings.

      You probably come from a different background than me, but in my case this has been the opposite.

      Especially in a smaller company without its own fleet of business analysts, meetings are extremely important. The programming team I work with has been non-productive for a long time simply because they've been *doing the wrong thing*.

      It doesn't matter how much of an uber-programmer you think you are, if you aren't meeting with the stakeholders before and during the project to make sure you're giving them what they want, then you're wasting not only the programmers' time, but everyone else's time too.

      Of course I don't mean to imply that every meeting at every company is valuable :) This has been my experience with project disasters that had to be redone from scratch. All because programmers insisted on doing "their solution" all by themselves instead of actually talking to the stakeholders.

    2. Re:Bad CIOs do not understand the Tao by TheRaven64 · · Score: 5, Insightful
      You are confusing meetings with communication. Communication is essential. Meetings are a form of communication. This does not mean that meetings are essential.

      Meetings between two people are incredibly productive, but their use drops off dramatically the more people you add. Most of the communication in a large meeting is between some subset of the group, with the rest being bored. Another common trap is to use meetings for one-to-many communication. These are much better handled asynchronously, because otherwise the speaker has to go at the speed of the slowest listener. The only time a meeting is the correct form of communication is when everyone invited to the meeting is an active contributor to the discussion. If someone is just there to listen, their time is probably better spent sending them a copy of the minutes later.

      I'd thoroughly recommend the book Peopleware to anyone interested in this subject.

      --
      I am TheRaven on Soylent News
  8. Learn from the bad CIO.... by Himring · · Score: 5, Interesting

    Blake Edwards said it best when receiving his oscar for life-long achievement: "I want to thank my enemies too. I couldn't've done it without the enemies...."

    I reported to a bad CIO for years. First off, the mind of a politician isn't much different from that of a corporate-climber. I found the same mind in my experiences with attornies. It's enough to make anyone appreciate the misanthrope Jonathan Swift. At the core of all these folks is a basic deceptiveness invented, grown and maintained with one single goal: power.

    I've read Ringer and I've read Lewis. Ringer says, "Look out for number One." Lewis rebutes (although he wrote this before Ringer by decades), "a life devoid of virtue is simple a life looking out for number one.... and void of its purpose...." Or something to that effect.

    I could write a novel containing my thoughts and experiences on the bad CIO, but in short I believe being absent any real talent, being totally goal-oriented and power-hungry, they practice basic machievelian manipulations and mob psychology to intimidate people into staying in line.

    In my experience, any true and honest person that happened into an officer position at a corporation is quickly devoured by the meat-eaters.

    If you want a life and job filled with honest work, non-game-playing individuals and good sleep at night, then read the signs and minds of those around you, build yourself, bend the questionable intentions of those around you into tools that form who you are, and, as Shakespeare put it, "to thine ownself be true." Eventually, you'll find that job and slowly realize "yes, I'm here. I can just do a fulfilling job and get paid."

    Trust me, it happens....

    --
    "All great things are simple & expressed in a single word: freedom, justice, honor, duty, mercy, hope." --Churchill
  9. Just a Bad Manager; Move Along . . . by Anonymous Coward · · Score: 4, Informative

    These are not characteristics of a bad CIO, but characteristics of a bad manager. TFA reads like headunter-scum puffery. It would point at any incompetent boss.

    "Nothing to see here folks. Move along." -- Leslie Nielsen in Naked Gun

  10. Spotting Bad CIO's. by DumbparameciuM · · Score: 3, Interesting

    This is really quite fascinating. I speak to between ten and thirty CIO's every day as part of my job. The exact number, obviously, depends on how generous their PA's are feeling, and their availability. Part of my job involves speaking to these executives to find out about their current priorities for the department over the course of the next financial year. After reading this, it's frankly astonishing how many of the individuals I've spoken to are guilty of these. Obviously, you can't qualify all of the points discussed in the article through one phone call. The one which stands forward most clearly in my mind was the CIO who crowed at me for a couple of minutes about what his budgets were like, and how he'd just cleared his server room to six blade servers because he'd virtualised so much of the infrastructure and blah blah blah. I spoke to his GM of Infrastructure, who told me that the CIO in question spent almost all of his time in the office, door closed, and would only pop his head out of the office to go to vendor meets or crow about who he was playing golf with that weekend. This GM was doing more of the IT to Business communication that the executive that he directly reported to was doing. I hear stories like this all the time.

    --
    "We are Samurai, the Keyboard...Cowboys"
  11. Seem like 'bad candidates' for any position... by argent · · Score: 3, Insightful

    A lot of these behaviors seem like they should be red flags for any candidate for any position, no?

  12. Problem not unique to CIO's by Politicus · · Score: 5, Insightful
    These problems are endemic to executives in general because corporate governance does not work. In theory, the board of directors looks out for shareholder interests and keeps executives in check. In theory, communism is a worker's utopia.

    In practice, because shareholder elections are a farce, most boards are compromised by being populated by other executives, typically leading companies in the same or similar industry as the executives they are supposed to oversee. This frees executives from shareholder control, essentially giving them reign over other people's assets. Lavish stock grants entrench executives by giving them share ownership which in turn increases their control over the board.

    Freed from oversight, executive goals diverge from shareholder goals. The limits to this divergence are mostly appearance based. You can't appear to be diverging from shareholder goals too much. Image is everything. To achieve this, executives typically vet those they hire based on loyalty. Many employees, while they profess to understand this, do not. So I repeat. To achieve the goal of appearing to promote shareholder values, executives hire first and foremost on the candidate's ability to be loyal to the hiring executive. This results in the typical knuckle dragging tribal culture found leading today's corporations.

    Saying that solving this problem is hard, is a major understatement because you are talking about making America's ruling class accountable. Solutions like co-determination do exist, however, but would require the right political climate to implement.

    --
    Politicus
  13. How to spot a bad CIO by jrothwell97 · · Score: 5, Funny
    1. Keeps pressing the spacebar to get text centred in Word
    2. Insists on capitalising APPLEMAC, and spelling it all as one word, and saying that they're rubbish in comparison to Windows because there isn't as much software
    3. Asks "what's a linux?" and thinks Tux is vermin
    4. Thinks "sudo" is the command to launch the Sudoku game
    5. Actually believes M$'s and IBM's marketing rubbish and reads IBM's 'CIO thought leadership pieces' every night before going to bed
    6. Constantly sends you E-mails saying "omg bill gates will send u $1000000 if u pass this message to 85000 of ur friends in the next 10 seconds!!!!! omg omg lolz"
    7. Fails to find lolcats funny
    8. Thinks Whose Line Is It Anyway is a high-stakes dramatic game show
    9. Believes having defragged your hard drive once is a qualification to become CIO
    10. Probably has a private golf course
    --
    Those using pirated Tinysoft signatures(TM) are a real threat to society and should all be thrown in jail.
  14. ATMI by Velcroman98 · · Score: 3, Insightful

    I formerly worked at ATMI, and they employed the dumbest CIO they could find. He has no IT training or knowledge, claiming his managerial accounting background will allow him to do the job. The CEO is a guy that surrounds himself with yes-men, and Kevin Laing is his personal puppy of a CIO.

    Kevin hired an infrastructure director, who was trying to gown up in our clean room and couldn't find any left handed rubber gloves. It's no wonder the companies stock has been flatlining for the past 5 years.

    Those poor bastards still working there will never get an annual bonus, because the CIO blows the budget horribly every year. The Help Desk manager has run off all the competant staff with full blessing of the CIO, I just don't see any upside to this guy at all. If the CEO and CIO were fired tomorrow, I'd guess there would be a jump in the stock just because they would be gone.

    Key attributes of Kevin Laing
    • They overpromise and underdeliver.
    • They don't take ownership of critical issues, nor do they demonstrate accountability for problems, but they're quick to take credit for successes.
    • Instead of working on projects that make meaningful contributions to the company's bottom line, they focus either on projects that will look good on their résumés or on sucking up to executives by giving them Blackberrys and new laptops with wireless Internet connections.
    • They overemphasize project management to the point where 90 percent of the timeline for projects is given over to planning and only 10 percent to implementation.
    • They espouse a different management practice every month.
  15. wrong way to recruit by wikinerd · · Score: 3, Interesting

    Bah. The correct way to recruit, for any position not just CIOs, is to look around and identify top talent, then *invite* them to your company. Posting an ad and then trying to decipher resumes is really not an intelligent way to hire anyone, let alone CIOs. You should, of course, post an ad and have a brief look at resumes in case there's some talent out there who has no connections to you or is invisible, so that they have a chance to reach you. But in general, most good talent is visible in some way, so you can watch them from a distance, identify their weaknesses and strengths, and then invite them when you need them (this of course doesn't guarantee that they will come, but it is for this reason that you should always keep a list of multiple potential CIOs that you could invite rather than just 1).

    As for the article... it suggests CIOs who change company too often might be bad. That's not an indicator of anything. That's not even a good heuristic. They may change employers for a great number of reasons, only some of them having even the slightest to do with their own performance, and many times the performance of a person is contingent on their environment. A resume cannot tell you anything about a person or their future performance. Academic degrees, even from top tier schools, mean nothing, and you cannot even trust references as you never know how and why a person recommends another, and basing your decisions on past employment record is not useful if you can't know what they were doing while being employed there (they could be playing chess all day thanks to them being the son of the company's president, etc).

    There is only one way to know whether a person will perform well: you have a set of requirements, and the person in front of you claims they can satisfy them. The way to know rather than guess their future performance is to *test* them, in real or near-real environments.

    How to test a CIO? You first have to identify what a CIO has to do within your company. Oftentimes, CIOs design processes and rules for information sharing, protection, and processing. So, if in your company you find that your CIO will likely spend their time coming up with improved processes and monitoring them, then why not get them do exactly that during the interview instead of trying to guess the unguessable from a resume or asking stupid interview questions with no meaning? One thing you could do is to have them manage a small team composed of employees in your company for 15 mins or half an hour or so, asking the wannabe CIO to devise rules that would enable the team to finish a simple virtual job quickly over the company's LAN, then simply hire the CIO who were able to make the team work faster during these 15 mins. This may cost some money, though, so you could build a computer simulation to do the same: the simulation would model some essential business processes, and the wannabe CIO would have to think of ways to let the simulated business components share information in the most effective way, then you would configure the simulator to run the policies the CIO suggested (or chosen from a multiple choice menu), and you would keep the time. Assuming the simulator was built in an intelligent way to capture the essential parameters of reality (which isn't an easy task, of course, which is why I recommend using real human teams for testing if you can spare some time), the CIO who thought of a policy that led the simulation finish faster would get hired. This doesn't even need to be done during the interview, it can be done remotely, eg over a Web-administered pre-hiring test, so you would need to invest absolutely no time and money in testing wannabe CIOs from the moment you build the test. One word of warning, though: the test must be built as to encompass emergent characteristics and complex noninear behaviours, just like real life, so that no one can predict the simulator's run time from the initial parameters.

    And another word of warning: Some talent dislikes being tested too much, which is why you shouldn't ask them to be tested for more than 15-30mins at a maximum, and only once.

  16. He? by Crafty+Spiker · · Score: 3, Informative

    The absolutely worst IT executive I ever had the displeasure to work for was a woman. Arrogant, rude and completely unqualified. It turns out that she had quite a horrid reputation in her prior jobs. Made a complete mess of things and then moved along to another (local) company where she proceeded to make the same mess. I will give her points for consistency. This all appears to be simply a matter of empty suits finding one of their own for critical executive positions. To my regret I was out the day that IT became a political space and not a technical one.

  17. The ego train by HangingChad · · Score: 5, Interesting

    The cult of personality CIO is probably the most destructive and wasteful of all of them. They're particularly dangerous in government. The last big contract I worked had one. He brought in "his" people to manage projects. Some of them were, in my opinion, charity cases. A couple had qualifications that included boarding their horses at the same riding academy. They had unproductive jobs and were bossy and abrasive on top of that. I watched them waste millions of dollars, produce nothing tangible or productive, then get promoted. The talented people took other jobs and left.

    It's very demoralizing when you're trying to do the right thing for the customer and be cost effective, then see someone ride in with his toadies, blow millions on something that never had a chance of working in the first place, then get moved up the chain. Makes you question if there's a margin in being practical and productive. I always thought that if you made good business decisions in IT, the customer would eventually come back to the value proposition. But it doesn't always work that way and I'm starting to question whether that's naive.

    I certainly have several first-hand experiences where the incompetent, impractical and wasteful have flourished.

    --
    That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
  18. Re:A point of disagreement with TFA by GooberToo · · Score: 5, Insightful

    In other words, security is a process. Security is not strictly a hardware and software solution.

  19. Re:But how do we get rid of them? by tompaulco · · Score: 5, Insightful

    So, how can we prevent these hoodlums from ruining our lives and get them either not hired to begin with or canned when we see their complete incompetence?
    You can't. Once someone reaches "C" level, they have something akin to diplomatic immunity. Even if they screw the shareholders out of billions of dollars and run the company into the ground, the only thing that might happen is they get fired, get a huge golden parachute, and some other company will immediately scoop them up for even more salary and stock.

    --
    If you are not allowed to question your government then the government has answered your question.
  20. We need a LIST! by Cragen · · Score: 3, Insightful

    We don't need a list of what they do! We need a list of who they are! So we can check it when job hunting. Now that would be helpful.

  21. Re:Bad sign #7 by Etyenne · · Score: 4, Insightful

    Personally, I would rather be led by a CIO with a Liberal Arts degree than one with a MBA, but that's just me.

    --
    :wq
  22. Updward Feedback by Tablizer · · Score: 4, Interesting

    I think a big problem in most organizations is insufficient bottom-up feedback. A CIO may be a great kiss-up to the CEO, but may otherwise be a crappy manager. If a formal process was put in place such that underlings ranked their supervisors, then the bad ones would either have to shape up or ship out.

    One interesting approach is a list of about 15 traits, and employees pick the top 3 that the manager needs to improve on. This avoids a "blunt" ranking that many organizations dislike, but at least gives the top layer feedback on the biggest problems.

  23. What's the Point? They'll Get a Reward by Jeramy · · Score: 3, Interesting

    Ours got CIO of the Year!
    http://www.informationweek.com/news/showArticle.jhtml?articleID=204702770

    This was a running joke inside our company as the man was considered woefully incompetent and borderline retarded by all who worked in IT. His true gift was looking like CIO and convincing IT magazines that he was good.