Slashdot Mirror
9 Reasons Why Developers Think the CIO Is Clueless
Esther Schindler writes "Finally, a Forrester analyst who understands the attitudes of software developers. Mike Gualtieri identifies nine behaviors managers need to steer clear of or risk being labeled 'clueless' — from control freak tendencies to being a vendor puppet. My favorite, however, is point #8: 'the CIO collaborates to death,' in which Gualtieri opines, 'And, if you never watched Star Trek then you shouldn't even be a CIO.'"
In all seriousness, the proper role of a CIO is to ensure that the proper information (the "I") is delivered to the people who need it in the least expensive and fastest manner possible.
Period.
It doesn't matter if that info comes in via computer, iPhone, or carrier pigeon. Just that the people have what they need when they need it, at the lowest possible cost.
A CTO has the task of picking the technology that makes that possible.
A CFO has to look at the real numbers and move them from column "A" to column "B" such that profit is maximized and cost is minimized. Without committing a felony in the process.
The CEO has to figure out WTF all the other CxOs are doing, try to watch the outside world, and figure out a plan that maximizes his paycheck without pissing off shareholders, getting sued into oblivion, prosecuted (see CFO), or committing a felony that he can't pawn off to the CFO. All while being liable for both mistakes and lies of the other CxO's under him.