Commentary

Chris Murphy
Editor, InformationWeek  

Tomorrow's CIO: No Tech Lightweights

Of course tomorrow's CIOs need to be broad business leaders, not just technologists. But skimp on the tech foundation, and CIOs may have no future at all.

Of course tomorrow's CIOs need to be broad business leaders, not just technologists. But skimp on the tech foundation, and CIOs may have no future at all.That's a conclusion that pops out for me after reading John Soat's article on Tomorrow's CIO. There's a risk of IT leaders underplaying the tech piece of what they do. In our survey, only half of IT execs rate "technical depth and breadth" as important or very important. Yet two thirds of non-IT execs rate it that highly.

The article's interviews likewise point to the importance of tech depth and breadth. FedEx CIO Rob Carter explains how he tracks developments in the biotech field, for example, for two reasons--because it's a growth sector that likely will need precision shipping and logistics, and because biotech's advances might someday, somehow be used inside FedEx. Dan Drawbaugh, the University of Pittsburgh Medical Center CIO, talks of looking eight years out to spot tech trends that UPMC might want to consider, both as a tech user and as a partner in health IT initiatives.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The article offers other interviews and data that point to the need for CIOs and other IT leaders to be the company's guide to new, tech-enabled opportunities. Tomorrow's CIOs shouldn't underestimate the need for deep technology understanding, as well as business savvy, in filling that role.

What's your take? Do CIOs and other would-be IT leaders under-value their own tech expertise?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links