The notion of value is ambiguous and abstract. An object or an act is not intrinsically valuable. We define what is valuable. We have a choice.
Some cultures decided that stones would be used to reflect something of value that can be exchanged — their currency. Eventually, the stones were so large that they could no longer exchange them. Instead, they would communicate the exchange. Eventually, the stone currency changed to something more transportable. They made a choice. They changed their notion of value.
Organizations have the same choices to make about what they value from IT. For instance, many organizations have valued speed of delivery and the adherence to budget, without the commensurate adherence to desired scope and quality. They celebrate hitting the delivery date and spending the budget allocated, but they do not measure to see if the benefit received equals the benefit expected. It may be that they are fearful of measuring what they already know — benefits are not equal to expectations. The burden this creates is the burden of lost benefits.
Application portfolio bloat is another burden that can be created by the sole attention to delivery and budget. A development team receives $1M to deliver a defined scope. They deliver it for 50% of the projected cost. Instead of returning the remaining funds to the next worthy project investment, they spend the remaining funds on additional enhancements. It’s not like they did not receive any value. However, they are not working on the priorities that are expected to deliver the most value. This condition enlarges the burden of lost benefits and further increases the unplanned expansion of the application portfolio.
Solely valuing delivery and budget takes your eye off of the sources of measurable value — the scope and the quality required to provide the return. The value is not delivered through the management of the budget, but in how the budget is applied to those things that provide the real return. Like ancient cultures who tire from carrying larger and larger stones, we can change what we value if the burden has grown too large. We can define value in new ways that reflect today’s needs. We can change our organization’s notion of value. But we must begin recognizing and demonstrating the burden created by what we currently consider valuable.
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.