Nicholas Carr Does It Matter Pdf Creator

• “Nicholas Carr may ultimately be correct when he says IT doesn’t matter.. (pdf download). Saying of “IT Doesn’t Matter”: “Carr’s.
• IT Doesn’t Matter by Nicholas G.Carr As information technology’s power and ubiquity have grown, its strategic importance has diminished. The way you approach IT investment and management will need to change dramatically. HBR AT LARGE. Calculators–best relegated to low level employees like secretaries,analysts,and technicians. It was the rare executive who would let his fingers touch a.

“Nicholas Carr may ultimately be correct when he says IT doesn’t matter.. (pdf download). Saying of “IT Doesn’t Matter”: “Carr’s.

When the Harvard Business Review published 'IT Doesn't Matter' in May 2003, the point was to start an argument, or, as they say in the more genteel world of academia, a debate.

The provocative title of the article, as well as its timing--it was published at the tail end of a long slump in technology spending--ensured that a dustup would ensue. The resulting debate has been impassioned and often revealing. And it's still going on.

The essay was written by Nicholas G. Carr, then editor at large of HBR and now a consultant and author. The central theme: There is nothing all that special about information technology.

Carr declared that information technology is inevitably going the way of the railroads, the telegraph and electricity, which all became, in economic terms, just ordinary factors of production, or 'commodity inputs.' 'From a strategic standpoint, they became invisible; they no longer mattered,' Carr wrote. 'That is exactly what is happening to information technology today.'

The reaction was swift. Within weeks, Carr was branded a heretic by many technologists, consultants and--especially--computer industry executives. Intel's Craig Barrett, Microsoft's Steve Ballmer, IBM's Sam Palmisano and others felt compelled to weigh in with varying degrees of fervor to reassure corporate customers. Their message: Don't listen to this guy. Keep the faith in IT's power to deliver productivity gains, cost savings and competitive advantage.

And the reaction continued. HBR got so many responses that it set aside a portion of its Web site to accommodate them, and Carr kept the controversy bubbling on his own Web site. He became a traveling celebrity of sorts, defending his stance in forums across the country, from the Harvard Club in New York City to the Moscone Convention Center in San Francisco, where he traded verbal jabs with Sun Microsystems' Scott McNealy. The article became fodder for countless columns in newspapers, business magazines and trade journals.

When 'IT Doesn't Matter' was published in HBR, I thought Carr had delivered an important, thought-provoking reconsideration of the role of IT in the economy and inside companies. Now that his analysis has been expanded to book length, I still do. This time, his ideas are packaged with a less incendiary title, 'Does IT Matter? Information Technology and the Corrosion of Competitive Advantage.' His message is unchanged, though more fleshed out and nuanced.

Carr's thinking, in my view, is flawed--at times seriously flawed--but not necessarily in ways that undermine his essential thesis. So let's first examine what his fundamental point is, and what it is not.

The title of the original article was misleading. Carr is not arguing that information technology doesn't matter. Of course it does.

The title of the original article was misleading. Carr is not arguing that information technology doesn't matter. Of course it does. Among other things, IT improves productivity by reducing communications, search and transaction costs, and by automating all sorts of tasks previously done by humans.

But Carr asserts that as IT matures, spreads and becomes more standardized, the strategic advantage any individual company can gain from technology diminishes. Paradoxically, the more the economy gains from technology, the narrower the window of opportunity for the competitive advantage of individual companies.

This was the pattern for railroads, electricity and highways, which all became utilities. In the IT world, Carr sees evidence of mature standardization all around him. The strategic implication, according to Carr, is clear. 'Today, most IT-based competitive advantages simply vanish too quickly to be meaningful,' he writes.

Thus, IT strategy for most companies should become a game of defense. The shrewd executive, Carr writes, will in most cases keep his or her company focused on the trailing, rather than the leading, edge of technology. He offers four guidelines for IT strategy: 'Spend less; follow, don't lead; innovate when risks are low; and focus more on vulnerabilities than opportunities.'

In Carr's view, there are two kinds of technologies: 'proprietary technologies' and 'infrastructural technologies.' The first yields competitive gain, whereas the second is just plumbing, at least from a strategic standpoint. Technologies shift from proprietary to infrastructure as they mature. When a technology is young, companies can gain a big strategic advantage, and Carr deftly describes how companies like Macy's, Sears Roebuck and Woolworths exploited the new economics of retailing made possible by rapid, long-distance shipments by rail, and how a new breed of national high-volume manufacturers like American Tobacco, Heinz, Kodak, Pillsbury and Procter & Gamble sprang up by gaining advantage from modern transportation, the telegraph and electricity.

