Next Generation Service Desk: Are you prepared?

Nev Wilshire keynoting at SDI
Nev Wilshire keynoting at SDI

Last week The ITSM Review was the Social Partner at the annual Service Desk Institute (SDI) conference. The tagline was “be inspired, take action, and be better” and I certainly get the impression that delegates left the conference with a big to-do list for improvement.

Despite the strong emphasis on the “future of technology” in the agenda, for me the primary message and theme running throughout the conference was the need for IT to stay relevant to the business. To put it bluntly, if IT doesn’t understand and share common goals with the business, then IT has no future.

From the sessions, to discussions in the bar, even to chatter in the lift (that was me earwigging on two delegates’ conversation), “the business” was a huge talking point. And correctly so in my opinion. And for once it was nice to step away from the process-driven IT service management (ITSM) conversations to look at the bigger picture.

With this in mind, rather than give you a running commentary of the event, I’ve chosen to focus on the advice given in two presentations which relate to this topic.

Kill Your IT Service Desk – Chris Matchett, Gartner

The primary difference between this presentation and most of the others is that Chris didn’t just tell us what the problems are and why we need to fix them, he actually gave us insight into HOW to fix them.

Chris discussed how most service desks are currently not meeting business expectations. This shouldn’t be news to most of you, as I think we all know that IT is struggling to cope with changes in customer behaviours and technologies, with an inability to meet consumer-driven employee expectations of service and support.  He further discussed how we’ve moved from “how do we stop Shadow IT”, to “how do we control Shadow IT” to “how do we harness Shadow IT?” Chris then outlined an improvement model to enable us to harness it and to get the service desk working in conjunction with the rest of the business.

Chris gave some excellent advice on how we need to move to a four-tiered support approach and how to develop an improvement roadmap for this.

In addition, Chris also highlighted how service desk analysts need to make the transition to become “business engagement analysts”.  A business engagement analyst has knowledge of business processes and is a leader with the ability to build partnerships and influence others.  He or she invests in softer skills, invests in design fundamentals, shadows the business, and engages the community.

Some extra pieces of advice from Chris:

  • Remember you need to control and embrace change or risk getting left behind it
  • Just because you’re performing well against industry standards this does not automatically equate to value to the business. Talk to your customers
  • Remember that one metric never tells the whole story. Place less emphasis on First Call Resolution (FCR) rates for example as the minute you fix the easy stuff like automating password reset your FCR will go down as the average incident gets more difficult. The automation is a good thing, but your FCR metric will make it look the opposite
  • Overwhelmed by password requests? Look to implement self service and give control back to your users
  • Remember that any new initiative needs management buy-in. Any change needs to be led from the top down.

Oh and then there was my favourite quote from Chris: “Is a password reset a request or an incident? Who cares, it’s just a pain in the arse”.

Service Catalog – Extending the Role Of The Service Desk – Olaf Van Der Vossen, CERN

Those of you who read The ITSM Review on a regular basis will know that Martin Thompson has written about CERN’s approach to service management before. So why am I repeating what he’s likely already said? That’s easy, because for me it was one of the stand-out presentations of the conference. Everybody is forever talking about how the IT will be dropped from ITSM and how IT needs to be better aligned with the business, only rather than just talking about it, CERN has actually done it.

CERN has implemented ITSM best practices across both IT and the rest of the business. This means that the service desk doesn’t just operate within IT but also manages requests and incidents from HR, finance, etc. They believe that you should make life simple for your customers by using ONE point of contact, ONE behavior, ONE tool, and ONE service description.

In this session, Olaf specifically looked at how a comprehensive Business Service Catalog is essential for success when extending service management beyond IT. You need to:

  • Know what you are supposed to be doing
  • Understand how these services are provided (and by whom)
  • Drive automation and smooth assignment and escalation

Olaf also spoke about how extending beyond IT can make things more complex. To address this you should:

  • Invest in training for your service desk staff
  • Provide extra coaching for non-IT support staff
  • Use a Service Portal to hide the complexity of your Business Service Catalog

