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.


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 th

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem