.png)
Most CIOs don't question whether ITSM matters. They question why it hasn't delivered. The frustration usually sounds like this:
The IT Service Management market is not struggling for attention or capital. Industry analysts value it at roughly USD 13–14 billion as of 2024, with projections approaching USD 30 billion by 2030 as IT environments grow more complex and interconnected (Grand View Research). Organisations are spending. Vendors are growing. Implementations are happening.
And yet, according to data from itsm.tools, only around 50–60% of organisations rate their own ITSM capabilities as "good" or "great." That's a striking execution gap in a market this mature. The tools exist. The frameworks exist. The gap is not product availability; it's operational alignment.
What makes this particularly worth examining is the downstream consequence. The same research shows that organisations with strong ITSM maturity are nearly 60% more likely to report successful digital transformation outcomes. ITSM isn't just an IT operations discipline; it's infrastructure for every technology-dependent business initiative the organisation wants to pursue. When it underperforms, the drag is felt well beyond the service desk.
Over-engineered ITSM platforms are typically designed for:
When deployed in organizations without the scale, skill sets, or governance maturity to support them, these platforms often create friction instead of structure.
Common outcomes:
In these environments, ITSM becomes an administrative burden rather than an operational accelerator.
The opposite problem is equally damaging.
Some organizations adopt lightweight or entry-level ITSM tools that:
As organizations scale, these tools struggle to support:
The result is tool sprawl, manual coordination, and fragmentation — pushing teams back into reactive behavior.
Even when tooling capability is theoretically sufficient, outcomes often fall short because:
Multiple studies show that organizations frequently under-utilize modern ITSM capabilities, significantly limiting potential efficiency and service quality gains (TeamDynamix / IDC ITSM Modernization Study).
In these cases, the tool becomes a passive system of record, not a driver of proactive operations.
Some organizations still operate without a formal ITSM platform, relying on:
While this may work at very small scale, it breaks down quickly as complexity increases.
Without tooling:
Firefighting becomes inevitable, not because teams are incapable, but because the operating model cannot scale.
Regardless of category, misalignment produces the same systemic effects:
When predictability is low, organizations fall back on heroics.
Firefighting becomes normalized.
The most important question is not: “Which ITSM platform should we choose?”
It is: “What level of operational complexity do we need to support, now and in three years, and does our tooling and usage enable that?”
This requires clarity on:
Only then does tooling selection or re-selection, make sense.
Here's the reframe that most ITSM conversations are missing: maturity isn't measured by the sophistication of the tool. It's measured by the consistency of execution, the ability to prevent recurrence, the predictability of outcomes, and whether the team workload is sustainable week over week.
A well-aligned ITSM practice, regardless of which platform it runs on, can deliver meaningfully faster incident resolution (industry data suggests 30–35% improvement is achievable), significant reduction in repeat incidents, and service quality that builds organisational trust rather than eroding it. Those outcomes don't come from the tool. They come from alignment between the tool, the process, and how people actually work.
Which means the most important question for any CIO isn't "which platform should we be on?" It's: "what level of operational complexity do we actually need to support, today and in three years, and does our current setup enable that?"
This requires clarity on:
Only then does tooling selection or re-selection, make sense.
Persistent reactive IT operations are rarely a people problem. The teams caught in firefighting mode are usually capable, often experienced, and frequently exhausted. The issue is structural: the operating model they're working inside wasn't designed to produce the outcomes being expected of it.
Proactive IT operations don't emerge from better tooling in isolation. They emerge when the operating model is clearly defined, tooling is genuinely fit for purpose, usage is disciplined and outcome-oriented, and the organisation has a path to evolve maturity without constant replatforming every two years.
CIOs who've made this shift describe the same turning point: they stopped evaluating tools and started diagnosing their operations first. The platform decision followed from that, not the other way around
Rogue Asia is a consulting-led technology services company operating across Malaysia and Singapore. We work with enterprise IT teams on operational diagnostics, platform implementation, and IT service transformation, starting with an honest picture of where you are before recommending where to go. Follow RogueAsia on LinkedIn for more insights on IT operations, service management, and enterprise technology.
