InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Industry Survey Reveals The Bitter Truth About IT ROI

Posted by Deborah Hartmann Preuss on Aug 17, 2006

Sections
Process & Practices,
Architecture & Design
Topics
Agile ,
Leadership ,
Delivering Value
Tags
ROI ,
Statistics ,
Value & Metrics ,
Management
The Ziff-Davis CIO Insight July 2006 Business Value survey reveals The Bitter Truth About ROI.  In the two years since their last such survey, there has been little improvement in how (or how well) IT is measuring value delivered.  The survey observes:
True, most firms now try to use metrics such as internal rate of return, return on assets, net present value, or activity-based costing. But besides customer satisfaction there's no consensus or consistency on which measures to use. It's still not a given that ROI should be measured both before and after a project. And half of all executives surveyed, whether IT or business executives, doubt that the measures are even accurate.
Findings include:

Only six out of ten companies measure the business value of IT.
At most companies, it's just guesswork.

Do CIOs measure business value often enough?
Only half do an ROI assessment both before and after an IT project is completed

Skepticism about ROI and business value metrics remains high.
Whether they measure in dollars or look at other forms of value, about half of respondents are skeptical about the accuracy of the numbers

IT executives exaggerate IT's impact on productivity.
Most IT executives believe technology's contribution to productivity is much higher than is indicated by economic indicators like the Bureau of Labor Statistics.

How best to measure IT's value?
No one "right way" to measure the value of IT emerges from the study.

Many technologies and IT services are meeting, and even exceeding, their business value expectations.
Security, systems development and web services do the best job of meeting or exceeding business value expectations; outsourcing, CRM and ERP fare worst.

Former ROI surveys are also available on the CIO Insight site:
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

ROI is an excuse for not listening to users by j c Posted
  1. Back to top

    ROI is an excuse for not listening to users

    by j c

    Every failed IT effort to get ROI from making something more efficient Ive seen didnt take into account current business practices sufficiently and just said well if I plop this system down I will save money.

    For example, having business process engineering folks going to satellite offices and coming back with a suggestion for a "new system" when the computers the users are using are crashing or operating so slowly they can barely do their jobs. Yeah, a new application is JUST what they need.

    Or companies using IT apps as a political ploy to unify operating practices between satellite offices and putting the home office stamp of approval on an application while ignoring the needs of the majority of the company.

    What does ROI mean if your software effort is doomed to fail and usually does?

    Maybe ROI should be second to success. Because ROI has been used to justify so many software failures. Maybe ROIs time is up.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.