Thanks to Best Practice frameworks, technological progress and improved knowledge of the potentials of IT, a lot can be done nowadays at Service Desk level to reduce cost, speed up operations and improve service quality – all things that can contribute to achieving business success. However, Service Management initiatives such as role changes and redistribution, adoption of new tools and technologies and the implementation of new processes to follow may not always be welcome by who in the end has to accept and embrace all these changes – Service Desk staff. Do you take into consideration what they think about Cloud Computing, Best Practice and self-service software before you sign off your projects?
Although it may seem unnecessary to seek IT staff involvement, this is actually very important, as the new tools and techniques adopted may not work at all without staff collaboration. Analysts working at your Service Desk might refuse to endorse the project as they may see it as impractical or unfit for your specific environment or just a needless complication when things are fine the way they are. It is essential, then, to think about how the organisation can get IT staff to collaborate and, perhaps, if it should listen to what they have to say before embarking on any projects and taking decisions they might later regret.
‘Change’ seen as a threat
A move from Lotus Notes to the fully ITIL-aligned Remedy or embracing the new technology potential of server virtualisation could seem sensible from a business and Service Desk manager’s point of view. However, any change can be seen as a potential threat by analysts – not only to their day-to-day work routine which they are more than happy with as it is, but often to their position. They fear they might not have the skills to use new technology or that this may easily do their job at no hourly cost (i.e. self-service software) therefore making their position redundant.
And virtualisation is perceived as the biggest threat: as it enables remote support, potentially centralised in a Service Desk located in another city or country, many in-house positions may be in danger. Although not unfounded, this fear shouldn’t become pure terror: it is still early days for complete virtualisation, so there is still place for an IT department within the office, plus some companies will want to keep their ‘virtual team’ internal anyway for extra security and control. This can also been seen as an opportunity. A need for analysts specialised in VMware, Hyper-V, Citrix and the like will arise, giving engineers a chance to acquire and practice new skills and the exciting possibility of working at a centralised, often global Service Desk.
Furthermore, as can be found in many other departments and roles, seniority has an impact on analysts’ willingness to accept change, creating a harder challenge for management. Engineers that have been working there for a long time and have gotten used to their old methods normally find it more difficult to accept innovation, especially when this is proposed by a new manager or an external consultant. More junior professionals or those who have only recently joined the company, instead, tend to be more willing to collaborate and curious to see new technologies and innovative processes in action. In fact, they might think working with new tools is a great chance to expand and update their skills, which is hopefully what the Service Desk manager will try to communicate even to the more institutionalised analysts.
This could also be a cultural issue: junior members will have grown up with a larger use of complex technology from an early age – the so-called ‘digital natives’ – whereas older personnel will have seen the origin of computing, and might find it more comforting to stick to the old ways of working.
Don’t impose – involve
If change is difficult to accept for many people, it can be even more unwelcome when it is forced into the system without previous communication, a good amount of explanation regarding its reasons, benefits and consequences on people’s roles, and perhaps a chance to express your own views and raise questions. In order to reduce resistance to change, the first step is to discuss the possible modifications with technical staff and people that will ultimately be involved in its use before taking a decision, giving engineers a chance to think it over and raise any concerns or doubts.
This can work to the business’ advantage as well. Current Service Desk employees can actually be a good source of information that you can learn from, as they might have suggestions and thoughts based on their practical experience at your company and in your specific environment. What works for one company, in fact, might not work for another, but it may be difficult to see some practicalities from a non-executive position. Instead engineers, being in direct contact with the IT system, might have reasons to believe the project you wish to carry out may be impractical or impossible to implement in your specific environment.
Listening to their doubts and fears, as well, is an important part of the process. Moreover, just by asking their opinion and interacting with them, you will make them feel that you value their opinion, that they are being considered and are therefore important.
Getting the best out of analysts
Even if you manage to convince IT analysts that the new changes are sensible and advantageous or have come to an agreement on what to implement and what not, adopting the new tools and following new procedures in a robotic manner is not enough to deliver a good service. Motivation is key to make any part of the business, the IT Service Desk included, work at their best and without it not much can be achieved. Invest in your employees and they’ll invest in you.
Reward schemes where hitting targets can lead to some type of benefit, for instance vouchers or prizes, are a good idea to keep the atmosphere competitive. However, if you do not have a budget that justifies this sort of expenditure, a monthly recognition for the best performing engineer can be sufficient. An ‘engineer of the month’ competition can increase staff’s motivation to try and reach the targets set not just for the prize, but also for fun.
You must be careful, however, when deciding which metrics to use to evaluate a good worker: number of calls may not coincide with incident resolution and call length might not be a symbol of quality, so you would have to make a balanced assessment taking various criteria into consideration before you award an engineer over another.
Adopting a holistic view
It is important to stop seeing IT as a service to the business, and adopt a more modern view where it is part of the business. If managed correctly, in fact, the IT Service Desk can be a great ally that will create strategic advantage and help companies improve their business and reach further success. This is why organisations should invest in IT staff and try to create a positive can-do attitude among them.
Managers can encourage skills improvement through workshops, training or further qualifications (for instance, ITIL V3) and turn challenges brought on by new technologies into opportunities. The introduction of new devices – iPad, iPhone etc – within the system, which might seem like an annoyance to some, should be taken as a great chance to be exposed to the latest technology and although managers shouldn’t expect all analysts to be able to support all types of devices, they may chose some engineers to specialise in supporting the latest ones in the market.
There is no need to train everyone- a good Service Desk or Delivery manager should be able to identify those engineers that are best suited for specialising in these technologies or teaching others, and have them trained accordingly.
It is not always IT’s fault
Often it is not analysts, but non-IT managers and C-executives that may be opposed to change – for instance, when the implementation of new Best Practice processes could eliminate prioritisation of calls based on ‘rank’ rather than the incident’s characteristics. Although it might be ok to adopt some level of flexibility, it is also important to ensure the possible ‘executive exceptions’ don’t have a negative effect on the Service Desk’s efficiency targets, and to do this the whole organisation, and not just IT, needs some sort of education to Best Practice.
Another difficult change could be the introduction of new software. Moving from Windows XP to Windows 7 or introducing a self-service tool to deal with simple and repetitive incidents such as password reset could throw non-technical personnel into a crisis. Again, preparation and education are essential for them to accept change. They need to understand why the change is being made, what are the benefits and how it will affect – possibly improve – their work. Guiding them in the discovery of the new tools, as well, will increase their acceptance as not being able to use the new application properly will not make the company achieve the benefits they were aiming at with its introduction.
With some good Change Management processes in place and the right communications means, it should be made clear across the whole organisation what changes will be made at Service Desk and user level and how they will affect them, what exceptions to the standard processes can and cannot be accepted and the consequences of not using a tool, not doing it correctly or making too many exceptions, not just on the Service Desk, but on the rest of the business as well. Only by communicating changes, explaining results and benefits and setting rules and exceptions it is possible for a IT Service Desk to function properly and meet efficiency targets while still keeping senior management happy, allowing the business to work fluently.
Sam Evanson, Operations Delivery Manager
This article was written for the June edition of At Your Service