If your organisation is one of those struggling—your ITSM tool no longer aligns with your IT requirements and the wider organisations strategy then this blog is for you—we discuss some of the key options you have concerning where you are right now, with tips on improving your chances of success.
Optimise
If you, your users, and customers are satisfied with your ITSM tool, but you require more advanced support to meet new demands by the business or even customers, then optimisation might be the right choice. Maximising what you get from your tool could save you a lot of time and money, compared to changing solutions, by boosting ITSM efficiency and speeding up productivity.
A couple of fundamentals to consider for optimisation:
Processes and practices
Optimisation shouldn’t be limited to the tool. It should start by optimising your processes or include new processes (e.g. asset management or problem management). Optimising is about questioning the current process and identifying where it should be done differently or where gaps prevent efficiency. Each action of a process should be justified to exist. It can be justified by the value to the customer, the operational efficiency, or compliance requirements. No matter what, the very famous “we have always done it this way” is not a justification. In order to ensure your ITSM solution is delivering the best value, implementing a continuous improvement approach will ensure the optimisation of your services is a priority.
Prioritise your people
As part of your optimisation strategy, don’t forget to 'optimise' the key factor of your ITSM solution, the people. Providing your IT service teams with continuous user training, especially after adopting more sophisticated technology, can go a long way in helping users get the most out of your investment. Training will help demonstrate the useful features of the tool and how their use will impact daily work and boost productivity—from setting up dashboards to understanding reports and available shortcuts.
Integration
A part of an optimisation strategy can be integrations to acquire features unavailable from the stand-alone tool. For instance, integrating Lansweeper’s sophisticated asset discovery tool to gain visibility and understanding of your IT landscape—to ensure there are no duplicates in tool functionalities.
You may also opt to link together different ITSM processes across different tools to enhance the overall efficiency of process management and slash manual efforts. An example of this is integrating
Jira Service Management and Jira Software to allow end-to-end visibility across IT development and operation teams to resolve issues quickly. Or, integrating Confluence to power knowledge bases to ensure adequate documentation of IT policies and processes.
Migrate
In the context of this blog, an ITSM solution migration is when all or some of an organisation's products, apps, processes, etc., are moved from one ITSM tool to another—using the new tool to build the solution.
But how do you know if migrating is the right option for you? Well, the drive for change usually comes down to one or more of the following factors:
- Your current tool may be too rudimentary and doesn’t offer enough versatility to deliver the level of service your end-users expect. For instance, the lack of a self-service portal or comprehensive knowledge base, which in turn is increasing the drain on IT resources and distracting them from more strategic tasks.
- Your current solution doesn’t provide enough scalability to keep up with developments in the tech and service management industry. For instance, you want a more complete platform that incorporates all of the elements of ESM (Enterprise Service Management) and aligns with modern best practices.
- Your existing solution is heavy on admin requirements or requires highly technical resources for maintenance—leading to exorbitant overhead costs and planned budget overshoot.
Start fresh
Last but not least, starting fresh or rebuilding everything from scratch. This is an underrated option but, in some cases, definitely worth it. Especially if you want to change the tool (e.g. moving from
ServiceNow to Jira Service Management). This can be done with your existing ITSM tool or a new tool.
Nowadays, tools are not only tools; they all come with a certain philosophy: the vendor expects you to use the tool in a certain way and relies on strong concepts you must understand. For instance, let's take ServiceNow, which hinges on the concepts of forms, categories, and subcategories. On the other hand, Jira Service Management operates with request types, issue types, and, occasionally, forms. While these may seem somewhat alike on the surface, they represent two distinct frameworks for conceptualising your IT Service Management (ITSM) processes. It's important to recognise that each tool comes with its own unique set of principles and structures, and understanding these distinctions is crucial for effectively utilising them and avoiding wasting time and money trying to fit a square peg in a round hole.