<img alt="dcsimg" id="dcsimg" width="1" height="1" src="//www.qsstats.com/dcsuuvfw300000gkyg9tnx0uc_3f7v/njs.gif?dcsuri=/index.php/c/a/Foreward/Novel-Approach-to-CIO-Education/1&amp;WT.js=No&amp;WT.tv=10.4.1&amp;dcssip=www.cioinsight.com&amp;WT.qs_dlk=XOvUuBAT7H763v8mdyY4-AAAAAg&amp;">

A Novel Approach to CIO Education

By Brian P. Watson  |  Posted 04-01-2008 Print
pagebreak title = 'No Guide to Being a CIO'}

Many CIOs say there are no guides for being a CIO. Are they right?

Austin: The MBA programs and generic management training programs don't deal with the peculiarities of IT, and the IT career path doesn't bridge the business discussion seriously enough. As an IT manager, you have to deal with all these business issues and IT issues that are really interwoven. Your job is to tease them apart and involve the right people in making decisions. But IT can't always separate them, and the businessperson says, "Let the techies worry about it."

A big question IT managers have to ask is, "How many necks are in the noose?" When you make a decision as a CIO, are you alone--or are the business guys in there with you? If they are, they will behave very differently when things go wrong because they'll feel responsible. If it's just your neck, they'll just yank on the noose and tighten it. This book is an approach to help distill the business and technical issues and get the right people involved.

But that doesn't always happen, does it?

Austin: Every time something goes wrong, the reflex of the CIO who came up through the IT ranks is to focus on what he knows: how to fix it. That's good, but in another way, that reflex can be deadly.

The moment something goes wrong, you should talk with your CEO and business partners. Otherwise, there's this vicious cycle in which the CEO doesn't want to talk to the CIO about the technical stuff because it makes his head hurt. And the CIO doesn't like those conversations because they're hard to explain.

And what happens then?

Austin: Their opinions of each other grow worse and worse. This happens in families, when members don't speak with each other. While they're not talking, they have worse and worse thoughts about what the other is thinking.

This is a big part of what Barton struggles with in the book. He really starts to understand his predecessor's reflex to pull back into his own domain instead of having a conversation with the CEO and senior VPs to see how everyone can make sure it won't happen again.

What about IVK--is it based on a real company?

Austin: This story is fictitious, though it's modeled on real situations we've seen, and it's as real as we could make it. But I don't want people to guess what company it is--that would be based on incorrect assumptions.

Back to homepage


Submit a Comment

Loading Comments...
eWeek eWeek

Have the latest technology news and resources emailed to you everyday.