Replacing an ITSM platform is a significant decision. The fact that a system is expensive, complex or frustrating doesn't necessarily mean it is the wrong platform.
But there comes a point when organisations should at least ask the question.
The strongest signal is rarely that the technology has stopped working. More often, it is that the cost, complexity and effort required to operate it have become disproportionate to the value it delivers.
When the economics no longer make sense
Licence costs are an obvious place to start, but they are only part of the picture.
The real economics of an ITSM environment can include platform subscriptions, additional modules, implementation partners, specialist administrators, development resources, integrations, upgrades and ongoing change.
Individually, each cost may be justifiable. Together, they can create a very different picture.
A useful question is:
If we were making this decision today, knowing what we now know about the total cost, would we buy the same platform again?
If the answer isn't an immediate yes, it may be worth examining why.
When simple changes become difficult
A mature ITSM platform should make service improvement easier, not stand in its way.
Consider how much effort is required to:
-
introduce a new service
-
change an approval process
-
modify a workflow
-
create a new form
-
onboard another department
-
integrate another system
If relatively straightforward requirements regularly become projects, the organisation may be carrying more complexity than it needs.
That doesn't automatically mean the platform should be replaced. The problem could lie in configuration, customisation, governance or the operating model around it.
But it is a signal worth investigating.
When specialist dependency becomes structural
Sophisticated platforms require expertise. That's not inherently a problem.
The question is what that expertise is being used for.
If specialist developers, administrators or external consultants are routinely required to make relatively ordinary service-management changes, dependency can become embedded in the operating model.
At that point, the organisation isn't simply paying for an ITSM platform. It is paying for an ecosystem required to keep that platform working and changing.
That wider dependency should form part of any assessment of whether the current approach remains appropriate.
When you're paying for considerably more than you use
Enterprise platforms have expanded enormously in capability.
For organisations making extensive use of that capability, the economics can make perfect sense.
But requirements change.
An organisation may find itself using a relatively conventional set of service-management capabilities within a platform designed to address a much broader range of enterprise requirements.
The important question isn't whether those additional capabilities are valuable.
It is whether they are valuable to you.
A platform can be excellent technology and still be more technology than an organisation needs.
When the operating model has changed
The platform that was right five or ten years ago isn't automatically the platform that is right today.
Cloud delivery, automation, AI, enterprise service management and increasingly integrated service models are changing what organisations expect from service-management technology.
At the same time, modern platforms can often deliver capabilities that previously required substantial customisation or specialist development as standard functionality.
That changes the equation.
The cost and disruption of replacing an established platform still matter, but so does the opportunity cost of maintaining an environment designed around yesterday's requirements.
Replacement isn't always the answer
There is an important distinction between identifying a problem and assuming a solution.
An expensive ITSM environment may need simplification rather than replacement.
A difficult-to-change platform may have accumulated unnecessary customisation.
High external support costs may point to an operating-model problem.
Poor user experience may be fixable without changing the underlying technology.
And in some organisations, a highly capable enterprise platform remains entirely appropriate.
The objective should therefore not be to build a business case for replacement.
It should be to establish whether the current environment remains the most proportionate way of meeting the organisation's requirements.
Perhaps the best question is a simpler one
Instead of asking:
Should we replace our ITSM platform?
Start with:
If we were designing our service management environment today, would we design it this way?
If the answer is yes, that is valuable confirmation.
If the answer is no, it may be time to understand what should change.
Sounding familiar?
Conversant and Mozaic's ITSM Operating Model Review provides a structured assessment of the cost, complexity and effectiveness of the current service management environment.
It looks beyond the technology itself — examining platform economics, processes, integration, specialist dependency, governance and operating model.
The outcome might be optimisation, simplification, a change in operating model or, where justified, consideration of an alternative platform.
The purpose is to establish what needs to change before deciding how to change it.