Quality over Quantity?

I returned from holidays last week and boldly started 2014 with a ‘polarising’ tweet:

OK, I'm back from holidays and have stepped into 2014.What's new? Has @AXELOS_GBP messed up #ITIL yet? #ITSM

Admittedly quite a blunt tweet, but I was hoping for some responses and got exactly what I bargained for with specifically two interesting ‘discussions’ following (using the term lightly as it was all in 140 character twitter statements, thus lacking some ‘finesse’).

One was rather obviously about AXELOS’ performance to date. More on that later, but first the other discussions which diverted into whether (ITIL) training should be of the best quality or the most accessible. John Custy (@ITSMNinja) mentioned that if ITIL exams were more expenses (based on AXELOS’ price increase) ‘maybe fewer, but more right people certified...’

This got me thinking, as I have always been a great advocate of training quality and a skeptic of the current ITIL certification scheme (see my blog from March 2013 on Action Based Learning).

However at the same time I can see the importance of training be accessible to a large audience, particular at the basic/entry/foundation level. Hence the title of this blog: Quality over Quantity/Accessibility.

The current ITIL Foundation course (or rather ‘Foundation Certificate in IT Service Management’) has become a volume-seller with around 20,000 exam each month. Plenty of organisation are sending all their IT staff to this course and the prevalence of the ITIL Foundation certificate has certainly helped to make ITIL the ‘de facto’ standard in IT Service Management.

Compare this for instance with COBIT. COBIT is seen as an equivalent if not better alternative to ITIL (with more prescriptive guidance, standard RACIs, a direct link to governance, risk, project management …). However, whilst there are COBIT qualifications available, it comprises mainly of Foundation, with then ‘specialised’ implementation or assessor courses which are not focused on general staff. And it is much harder to obtain with fewer organisation (in fewer locations) offering this course less frequently (although there is always the on-line option).

And it is a similar story with MOF (Foundation only), TOGAF (Foundation or Certified qualifications), LEAN or AGILE. Whilst there certainly is certification in those methodologies, it is far less known, far harder to obtain (not because of difficulty but because of availability) and far less recognised.

As mentioned, I believe this is part of the success of ITIL and in order to maintain this it is important that AXELOS not only maintains the quality of the ITIL certifications, but maintains or even improves the availability/accessibility/quantity. Most certainly at entry/Foundation level but also for Intermediates, which have a far smaller uptake. The more people are trained and certified in ITIL, the more people will want to use it (and the more people use it, the more we can work towards quality improvement of the theory).

That doesn’t mean that quality is not important. And whilst I hope that future updates to ITIL will improve the quality of the theory, and with it the quality of the certification (for instance a lower, operation-only Foundation, more practical and less factoid based, periodic exam refreshers to maintain higher levels, …). We need to look at the situation at hand: The Foundation is course is so prevalent that a lucrative and significant grey circuit has developed offering courses that do not (always) meet the existing quality standards. This (in my opinion) is a real threat to both AXELOS, the ATOs and the market.

For instance I believe we can all agree that the existing ITIL Foundation syllabus only just fits in a three day format. There is a lot (too much!) theory to explain and the danger is of the course becoming death-by-powerpoint, theory-overload with not enough time to discuss practical application of the principles. So, I was not overly impressed when I was approached by a (non-accredited) training organisation with the question whether I could deliver the Foundations in two (albeit extended) days … over a weekend … including the exam. I declined and sincerely question the quality and outcomes of a course like that.

Because as important as certification is, there is more to training than that. However we need to look beyond the IP-owner and training organisations and realise that it is the responsibility of the organisation/manager who sends staff to training to obtain ‘value’ from it (as well as the staff attending training). I advocate an immediate follow-up on training: at Foundation level an attendee could do a review of existing procedures, tools and documentation (and discuss any questions or suggestions with the process manager/owner). At Intermediate level this can become a more formal assessment and CSI/SIP and at Expert level the scope increases (all lifecycles) and would include tactical or even strategic customer relationships.

Anyway, bringing this rant to a close: the quality of training is paramount and any customer/participant of training is responsible for choosing the best training and getting the most out of it. The better training organisations (and fortunately there are plenty of them) will maintain quality and inject this into their offering.

The role of the ‘examiner’, in our case AXELOS, is to design a qualification scheme that is acceptable by the market, but also to maintain a delivery model that will make it available to that market.

