Commentary

Bob Evans
Senior VP, Global CIO  

Forrester's Year-Old CIO Outlook: Where's 80/20 Plan?

Thirteen months ago, Forrester's Bobby Cameron offered a summary of his $379 CIO agenda for 2008: become a business change-agent, etc. The summary failed to mention attacking the 80/20 demon, which should be the top priority for CIOs in 2009. Because if they don't undertake that battle, all the other transformation happy-talk will remain just that -- a lot of talk.

Thirteen months ago, Forrester's Bobby Cameron offered a summary of his $379 CIO agenda for 2008: become a business change-agent, etc. The summary failed to mention attacking the 80/20 demon, which should be the top priority for CIOs in 2009. Because if they don't undertake that battle, all the other transformation happy-talk will remain just that -- a lot of talk.Here's what Cameron's summary from 13 months ago says:

The pace of technology change -- and therefore business expectations and IT culture -- is accelerating, fueled by three things: IT's brief but turbulent history, a crush of external forces that reset IT spending and user attitudes, and the strength and resourcefulness of CIOs themselves. To survive in tomorrow's context, a CIO will need to disperse staff and capability out to business units at the same time as they acquire capacity from a supply grid. Meanwhile, the CIO must switch focus from efficiency and cost to enabling greater experimentation and iteration of new ways of competing for the firm. The best will take over their firms' operational services, run P&L lines, become COOs, and in tech services firms, aim sights on becoming CEOs.

More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Nobody can argue with the aspirational arc of Cameron's overview -- create new ways to compete, take on more responsibility, become a CEO -- but that's not going to happen just because the CIO snaps his fingers and decides it would be valuable to "disperse staff and capability out to business units." Because they won't be able to make such moves since all hands will be needed to feed the 80 part of the 80/20 beast.

If CIOs have not declared war on the 80/20 ratio for 2009, they will very likely fail or at best fall woefully short on other major initiatives for the coming year because the funds and organizational flexibility they'll need to complete those other initiatives will remain locked up and inaccessible within those legacy systems and processes and policies that consume 75% or 80% or even more of many IT budgets.

And while such shortcomings would look bad even in a robust economy, now is the worst possible time for such failures. In these times of relentless cost-cutting where superb execution is critical, the inability of a CIO to help deliver new and unique competitive advantage will stand out like a car-company CEO taking a corporate jet to the next groveling-for-dollars meeting with the wizards of Congress. It will have disastrous consequences.

If I were a CIO, and I were paying Forrester or Gartner or some other IT-advisory firm many thousands or tens of thousands of dollars per year for strategic counsel, I'd be telling Bobby Cameron and other experts in the field to send me the book on exactly what I need to do to turn my 80/20 maintenance/innovation spending habit into 50/50 by the end of 2009. Because otherwise, I'll be giving my CEO no recourse but to get to rid of me and bring in someone who can slay that 80/20 demon and thereby unlock the resources needed to do all the fun stuff that Bobby Cameron hinted at 13 months ago.


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