Avoid Metrics Overload - Striking the Balance for Value Realization

by Ryan Ogilvie
Date Published April 4, 2024 - Last Updated April 4, 2024

In the realm of IT Service Management, metrics play a pivotal role in evaluating the efficiency, effectiveness, and overall performance of IT services. From incident response times to customer satisfaction rates, metrics provide valuable insights into the health and success of IT operations. However, there's a fine line between leveraging metrics for informed decision-making and drowning in a sea of excessive data. Together, we'll explore the pitfalls of excessive metrics and the challenges they pose to value realization within ITSM, as well as some ways to optimize metric usage with some practical examples.

During my career, I have seen my fair share of challenges related to metrics. Unfortunately, an issue I have run across is the organization that feels the need to measure everything so we can improve our operations. While this might seem like a good idea, there are drawbacks to having too much information. Here are some of the key pitfalls I have come across.

Complexity: One of the most significant pitfalls of excessive metrics is the overwhelming complexity they introduce. When organizations attempt to track every conceivable aspect of IT service delivery, it often leads to an avalanche of data that is difficult to interpret and act upon. For instance, monitoring dozens of Key Performance Indicators (KPIs) related to incident management, change management, and request fulfilment can quickly become too much for both practitioners and leadership to comprehend and be able to act upon.

A Practical Example: Consider an IT Service Desk. The focus of the team is to ensure that incidents and requests that are coming in are being worked on where appropriate and triaged to other support teams when the need arises. Metrics that are captured beyond that focus may have a point of interest but is not really helping the manager of the team to determine if they will need additional resources, some automation or other assistance to make work easier. This surplus of metrics muddies the essential performance indicators, making it challenging to identify areas for improvement and take decisive action. This volume of information makes it hard to see the forest through the trees, even if the potential improvement might otherwise be Aright in front of us.

Misaligned Incentives: Excessive metrics can also result in misaligned incentives within ITSM teams. When individuals or teams are evaluated based on a multitude of metrics, they may prioritize activities that maximize their performance on those metrics rather than focusing on the broader goals of the organization. I have worked with teams that call this "gaming the system." These teams tend to utilize metrics that make them ‘look good’ within IT but in reality, these metrics may only matter to that team or department. This type of focus may look good in the short term but can come at the expense of long-term value creation. Your goals should align to the business objectives for the metrics to matter.

A Practical Example: A typical example of this that I have seen is where an IT support team is measured solely on the number of tickets closed within a given time frame. In their pursuit of meeting this metric, support agents may rush through incidents or requests without adequately addressing underlying issues or providing satisfactory resolutions to users. As a result, customer satisfaction plummets, and the organization's reputation suffers, despite the team meeting its closure targets. This may even spawn off additional issues when repeat requests or incidents are created to address the lack of support from the initial request that was closed too quickly.

Analysis Paralysis: Excessive metrics can lead to analysis paralysis, where stakeholders become inundated by the sheer volume of data available and struggle to make informed decisions. When confronted with an abundance of metrics, practitioners and leadership may find it challenging to discern meaningful patterns or trends amidst the noise, resulting in delayed decision-making and missed opportunities for improvement. I have seen cases where some organizations produce a monthly metrics report for leaders to review via email that are pages long filled with information that has no context for the audience and is simply glanced at. Unfortunately, this type of activity comes at the expense of someone compiling these metrics for several hours with that same person wondering if anyone is even reading it.

A Practical Example: Consider an ITSM dashboard populated with dozens of metrics related to service desk performance. Rather than providing actionable insights, the sheer volume of data overwhelms stakeholders, making it difficult to identify underlying issues or prioritize areas for intervention. Amidst a sea of bar graphs, pie charts and other analytics the people viewing the dashboard are unable to focus on what’s important. As a result, critical issues may go unnoticed, and opportunities for process optimization may be overlooked. Having a simplified dashboard that you are able to dive into makes more sense. When someone is looking to find out more information they can click into the metric to provide more detail that may apply.

Resourcing: Always a hot topic for any team. Maintaining and analyzing a plethora of metrics requires significant resources in terms of time and technology. Excessive focus on metric analysis can divert attention and resources away from more strategic initiatives aimed at driving innovation, improving customer experience, and delivering tangible business value. As I mentioned above, I have seen teams spend loads of time on building, reviewing, displaying, and translating metrics for teams that may still not even understand how this applies to the bigger picture.