Once a technology moves into the infrastructure category, however, corporate opportunity wanes. In IT these days, Carr sees just about everything being folded into the infrastructure, including the Internet, Web services, Linux and Windows. Carr is particularly insightful on the subject of enterprise software, such as SAP's enterprise resource planning offerings and Siebel's customer relationship management programs. As he does throughout the book, he succinctly draws an analogy between technologies of the present and those of the past. In this case, enterprise software is depicted as the modern version of machine tools.

Before the 20th century, machine tools were gadgets made by each factory to suit its own requirements. But then machine-tool vendors emerged. Their economies of scale brought standardization and lower costs to the machine-tool industry. Innovation continued, but it was the vendors who developed and distributed those innovations for all manufacturers--and thus no competitive advantage accrued to any individual manufacturer. Carr sees a similar 'vendorization' in enterprise software, where core business processes like supply chain management and customer relationship management are handled by standard software packages. The result is a straitjacket of standardization, leaving little room for a company to distinguish itself. Small wonder, Carr writes, that in the late 1990s enterprise systems came to be called 'companies in a box.'

Even the companies that seem to be IT-based success stories, notably Dell and Wal-Mart, are not, Carr tells us.

Even the companies that seem to be IT-based success stories--notably Dell and Wal-Mart--are not, Carr tells us. Yes, Wal-Mart was a leader in using advanced computing and private networks to link sales, inventory and supply information. But Wal-Mart's real edge today, Carr says, is the scale of its operation, which enables it to strong-arm suppliers and zealously pursue efficiencies everywhere. And Dell, he contends, has an edge over rivals because of its direct marketing and build-to-order strategy. 'It's true that IT has buttressed Dell's advantage, but it is by no means the source of that advantage,' Carr writes.

More generally, Carr observes, strategic advantage derives not from technology itself but from 'broad and tightly integrated combinations of processes, capabilities, and, yes, technologies.' Translation: How you use technology, not the technology itself, is the crucial variable. 'Indeed,' Carr writes in his preface, 'as the strategic value of the technology fades, the skill with which it is used on a day-to-day basis may well become even more important to a company's success.'

It has the ring of innocuous truism, but wait a moment: Does that statement really apply to a utility-like infrastructure technology? Does the skill with which we use electricity, commuter rail service or the telephone have anything to do with corporate success or failure? No one seeks insights from research companies like Gartner or advice from consultants, now including Carr, on how to use real infrastructure technologies. This suggests that information technology may be a bit different after all.

The main difference between computing and the industrial technologies Carr cites is that the stored-program computer is a 'universal' tool, which can be programmed to do all manner of tasks. The general-purpose nature of computing--especially software, a medium without material constraints--makes it more like biology than like railroads or electricity. It has the ability to evolve and take new forms. Speech recognition, natural language processing and self-healing systems are just three of the next evolutionary steps on the computing horizon.

Carr might dismiss such comments as romanticized nonsense--and he certainly could be right. Yet understanding the nature of the technology is crucial to determining whether computing is truly graying or, more likely, whether some parts of the industry are maturing while new forms emerge further up the food chain. Are we seeing old age, or merely the end of one stage in a continuing cycle of renewal?

Carr notes that the technology bubble of the 1990s resembled the booms and busts of railway and telegraph investment, which marked the passing of youthful exuberance in those industries. In the computer industry, however, there already had been two previous boom-and-bust cycles--in the late 1960s, when mainframe time-sharing services appeared to be the computing utilities of their day, and in the mid-1980s, when legions of PC companies were founded and soon perished. Again, the pattern seems to be cyclical and evolutionary, as innovations accumulate and eventually cross a threshold, opening doors to broader market opportunities.

Let's take one potential example, Web services. The nerdy term refers to the software protocols that could allow a new stage of automation as data and applications become able to communicate with one another over the Internet. More broadly, Web services are seen as the building blocks of a new 'services-based architecture' for computing. Carr briskly brushes Web services into his 'vendorization' bucket. He writes, 'Here, too, however, the technical innovations are coming from vendors, not users.' The vendors, IBM, Microsoft, Sun Microsystems and others, are working jointly only on the alphabet soup of software protocols: XML, UDDI, WSDL and so on.

