Commentary

Tomorrow's CIO: The Qualifications

What are the attributes that make for a good CIO, today and going forward? Here's another peek at our "Tomorrow's CIO" research survey results, specifically the attributes and abilities both CIOs and executive management are looking for in top technology talent. How does this line up with your own ideas about what it will take to prepare for the challenges of Tomorrow's CIO?

What are the attributes that make for a good CIO, today and going forward? Here's another peek at our "Tomorrow's CIO" research survey results, specifically the attributes and abilities both CIOs and executive management are looking for in top technology talent. How does this line up with your own ideas about what it will take to prepare for the challenges of Tomorrow's CIO?Q: As your company cultivates executive-level technology talent, which attributes/abilities are considered most important?

Leadership Ability to execute/meet deadlines Collaboration/communication Vision Innovation Team building Consensus building Technical breadth and depth


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

And in that order. Surprised? I'd venture to guess, by how high collaboration/communication skills scored or by how low (relatively) technical breadth and depth scored.

What do you say? Are these the right attributes/abilities -- and in the right order? Let me know.

Look for the "Tomorrow's CIO" feature story on InformationWeek.com and in InformationWeek magazine on June 16. And sign up for the InformationWeek 500 Conference, the theme of which is "Tomorrow's CIO," Sept. 14-16.


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