Skip to main content

Service Measurement

Before my life as an ITSM professor, I was responsible for delivering the monthly reports on IT at a large specialty retailer organization with multiple remote locations in several states across America.  I delivered many of the standard reports for Service Desk, Change Management and System Availability.  System availability was a standard report that reviewed from a system / hardware perspective just how available the systems and their supporting components were throughout the month.  This was delivered in percentages and the goal was to maintain 100% infrastructure availability.

Even though many of the individual systems and components were meeting their required SLAs, our customers were still not satisfied with the availability and performance of critical services.  We needed to re-address what should we be measuring and how should we be reporting achievements back to the business and customers. We decided to report on the end to end delivery of our services and the actual customer experience from their perspective.
Three basic measurements were utilized
  • Availability of the service
  • Reliability of the service
  • Performance of the service
It was still valuable for us to also continue measuring these aspects for the underlying components.    The individual metrics would be used as input into our new Service Availability Report.  The key here was developing a service measurement framework that would from a statistical analysis model, coincide with what the customers were experiencing.  Of course,  this took some trial and error. As with any activity,  we took a continual service improvement approach to refining what measurements and metrics we used to show all aspects of availability and unavailability of our services.
By re-evaluating our measurements with all stakeholders, we were able to establish an agreed definition of what success should look like.  By choosing the correct measures, defining the critical elements, creating clear and relevant objectives and having define roles and responsibilities, we were able to successfully and accurately report the true customer experience and deliver a more sustainable and relevant level of service to our customers.

Comments

Unknown said…
Are there any details you can provide about how you approached calculating these measures? This is a challenging area!

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

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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th