Whilst this includes maintaining quality (EIs, ATOs, …) there is more to it. And a first action of increases the price of exams (and thus their revenue) does not necessarily give out the right signal. But that is a different discussion (on AXELOS’ performance, which I promised Andrea Kis (@AndieKis) to have in 170 days).

Best wishes for 2014!

the ITIL Zealot

January 2014

The Alternative to ITIL …

If I follow the social media ITIL seems to be over the hype-curve, with many people predicting its impending demise, often due to various reasons:

• The joint venture with Capita (AXELOS) will make it too commercial
• COBIT (or …) is better
• DevOps will replace it
• Cloud computing has made it obsolete
• BYOD has made it obsolete

In our MALC course we actually debate the relevance of ITIL, whereby I as the facilitator take the opposing view, often using the very reasons I’ve highlighted above. It is refreshing to go over to the ‘dark side’ and attack the ITIL framework for all its weaknesses (or heralding the benefits of those mentioned above). At one stage we nearly decided to quit the course and start doing COBIT Foundations instead!

But it also makes me realise all the good things about ITIL and how to actually, practically apply it. I will address the ‘negative’ reasons in reverse order, but first I think it is important that at the heart of all this we are talking about IT service management. Service management is all about delivering (IT as) a service to the customer: a fixed-price, black-box, repeatable, guaranteed, managed & measured value.

This immediately invalidates any reasoning that a new kind of technology (for instance Cloud, BYO) will replace ITIL. ITIL\service management is not about technology, but which processes (\activities) to follow to make sure the technology delivers the benefits (=value) they’re supposed to. So, whilst Cloud and BYOD may make it easier to manage the technology, it is still required to define business value, guarantee the design, transition this, operate it and measure to validate or improve.

Service management is also a ‘best practice’, of which my favourite definition is ‘common sense written down’. And common sense doesn’t really change, so any ‘movement’ or development (like DevOps, return-to-core, rightsize, … even Agile or Lean) can at best only marginally change our opinion of common sense, but not completely invalidate it. Thus they won’t replace ITIL, but provide a different perspective on the guidance it provides.

ITIL is nothing more than the best-known proponent of the IT service management best practice. It has been around for a long time (25 years+), is recognised globally and arguably is the most accepted of the methodologies (certainly in terms of people certified, tools sold and ‘implementation’ performed).

This does not mean ITIL is perfect (despite the nom-de-plum I’ve chosen, even I don’t believe that). I fully recognise the weaker points of ITIL: its generalisms, inconsistencies, less-than-complete or defined strategy processes, its lack of dealing with the real-world (although complimentary publications like the ABC of ICT, Planning to Implement Service Management etc., do a good job of that).

As a consultant (and trainer) it’s these imperfections that make ITIL such as rich source of work: it has to be understood and adapted before it will succeed!

But ITIL has a few things going for it that will make it hard to ‘usurp’ as the leading service management methodology:

· Its ‘completeness’
· Its ‘installed base’

ITIL (since v3) now covers a lifecycle, which means that it just about covers everything you want\need in an IT organisation. Sure, there are some glaring omission (organisation & risk management, or a better defined governance framework) but by-and-large everything is covered.

Many of the other framework focus on one particular element (PRINCE2 for project management, Agile for development, Lean Sigma for process improvement, ISO2700x for security management) which at best makes them complimentary to ITIL, not a replacement.

There are but a few other ‘complete’ frameworks out there. MOF (the Microsoft Operations Framework) is not vendor-neutral and Microsoft hardly has the right audience (too many techo’s, not enough business managers). Plus it is by-and-large based on ITIL anyway. ISO\IEC 20000 is also based on ITIL and its prescriptive nature makes it less friendly to adopt & adept (though together with the additional guidance that is being released it certainly provide a good source of content, perspective and ideas).

This leaves us with COBIT (OK, potentially TOGAF or USMBOK but this is not meant to be an exhaustive comparison). Without going in too much detail, I’d consider COBIT the biggest ‘competitor’ to ITIL. In many perspectives COBIT is better than ITIL (more consistent, contains better governance and risk, provides a quick start, has ‘default’ RACIs, …). In fact if I were to start with a greenfield organisation I might even consider using COBIT instead of ITIL … but, be honest, how often do we come across this.

And so, based on the installed base of ITIL-trained people in the market (including consultants), the number of ITIL-based tools deployed (and/or available) it is very hard to ignore ITIL as the premier service management methodology. Again, this does not mean ITIL is perfect and many of the other frameworks referred to in this blog can be used in conjunction with ITIL, but they’ll not replace it.

