A featured contribution from Leadership Perspectives, a curated forum for enterprise technology leaders, nominated by our subscribers and vetted by the CIOApplications Editorial Board.

Adapthealth

Metrics, a Tool to Measure IT Operational Performance

A passion of mine outside of work is following Major League Baseball. While many aspects of the game have changed over the years, many fans in my age bracket agree that there is too much reliance on analytics, which diminishes the human element from the sport. I recognize the value of baseball analytics as a tool; however, using analytics as the primary or sole means to construct a lineup or to make in-game decisions may not produce the desired results. I have noticed similar parallels in the overuse of analytics in Major League Baseball and in how metrics are used in IT Service Management (ITSM).

Metrics can be useful took to measure IT Operational performance and servicing value, but much like analytics in baseball, if metrics are overused, the desired outcomes are not achieved, and IT could be misaligned with their customers. For example, in the past,

I worked for an organization where, by my estimations, the patch compliance team was achieving a 98% or greater success rate over a period of several months. However, the organization used a strange method for calculations, which showed the patch compliance team as below their SLA of 95% or better measured on a monthly basis. I suggested to the team manager, they should revise how they were reporting, but I didn’t have the authority or influence to implement new approaches, and so nothing changed.

IT leaders need to work with customers to ensure their framework and methodology for measuring ITSM metrics are aligned with business objectives

The reality was that most of the servers were compliant each month, but due to the way results were calculated and reported, the customers thought there were ongoing security issues and that the team was regularly failing.

Another company where I worked utilized a Service Desk SLA to measure the number of incidents closed on first “call” resolution. Upon assuming leadership of the Service Desk, I reviewed the SLAs and discovered a considerable inconsistency -- the volume of incidents compiled to calculate this metric appeared to be very low compared to the overall work volume of the team. I realized that calls rather than “contacts” were being added together to show the results of this metric. Once the SLA was updated to include all contacts to the Service Desk, i.e., phone calls, emails, portal entries, etc., then the SLA was accurately portraying how well the Service Desk was providing value to the customers.

These two examples show how two separate IT organizations decided what was best to measure as opposed to working with customers to determine what data is meaningful and relevant. It is important for IT leaders to remain cognizant that service level agreements are “agreements” between IT and the customer, not a siloed metric that IT prioritizes as the true measurement of success. IT leaders need to work with customers to ensure their framework and methodology for measuring ITSM metrics are aligned with business objectives.
This will allow IT to be viewed as a valuable and vital part of the overall organization and to not appear “off on their own”. Let us strive not to be the Major League Baseball team who gets lost in their numbers!

The articles from these contributors are based on their personal expertise and viewpoints, and do not necessarily reflect the opinions of their employers or affiliated organizations.