A Practical Example: Suppose an organization invests heavily in implementing a sophisticated metrics dashboard capable of tracking hundreds of ITSM metrics in real-time. While the dashboard provides comprehensive visibility into IT operations, the resources expended on its development, maintenance, and upkeep detract from investments in initiatives that directly contribute to business growth and competitive advantage. Taking that one step further, some dashboards may not require the upkeep however those that are reviewing may not fully understand where the numbers are coming from, and additional work might need to be done to reverse engineer how they arrived at a number. In cases like these it may make more sense to have an Operational dashboard for internal day to day work and a business or leadership facing dashboard with your key performance indicators.

Optimize to Maximize Value

So how do we optimize the metrics to maximize value? Let’s look at how we can do this with practical insights drawn from key process areas including incident management, change management, problem management, and request fulfillment.

Incident Management: Efficiency and Service Restoration

In incident management, metrics play a vital role in gauging the efficiency of response and resolution processes. Practitioners should focus on metrics such as Mean Time to Resolution (MTTR), First Call Resolution Rate and Incident volumes.

Leadership can leverage these metrics to identify bottlenecks in the incident management workflow and allocate resources effectively. By continuously monitoring and analyzing these metrics, organizations can streamline processes, optimize resource utilization, and ultimately minimize the impact of incidents on business operations.

Change Management: Risk Mitigation and Compliance

Change management revolves around implementing changes while minimizing risks and disruptions to services. Metrics such as Change Success Rate, Change Lead Times, Changes by Type and Changes by Risk provide visibility into the effectiveness of the change processes. For example, a high Change Success Rate indicates robust change management practices, leading to fewer incidents and service disruptions.

Understanding Change Lead Times and Change Success Rate allows us identify areas for improvement and enhance agility in responding to business needs. Leadership can use these metrics to assess the overall risk that may be introduced to the organization and ensure compliance and regulatory requirements is being met.

Problem Management:
Root Cause Analysis and Prevention

Problem management focuses on identifying underlying causes of recurring incidents and implementing long-term solutions to prevent their recurrence. Key metrics include First-Time Fix Rate, Percentage of Problems Resolved, and Mean Time Between Failures (MTBF). These metrics help measure the effectiveness of problem resolution efforts and the ability to address underlying issues proactively.

By analyzing trends and patterns revealed by these metrics, practitioners can prioritize problem investigations and allocate resources to address systemic issues. Leadership can leverage these insights to drive a culture of continuous improvement, fostering collaboration between IT teams and business stakeholders to identify and address root causes effectively.

Request Fulfillment: Service Efficiency and Customer Satisfaction

Request fulfillment involves delivering services and fulfilling user requests promptly and efficiently. Metrics such as Request Volume, Request Resolution Time and First Contact Resolution Rate can paint a pretty telling picture of how our requests are submitted, triaged and completed.

Practitioners should focus on streamlining request fulfillment processes, minimizing manual intervention, and automating repetitive tasks to improve efficiency and reduce lead times. Leadership can use these metrics to identify areas for service improvement, allocate resources based on demand patterns, and enhance the overall user experience.

The important thing to keep in mind with any of these metrics is that don’t have to exist in a vacuum. Having open dialog with your business, clients and support teams on these metrics only enhances their accuracy and value.

Be open to have the results of the metrics challenged. After all, if we think we are providing excellent service, and the user bases sees it differently we should understand where the disconnect exists.

Optimizing metric usage in ITSM is essential for driving value realization and achieving organizational objectives. Practitioners and leadership must adopt a strategic approach, focusing on metrics that provide actionable insights and contribute to continuous improvement. By leveraging metrics effectively in areas such as incident management, change management, problem management, and request fulfillment, organizations can enhance service quality, mitigate risks, and ultimately deliver value to stakeholders. Embracing a culture of data-driven decision-making and continuous improvement is paramount in today's rapidly evolving IT landscape.

Tag(s): service strategy, service management, best practice, infrastructure management, ITSM, supportworld


More from Ryan Ogilvie

    No articles were found.