Yet when technologists talk of a services-based architecture, they are speaking of a new computing platform that they see as the next big evolutionary step in decentralizing the means and tools of innovation--much as the minicomputer was a new platform that decentralized computing away from the mainframe, and then the PC put power in many more users' hands. Computer scientists regard the Web as a 'dumb' medium, in a sense. It is, to be sure, a truly remarkable low-cost communications tool for search, discovery and transactions, but the Web is mostly raw infrastructure, because it is not very programmable. Web services hold the promise of making the Internet a programmable computing platform, which is where differentiation and potentially strategic advantage lie.

Carr approvingly cites studies showing a random relationship between total IT spending and corporate profits.

I cite this as only one example of where Carr's desire to fit everything neatly into his thesis leads him astray. There are others. He mentions Linux, and its adoption by Internet pacesetters such as Google and Amazon, as proof that commodity technology is plenty good enough for almost any need. Linux, the open-source operating system, does allow those companies to build vast computing power plants on low-cost hardware from the PC industry. But the other great appeal of Linux--and open-source software in general--is that it also frees those companies from the vendors. The rocket scientists at Google and Amazon can tweak the software and change it without seeking permission from Microsoft or Sun Microsystems or anyone else. Today, Google is both a brand name and verb. But technological differentiation has been the bedrock of its comparative advantage. It is the better mousetrap in Internet search. As an example, Google undermines, rather than supports, Carr's point.

His thesis is often the same kind of straitjacket of standardization that packaged software, as he says, is for companies. Carr approvingly cites studies showing a random relationship between total IT spending and corporate profits. But these merely demonstrate that aggregate technology spending is not the only, nor even the crucial variable in determining corporate profitability. That is hardly surprising. Again, it is how companies use the technology--integrating the tools with people and processes--that counts the most. And Carr can be quite selective in citing the work of others. He points to research from Paul Strassmann, an industry consultant, that supports his case while gliding over the fact that Strassmann was a prominent critic of Carr's original HBR article.

Still, these can all be seen as quibbles. They do not necessarily shake the accuracy of Carr's central point--that the period of sustainable advantage a company can derive from technology is diminishing. But is that really surprising? Everything, it seems, moves faster than it did 10, 20 or 30 years ago, including technology. To say that the advantages technology gives a business are more fleeting than they once were is not to say those advantages aren't worth pursuing. Dawn Lepore, vice chairman in charge of technology at Charles Schwab, estimates that a lead in new IT-based financial products lasts from one to 18 months. 'You still get competitive advantage from IT, but there is no silver bullet,' she observes.

Carr's book is a thoughtful, if at times overstated, critique of faith-based investment in technology, and it makes a real contribution to the field of technology strategy. But Carr understates the strategic importance of defense. The old adage in baseball is that defense and pitching win championships; in basketball it is defense and rebounding. In business, if you don't make the defensive technology investments to keep up with the productivity and efficiency gains of your industry peers, you simply lose.

The drift toward more-standardized technology that Carr describes also points to a different kind of pursuit of strategic advantage. It may not be IT-based, but it is certainly dependent on technology. This is what Irving Wladawsky-Berger, a strategy executive at IBM, calls the 'post-technology era.' The technology still matters, but the steady advances in chips, storage and software mean that the focus is less on the technology itself than on what people and companies can do with it.

The trend is already evident in companies and in universities. The elite business schools and computer science programs are increasingly emphasizing multidisciplinary approaches, educating students not only to be fluent in technology, but also in how to apply it. In companies, the same is true. The value is not in the bits and bytes, but up a few levels in the minds of the skilled businesspeople using the tools. Large chunks of the technology may be commoditizing, but how you use it isn't. That is where competitive advantage resides.

To read more articles like this one, visit http://www.strategy-business.com/.

Copyright © 2004 Booz Allen Hamilton Inc.

Reprinted with permission from strategy+business, a quarterly management magazine published by Booz Allen Hamilton.

Nick Carr's article 'IT Doesn't Matter' was published in in Harvard Business Review in May 2003 and ignited an industry firestorm for its perceived dismissal of the strategic value of IT.

