Skip to main content

Preparing for the Future of ITSM

Sean Sebring
SolarWinds

The global IT skills shortage will persist, and perhaps worsen, over the next few years, carrying a collective price tag of more than $5 trillion. Organizations must search for ways to streamline their IT service management (ITSM) workflows in addition to, or even apart from, hiring more staff. Those who don't find alternative methods of ITSM efficiency will be left behind by their competitors. Fortunately, there are best practices any organization can embrace to empower clients and create a path to a future-proof ITSM framework.

To find these best practices, SolarWinds analyzed over 2,000 ITSM data systems and 60,000 points of anonymized and aggregated customer data. The data found three proven techniques — service level agreements (SLAs), automation rules, and self-service portals — that save time, conserve resources, and lessen the workload on ITSM staff.

1. Service Level Agreements Create Accountability and Direction

The first step to building a mature and future-proof ITSM function is developing SLAs for each type of ticket that comes through the ITSM help desk. This creates a level of accountability the entire team can refer to. Per data in the report, SLAs help resolve tickets an average of 2 hours faster than organizations that don't employ them. If a team can maintain fast and effective ticket resolutions, it helps build customer trust, optimize resources, and lead to greater ROI.

In addition to accountability, SLAs help create benchmarks that ITSM leaders can use to decide whether to increase or decrease the scale of their operations. Teams should develop a regular cadence for checking in on SLA completion rates. If service desks continually meet their SLAs, it may be time to set new goals and benchmarks to measure efficiency. If the opposite is happening, the team can use the percentage of SLAs to potentially scale back operations or pinpoint potential adjustments.

2. Automation Rules Speed up Workflows

The report suggests a relationship between automation and an organization's ability to meet its ITSM SLAs. Data from the report shows that when ITSM desks embed automation rules/artificial intelligence (AI) within their workflows, they have a lower percentage of SLA misses — or the percentage of total tickets the desk could not complete. Teams that use methods such as automated ticket routing, incident identification and categorization, and smart notifications will be able to cut their SLA misses in half while simultaneously expediting their resolution times.

The best way to install automation throughout various workflows is through a comprehensive ITSM platform and an implementation plan that grows as the organization does. The right ITSM platform will allow teams to leverage AI technology to improve service catalog searches, offer service suggestions, and ensure teams don't spend time working on tickets irrelevant to a client's root problem.

3. Self-Service Portals and Knowledge Base Articles Empower Clients

Self-service portals play a vital role in an organization's automation workflow. A complete self-service portal can simultaneously relieve staff workload while allowing clients to partner with ITSM staff as they solve their own issues. According to the report, self-service portals can reduce ticket resolution times by as much as two hours.

Knowledge base (KB) articles provide clients with the information they need for a successful self-service portal experience. To be most effective, KB articles must be both comprehensive and easy to understand. As the client takes charge of resolving their own ticket, the information in each article must also be easy to find. When self-service portals and KB articles work correctly, they result in more free time for customers and ITSM agents to focus on the most important tasks that require a human in the loop.

The Future of ITSM is More About Workflows Than Staff

A popular English proverb from the 1300s states, "Many hands make light work." While conventional wisdom would agree, data from the report found no direct correlation between the number of ITSM staff members and the time it takes to resolve tickets. It should be noted that ITSM leaders will, and should, try to address the IT hiring shortage through non-traditional hiring means — training non-IT staff and implementing skills-based hiring, for example — but that shouldn't be the only priority. It would behoove today's IT decision-makers to focus much of their efforts on the tools and workflows that are proven to make IT teams run smoother and more efficiently. In other words, a future-proof ITSM framework is one that shuns conventional thinking and embraces unconventional practices to adapt alongside modern enterprises. 

Sean Sebring is Solutions Engineering Manager at SolarWinds

Hot Topics

The Latest

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Preparing for the Future of ITSM

Sean Sebring
SolarWinds

The global IT skills shortage will persist, and perhaps worsen, over the next few years, carrying a collective price tag of more than $5 trillion. Organizations must search for ways to streamline their IT service management (ITSM) workflows in addition to, or even apart from, hiring more staff. Those who don't find alternative methods of ITSM efficiency will be left behind by their competitors. Fortunately, there are best practices any organization can embrace to empower clients and create a path to a future-proof ITSM framework.

To find these best practices, SolarWinds analyzed over 2,000 ITSM data systems and 60,000 points of anonymized and aggregated customer data. The data found three proven techniques — service level agreements (SLAs), automation rules, and self-service portals — that save time, conserve resources, and lessen the workload on ITSM staff.

1. Service Level Agreements Create Accountability and Direction

The first step to building a mature and future-proof ITSM function is developing SLAs for each type of ticket that comes through the ITSM help desk. This creates a level of accountability the entire team can refer to. Per data in the report, SLAs help resolve tickets an average of 2 hours faster than organizations that don't employ them. If a team can maintain fast and effective ticket resolutions, it helps build customer trust, optimize resources, and lead to greater ROI.

In addition to accountability, SLAs help create benchmarks that ITSM leaders can use to decide whether to increase or decrease the scale of their operations. Teams should develop a regular cadence for checking in on SLA completion rates. If service desks continually meet their SLAs, it may be time to set new goals and benchmarks to measure efficiency. If the opposite is happening, the team can use the percentage of SLAs to potentially scale back operations or pinpoint potential adjustments.

2. Automation Rules Speed up Workflows

The report suggests a relationship between automation and an organization's ability to meet its ITSM SLAs. Data from the report shows that when ITSM desks embed automation rules/artificial intelligence (AI) within their workflows, they have a lower percentage of SLA misses — or the percentage of total tickets the desk could not complete. Teams that use methods such as automated ticket routing, incident identification and categorization, and smart notifications will be able to cut their SLA misses in half while simultaneously expediting their resolution times.

The best way to install automation throughout various workflows is through a comprehensive ITSM platform and an implementation plan that grows as the organization does. The right ITSM platform will allow teams to leverage AI technology to improve service catalog searches, offer service suggestions, and ensure teams don't spend time working on tickets irrelevant to a client's root problem.

3. Self-Service Portals and Knowledge Base Articles Empower Clients

Self-service portals play a vital role in an organization's automation workflow. A complete self-service portal can simultaneously relieve staff workload while allowing clients to partner with ITSM staff as they solve their own issues. According to the report, self-service portals can reduce ticket resolution times by as much as two hours.

Knowledge base (KB) articles provide clients with the information they need for a successful self-service portal experience. To be most effective, KB articles must be both comprehensive and easy to understand. As the client takes charge of resolving their own ticket, the information in each article must also be easy to find. When self-service portals and KB articles work correctly, they result in more free time for customers and ITSM agents to focus on the most important tasks that require a human in the loop.

The Future of ITSM is More About Workflows Than Staff

A popular English proverb from the 1300s states, "Many hands make light work." While conventional wisdom would agree, data from the report found no direct correlation between the number of ITSM staff members and the time it takes to resolve tickets. It should be noted that ITSM leaders will, and should, try to address the IT hiring shortage through non-traditional hiring means — training non-IT staff and implementing skills-based hiring, for example — but that shouldn't be the only priority. It would behoove today's IT decision-makers to focus much of their efforts on the tools and workflows that are proven to make IT teams run smoother and more efficiently. In other words, a future-proof ITSM framework is one that shuns conventional thinking and embraces unconventional practices to adapt alongside modern enterprises. 

Sean Sebring is Solutions Engineering Manager at SolarWinds

Hot Topics

The Latest

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...