Thus the best alternative for ITIL is … an updated ITIL. Which bring us to our last argument: the new joint venture AXELOS who now owns ITIL. A great opportunity lies before them to invest in ITIL (and the other best practices in the portfolio) and bring an update to the market that includes lessons learned in the market, benefits from other methodologies but above all in a consistent package with supporting products (quick guides, implementation guidance, …).

Currently they’re making all the right noises, so I will remain cautiously optimistic that AXELOS will improve ITIL. However, there is a very real risk that AXELOS could instead be the death knell for ITIL too: if they overemphasise the commercial side or focus too much on the UK\home market they will restrict the use and global involvement of the community in the on-going development of these best practices.

In that case I might switch my allegiance to COBIT or USMBOK, but for now I’ll remain the ITIL Zealot.

the ITIL Zealot
July 2013

The Power of Service

In preparation for my itSMF-A LEADit presentation in Canberra this year (‘Around ITIL in 30 analogies’), I was having a good look at the various analogies I use during my training and other ITSM related activities. I love the use of analogies as it is an easy way to explain complex, abstract concepts such as service management.

This was confirmed when last week I was delivering an ITIL Foundations course, using many of those analogies (sorry, you’ll have to come to the presentation to hear them all) and once more seeing their effect. In particular when explaining the concepts of service management and a service I spent a lot of time emphasising that this is not so much about ITIL, but more ‘zen’, a state of mind whereby the whole organisation is focused on delivering value to the customer, in a fixed-price, black-box, guaranteed, repeatable and managed way.

ITIL is merely a way of achieving this (and then only the Process-part of the 4 Ps). In the course we then move into the various processes and their intricacies. It is not until I reach the Service Desk function (in our course, on the last day, after all the lifecycles & processes) that I truly get to focus on the delivery of service again.

This of course as the Service Desk is the Single Point of Contact for the User and as such the visible part of the IT Service organisation. I have once before sung the praises of the Service Desk and how important it is to get it right [HERE]. But I extend this by explaining how important service (perception) is, far more important than (product) quality.

Take for instance a mobile phone (an easy to understand analogy, as most of us will have one). If you buy a mobile phone from shop X and it never fails, you would be a satisfied customer. And when it comes time to replace the phone, you may go back to shop X, but perhaps shop Y has a better offer at the time. The perfectly delivered product (meeting service targets/expectations) has not generated a particular relation\commitment with the provider.

On the other hand, if you buy a phone and it breaks, you’ll take it back to the shop. If this shop is hard to reached (closed, not answering phones, …), not friendly (‘have you touched it’, ‘it’s your fault’, …) and not good in their response (they’ll charge you, take forever to repair, …): you will never go back to this shop. A bad service has destroyed the relation.

But if, when you go back with your broken phone, the shop-assistant is most apologetic and offers you a satisfactory solution (replacement, credit, …), not only are you walking away a satisfied customer, but you will almost certainly come back to this shop for future purchases (provided of course the phone doesn’t break every month). The excellent service here has turned a negative (broken phone), into a positive: a satisfied customer with an improved relation with the provider.

Now, this part of the service is often called ‘service’ as well, although it is far more intangible, more about perception. It is the people-aspect put on top of the actual service delivery against its targets. This is things like the availability of the Service Desk, the friendliness of its staff, the response and follow-up provided.

A bad product (or service) will lose you customers, but a good one will not necessarily gain you any. People more or less expect this and you won’t get credit for something that work the way it is expected to. This is a similar issue as Problem Management faces, in particular the pro-active part: the better you do, the less people notice it!

However where bad service-perception will also lose you customers, good service will gain you. Perhaps not so much new customers, but it will cement and improve the relation with your existing ones. Hopefully improve this beyond the black and white numbers of the contract, but more into a mutually beneficial relationship whereby the IT Service Provider is truly able to provide service (and added value) to the business.

So, back to the starting point of explaining concepts: Whilst ITIL has a definition for service, and explains the function of the Service Desk … people (in my case course attendees) need to understand the true objective of a service, one that goes beyond ITIL, any of its process or functions and should be at the heart of all your staff and their actions: delivering value to your users\customers!

the ITIL Zealot
April 2013

What is wrong with ITIL training?

ANSWER 1: EVERYTHING

• ITIL Training is just another way for consulting and education firms to get your money
• ITIL Training just focussed on the process theory and facts
• Multiple choice is an inadequate way of testing someone’s capability

