Skip to main content

The Elusive Case πŸ“– of Leadership Buy-In πŸ”Ž

For over 20 years, one question keeps resurfacing: How do we secure buy-in from senior
management for our ITSM initiatives
? It’s a challenge that never seems to fade. Like any good mystery, just when you think you have it solved, a new player enters the scene and changes the game.

In February 2024, we were delighted to have David Cannon and Ken Jarvis present our monthly webinar, on the topic Getting and Keeping Executive Buy-in for your ITSM Program

I personally find it difficult to revisit all the audio content on my wishlist, so I appreciate it when I can read a concise summary - like CliffsNotes for Webinar. Or in this case, LisaNotes, as I am building on some of the ideas presented. 

In prepping for the webinar, Donna Knapp postulated, "Are we even asking the right question? Should we be asking instead, What will make executives care about ITSM?"  

As Dr. Lanning says in the movie I, Robot, "That, detective, is the right question". 

The Top Challenge: Leadership Support
As discussed in the webinar, research consistently shows that a lack of senior leadership support is the top challenge for ITSM programs, year after year. In fact, a 2022 Axelos survey confirmed that lack of management buy-in remains a primary obstacle. 

The Axelos research also highlights which ITSM processes organizations were actively working on: service desk, incident management, service request management, change enablement, and problem management. While important, these are operational concerns that may not always capture executive attention. Most executives, especially CIOs, are focused on strategic initiatives—often far removed from day-to-day IT operations.

So, how do we bridge the gap? How do we convince executives that ITSM is relevant to their goals?

What Do Executives Care About?
For our webinar, David pulled together research by looking at reports from Gartner, Forrester, and CIO Magazine. He presents that the top challenges CIOs face today can be grouped into two categories: strategy/business alignment and technology. (Download slide deck)

On the strategic side, CIOs are concerned with:
  • Cybersecurity threats
  • Economic uncertainty
  • Hybrid workforce dynamics
  • Digital transformation
  • Innovation
On the technology side, their challenges include:
  • Acquiring and retaining talent
  • Cloud complexity and spending
  • Infrastructure modernization
  • Data management and analytics
  • AI and emerging technologies
It’s clear from this list that ITSM or ITIL doesn’t feature explicitly in their thinking. CIOs aren’t asking, "How can ITIL solve my problems today?" They’re focused on high-level initiatives that drive the organization forward. For ITSM professionals, this presents a challenge - one that requires positioning ITSM as a solution to the problems that matter most to executives.

Understanding What Executives Care About 

The key to securing buy-in from anyone, for anything, is understanding "What’s in it for them?"

While ITSM may be a priority for us, executives often see it as a background operation—something that should "just work." They may not grasp the full importance of ITSM, especially if they come from a business background. This disconnect can lead to resistance, or at least, indifference when it comes to allocating resources.

To bridge this gap, we need to frame ITSM as a tool that supports the broader goals executives care about, like digital transformation or innovation. Mapping ITSM metrics to those goals is crucial. For instance, if an executive is focused on improving customer experience, you could demonstrate how an efficient incident management process reduces downtime and improves service quality. Here are a few other scenarios: 

Innovation - Streamlined change management, supported by ITSM, reduces risk in deploying new services or technologies. Period. Full Stop. But sometimes it's good to remind the higher ups of that. Metrics like "change lead time", "change success rate" or "percentage of failed changes" showcase how controlled processes enable faster, safer innovations, helping the business bring new products or features to market quickly.

Agility - For executives focused on business agility, ITSM’s role in automation and workflow orchestration can be linked to faster response times. Metrics such as "mean time to restore (MTTR)" or "incident response time" can show ITSM’s role in automation and workflow orchestration can be linked to both greater system stability and faster response times when things do go wrong.

Compliance and Risk Management - If the executive is concerned with governance or regulatory compliance, you can emphasize how ITSM ensures compliance through well-defined processes in incident, change, and problem management. Metrics like "audit compliance rate" or "percentage of changes compliant with policy" demonstrate how ITSM mitigates risk and maintains operational integrity. 

By aligning ITSM outcomes with these strategic goals, it’s clear that ITSM delivers more than technical support—it becomes a critical enabler of business success.

Want to brainstorm and come up with more ideas? 
Chat with an ITSM Academy Subject Matter Expert. 

Keeping Executives Engaged Over Time
Even after securing initial buy-in, the challenge is to keep executives engaged throughout the lifecycle of the ITSM program. This is especially true for long-term initiatives like Enterprise Service Management (ESM) or ITSM, which can span years.

To keep them engaged, you need to regularly review the ITSM metrics presented. Are you aligning them with strategic goals? Is it clear that the data on their dashboards is aligned? Can they see, at a glance, how it’s impacting the organization? Metrics such as service reliability, time to resolution, and customer satisfaction are valuable, but they should always be framed in the context of broader business objectives like efficiency, innovation, or customer experience.

Grassroots Efforts and Selling ITSM Differently
"But I'm just a Change Manager, a cog in a wheel, how am I supposed to know what's a priority for my leadership?" you may ask.

Talk to E V E R Y O N E - As an ITSM professional, you are likely in a unique position to interact with multiple teams across the organization. Take advantage of these touchpoints to ask questions about broader business initiatives. Attend meetings, read leadership communications, or reach out to key stakeholders to better understand what leadership cares about. Even casual conversations can provide valuable insights.

Research the strategic documentation available to you - You don’t have to guess. Organizations often have strategic plans, quarterly goals, or executive dashboards. Familiarize yourself with these documents—they often outline leadership’s priorities in terms of growth, innovation, or efficiency.

Like any great mystery novel, the case for executive buy-in to ITSM isn’t solved in a single chapter. Instead, it unfolds bit by bit, requiring patience, strategy, and sometimes, a fresh approach to clue in the decision-makers. As ITSM professionals, we find ourselves playing detective, collecting insights and mapping each discovery back to what matters most to the leadership team.

In this ongoing story, our objective is to reveal how ITSM isn’t merely a side story; it’s an essential plot line driving the organization toward its larger ambitions. The tools for solving this case lie in linking ITSM metrics to strategic goals, building relationships with key stakeholders, and uncovering what truly resonates with executive priorities.

The best mysteries keep readers hooked by answering some questions while leaving others just out of reach, drawing them deeper into the story. In the same way, keeping executives engaged in ITSM is an evolving process, one that requires staying alert to changes in their goals and challenges, and adjusting our approach as new 'chapters' unfold.

So, if you’re ready to crack the case on leadership buy-in, remember this: the ITSM Academy team is here to help you uncover the clues, connect the dots, and solve the mystery—page by page, chapter by chapter.

Comments

Popular posts from this blog

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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

In the rapidly evolving landscape of IT service management (ITSM), the principles of service design have expanded beyond just focusing on technology. As we embrace new methodologies and innovations in 2024, the Four Ps of Service Design remains a critical framework to ensure comprehensive and effective service delivery. See also: The New Four P's of Service Management These Four Ps are People, Processes, Products, and Partners. 1. People: At the core of any service design are the people who deliver and consume the services. In today's world, this includes a diverse range of stakeholders from employees and customers to vendors and partners. Effective service design considers user experience (UX) and employee experience (EX) to ensure services are intuitive and meet the needs of all users. The rise of AI and automation has transformed roles, making it essential to invest in continuous learning and development to keep skills relevant. 2. Processes: Streamlined and efficient proc

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