Last week I wrote about importance of treating the information as an asset. The bottom line is that due to its intangibility, its value is difficult to measure, and thus more often than not, totally neglected and ignored. However, unless the value is shown, the managers will continue sidelining information management projects, unwillingly leading the organizations further into information overload chaos.
So is there any practical advice how to approach the value information estimation? There is no simple answer as every organization perceives and uses information in different ways. However, like with Generally Accepted Accounting Principles, certain set of rules could be worked out allowing building foundation for estimation model.
Why do we need it?
With hundreds of projects, that organizations need to allocate limited financial and human resources, information management projects, usually are low on the list. Exceptions are fancy pet projects, like for example – implementing latest trendy applications. Often such projects bring limited benefits to the organization comparing with costs and efforts invested. Usually their business cases have financial models built on shaky numbers, basing primarily on soft benefit estimations, often discounted by accountants.
The reason why we want to estimate value of information is to make sure that the scarce resources are channeled to these projects that address needs related to what is most important to the organization. The segmentation of the information value could be done from the following three perspectives:
– Business need – when information is part of the business workflow; related to improvements in productivity; when information is taking direct part in marketing strategy or it needs to be visible to external business stakeholders. Key role here also plays ensuring single version of truth – when the organization wants to make sure that the decisions are made based on latest version of information. The business need also includes improvement of the productivity by allowing users to find the information faster, but also to spend less time managing information that does not have to be managed to the same degree (ex. transitional records). Pareto rule applies here pretty well – spend 80% of your time on managing 20% of the most important informational artifacts.
– Risk – organization needs to comply with legal, regulatory or statutory requirements; needs to provide evidence of business decisions, activities and transactions
– Costs – to replace the information or costs related to acquire information, licensing and subscriptions
The value of information is realized only through its use and this should be criteria for its measurement. However – the ‘use’ is totally subjective. Attempts to measure information value by representing it through more tangible dimensions like availability through business intelligence tools or data volume cannot be successful. For example, in case of BI – the way how well information is aggregated cannot determine capabilities of organization’s management. On the other hand, volume of data does not reflect its quality, content or ability to find information within it.
Valuation approaches
As mentioned above, the valuation of the information is often complex due its dependency on many, often intangible factors. However there are some situation that the straight valuation could be done. But first let’s put some groundwork. There are two types of approaches:
– Qualitative – tending to be subjective, describing information in terms of some categorization, often informal
– Quantitative – based on hard numbers and as such, more objective and reproducible
The information valuation fits somewhere in the continuum between purely qualitative and purely quantitative. The degree of how close it will be to either side of the spectrum will depend on type of information, how it is used, its purpose, type of business organization, risks impacts, organizational culture and so on. The organization needs to develop set of classes for its informational assets and categorize the assets accordingly. Once this is done, various strategies to manage the information and prioritization of related projects will be possible.

The development of such set of classes should be governed by some basic principles.
Read more »
Recent Comments