Tools in ITSM maturity: fit, data and integration matter more than feature count
The platform is the most visible part of any ITSM or ITOM program and the easiest to blame. This domain looks past the feature list to ask whether the tool fits the process you designed, runs on data you can trust, and can be upgraded without drama.
The tool is rarely the whole problem, and rarely innocent either
In ITIL 4 this is the information and technology dimension: the information, systems and technologies that support service management. A platform such as ServiceNow, Jira Service Management, BMC Helix, Freshservice or Ivanti gives you capability. It does not give you design.
Satisfaction with tools is improving but far from universal. In the ITSM.tools 2025 poll of 229 practitioners, 47% said they were happy with their tool, up from 37% in 2023, while 40% were replacing, planning to replace or reimplementing it. The reasons given mostly describe fit, cost and unmet outcomes rather than a single missing feature. The poll is self-selected, so treat it as a signal from engaged practitioners, not a market measurement.
Data is the quieter half of the story. ServiceNow’s own community guidance notes that a CMDB deteriorates when its data is not maintained and no governance structure exists around how it is populated, used and secured. Event management and service mapping then inherit those weaknesses. A tool assessment that ignores data ownership is only a feature checklist.
Reasons given for changing ITSM tools, 2025 poll
Seven things we look at in the tools domain
We score the tool against the process you have designed, not against a vendor feature list, and we look hard at the data underneath it.
- Fit to processWhether workflows, forms and approvals reflect the designed process, or the process has bent to what the tool does by default.
- Configuration versus customizationHow much is standard configuration and how much is custom code that will complicate every upgrade.
- Integration and data qualityDiscovery, monitoring, CMDB and event management feeding each other, with named owners for the data.
- Licensing and total costLicense model, admin effort, and whether you are paying for capability you do not use.
- UsabilityHow agents, approvers and requesters experience the tool, and where they work around it.
- Reporting and analyticsWhether reports are trusted, reproducible and used to make decisions.
- Vendor roadmap and upgrade pathHow current the platform is, how upgrades are handled, and how vendor AI features will be adopted safely.
Three points on the scale for tools
Every domain is scored on the same five levels. These are the anchor points we use most often when we talk with clients about where they are and where they should aim.
Spreadsheets, email or a platform used out of the box with little configuration. Systems are silos and reporting is manual.
One platform configured to the defined processes. Core integrations work, an authoritative CMDB covers scoped services, and standard reporting is trusted.
The platform is configured rather than customized. Automated discovery feeds a service-aware CMDB, data quality is measured, and upgrades are routine.
Three patterns we see again and again
Customization to mirror the old process
Heavy custom code reproduces how things used to work. Upgrades become projects, technical debt grows, and the vendor roadmap stops being usable.
A CMDB without owners or scope
Discovery is switched on and records pile up. Nobody owns data quality, nobody trusts the relationships, and impact analysis goes back to tribal knowledge.
Replacing the tool to fix a process problem
A platform is swapped because the old one did not work. The same process is rebuilt on the new one, and the same complaints return a year later.
These are practitioner observations from assessment and implementation work, not survey findings. They are why the tools domain asks about fit, data and upgrade path rather than counting features.
One domain of six, scored on the same 0 to 5 scale
Tools is scored from questions on process fit, configuration discipline, integration, data quality, cost, usability, reporting and upgrade path. It is deliberately scored apart from process, so a strong platform cannot hide a weak process, and the reverse. See how the numbers are produced on our scoring methodology page, or read the other domain guides.
Find out whether your tools really fit your process.
No sales call required to get your first read, just the assessment.
Start free trial assessmentSources. ITSM.tools, ITSM Tool Churn in 2025 (2025). AXELOS, ITSM Benchmarking Report 2022 (survey fieldwork Q4 2021). ServiceNow Community, 5 Steps to Monitor CMDB Health Proactively (2023). Survey figures are reported as published by each source.