Plan, Do, Stop! Why ITSM Implementations Fail

You learn something every week. My big learning moment this week was when I sat in on a panel debate hosted by Michelle Major-Goldsmith at the Service Desk Show at Earls Court. The panel, made up of Paul Wilkinson (Gaming Works), Kevin Holland (UK Public Sector) and Stephen Mann (Forrester) debated the success (or otherwise) of ITIL adoption in IT organisations. It was alarming to say the least.

First the good news: in a recent survey of 491 members of the IT Service Management Forum (itSMF), Forrester found that ITIL beneficially improved service productivity (85%), quality (83%), business reputation (65%), and cost savings (41%). However over 50% of service management implementations fail! I’ve captured some of the discussion and key points to share with you as well as our own experiences working as service management consultants out in the field.

One of the top reasons is that IT professionals often fail to understand that, pivotal to our success, is recognising the needs of our business and being able to articulate how the implementation of service management can improve service delivery – with direct and measurable benefit to the business. To bring this message home Paul Wilkinson challenged to twenty or thirty ITIL Experts in the audience to define “a service” – pretty basic stuff taught on the first day of an ITIL Foundation Course. None could!

A SERVICE is a means of delivering VALUE to customers by facilitating OUTCOMES customers want to achieve without the ownership of specific COSTS & RISKS. *

Around 85% of the people in the room claimed to hold a Foundation certificate in ITIL Service Management. About 20% of the group offered that they held advanced qualifications. Yet many of them indicated that they were not seeing value from their training investment.

I’ve written before about training and education being different facets of learning. It’s the difference between know how and know why. Education is giving out information and communicating to your students. Training is about putting the knowledge into practice and building skills. Sadly this confirmed our fears – very few organisations engage suitably qualified organisations to help show them how it’s done.

Paul provided an interesting anecdote about the CIO who wanted to recruit service management people but (sensibly) refused to do so based on a CV of ITIL qualifications; instead he directed the recruitment consultants to, ‘Send me a CV that describes how the candidate delivered valuable outcomes to his/her customer’. Rather than the usual piles of CV’s, he had just a few to select from.
So who is to blame for this appalling mismatch of aspiration and achievement? In, short – all of us!

  • IT staff – just wanting the certificate without thinking about how to use the knowledge gained to deliver value back at the workplace.
  • The line manager – failing to support the after training experience by providing opportunities to test and develop the knowledge gained in the classroom.
  • The CIO – who didn’t explain how the training would support the organisation’s vision and strategy. ITIL certification becomes a tick box exercise and frankly a waste of the organisation’s s money!
  • The Training Providers – who teach by rote, focusing on the exam and not able to offer real-world experience.
  • The official ITIL Accreditor and the Examination Institutes – for the format of the syllabi and examinations.

ITIL processes alone will not deliver success. It’s all about recognising value. Be clear of the benefit you will gain versus the cost of implementation. Test the value of what you do and how you do it!

Most IT organisations succeed with the most commonly adopted processes (Incident, Problem and Change Management but then it gets much more difficult when they need to talk to their customer. Engaging in Business Relationship or Service Level Management is beyond their skill levels. All too often we are afraid of asking the customer their view on what we do for fear we will hear things we’d rather not know. This is risky! Organisations that do this end up making ‘improvement’s that were neither warranted nor required.

Paul concluded paraphrasing W. Edwards Deming, all too often we: Plan, Do, Stop!


* Quote from ITIL Core Guidance Service Lifecycle books, copyright Cabinet Office 2011

Project Management Made Plain

The new Kingsway Business Park is taking shape in the land that lays beyond the bottom of my garden. The activity of the last three months has been the preparatory work for the new Asda frozen food distribution centre which is absolutely enormous. Janice & I have watched with interest the road-building and the tarmac and pipe-laying that’s been going on – only to realise that all of this was for the fourteen (at the last count) portable buildings to house the site management for the rest of the project.

Despite the travails of Rochdale weather, these guys have it pretty easy. The ancient Egyptians built enormous structures in a relatively short timescale. To complicate matters further for them, the process was continually subject to the changing demands of the Pharaoh; the weather; diseases; and wars.

How did they get millions of stones to the right place and make sure that tens of thousands of people worked as efficiently and effectively as possible? Obviously this didn’t just happen all by itself. They could not have been done it without effective project management.

These days we have well-proven practical methodologies like PRINCE2® to help us. It provides Project Managers with an excellent process for ensuring a project starts sensibly; is controlled throughout; and is delivered successfully. And yet, I am continually surprised by how many people find project management such a difficult concept to comprehend. I suppose I’m one of the lucky ones – I’ve always felt that project management is just structured common sense – then again, that’s how I view ITIL.

So when we decided to develop our own PRINCE2 material, I was really pleased and supportive of the approach that my trainers wanted to adopt – no PowerPoint!
Using practical exercises instead of the ubiquitous PowerPoint presentation, Sysop students work through a series of facilitated and very logical case-studies which enable them to understand PRINCE2® in a much more effective and practical way. By the end of the course they have developed their own reference book crammed with the project templates that they have developed – an invaluable reference guide back in the workplace.

Even Richard Pharro, CEO of APMG was impressed. He said: “It is encouraging to see Accredited Training Organisations making the learning experience of delegates as exciting as possible. Learning in a way which enables students to utilise their practical experience when they get back to the office will help them become more effective project managers. I am confident the Sysop workshops will be very popular.”

More information:

The Mysterious Service Design Package

This week, I went to the itSMF regional meeting held at the Co-op Bank HQ in Manchester. We were privy to two superb presentations from the Co-op team. Ian Macdonald set us thinking about base-lining and benchmarking but, for me, the star of the day was Andy Birds who talked about the Mysterious Service Design package.

Anyone who has been around IT service management for a while will have lamented the lack of involvement of application developers in the overall service design process. For all too long, services are declared “live” even though the operational requirements of maintainability, availability and reliability have not been properly considered. The team at Co-operative Bank has taken this crucial area of service design to heart and embraced the service design package.

Andy was able to demonstrate that by paying due regard to the communication and documentation flow, from service design to everyone else downstream of an implementation, not only was there a considerable dividend in the quality of the implementation but that the total cost of ownership (TCO) was reduced.

Sure, things don’t always go by the book. When other pressures come to bear and incomplete services just have to go live, the Co-op team are not only well able to allocate responsibility but, more importantly, gain acceptance of the risks and consequences at the appropriate level.

There aren’t that many case studies around of successes in service design. This certainly was one that deserves a greater audience.

Stuart Sawle