Something old, something new, something borrowed, something blue

Something old, something new, something borrowed, something blue

I took delivery of the five ITIL v3 books from the itSMF today – the online versions just haven’t been doing it for me, call me old fashioned if you will, but Rob England has the same problem.

I’m currently writing about Unified Event Management as part of a series of articles about integrating Unified Computing Systems into organizations via frameworks like ITIL.  I’m not an ITIL fanboy despite, or probably because of, my long exposure to it (since the early part of this millennium), but ITIL’s independent, industry standard language really helps me and my customers make sense of each other.

You know how ITIL is about best practice?  Well I’m calling those best practices patterns, and providing real implementations of those patterns for Unified Computing: filling the ITIL gap, you might say.

Even Management is in the ITIL v3 Service Operation manual so that’s the first one I had a look at.  Imagine my surprise when, after opening the Introduction I saw a reference to Adaptive Enterprise.  Gadzooks!  My spider sense triggered the alarms and I though “What’s a HP marketecture term doing in a vendor agnostic, industry best practice guide?”.

I looked back a few pages in the Service Operation manual to the Acknowledgements page and there we have the smoking gun: two out of three of the authors are HP employees.  Sigh.

There are many other contributors acknowledged in this book, from many organizations including IBM, Pink Elephant and all the rest, and I’m amazed that none of them picked up on this vendor sales pitch and had it removed.  Where’s IBM’s On Demand?  Or Cisco’s Unified Computing?  Or anyone else’s?  Of course, you can’t put them all in, so you shouldn’t put any in.

Unless, of course, Adaptive Enterprise is a new ITIL term and means something universal no matter what the vendor?  Nope.  Check out this Google query for adaptive enterprise ITIL – no link between them other than HP marketing.  I won’t be using Adaptive Enterprise in my work at Cisco, and I doubt that anyone at IBM will be.  But this is about more than vendor envy.

On the one hand, you might want to tip your hat to HP and say “Well done on getting your pitch into the industry standard books!”.  On the other hand, it might make you think twice about ITIL and maybe, if you are an ITIL Skeptic, confirm your suspicions that ITIL is by the consultants, for the consultants.

Here’s the smoking gun :-)   The first picture shows the offending marketing term, and the second picture shows the two David’s from HP, listed as authors.  Whilst both David’s work for HP, they are also heavily involved with itSMF:  Mr Cannon is on the Board of Directors, itSMF USA, and Mr Wheeldon is a Founder Chairman of itSMF International. I’ve sent a message via LinkedIn to both of them asking for their comments.

Update:  David Cannon got back to me with some great points, and I’ve invited him to add them to this blog – which he’s done (check out the comments – thanks David!).  As always on my blog I’ve added a bit of drama and fun to make an otherwise dry subject a bit more interesting – as David said, the “smoking gun” and photos was a bit “Dealey Plaza”, which means nothing to a Brit :-/  For the record, I don’t doubt both David’s integrity and commitment to their work – I’m a fan, honest!

When did Adaptive Enterprise enter the ITIL lexicon?

When did Adaptive Enterprise enter the ITIL lexicon?

Two out of three authors are called David from HP

Two out of three authors are called David from HP

You might be thinking “Who cares?” but I ask you to stop for a moment and consider ITIL’s greatest purported use: a common language across the IT industry.  Thanks to ITIL, we all kind of know and even sometimes agreee at what’s involved with Incident Management, even if your team is called Help Desk and mine is called 1st Line Support.  If the ITIL lexicon becomes infected with vendor jargon then it loses one of it’s major positives.

If you don’t believe in ITIL, then I guess you can sleep easy: but for those of us who rely on ITIL as a independent, industry standard communication tool so we can understand the large, complex enterprises that we work with every day, it might diminish ITIL’s credibility as that important independant tool and make life that bit harder.

I wouldn’t want to put Cisco terminology into ITIL: it’s a separate, value-added exercise to use independent ITIL as a tool to help my customers succeed with Unified Computing.  That’s why I’m working on a series of articles that add vendor specific (Cisco, EMC, VMware, and others) patterns and implementations to ITIL.  I think that’s the best way and we should, if possible, keep ITIL clean and free from vendor-specific phrases and keep the pool we swim in as clean as possible.

Related posts:

  1. Is the ITIL make-over like putting lipstick on a pig?
  2. Is ITIL ‘Gerin Oil’ for IT?
  3. Does your Desktop Service Strategy look a bit like this?
  4. Making ITIL real: Change Management for Technology Adoption
  5. ITIL is about Technology Adoption