Commentary

Tomorrow's CIO

In writing my feature story about "The Evolving CIO," I interviewed M.S. Krishnan, professor of business information technology at the Ross School of Business, University of Michigan. Here are some notes from that conversation on how CIOs can step up to the next level: of their careers, and of what their organizations are increasingly expecting of them.

In writing my feature story about "The Evolving CIO," I interviewed M.S. Krishnan, professor of business information technology at the Ross School of Business, University of Michigan. Here are some notes from that conversation on how CIOs can step up to the next level: of their careers, and of what their organizations are increasingly expecting of them."Alignment is not going to work," says Krishnan.

Say what? Hasn't business-IT alignment been the prime directive of every CIO since the moniker was invented? Yes, except that the results of the most recent survey by the Society for Information Management of CIOs and senior IT executives found that the No. 1 item in the survey's list of Top IT Management Concerns was "attracting, developing, and retaining IT professionals," knocking "IT and business alignment" out of the top spot for the first time in four years and suggesting business-IT alignment is losing steam as a CIO imperative.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

For Krishnan, alignment isn't enough. "Alignment is one-sided, " he says, more closely associated with order taking than innovating. Order taking is the traditional role of the IT department, and by extension the CIO. Krishnan prefers to use the word "synchronization:" business and IT must be synchronized in what they're trying to accomplish and how they're going to go about doing it.

First, CIOs have to be forward-looking about technology. How many CIOs have experimental labs inside their offices, for example, to examine new technologies and think how they can be applied to better serve their companies' customers? Not something like VMware and virtualization, which address "how much hardware cost can we cut down next year?" That's very important, he says, but not as important as experiments that address the question of "how do you use this technology to alter the business model, to add value?" Here he's talking about technologies like RFID or wireless that can significantly impact a company's business processes.

Second, CIOs have to be proactive in taking responsibility for the business processes they oversee every day. For example, companies are going to increasingly leverage global resources, tapping into the competencies available around the world. And this goes beyond the IT function. Given the widespread use of offshore outsourcing over the last 10 years, who in most organizations has the deepest knowledge of and experience working with global companies? And how can CIOs leverage that knowledge and experience? What if, for example, the CIO office sponsored workshops across the company on how to manage global relationships?

These are examples of how today's technology manager can become tomorrow's proactive, forward-looking, innovation-oriented CIO. It's a different role for CIOs, Krishnan admits, but a necessary one to stay relevant to the demands of modern-day business. It's a role CIOs need to embrace, otherwise they will be "marginalized," he says. If they don't embrace it, Krishnan says, "it's their loss."

Do you have examples of how today's IT manager can become tomorrow's CIO? Let us know.


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