Skip to main content

The Future of ITSM: How Are Roles (and Rules) Changing? Part 2

Dennis Drogseth

Both the “rules” and the “roles” governing IT Service Management (ITSM) are evolving to support a far-broader need for inclusiveness across IT, and between IT and its service consumers. Recent EMA research, What Is the Future of IT Service Management? (March 2015), exposed a number of shifting trends that might surprise many in the industry.

Start with Part 1 of this blog

Research highlights show the following trends in rules and roles:

■ Cloud continues to be a game changer. ITSM teams are playing a more dynamic and service-aware role in managing cloud investments through a growing focus on such things as higher levels of automation and more attention to DevOps. ITSM teams are also integrating cloud services into their service catalogs — with SaaS (internal cloud) services, IaaS (internal cloud) services, and SaaS and IaaS services in public cloud tied for third.

■ The move to support enterprise services is also changing ITSM rules and roles. Only 89% of respondents had plans to consolidate IT and non-IT customer service — up from just two years ago when only 75% had plans to consolidate.

■ Mobility is seriously changing the ITSM game — in terms of both improved IT efficiencies and end-user outreach. 85% of our respondents had mobile support for end users, often across heterogeneous environments (tablets, iPhones, and Android phones, as examples). And 50% allowed end users to make ITSM-related service requests via these devices, making ITSM teams, and IT as a whole, considerably more consumer-friendly.

■ In parallel, the demand for more unified and effective endpoint management is expanding the requirements for role-based expertise. The leading requirements/skills here include capturing software usage, software license management, software distribution, operating system deployment, and patch management — across a fully heterogeneous set of endpoint options.

We also looked at success rates in an attempt to understand the chemistry of the most successful ITSM teams. To do this, we contrasted the 18% of respondents who viewed their ITSM initiative as “extremely successful” with the 12% who felt they were only “somewhat successful” or were “largely unsuccessful”. Those who were “extremely successful” were also:

■ Four times more likely to have integrated their IT and non-IT service desks

■ Twice as likely to have a CMDB/CMS-related technology deployed

■ Dramatically more likely to support cloud in service catalogs

■ Twice as likely to be leveraging mobile for ITSM professionals

■ Nearly four times more likely to offer service consumers mobile support for ITSM-related actions

■ Twice as likely to offer users access to corporate applications through mobile

■ More than twice as likely to be slated for growth

Overall, the news seems encouraging for ITSM teams willing to reach out and embrace a growing set of technologies and responsibilities. This means being ready to support new roles and expertise, while promoting more informed dialog, both between enterprise end-users and the service desk and between ITSM teams and the rest of IT — including operations and development. The news is probably not so good for the fainthearted seeking to cling to traditional ways of working in an “ITSM silo.” In other words, both the need and the opportunity for ITSM leadership awaits you — and our data suggests that the time to engage is now.

Image removed.

The Latest

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

The Future of ITSM: How Are Roles (and Rules) Changing? Part 2

Dennis Drogseth

Both the “rules” and the “roles” governing IT Service Management (ITSM) are evolving to support a far-broader need for inclusiveness across IT, and between IT and its service consumers. Recent EMA research, What Is the Future of IT Service Management? (March 2015), exposed a number of shifting trends that might surprise many in the industry.

Start with Part 1 of this blog

Research highlights show the following trends in rules and roles:

■ Cloud continues to be a game changer. ITSM teams are playing a more dynamic and service-aware role in managing cloud investments through a growing focus on such things as higher levels of automation and more attention to DevOps. ITSM teams are also integrating cloud services into their service catalogs — with SaaS (internal cloud) services, IaaS (internal cloud) services, and SaaS and IaaS services in public cloud tied for third.

■ The move to support enterprise services is also changing ITSM rules and roles. Only 89% of respondents had plans to consolidate IT and non-IT customer service — up from just two years ago when only 75% had plans to consolidate.

■ Mobility is seriously changing the ITSM game — in terms of both improved IT efficiencies and end-user outreach. 85% of our respondents had mobile support for end users, often across heterogeneous environments (tablets, iPhones, and Android phones, as examples). And 50% allowed end users to make ITSM-related service requests via these devices, making ITSM teams, and IT as a whole, considerably more consumer-friendly.

■ In parallel, the demand for more unified and effective endpoint management is expanding the requirements for role-based expertise. The leading requirements/skills here include capturing software usage, software license management, software distribution, operating system deployment, and patch management — across a fully heterogeneous set of endpoint options.

We also looked at success rates in an attempt to understand the chemistry of the most successful ITSM teams. To do this, we contrasted the 18% of respondents who viewed their ITSM initiative as “extremely successful” with the 12% who felt they were only “somewhat successful” or were “largely unsuccessful”. Those who were “extremely successful” were also:

■ Four times more likely to have integrated their IT and non-IT service desks

■ Twice as likely to have a CMDB/CMS-related technology deployed

■ Dramatically more likely to support cloud in service catalogs

■ Twice as likely to be leveraging mobile for ITSM professionals

■ Nearly four times more likely to offer service consumers mobile support for ITSM-related actions

■ Twice as likely to offer users access to corporate applications through mobile

■ More than twice as likely to be slated for growth

Overall, the news seems encouraging for ITSM teams willing to reach out and embrace a growing set of technologies and responsibilities. This means being ready to support new roles and expertise, while promoting more informed dialog, both between enterprise end-users and the service desk and between ITSM teams and the rest of IT — including operations and development. The news is probably not so good for the fainthearted seeking to cling to traditional ways of working in an “ITSM silo.” In other words, both the need and the opportunity for ITSM leadership awaits you — and our data suggests that the time to engage is now.

Image removed.

The Latest

Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...

Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...

Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...