Part two of the two-article series offer 10 tips on “configuration, customization, and integrations” and “vendor relationship and (lack of) communication” needs. These are probably at different ends of your IT organization’s ITSM-tool selection criteria, but both will cause it serious pain if the right questions aren’t asked and suitable responses, and evidence, received.
Configuration, Customization, and Integration TipsWhile ITSM tools offer “out-of-the-box” ITIL best practices, there will often be the need to customize or to configure them to your organization’s preferred – or required – ways of working. Plus, your ITSM tool is not an island with a need for it to work with both other IT management and business systems.
The key tips here are:
- Know the differences between ITSM-tool delivery models – this is a wider area than just this checklist point, but it needs to be considered somewhere. There’s on-premises and software-as-a-service (SaaS)/public cloud delivery models, then variants on these such as hybrid and private cloud, and subscription pricing for on-premises. There are numerous pros and cons for each delivery model, but the important ones to consider for this checklist point are the ability to customize (and delivery model limitations), the relative ease of customizations and integrations, and how customizations and integrations fare during tool upgrades. The latter is returned to in bullet 5. below.
- Understand the difference between “clicks” and “code” – because it’s easy for people to use the terms configuration and customization interchangeably, including in ITSM tool selection, and it’s also dangerous. Configuration is usually as simple as clicks, and customization is usually code-based. So, nail down the terminology in your internal and external conversations.
- Aim for configuration wherever possible but don’t discount the need for customization and integrations in the tool selection process – configuration is easier to do and, as bullet 5 outlines, customization can create future issues. But will your organization always be able to survive purely with configuration? If it has with previous ITSM tools, then maybe you’ll be okay. But, if it hasn’t, then at least understand a new tool’s customization capabilities even if you expect to never use them – you just might need to though. The same is true for integration capabilities, although there’s far more chance that your organization will need to benefit from multiple integrations to other IT and business systems.
- Test the ease of configuration, customization, and integrations using real use-case scenarios – because watching someone, who’s experienced with a particular tool, demo an example that’s easier than your organization’s required, real-world, use-case scenarios might be interesting, but it’s not necessarily a true picture of what can and can’t be done; and the relative ease.
- Understand the impact of customization and integrations on future tool upgrades/versions – it’s critical, especially as cloud-based ITSM tools are changing far more frequently than their on-premises equivalents, that the ability to benefit from new releases isn’t held back by anything that has been introduced into the mix by your organization (customizations and bespoke integrations). Thus, don’t just look at what can be done now, also look forward to how vendor changes will impact your required changes and integrations – plus, of course, the effort and costs involved in keeping your new ITSM tool as you need it to be over time.
Vendor Relationship and (Lack of) Communication TipsRelationships with partners and suppliers are becoming more important in an increasingly services-based business world. From getting fit-for-purpose support, to ensuring that products and services live up to both current and future organizational needs.
The key tips here are:
- Know the ITSM-tool vendor landscape and which vendors suit different customer types – but you don’t need to know as much as an industry analyst. There are hundreds of IT help desk and ITSM tools on the market and it’s helpful to know about possible tools (and vendors) long before your organization is at the point of new-tool investment. Because, once they’re in your subconscious, you’ll be more likely to pick up on “mentions” of them – be it in their own content or that of others. Thus, allowing you to get an appreciation of what they offer and how well they’re doing – especially for organizations similar to your own – over time rather than just at the point of needing a new ITSM tool.
- Understand what your wants and needs from a vendor relationship perspective are – which is hopefully much more than a one-time exchange of money for software/service, followed by annual contacts for renewals and upsells. Look to create a relationship, with proactive communication mechanisms, such that the vendor is proactively assisting your successes with their ITSM tool. After all, this benefits them as much as you, and makes it easier for them to land those renewals and upsells.
- Know the IT industry research into ITSM tool vendor satisfaction and dissatisfaction – many sources are free and others that are behind paywalls, including the growing prevalence of crowd-sourced tool-review websites. A word of warning here though – while such websites contain valuable insight into customer experiences, there’s also a need to understand how they work and when they don’t. In particular, if they’re being “played” in terms of enticing happy customers to post reviews and, more worryingly, any conclusions drawn by the websites that don’t really stand up if one looks at how things – such as reported market share – are established.
- Use Google or similar, and social network sites, to better understand what other customers are saying (about both ITSM tools and vendors) – it’s a simple, and cheap exercise to undertake but, as with crowd-sourced information, it’s important to understand that not everything you’ll read is a true reflection of a particular tool or vendor. What it does do though, as a minimum, is allow your organization to a create list of difficult questions to ask each vendor under consideration.
- Agree on the organizational value of the vendor relationship (along with other business requirements) – is finding a vendor you can work with super-important to you? Consultant and ITIL author Stuart Rance offers this sage advice to clients when selecting a new ITSM tool: “Select a vendor you think you can work with.” The quality and effectiveness of the vendor relationship is a growing area of concern for ITSM tool customers, and a possible barrier to tool exploitation. So is the lack of ongoing communication. So, do sufficient research to help ensure that your organization gets what it needs in terms of relationships and communication.