Hiding with embarrassment

It’s almost like an evangelical event: the ITIL ministers, preachers and followers converge on the unholiest of places, Las Vegas, for their annual Pink conference.  There should be much wailing and nashing of teeth because of the failure of ITIL, but most civilizations can’t see their downfall coming and ITIL is no different.

In my fifteen years of working in IT, across banking, managed services, data center virtualization and now data center unification, I’ve met ITIL, flirted with it, fell in love, realised it wasn’t the girl I thought it was, and since then seen many others go through the same process.

ITIL just doesn’t work.  An ITIL practitioner (believer) might even agree with you, but won’t blame ITIL and instead will blame the people “doing it wrong” or the organization “is unable to change”.

The crazy thing is that many ITIL people, probably the majority, have their heart in the right place, like most believers.  It doesn’t matter that their actions are either useless or cause harm, as long as they are trying to do the right thing.  It’s not their fault if it doesn’t work or goes wrong.  It’s the unbeliever, the incorrect implementor or the inert, resistant organization.

So why doesn’t ITIL work?  Here’s just a handful of real life anecdotes from my own real life, but with a survey I bet I could get you a hundred times these in 24 hours.

  • How many CMDBs have you got – do I need to say any more?
  • I need an interpreter – lock an IT Manager in a room with coffee, biscuits and the Service Strategy book – when he’s done, ask him to explain it.
  • There’s no Technology in ITIL – Rob England, The IT Skeptic, is the biggest offender here and a self-professed technophobe.  Yet he’s preaching to IT staff how to run themselves?!

I could go on and on about the lack of prescriptive advice, such as how useless Capacity Management is in ITIL, or even how ITIL is more 1960s that 2010.  I work on a number of cloud solutions and mostly on the operations model around them: I would never, ever, refer to ITIL.  Ever.  It’s useless.

Just one more note from the ITIL apologists: “But ITIL is a language for IT to communicate”.  Behave!  That’s the most patronising thing I’ve ever heard.

The most important and critical failure of ITIL in my view is that it just doesn’t balance the books.  For the massive investment, you just don’t get the return and often end up losing out.  Here’s some costs to consider:

  • Tools – how much do the BMC/Service-now/etc tools cost?  $millions?
  • Customization of Tools – who uses the tools out of the box?  How many developers do you need?  Five?
  • Administrators of Tools – another five?
  • Dedicated process teams – fiver per Change, plus a manager, plus …
  • Time taken away from IT staff to work on ITIL - let’s say a day a week per member of staff…
  • ITIL consultants? $3k a day?
  • ITIL training? $3k per person per course?

Could that total be about $3-5 million?  Depends on the size of the org, I guess, and how good the ITIL salesman is.

And what value in return?  You’ll hear talk of “less incidents”, and “improved change” but when you try to talk KPIs you will find the ITIL guys wanting to sell you more consulting and training because there’s no way YOU, poor IT guy, could ever work that out for yourself.

What would happen if the IT org didn’t even look at ITIL and instead went it’s own way on IT Service Improvement?  You don’t need ITIL to start improving IT!  Don’t believe the hype!

I really wish ITIL was better.  ITIL v3 was an improvement on v2 only because it glued all of the high-level stuff together in a nice order, but there’s still no depth.  And it was written by vendors like HP and Accenture!  There’s still no T in ITIL.  If ITIL v4 became more detailed, relevant, prescriptive, then I might start attending a few sermons.

Related posts:

  1. ITIL is about Technology Adoption
  2. Is the ITIL make-over like putting lipstick on a pig?
  3. ITIL Certification is an oxymoron
  4. The ViewYonder ITIL Tragic Quadrant
  5. Making ITIL real: Change Management for Technology Adoption