25 Top ITSM Takeaways from SITS17

 In Blog, DevOps, ITSM

The annual Service Desk and IT Support Show (SITS) is done for another year. We came, we saw, we chatted, and we demoed – but what’s really important for those reading this blog is the sharing of the key advice and stats from some of the many SITS educational sessions.

This year, there was a lot of educational content related to hot topics – digital transformation, artificial intelligence, DevOps, enterprise service management, and service integration and management (SIAM) – plus some that related to ongoing IT service management (ITSM) and service desk challenges. For example, IT self-service and metrics – two areas where some IT departments continue to struggle.

Here are our 25 key SITS17 takeaways that just so happen to cover all of the above areas.

Digital Transformation

The panel debate entitled Dont call it digital transformation its organisation and people offered a number of interesting insights, five of which were:

  1. If IT departments are solving IT issues to simply make IT better, then they’re setting themselves up for failure – instead, focus on better business.
  2. IT needs to better understand who its customers really are. Not just the end users but the ultimate customers of the business.
  3. A digital-first mentality means that IT departments need to stop asking “WHO can approve a change” and instead ask, “WHAT approves a change”.
  4. IT departments have a lot of data but not many insights. Break down the organisational siloes for better insight.
  5. How can you expect customers to trust your business if your internal processes aren’t up to scratch? Digital transformation also relates to internal business processes.

Artificial Intelligence

A different panel debate called Artificial Intelligence (AI) positive opportunity or job risk?, started with an audience show of hands as to who was worried about the impact of AI on the service desk and who thought it would help. The audience was overwhelmingly in favour of AI being a positive thing for service desks.

The session then followed a positive path, with five of the most memorable points being:

  1. There’s an old IT adage – “You can improve on time, quality, and cost – choose any two of the three”, but AI allows you to improve all three.
  2. AI isn’t stealing jobs – it’s instead enabling people to focus on other tasks, tasks that create even more value.
  3. Don’t think of AI as “us” OR “them/it”. Think of AI as “us” AND “them/it”.
  4. “How are we going to use AI?” is the wrong question. “How are we going to deliver a better customer experience?” is the right question – with AI part of the solution.
  5. Customers will push back on AI technology if IT departments deliver AI technology. So, it’s important not to deliver the technology, and to instead, deliver customer solutions that are improved through AI.

DevOps, Enterprise Service Management, and Self-Service

The Service Desk Institute (SDI) was at SITS sharing its statistical love – with David Wright presenting new SDI research data in his “Service Desk trends in 2017 session.

  1. The benefits most associated with taking a DevOps approach are:

 

 

 

 

 

 

Source: SDI (Service Desk Institute)

On the flip side, resistance to change, getting all parties involved (joint top at 73% of survey respondents), and stakeholder buy-in (43%) were cited as the main challenges associated with DevOps adoption.

  1. SDI bullishly estimates UK enterprise service management adoption to be circa 85%:

 

 

 

 

 

 

Source: SDI (Service Desk Institute)

While this figure might appear high, it’s worth comparing this stat to generic stats around the level of ITIL® adoption – as this will include organisations that merely use some elements of incident management best practice, say, through to those that have adopted far more of the 26 ITIL processes and four functions.

Thus, when we consider the level of enterprise service management adoption, it will no doubt include organisations that range from using an IT service desk tool to manage complaint tickets, say, through to those that have business-wide enterprise service management strategies. And, within these, there might be more organisations that don’t know they are “doing” enterprise service management than there are that know they are.

  1. 64% of organisations state that their IT self-service initiatives failed (in particular in achieving a positive ROI):

 

 

 

 

 

 

Source: SDI (Service Desk Institute)

With a common cause being the viewing of self-service as a technology project rather than a people-change initiative.

To succeed, IT departments need to create self-service capabilities that people actually want to use – where it’s easier to use than calling – and use organisational change management techniques to help, and to encourage, them to do so.

SIAM

Steve Morgan presented on 10 tips for a successful SIAM implementation. There were lots of takeaways, five of which were:

  1. SIAM is much more than a process improvement programme, a tooling programme, or a sourcing programme.
  2. When defining your SIAM scope, use ITIL and COBIT® as a reference point to build a process/control-based operating model.
  3. SIAM tooling-strategy thinking shouldn’t be confined to ITSM tools. There’s also a need to define ownership and interoperability data-exchange principles.
  4. The important thing to remember with SIAM is that it’s about behavioural and cultural change.
  5. SIAM key performance indicators (KPIs) should encourage innovation, collaboration, business focus, and service awareness. And, remember that metrics drive behaviours.

ITSM Metrics

James Finister’s session, “Make metrics matter”, was first presented (by James) many years ago, but it hasn’t lost any of its relevancy for IT departments. Five of James’ key points were:

  1. Metrics too often: state the obvious, look to the past, reinforce preconceptions, don’t measure what we think we do, don’t contextualise, and aggregate not integrate.
  2. Keep metrics relevant – “yesterday’s target is today’s millstone and tomorrow’s redundancy package”.
  3. Measure outcomes not effort, and don’t mistake the two.
  4. The “metrics that matter” aren’t found as an easy-to-use list in ITIL.
  5. Use metrics to predict the future not to relive the past.

 

ITIL® is a (registered) Trade Mark of AXELOS Limited. All rights reserved.
COBIT® is a registered trademark of Information System Audit and Control Association® (ISACA®).

 

 

Recent Posts