Skip to main content

ITSM Futures: A Closer Look at Mobile and Unified Endpoint Management

Dennis Drogseth

In my last blog, I discussed how IT service management (ITSM) roles (and rules) are becoming more operations-aware. The blog examined a number of key game-changers for ITSM, including a growing requirement for shared analytics; the rise (not the demise) of the CMDB/CMS and service modeling; cloud as both a catalyst for innovation and a resource to be managed; and support for enterprise services such as facilities and HR. I also discussed two topics, mobility and unified endpoint management, that I’d like to examine in more depth here.

Mobility is King

OK — you probably didn’t need me to tell you that mobility is critical, but let me place its growing criticality in a more specific ITSM context with a few numbers.

■ 62% of our 270 respondents viewed lifecycle mobile support as “significantly” or “completely” impacting ITSM directions.

■ Mobility is anything but one-dimensional. In fact when we got the data for how actual mobile endpoints are being used by end users and ITSM professionals, the charts looked almost identical.

- 48% of end users and 45% of IT professional usage includes tablets, iPhones, Androids, and other mobile devices.

- 26% of both end users and IT professionals are using a mix of iPhone, Android, or other similar mobile endpoints (but no tablets).

- Only 15% (of end users) and 17% (of IT professionals) say they are not yet focused on any mobile devices.

■ 63% are using mobile endpoints in support of ITSM professionals with the following top-ranked results:

- Improved responsiveness to IT service consumers

- Increased IT efficiencies and reduced OpEx costs

- Improved collaboration between the service desk and operations

■ About two-thirds of our respondents allow end users to access corporate applications via mobile endpoints. And 50% of respondents offer their end users mobile access for ITSM-related requests and other interactions. Of these last, 78% saw “meaningful” or “dramatic” improvements in service delivery.

How Unified is Unified Endpoint Management?

Mobile is, of course, part of a bigger picture when it comes to endpoints. And here, our respondents generally favored integration and unified approaches. For instance, concerning mobile management, 58% preferred an integrated application that could support device management, configuration management, and enterprise mobility. Looking at endpoints more broadly, 82% viewed a unified console for managing mobile and traditional endpoints as “important” or “essential.”

When it came to unified endpoint management, the top seven functional priorities were:

■ Understanding software usage

■ License management

■ Software distribution

■ Operating system deployment

■ Patch management

■ Inventory management

■ Security

And the Winners Were …

So, how did the "extremely successful" map more specifically to questions of endpoint management and mobile empowerment? In my last blog, I mentioned that the extremely successful were twice as likely to leverage mobile for ITSM professionals, four times more likely to offer service consumers mobile support, and twice as likely to offer users access to corporate applications through mobile.

Here are a few additional data points regarding extremely successful priorities as opposed to those who were only somewhat successful, or unsuccessful:

Those who were extremely successful were:

■ Nearly eighteen times more likely to view lifecycle support for mobile users as “completely impacting” service desk operations

■ Three times more likely to have an overarching strategy for managing endpoints

■ Three times more likely to view managing and remediating endpoint issues at the service desk as critical

■ Four times more likely to prefer a single unified console for endpoints

So as you can see, the data here strongly suggests that a more progressive focus on both mobile and endpoint management helps to put ITSM teams in the winner’s circle.

Image removed.

Hot Topics

The Latest

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 ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

ITSM Futures: A Closer Look at Mobile and Unified Endpoint Management

Dennis Drogseth

In my last blog, I discussed how IT service management (ITSM) roles (and rules) are becoming more operations-aware. The blog examined a number of key game-changers for ITSM, including a growing requirement for shared analytics; the rise (not the demise) of the CMDB/CMS and service modeling; cloud as both a catalyst for innovation and a resource to be managed; and support for enterprise services such as facilities and HR. I also discussed two topics, mobility and unified endpoint management, that I’d like to examine in more depth here.

Mobility is King

OK — you probably didn’t need me to tell you that mobility is critical, but let me place its growing criticality in a more specific ITSM context with a few numbers.

■ 62% of our 270 respondents viewed lifecycle mobile support as “significantly” or “completely” impacting ITSM directions.

■ Mobility is anything but one-dimensional. In fact when we got the data for how actual mobile endpoints are being used by end users and ITSM professionals, the charts looked almost identical.

- 48% of end users and 45% of IT professional usage includes tablets, iPhones, Androids, and other mobile devices.

- 26% of both end users and IT professionals are using a mix of iPhone, Android, or other similar mobile endpoints (but no tablets).

- Only 15% (of end users) and 17% (of IT professionals) say they are not yet focused on any mobile devices.

■ 63% are using mobile endpoints in support of ITSM professionals with the following top-ranked results:

- Improved responsiveness to IT service consumers

- Increased IT efficiencies and reduced OpEx costs

- Improved collaboration between the service desk and operations

■ About two-thirds of our respondents allow end users to access corporate applications via mobile endpoints. And 50% of respondents offer their end users mobile access for ITSM-related requests and other interactions. Of these last, 78% saw “meaningful” or “dramatic” improvements in service delivery.

How Unified is Unified Endpoint Management?

Mobile is, of course, part of a bigger picture when it comes to endpoints. And here, our respondents generally favored integration and unified approaches. For instance, concerning mobile management, 58% preferred an integrated application that could support device management, configuration management, and enterprise mobility. Looking at endpoints more broadly, 82% viewed a unified console for managing mobile and traditional endpoints as “important” or “essential.”

When it came to unified endpoint management, the top seven functional priorities were:

■ Understanding software usage

■ License management

■ Software distribution

■ Operating system deployment

■ Patch management

■ Inventory management

■ Security

And the Winners Were …

So, how did the "extremely successful" map more specifically to questions of endpoint management and mobile empowerment? In my last blog, I mentioned that the extremely successful were twice as likely to leverage mobile for ITSM professionals, four times more likely to offer service consumers mobile support, and twice as likely to offer users access to corporate applications through mobile.

Here are a few additional data points regarding extremely successful priorities as opposed to those who were only somewhat successful, or unsuccessful:

Those who were extremely successful were:

■ Nearly eighteen times more likely to view lifecycle support for mobile users as “completely impacting” service desk operations

■ Three times more likely to have an overarching strategy for managing endpoints

■ Three times more likely to view managing and remediating endpoint issues at the service desk as critical

■ Four times more likely to prefer a single unified console for endpoints

So as you can see, the data here strongly suggests that a more progressive focus on both mobile and endpoint management helps to put ITSM teams in the winner’s circle.

Image removed.

Hot Topics

The Latest

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 ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...