The Death of ROI? - Page 1

Apr 22, 2008

Patrick Gray

The IT industry has long searched for a way to justify its cost, hunting for the perfect metric that shows the results of IT spending. Early in this quest, total cost of ownership (TCO) was flagged as the metric du jour. TCO provided a benchmark that indicated how much your IT was costing the company, and provided an easy way to compare IT spending choices.

Unfortunately, TCO focused on the utility aspect of IT, and put IT spending clearly in the camp of an ongoing cost, rather than an investment that could provide real returns to the corporation.

The obvious replacement for TCO was return on investment (ROI), the traditional financial benchmark that indicates how much money resulted from a particular investment. This was the perfect metric for IT spending that had a very well-defined and easily measured result, but runs into trouble for “soft” returns.

By way of example, a salesman could take $5,000 and put it into a savings account earning 2%. After a year, he would have $100 to show for his investment. Alternatively, he could buy a $5,000 suit. If he closes a $5M sale while wearing his new suit, what portion of the $5M was due to the suit?

IT spending runs into a similar quandary, since few projects are based solely on obvious financial returns. So, how do we value the “softer side” of IT results?

While there are complex financial machinations that can be used to determine the financial value of things like “goodwill" we need not delve into such complexities for IT spending rather we must seek to quantify the inherent value, both tangible and intangible in our IT spending.

To do so, I recommend the following four step process:

Start with clearly defined objectives. IT projects are often twisted into becoming all things to all people. Concrete objectives that are universally accepted are not just a great project management tool, they also comprise the basis for valuing IT spending.

Each objective should have a corresponding measure and a target for that measure. The measure may be cut-and-dried. For example if a current transaction takes 10 seconds and costs $10, one can likely assume the transaction costs $1/second and any reduction will have a corresponding cost savings. Even the intangible should have some measure. An objective like “increase customer satisfaction” can be measured by surveys. A “more effective sales force” could be measured through changes in the size of sale, or the time to close a sale.

Each measure should have an associated value. Again, this is easy for the “hard” metrics and will require some approximation for softer metrics. Even for the more intangible, there should be a way of putting a value on each measurement or that measurement is likely ineffective. If you cannot tie some value to the measurement, you likely have an unachievable objective or a poorly selected metric.

These measures can also be used to track a project’s process, and identify areas of concern before they spiral out of control. With defined objectives, appropriate measurements and a value tied to each, the potential value of the IT investment becomes increasingly clear. However, there is one critical element that is often ignored.

Page 1 of 2


0 Comments (click to add your comment)
Comment and Contribute

Your comment has been submitted and is pending approval.



 (click to add your comment)

Comment and Contribute

Your name/nickname

Your email


(Maximum characters: 1200). You have characters left.