I guess from a negative perspective the above statements are true (to a degree). ITIL V3/2011 has made the training path more complex: whereas before it was Foundations and then either Managers or Practitioners, now it is Foundations, either Lifecycle or Capability, or some kind of combination of those and then Expert ... In particular the distinction between Lifecycle and Capability is very unclear with large areas of overlap (for instance Service Operations vs. Operational Support and Analysis) and even more puzzling gaps (little or no CSI in the Capability Courses, limited Strategy, no Design Coordination ...). APMG could have done a better job with positioning the courses, and limiting the options.

The second (negative) argument is that ITIL training is (just) focused on theory. Again there is some truth in this, mainly as most courses will be followed by an exam, which focuses on the theory (see next point). But from Intermediate up, each course is supposed to provide more than 50% practical, interactive exercises. The exception is the Foundations which does require a lot of theory to be explained, and unfortunately due to market pressure, predominantly in a 3 day / 20 hour time span.

I think the 3 days are about the maximum what a ‘novice’ (or manager) can bear, so if we don’t want to tinker with the time-element of the Foundation course, then perhaps we should look at the content. Years ago a rumour surfaced that the Foundation course might be split in two: one basic with Operations & Transition; and one more ‘advanced’ with Strategy, Design and CSI. I thought this was a great idea, but unfortunately it never materialised. 

Most consulting\training firms, or in-house training organisations will have developed an ITIL Overview or Introduction which provides the basics in one or even half-a-day. And because there is no exam-pressure you can focus on the key-concepts.

And therewith we come to the biggest argument, which is that the exam ruins a good course. I think no-one will deny that multiple choice exams are an awfully inadequate way of testing someone’s capability (no matter how much 'Bloom's taxonomy you throw in). And unfortunately the ITIL multiple choice exams are no exception. At Foundation level the question often require knowledge of specific, theoretic factoids. Something that could be easily found in the ITIL documentation (, pocket guide or glossary-of-terms) and therefore hardly a necessary skill or capability. It should focus on the larger concepts of Service Management, the lifecycle and the key processes, perhaps with small (one or two paragraph) scenarios.

The Intermediate exams are slightly better with ‘scenario-based, gradient-scored’ questions. These questions at least relay the message that not all answers are wrong or right, but that some are ‘more right’ given the circumstances. But unfortunately then a significant number of questions still rely on knowing the exact, ITIL way or in other words more factoid book remembering, rather than true understanding.

Taming the Beast of Information Overload
http://www.foundationnews.org/CME/article.cfm?ID=1003:

And at Expert level this becomes an even bigger issue as the difference between the answers becomes smaller and the correct answer (at least in my opinion) almost always is ‘it depends’. With an essay-style question you can get points even if you made the wrong choice, depending on your ‘defence’ of that choice. With multiple choice it is an all-or-nothing. And sorry, I may be overestimating my own ITIL power, but if after 20 years of almost daily working with the material I still score a 0-point answer (on the MALC), I actually believe there is something wrong with the question, rather than with me or the theory.

ANSWER 2: NOTHING

I admit that all of the above arguments hold an element of truth. However, I think that in the end it is up to both the course candidate and provider to achieve a satisfactory outcome.

The provider of the courses needs to work within the syllabus (and exam requirements) but most courses give ample opportunity to add examples, exercises, discussions and other elements to ensure understanding and provide practical guidance.

The candidate also has a responsibility. If they just come to the course to be a few days away from work, or expect to find a silver service management bullet that will be spoon-fed to them (oops, mixing some metaphors), it will be a disappointing experience. The candidate needs to be open to learning, participate in the course, question everything (most trainers will welcome the challenge of questions as this will allow them to expand on the theory and provide insight for not only the questioner but the other participants too) and ensure the course enhances their understanding. I think it should be mandatory for candidates to create a next-steps plan after each course (and for their managers to demand, verify and control these).

The exam is just a bump in the road, and fortunately with thorough understanding of ITIL and a modicum of learning the exam can be easily passed (perhaps not with a 100%, but passed nonetheless).

In a future blog I might address the various type of training (on-line, classroom, blended) and well as the customisation or training and creation of a training path (with overviews, simulations, accreditation etc.). But I’ll leave you with a musing on the difference between education and training: education is more theoretic\school-based whereas training has a practical connotation. After all you wouldn't want your teenage-daughter to come home from school raving about the sex-training she had that day!

the ITIL Zealot
May 2012