Skip to main content

Metrics and Business Value

IT managers gather and distribute metrics that reflect their group’s performance on a regular and timely basis.  But outside of their immediate organizations do these metrics have any real meaning or impact? Do these measurements really define the value that IT is delivering?  Business executives shouldn’t have to work to see the positive impact of IT performance.  It should be made readily visible, in language they can grasp quickly and easily.  In many IT organizations there is a continued focus of their reporting towards the performance of the technology and not the value being delivered to the business.  This emphasis continues to create a gap between IT and the rest of the organization. (1)

What metrics do you employ?  Service metrics, measuring the end to end performance of your services, based on your technology metrics.   Technology metrics, performance of your components and applications. Are they available when needed? Do you have the correct levels of capacity to meet dynamic demand?  What best practice processes do you engage and how are they measured?

Many of the organizations I have visited do these things, but stop short of having a strong overarching vision about what they want their technologies to accomplish and what the business value and benefit should be.  There is a lack of coordination among the many silos that make up the IT organization and what services should be rendered to their customers.  Many even operate without even giving much thought to “what value are we generating for our organizations. 

So I take us back to the “Continual Service Improvement” approach:

  • What is the vision?  Ensure business and IT strategic alignment.  An overarching vision of how our technology generates business value in measurable ways the business can understand.
  • Where are we now?  Do we have strong governance strategically, tactically and operationally to ensure are efforts are well coordinated across all of our silos?
  • Where do we want to be?  Have we identified areas where vision and alignment aren’t what they should be and defined plans and activities for improvement?
  • How do we get there?  Implementation of prioritized plans and activities to build strong digital skills and culture.
  • Did we get there?  Use of appropriate measures defined by both business and IT to validate our course of action and verify results of business outcomes.
  • How do we keep the momentum going?  Continued diligence in ensuring that our technology continues to generate business value.

                                                                   
1 The Real Business of IT – Richard Hunter, George Westerman

For more information on Continual Service Improvement training and certification go to http://www.itsmacademy.com/itil-csi/ 

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

ITIL 4 – Mapping the Customer Journey

All service providers are in the business of customer and user experience. It is not enough to compete on products and services, how services are delivered is as important as what is delivered.

The customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers. In order to focus on the outcomes and on the customer/user experience, service providers are seeking to master the art of mapping their customer journey. Doing so allows them to maximize stakeholder value through co-creation of value throughout the entire value chain.

The customer journey begins by understanding the overall macro-level of steps or groups of activities that generate the need for interaction between the customer and the service provider. These activities begin at “Explore” and end with “Realize” where the value is actually being consumed by the end-users.
The Band of Visibility