In research done earlier this year, we looked at changing patterns of IT service management (ITSM) adoption across a population of 270 respondents in North America and Europe. One of the standout themes that emerged from our findings was the need for the service desk to become a more automated and analytically empowered center of authority across IT as a whole. Rather than casting the service desk as a reactive, low-tech bastion of ineffective customer interaction, the data outlined requirements for a much more dynamic ITSM team—a team that could govern decision making and automate actions in dialog with operations, development, and business stakeholders.

A Little Context

The factors driving the need for analytics and automation in support of ITSM transformation were manifold. Here are just a few key points:

  • Outreach to the Enterprise – ITSM organizations enjoying investment and growth took on more responsibilities across line-of-business silos. Successful ITSM groups were also consolidating IT and non-IT service desks in terms of process and other efficiencies. Both of these requirements suggest enhanced levels of automation and superior analytic intelligence across a widening enterprise landscape.
  • Support for Cloud – Another key factor in ITSM team growth, “support for cloud” was also a reason for ITSM decline when it wasn’t forthcoming. When asked about unique cloud requirements, improved levels of IT process automation was ranked number one—tied with improved integrations with operations for more effective incident and problem management, which in itself requires better analytic awareness and more automated process workflows. Automation was also indicated in the next two priorities for managing cloud—more dynamic capabilities for capturing change interdependencies and improved levels of automation for provisioning and configuration.
  • Support for DevOps – A surprising 65% of our research respondents indicated some level of pre-existing support for development through the service desk, and an additional 16% had plans for integrated DevOps support. Top priorities included integrated workflows and scheduling, as well as active provisioning via configuration automation and a configuration management database (CMDB). Also critical were effective insights on application quality, usage, and value, which also require analytic investments.
  • Support for Mobile – Sixty-two percent of respondents viewed mobile as “significantly” or “completely” impacting their ITSM strategies with strong priorities for integrated consoles for monitoring and optimizing a broad array of endpoints, which once again requires investments in superior levels of analytics and automation.

ITSM Analytic Priorities

Our research also delved more deeply into how and why analytics were valued. For instance, we saw that 69% viewed big data and analytics either as a resource shared between operations and the service desk or as primarily an ITSM requirement. When we asked for more specifics about how and why analytics could be used, we saw especially high marks for: analytics for incident/problem and availability management; analytics for IT governance in terms of efficiencies and effectiveness; and analytics for change management. In another question, respondents indicated top rankings for:

  • Analytics to promote superior decision making between ITSM and operations
  • Analytics to support superior decision making between ITSM and business stakeholders
  • Analytics that can draw from an ITSM knowledge base
  • Real-time predictive analytics

ITSM Automation Priorities

I often like to make the connection that the relationship between analytics and automation is a handshake between insight and speed. Just as speed without insight can lead to train wrecks, simply knowing what’s true without clear paths to accelerate action can lead to costly inefficiencies. When asked about functional priorities for ITSM, enhanced automation for self-service came in first place. Then, when we asked for specific priorities in change- and configuration-related automation, we saw the following priorities:

  1. IT process automation or runbook
  2. Systems configuration automation
  3. Workflow between the service desk and operations
  4. Storage and network configuration
  5. Application provisioning  (in general and for self-service)
  6. Automation in support of assimilating cloud resources
  7. Mobile and endpoint configuration

Success Factors

Perhaps not surprisingly, we saw that those who viewed themselves as “extremely successful” in their ITSM strategies were twice as likely to invest in advanced levels of automation for managing change as less successful groups. They were also more likely to promote higher levels of analytics across the board along with more unified approaches for endpoint management, cloud optimization, and superior levels of integration with operations and development.

So while there are other key game-changing technologies that play to ITSM transformation—most notably service modeling in the CMDB/CMS and application dependency mapping—our data indicates that analytics and automation reside at the very center of ITSM transformation. Perhaps then it’s not surprising that in our most recent research analytics and automation were shown to also be at the very heart of IT and digital transformation.  And as we concluded with that research, analytics and automation are also the foundation for something even more important than technology itself—superior levels of dialog and community-building across IT and between IT and the business it serves.