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

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...

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

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...