Calculating the value of IT
- Reduce text size Decrease text size
- Increase text size Increase text size
- Print article Print
- Jump to comments Comment
- Share this article Share
- Email article to a friend Email
IT executives are expected to make more rigorous business cases to back up their spending plans. An industry of consultants and academics has grown up to help them calculate accurate returns on IT projects.
IT executives are expected to make more rigorous business cases to back up their spending plans. An industry of consultants and academics has grown up to help them calculate accurate returns on IT projects.
Chips and beans
It is rare for IT proposals to inspire high-fives around the boardroom these days. Chastened by recent experiences, many executives are only too aware of the downside of pursuing an unquestioned belief in technology's ability to create wealth.
And while formal cost-benefit analysis is still a rarity, the threshold at which Fortune 200 companies mandate a comprehensive ROI analysis for new projects has dropped on average from $1 million to $250,000 over the past three years, according to CIOview.
But those looking for prototypes for their financial arguments are faced with a forbidding array of acronyms and equations founded on classical capital market theory. To cope with the special needs of technologists, new ones have been created - as well as plethora of software to work them out.
Whichever one an organisation picks, all of them are founded on two assumptions: that companies should invest in projects that deliver the greatest benefits; and, more profoundly, that it is possible to predict, and put a value on, the costs and the associated business changes.
IT projects often fall outside the first of these because they are often necessities: no one expects email or antivirus to be subjected to a strict quantitative analysis.
Nevertheless, many believe it is a useful discipline to try to translate all of IT's activities into costs and benefits. And often the real value is not in the final numbers themselves, but in the engagement with other parts of the business needed to work them out.
| |||
| |||
| |||
| |||