I also want to mention a great question from a member of the audience:

“In such a large organization, how do you provide your service desk staff with the knowledge to answer every single request and incident that comes in?”

The answer was simple: You train dedicated teams of second and third line support in specific business areas. This then means that first line support teams can delegate the more difficult queries as required. You also need service desk analysts who can communicate well, as extra effort is needed here when dealing with enquiries on subjects you don’t understand (potentially from customers in other global offices with whom you’ve never had any interaction before).

Olaf also jokingly advised that teams should prepare for really random questions like  “I’m coming to Geneva tomorrow, what’s the weather going to be like?”

In addition to the content of the presentation, I also want to mention Olaf himself, primarily because he made me smile (much like Olaf in Frozen really!). He was very personable, made the audience laugh, and was very easy to relate to. I would have quite happily stayed for a further 45 minutes to listen to him present more on what CERN has achieved.

In Summary

The atmosphere was great, and the awards dinner was definitely one of the best I’ve attended recently (likely down to the brilliant finalist videos – here is my favourite). Congratulations again to all of this year’s winners.

Some of the keynotes I felt lacked the “wow” factor, but I really am the hardest person to please when it comes to keynotes (my favourite is still John O’Leary) as I literally want my socks to be blown off every time I see one (which probably is wrong on my part, nobody else’s).

That said I did very much enjoy listening to Neville Wilshire, even though he made me sing and dance to The Killers at 9.30am. His advice regarding looking after your employees and providing excellent customer service was spot on, plus he made me giggle when he told us we all needed BIG BALLS (yes I am a giggling 7 year old inside).

Mr Happy Man Alexander Kjerulf was not totally my cup of tea (sorry but he said it himself – it’s because I’m British!), but I thank him for providing us with entertainment long after he’d left (I don’t think I’ve ever high fived so many people or heard as many “you’re awesome” statements in my life before).

Overall it was a good conference, with what I think has great potential to be even better next year. For me the main thing that I felt was missing from some of the sessions was the “how”, but honestly this isn’t specific to SDI as I generally feel this way about all ITSM conferences. Sometimes I worry that I’m becoming cynical because I attend so many of these events, but upon chatting to delegates I definitely got the impression that focusing on the HOW would make the event even more beneficial to them.

Would I recommend that you attend this conference? Yes most definitely, but don’t just take it from this cynical, giggling 7-year old. Just look at what the delegates had to say:

Service Management at the speed of light

ServiceNow recently held a three-city European forum. The event was a compact version of the larger ‘Knowledge’ event held in the US and a chance for customers to share experiences and hear from ServiceNow bigwigs.

I found the most fascinating session of the day was from Reinoud Martens, Service Manager at CERN, the home of particle accelerators and clever physicists searching for the origins of the universe.

“At CERN, the European Organization for Nuclear Research, physicists and engineers are probing the fundamental structure of the universe. They use the world’s largest and most complex scientific instruments to study the basic constituents of matter – the fundamental particles. The particles are made to collide together at close to the speed of light. The process gives the physicists clues about how the particles interact, and provides insights into the fundamental laws of nature.” About CERN

Reinoud’s session was entitled ‘ITSM also works outside its comfort zone’ and explored how CERN implemented IT Service Management best practice across IT and many other business functions. Reinoud kindly answered some follow up questions via email below.

Service Management beyond IT

Reinoud is Service Manager for a group called ‘General Services’ at CERN.

General Services serves IT services but also a myriad of other business services at CERN such as Civil Engineering, Facility Management, Medical and Fire Protection.

A user at CERN can log a password reset or seek help with a faulty laptop – but they can also rent a car, alert facilities to a blocked drain, book a hotel room, have an old filing cabinet towed away or log an expense claim – all from the same Service Management destination; the CERN Service Portal. In total CERN supports 282 active services across 494 operational functions.

Service Management Singularity