Ten years ago, Nick Carr said IT doesn't matter -- sort of.

The jarring headline of Carr's May 2003 article, 'IT Doesn't Matter,' is what many people remember, and it tends to overshadow his more thought-provoking thesis: that companies have overestimated the strategic value of IT, which is becoming ubiquitous and therefore diminishing as a source of competitive differentiation.

'The opportunities for gaining IT-based advantages are already dwindling,' Carr wrote in the Harvard Business Review article. 'Best practices are now quickly built into software or otherwise replicated. And as for IT-spurred industry transformations, most of the ones that are going to happen have likely already happened or are in the process of happening.'

[ Q&A:Nick Carr on 10th anniversary of 'IT Doesn't Matter'

BLOG POST:IT Doesn't Matter: What every IT pro needs to know to survive in the cloud era -- Part 1 Part 2]

Carr advocated spending less on IT, both to reduce costs and to decrease the risk of buying soon-to-be obsolete equipment and applications. He also predicted the rise of utility-like computing: 'The arrival of the Internet has accelerated the commoditization of IT by providing a perfect delivery channel for generic applications. More and more, companies will fulfill their IT requirements simply by purchasing fee-based 'Web services' from third parties -- similar to the way they currently buy electric power or telecommunications services.'

I knew I was writing something that was provocative and that went against the grain of a lot of the rhetoric that was out there about information technology and business. But the reaction went way beyond what I expected.'

— Nick Carr

The article ignited an industry firestorm. It wasn't shared on Facebook, it didn't trend on Twitter and it wasn't voted up on Reddit -- none of those sites existed at the time. The article went viral the old school way: It was passed around the office, written about by other publications and discussed on IT news forums such as Slashdot.

Carr spoke with Network World this month about his inspiration for the article, the backlash, and the article's unexpected longevity. (Read the full Q&A here)

'I knew I was writing something that was provocative and that went against the grain of a lot of the rhetoric that was out there about information technology and business. But the reaction went way beyond what I expected,' Carr says.

His editor agrees. 'He, I, and we (all of us at HBR) knew that it would be controversial,' said Tom Stewart, former editor of Harvard Business Review, in an email to Network World. 'We also suspected that it might be misinterpreted as being a Luddite's argument for typewriters rather than a nuanced argument that IT was strategically important not for itself but for what it enabled one to do, just as (using the analogy Nick used) electricity was more important for what people did with it than for the fact that it spawned a utilities industry.'

7th birthday party program script. Leader Board Leading Today Pts Helpful 1. 200 86% Leading this Week Pts Helpful 1. 200 95% Leading this Month Pts Helpful 1.

'Our suspicion proved well-grounded: Nick was attacked as much for what he did not say as for what he said -- maybe more,' said Stewart, who today is chief marketing and knowledge officer at Booz & Company.

IT suppliers were the most upset, Carr recalls, since he essentially was telling corporate leaders to ignore vendor hype and to stop overspending on IT.

'The biggest backlash came from IT companies. Steve Ballmer called it hogwash, Carly Fiorina dissed it. All the vendors were really up in arms,' Carr says.

In the trenches, CIOs and IT executives had more mixed reactions. 'Some of them really took offense at the article, but others said, 'Yeah, I can see a lot of sense here. This is kind of where we're heading, this is what I'm trying to do,' Carr says.

Andi Mann, a former industry analyst and longtime enterprise technologist, saw that dichotomy among the IT executives he worked with. Some IT pros, threatened by the thought of losing control, wanted to prove Carr wrong to their CEOs and maintain the status quo. Others saw Carr's essay as a wake-up call.

'One group was trying to maintain their legacy and trying to stop the momentum of change, of innovation, of enabling rather than controlling the business,' Mann says. 'The other group was saying to me, 'I think this guy's onto something, and I want to be the innovative CIO, I want to be the CIO who actually uses this technology.' Both groups were interested in trying to prove Nick Carr wrong, but for different reasons and in different ways.'

Making a career of it

'IT Doesn't Matter' turned out to be a career-defining missive for Carr, who followed it up with multiple books (including 2004's 'Does IT Matter?' and 2008's 'The Big Switch') speaking engagements, and another ire-raising essay titled 'The End of Corporate Computing.'

Looking back on the 10-year-old HBR essay, Carr says he got some parts right and some parts wrong.

'Back then, IT companies tried to sell the latest server model as the key to strategic advantage -- you need to be on the cutting-edge of infrastructure or your business is going to be overwhelmed by competitors. At that level, the idea that the basic technology was going to be neutralized as a competitive differentiator has basically panned out,' Carr says.

On the other hand, IT pros have new challenges to address, such as cloud strategy, mobility and social media. 'From another point of view, I think I probably understated the new things that IT departments would have to grapple with. I don't think I expressed the full range of what was to come,' he says.

Industry watchers agree -- to varying degrees.

'He didn't look into the future. He looked at the present state and saw a lethargic, slow, controlling, almost domineering department of IT,' says Mann, who today is vice president of strategic solutions at CA. 'He got it right: IT needed to be fundamentally different. But he also got it hideously wrong.'

Suggesting that IT doesn't matter, that it's commoditized, and that cloud providers can do the job of IT fundamentally underestimated the value that IT brings to businesses, Mann says. 'Nick Carr is a provocateur and author rather than a technologist, and I don't think he understood what IT does when it does it well.'

More on the same page as Carr was analyst David Tapper, vice president of outsourcing and offshore services at research firm IDC, who says he fundamentally agreed with Carr's article.

'I think he got people to start to think about it, to say, 'Let's step back from what we do and ask: Where is this all going, folks?' He was right. I think he needed to modify it a little bit, but he struck the right chords,' Tapper says.

To Tapper, one distinction Carr should have made is to specify who will care about IT in the future: 'I think he should have said, 'To whom should IT matter?' Because it won't matter to the consumer, it will matter to the suppliers and the service providers,' Tapper says. 'The service providers are the ones that are going to buy all this stuff, they're going to integrate it and operate it.' To everyone else, technology is just a tool to do their jobs, something that's taken for granted, according to Tapper. 'Do I wake up in the morning thinking about my telephone or the boiler in my house? No. Only when there's a problem. Otherwise I never give it a second thought.'

Tapper agreed with Carr's prediction that IT would move to a utility model. 'Once the masses of the world need something, it always becomes a utility. There are no exceptions,' Tapper says. 'It's the only way you can deliver it. And technology is now something we can't live without.'

March to the cloud

Ten years after the HBR article, companies still have a long way to go on the path to cloud computing.

'If you look at IT, the bulk of investment these days, certainly on the vendor side, is on cloud systems and applications,' Carr says. 'On the other hand, if you look at corporate spending, cloud is still a fairly small percentage of overall spending, even though it's growing quickly. So we're still kind of between two eras.'

Tapper agrees. 'Companies are in the stages of restructuring their IT departments and trying to form them around cloud categories, such as platform as a service. They're outsourcing or procuring different clouds. They're trying to get it under control. It's a bit out of control now -- one company had 30 Amazon contracts and didn't know about them.'

Back when 'IT Doesn't Matter' was published, the idea of utility-like computing was relatively new in the trenches of enterprise IT. But Mann saw some IT leaders accept the implicit challenge and begin laying the groundwork for cloud computing because of Carr's article.

'There were a couple of organizations that specifically started talking to me about virtualizing everything, automating everything, implementing chargebacks and things like that. That was the start of a number of my clients' journeys to the cloud,' Mann says.

The fact that it's still being talked about suggests Carr made some valid points.

Singh enrolled for the 12-week transformation programme with Stevens, taking place a stringent protein eating plan which concerned having every single two several hours. He managed to obtain the demanded search in 6 weeks. Singh saw a picture of Hrithik Roshan with muscles and questioned Roshan trainer Kris Gethin to train him; Gethin questioned Lloyd Stevens that can help Singh. Singh, who plays a Gujarati boy, had to know some Gujarati abuses and also obtain muscle for his character during the movie. Ram, even so, manages to encourage the policemen to go away in Trade for the list of his blue films.

'If Nick had just merely [been] a provocateur/bomb-thrower/iconoclast -- i.e., had he been wrong -- then the article would have been a 9 days' wonder, not something you'd like to write about on its 10th anniversary,' Stewart said.

At the very least, the article left a lasting impression. 'It's still a bit of a raw nerve for a lot of people,' Mann says.

Ann Bednarz covers IT careers, outsourcing and Internet culture for Network World. Follow Ann on Twitter at @annbednarz and reach her via email at abednarz@nww.com.