Do you know the signs of potentially bad ITSM advice? There’s definitely a lot of stuff written on IT service management (ITSM) out there on the Internet – whether it be someone trying to be genuinely helpful to others, a mechanism through which to raise one’s profile, SEO-targeted marketing collateral, or something else. I should know because I write or publish a lot of such advisory pieces. But, hopefully, without the warning signs I’ve captured below.Here @StephenMann dives into 9 all-too-common signs of bad #ITSM advice – signs that should make you question the quality of what you're reading. Click To Tweet
You might be thinking “But they’re just words, we all use the wrong words sometimes.” And you’re right, we do. However, when blogs, articles, eBooks, papers, or other written content is marketing collateral in particular – and it has been checked, edited, and proofed – the continued inclusion of the highlighted “red flag” words and phrases has to be treated as more worrisome than a simple typographical error. It’s likely bad ITSM advice.
So, what follows is a list of the things to look out for when reading ITSM content. While you might think that their use is a simple mistake, it might instead be a sign that the author and the company they’re representing don’t know as much as they think they do. Which has to be worrying if they’re potentially offering misinformation as advice to you and many others.Check out this article by @StephenMann which shares 9 things to look out for when reading #ITSM content. Does the author really know as much as they say they do? Click To Tweet
9 all-too-common signs of bad ITSM advice
It’s difficult to know how to structure the following words and phrases. So, they might appear a bit of a jumble presented in the order I recalled of them. However, they’re all ITSM-content related “clues” that, when seen, give me – and should give you – cause for concern. That you’re looking at bad ITSM advice.
- “IT Infrastructure Library” – this long-form version of ITIL was dropped with ITIL v3 in 2007. For it still to be unwittingly used by writers proclaiming that what they have said is important has to be a big, big warning sign of content issues and bad ITSM advice.
- “ITIL v4” – it’s ITIL 4, not ITIL v4. To call it v4 might seem a simple mistake but, for me, it’s a sign that the author, and the company they might be working for, hasn’t really spent the time understanding the new version of ITIL. But they’re still happy to tell you what it’s all about!
- Still quoting ITIL v3/2011 – yes, believe it or not, I still see people talking about the older version of ITIL as though it’s the latest and greatest version of ITIL. Of course, some of what’s in this version is still great but you’ll be missing out on so much more (especially since lots has happened in IT and service delivery since 2011!).
- “Implementing ITIL” – it’s a phrase I try to avoid but I know that I’ll have used it (but hopefully in a process implementation context). The reason for concern here is different from the three bullets above because, this time, the author potentially sees ITIL as merely a set of processes/practices to implement. Rather than as a different way of thinking about IT delivery and support. This “clue” can also come in the form of ITIL being treated as a project – something that has a stated start and finish.
- “ITIL compliant” – this is likely to be seen in marketing collateral more than anywhere else. The bottom line is that ITIL is guidance, not a standard, so your organization can never be compliant with it. Look to ISO/IEC 20000 if you need a service management standard to be compliant with.
- Quoting ITIL as “the only way” – this manifests in a number of ways. From the quoting of ITIL as scripture to be deviated from at your peril, through stating “as per ITIL,” to acting as though ITIL is the only body of service management good practice out there. Plus, there’s the adverse effects of the many ITIL vs. DevOps, ITIL vs. Agile, etc. views that further exacerbate the issue. No matter the reason, fanatically pushing the exact words of ITIL on people, and organizations, isn’t what its many authors intended.
- The use of outdated statistics. OK, so it’s not a specific word or phrase, but it’s an important warning sign of bad ITSM advice. So many blogs and articles don’t cite the source and date of the stats they throw about. You’d be surprised, or maybe not, at how often my researching a stat (because I want to borrow it for something I’m creating) highlights a 10+-year-old stat being passed off as though it was freshly minted. It’s not as though nothing has changed in IT and business operations in the last three years let alone ten years.
- Outdated content. If the content Google or a kind human has pointed you too has no published date, then be cautious. Or if it’s more than two years old be cautious too (and yes, I know we have ITSM.tools content that’s older than this). A good example is change management – or change enablement as ITIL 4 now calls it – because so much has changed with change management/enablement best practice in the last half-decade.
- “Guaranteed exam passes” – it’s slightly going off-topic, but if you’re happy to go with a training provider which can guarantee that you’ll pass your ITIL exam, then please take a moment to ponder how they can guarantee this and what it means for the value of what you’ve learned.
I’m sure I could keep going – and, in fact, there’s at least one other article to be written around the misuse of ITSM and ITIL and the associated advisory services – but you’re likely bored of me ranting/rambling by now. So, what would you add to this list? Please let me know in the comments.