The goal at CERN, as Reinoud eloquently described is to:

 1. Make life simple for users and supporters by providing:

  • ONE point of contact (One #, One URL, ONE place)
  • ONE behaviour; Unified processes for all services
  • ONE tool shared by all service providers (sharing information and knowledge)
  • ONE service description in a business service catalogue

2. Improve efficiency and effectiveness

  • Alignment with good practice (ITILV3 and ISO20K)
  • High level of automation
  • Framework for continuous improvement

And do this for ALL SERVICES (not just IT).

Interview with Reinoud

Q. What drove the initiative for one Service Portal across all these disciplines? Could you describe what existed before?

Aerial View of the CERN taken in 2008
Aerial View of the CERN taken in 2008

Before there were many numbers to call or people to know to get your needs fulfilled or to report a problem. There was an IT helpdesk, and a facilities management number to call, but their respective scopes were not 100% clear and there was a lot not covered by either of these numbers.

The most common way to find the right help was a Google search on the domain that would return a lot of obsolete or wrong information (Every service published it’s own pages which were not removed after reorganizations or updated after changes).

Many people published their own service catalogues with numbers to call. So there was a lot of confusion and chaos, although there might have been some islands of excellence hidden here and there.

IT used a ticketing system with which they had difficulty upgrading; this system was also partly used outside IT for example Application Support. Even within IT some groups had their own systems. Outside IT there was no real ticketing system in place.

Some requests that have to follow strict authorization rules were and are supported in a custom workflow system developed at CERN where people fill out request forms by themselves (e.g. for taking leave, or for ordering equipment).

The initiative was driven by:

  1. The realization that CERN needed to become more customer/user focused, also as we moved from a project phase (building LHC) to an operational phase (running LHC).
  2. The need to support an exploding user population with less or at best constant resource levels.

Q. Did you face any political resistance when IT joined General Services (I’m thinking that certain departments might not want to relinquish control)?

An event showing characteristics expected from the decay of the SM Higgs boson to a pair of photons (dashed yellow lines and green towers).
“Approximately 600 million times per second, particles collide within the Large Hadron Collider(LHC). Each collision generates particles that often decay in complex ways into even more particles. Electronic circuits record the passage of each particle through a detector as a series of electronic signals, and send the data to the CERN Data Centre (DC) for digital reconstruction. The digitized summary is recorded as a “collision event”. Physicists must sift through the 15 petabytes or so of data produced annually to determine if the collisions have thrown up any interesting physics.” Computing at CERN

It happened the other way around, as the ‘chaos’ was probably bigger outside the IT area. The initiative started in general services during first half of 2009. In 2010 IT joined forces to propose a potentially CERN wide (for infrastructure services) solution. HR and Finance were to join later.

Obviously we encountered a lot of resistance, scepticism and ‘other attitudes’. Many predicted this project would fail, so they adopted a very passive attitude, but after one year of ‘production’ these people also realized the benefits invested effort to make things work. It’s not something you can do overnight.

Q. From your presentation it was very clear that you have taken best practices from ITSM (ITIL and ISO20000) and applied them to other business disciplines. Can you cite any examples of where IT can learn from these other disciplines? Do such best practices exist in other areas?

There are no examples where the standard needs to be ‘extended’ for IT based on our experience for non IT. There are ‘small implementation detail examples’ where IT could ‘profit’ from the ‘culture’ in other areas. For example business services that are person facing will like to hide the fact that there is an automated process and tickets behind requests and incidents as much as possible; so they wish to make the system ‘more human’ with special notifications, or service dependent ‘signatures’.

We have been looking at other standards but really found no alternative … including external consultants. There may be standards for libraries for instance; but we can’t support a standard per service (with over 280 services), and in the end these alternative standards for very specific domains contain the same ‘common sense’ that can be found in ITIL and ISO20k.

Q. Can you elaborate on the section of your presentation regarding ‘Cultural Change’? In particular I recall how you used a combination of Knowledge Management (this is how things work around here) and Service Catalogue (and this is how things get done). What led to this approach?

The culture change has to do with technicians that are focused on solving technical problems (say fix a water tap) but really don’t caring about the ‘caller’ at all. They will close a ticket not when the work is done, but when they want to bill their work; this can be much later. As a result the caller gets out-dated feedback and thinks the system does not work.

It gets worse if they need a spare part; they will not inform the caller or update a ticket; they will maybe note in a piece of paper they have to get a spare part and the user thinks nothing is happening. It’s this customer/user awareness and what it means in the day-to-day life of workmen that are ‘supporters’ for the infrastructure services that is the problem. The sharing of knowledge between supporters and with users (FAQ’s) is something that came ‘automatically’. We had many local FAQ’s and wiki’s but now we provide a global infrastructure.

Service Catalogue is what is available to the users, not how things get done. The focus is on the what (scope, when available quality) then obviously there is a link to support teams. So it orchestrates how things get done as an additional benefit.

Note: Sample of CERN Service Portal users:

  • Engineers
  • Physicists
  • Technicians
  • Administrators
  • Computer scientists
  • Craftspeople
  • Mechanics

But also:

  • Computer illiterate support staff
  • Candidates for job opportunities from around the world
  • Suppliers

Q. What does ‘Coaching’ look like for non-IT supporters? I remember you mentioned taking supporters through the equivalent of ITIL foundation for business services, but not using ITIL foundation – can you elaborate on this point?

We organized awareness training for non-IT people, a sort of shortened ITIL foundation course not referring to IT situations. E.g. configuration management for a medical service is understanding who your ‘patients’ are, what their ‘status’ is in terms of health parameters etc. If a medical service has not a good register of this they are bad in configuration management.

Explaining the ITIL concepts, naming conventions, processes and ideas but staying away from IT examples… this is not always easy in areas as release and deployment management for a cleaning service or a materials management service…so you must be ‘creative’ and maybe skip some very specific areas in certain cases. Most areas however are relevant to most services (if you take a step back and ‘reinterpret’ the concepts).

This is not enough, you also need to explain again and again what the underlying ideas of the processes are, and how they should use the system (e.g. impact and urgency priority; not closing a ticket that is wrongly assigned, but assign it to the right function, or return to service desk, etc..). This is more laborious for non-IT people than for IT ‘supporters’.

Q. Why ServiceNow?

We looked at the market second half of 2010 once we knew what we wanted to deploy (Single point of contact, unified processes and single web based tool shared by all with in the heart this business service catalogue driving the automation and a service portal); we started with a long list of around 40 tools, quickly shortened down to 6 which we evaluated in more detail based on a long questionnaire; ended up with two for which we did a POC at CERN and some reference visits.

We took into account lots of criteria covering: functionality, configurability/flexibility, architecture, interface, future evolution, etc. The fact that ServiceNow was a SaaS solution played a role (this was an ‘experiment’ for CERN’s IT department and they were ready to test it; it certainly helped dramatically reduce the time between the choice and being operational).

Obviously total cost of ownership also played a key role. Anyway things may have evolved in the last 3 years, so although we don’t regret this choice a second, the outcome could be different today. I have no idea of what is going on in this area on the market today (I am no IT guy anymore and have other things on my mind lately).

Q. Finally, your advice to organizations looking to embark on a similar journey?

Top Three Takeaways from Reinoud’s presentation:

1. ITSM is RELEVANT beyond IT and it WORKS

2. Essential for success are:

  • A comprehensive Business Service Catalogue
  • To know what you are supposed to be doing
  • To understand how these services are provided (by whom)
  • To drive automation and smooth assignment & escalation
  • A Service Portal to hide the complexity of all of this
  • A good tool  (that lets you be ‘agile’)
  • Extra coaching for non IT supporters

3. You can do this in your own organization

CERN Service Portal

Images of the CERN ‘Service Portal’ below:

Service Portal Features:

  • User access to all services
  • Search function
  • Browse the catalogue
  • Report issues
  • Follow-up issues
  • Access knowledge base
Click to enlarge
Click to enlarge
Click to enlarge
Click to enlarge

About CERN in 3 Minutes

Accelerator Event Image Credit, Aerial View Image Credit