The cost of standing still: why fear of ITSM change is your organisation's biggest risk

There are typically three forces at work here:

Years of customisation, integration work, and process design represent an enormous investment—financial and human. This creates a classic sunk cost trap: the tendency to continue investing in a failing course of action because of the resources already committed, rather than making decisions based on future value. Leaders who championed the original implementation have a particular incentive to protect the narrative that the platform still works. The result is that real problems get minimised, and the business case for change never quite gets the serious hearing it deserves. Organisations therefore should look within, take a step back, dissect reasons stakeholders have shared and think, are we taking the easy route for short-term mediocre output.

Large enterprises are perpetually mid-transformation. There's always another programme of work competing for attention, budget, and change capacity. ITSM rarely sits at the top of the strategic agenda—it's the infrastructure that makes everything else work, and it tends to be noticed most when it fails.

Organisations should look to ringfence ITSM as a strategic transformation that is an enabler of other programmes across the organisation. The transformation project should be tackled incrementally, modernising high-impact areas first rather than attempting a single, high-risk overhaul. This keeps the momentum and agility, in case priorities change temporarily.

Over time, the platform doesn’t just shape processes—it shapes behaviour. Teams begin to design around limitations rather than challenge them. Workarounds become standard practice. Change feels difficult, so it’s avoided. The organisation gradually loses its ability to adapt. What should be straightforward improvements turn into complex initiatives, requiring disproportionate effort and coordination.

This isn’t just a tooling issue—it’s an operating model problem and a cultural challenge. When your core service platform resists change, the business does too.

The costs of ITSM stagnation are real, but they're diffuse and slow-moving—the kind that don't trigger an incident report or show up cleanly in a quarterly review. They accumulate quietly, until they don't.

Let's take a look what truly is at stake:

When service management tooling is clunky, slow, or requires constant workarounds, it erodes the experience of every person who touches it, from IT teams to the employees raising requests. The best IT professionals, who have choices about where they work, are drawn to organisations with modern tooling and clean ways of working. Legacy ITSM platforms are increasingly a talent problem, not just a technology problem.

Although many talented IT professionals would relish the challenge of a transformation project, they may not see maintaining an inept system as rewarding or a good use of their skills. Poor tooling should not be seen as an operational inconvenience, but as a direct risk to retention, productivity, and long-term capability.

This is where the stakes are highest, and where the gap between modern and legacy platforms is widening most rapidly. According to Atomicwork's State of AI in ITSM 2025 report, AI adoption is quickly becoming a baseline expectation: more than half of organisations are already using it for data analysis, and nearly half for end-user assistants and incident management. Organisations on platforms that can't natively integrate these capabilities aren't just missing out on efficiency gains—they're not accessing benefits that could truly level up their capabilities. The longer you wait, the wider that gap becomes, and the harder it gets to close.

In our experience working with organisations through ITSM transformations, "too complex to migrate" is sometimes accurate—but more often, it's a reflection of how the risk is being framed, not an objective assessment of what's actually possible. Complexity is real, but it is manageable when approached methodically, with the right expertise and the right tooling.

More importantly, it's worth asking what the complexity itself tells you. Platforms that require extensive customisation to meet standard enterprise requirements are, by definition, poorly matched to those requirements. The customisation that makes migration feel difficult is the same customisation that makes day-to-day operation expensive, brittle, and dependent on specialist knowledge. If your environment has reached a point where no single person fully understands it, that isn't stability—it's accumulated risk.

Modern platforms are designed with extensibility and configurability as core principles, not afterthoughts. What requires bespoke development on legacy platforms is increasingly achievable through configuration—which means migrations that once felt genuinely daunting are becoming significantly more tractable.