Commentary

Tomorrow's CIO: Process Before Technology

Which comes first: process improvement or technology implementation? If you answered the former, congratulations, you are well on your way to being Tomorrow's CIO. If you answered the latter, well, good luck with that patch-management project because that's what you're going to be doing for a long time to come.

Which comes first: process improvement or technology implementation? If you answered the former, congratulations, you are well on your way to being Tomorrow's CIO. If you answered the latter, well, good luck with that patch-management project because that's what you're going to be doing for a long time to come.In researching our upcoming "Tomorrow's CIO" feature story and analytics report, one thing has become clear from the discussions I've had with CIOs and other technology and corporate execs: CIOs need to comprehend the business processes within their organizations, and figure out how to improve those processes, before they apply any new technology.

CIOs must specialize in "understanding what other units do," says Stephen Pickett, past president of the Society for Information Management and current chairman of the SIM Foundation. CIOs must make sure that their IT organizations aren't "just being a service provider to those entities but contributing to their success," says Pickett, who's also VP and CIO of Penske Corp.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

One of the things a CIO needs to know, Pickett says, is "how to fix a process that's broken." A good CIO, he says, can analyze an inefficient sales process, for instance, "and make suggestions to salespeople about how to fix it." And CIOs must do that analysis, and make those recommendations, "before they can apply technology to that process."

Ed Kamins exemplifies that process-oriented mentality and approach. He is the chief operational excellence officer for technology distributor Avnet, a position he says may well be the future of the CIO role. "I'm really the chief process officer," he says.

His position, which he took on four years ago when he was still Avnet's CIO, then moved to full time a year later, was the result of "the realization [that] if you automate a bad process, you get a faster bad process that digs a hole and wastes money faster," he says. It's a lesson well learned by forward-thinking CIOs looking to make a significant contribution to their organizations' competitiveness and business growth.

Kamins' best piece of advice for CIOs: "Before process automation, process improvement."

Easier said than done? You tell me. How involved are you in process improvement in your organizations?


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