Skip to main content

Creating Value with Assets & Services

A lot of talk floats around of creating IT as a strategic component when 60% of its activities are service or support related. The art of IT alignment with proper governance wrapped around them not only makes IT a strategic component but enables its support functions to add value to business assets and services. In some instances values can be quantified in financial terms and in some non-financial terms. The non-financial terms are equally important as they fuel the financial components on a continuous form of inputs or future ROI's and VOI's. These non-financial value creation ideas can be:

1) Customer Perceptions: Customer's preferences are influenced by perceptions and in turn perceptions are influenced by attributes of a service or product in terms of value, desire, previous experience, position in the marketplace, need and self-image.

2) Reference values of services: This may be very vaguely defined and sometimes may be plain facts. To find our reference value of services or products, an organization needs to create a on-going dialog with its customers that feeds data into a knowledge base that teaches the producer or creator of the service or the product valuable lessons learnt, what brings value, how value can be added and how best take advantage of preferences and perceptions the customer generates.

3) Finally the economic value of a service to a customer is the sum of the customer's reference value and the net difference in value the customer associates with the service. The positive difference comes from the service's utility and warranty. Negative difference comes from losses suffered by the customer as a result of utilizing the service.




Popular posts from this blog

IT as a Innovation Partner in Business

Usually in Business organizations and especially in organizations where R&D is a separate department itself a tension persists on keeping the IT department away from any decision when it comes to innovation or process improvement. In short the IT department is generally seen as less of a help and more of a hindrance to innovation efforts. One of the main reasons is traditionally information systems are designed to impose structure on process, achieve pre-defined goals, produce metrics and minimize need for human interaction (in some case over maximize human interaction leading to nothing but "meetings").

While Innovation activities are highly unstructured and emergent, IT cannot be ignored or kept in isolation because IT can help in visualization tools, data mining efforts, uncover hidden relationships between data and create tools of knowledge management/information repository that so desperately is needed cross functionally but especially by the innovators within a org…

Analysis of SAP’s Platform Strategy

The software industry has been through high and lows up with the constant advent of new technological innovations and rapid changes in the global economic landscapes. SAP is the leading enterprise application software giant started by Hasso Plattner. The rise of Enterprise application industries started in early eighty’s with organizations needing one single software program that was capable of serving the multiple needs and functions of various departments. One single enterprise-wide application software means integrating applications that fused together for the smooth exchange and extraction of information. For example when customer services sold a product and got stock updated in the inventory by the warehouse people and the same data could be pulled by the Finance department. Enterprise Application software’s were designed exactly to do the latter mentioned processes seamlessly. SAP started by break away engineer’s Plattner and group build the company on strong engineering fort…

How Dashboards can mislead

Read an interesting article from John Shapiro professor at Northwestern Kellog on how dashboards can mislead executives and I cannot agree more. To be honest, I love visualization of data and have pushed my data architects and report writers to give me snapshots of various measures but how often the rich data didn't mean anything as it did not align with organizational goals. Even more, what information is important to me is not necessarily relevant to other executives in the organization.  Data analytics visualized on dashboards typically describe existing measures on past phenomena, some better ones predict future events and past data and the best one prescribe a course of corrective or strategic actions.

Shapiro talks about three types of traps executives can fall for:

1. The Context Trap:  We equate empirical data to the objective. I have blatantly used the cliche "numbers don't lie." But this belief can be dangerous because we can track wrong measures or metrics…