If an article, 10 years after its initial publication date, is featured in several look backs, reviews, Q&As and still gathers reactions and emotional analysis, it can be concluded it must have struck a chord – or in this case – more an open nerve.
In May 2003*, the Harvard Business Review published “IT Doesn’t Matter” , an article by then still largely unknown editor “at large” Nicholas Carr.
The premise of the article was that infrastructure has a diminishing impact on competitiveness and that IT was infrastructure (although Carr in the recent Q&A seems to indicate he meant IT Infrastructure is Infrastructure, a lot less controversial idea).
Given all the recent analysis around, I only want to zoom in on one aspect.
What still amazes me after all these years is how the last decade of IT was impacted/hindered/predicted/paralleled (pick one based on your personal emotional state with regard to the article) by the three short recommendations that were included – almost as an afterthought – in a small breakout box on page 8 of the article.
The article gave the following three “New rules for IT management”
- Spend Less : Which arguably coincided with a decade of corporate IT anorexia?
- Follow, don’t lead : Today we know that consumer-play IT – and not corporate IT – leads most of IT innovation (think Facebook, Twitter, Google, Netflix), and Web-scale IT is arguably about corporates following consumer-plays?
- Focus on vulnerabilities (as for any utility the dependence on external providers increases) – Which ironically is today’s main argument for corporate’s preference for private (over public) clouds?
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.