How do you measure the business impact of an ITSM implementation?
Leadership wants to know what will change once we roll out an IT service management system and when it will pay for itself. Which metrics should we compare before and after, and how do we turn them into money?
10 November 2026
0
3 min
Answer
The impact of an IT service management (ITSM) system is measured with the same set of metrics before and after go-live: SLA compliance, ticket resolution time, the share of tickets closed by the first line, the change success rate, and the number of major incidents. You turn the impact into money through labor: how many tickets, how much time each one takes, and what an hour of a specialist's time costs. Take the "before" measurement before launch, or you will have nothing to compare against.
Which metrics to use
Six metrics are enough for the comparison:
- SLA compliance: the share of tickets resolved within the time set in the service level agreement.
- Resolution time: from ticket registration to closure, tracked separately for incidents and service requests.
- First-line resolution: the share of tickets closed without escalation to the second line. The higher it is, the less load falls on expensive specialists.
- Self-service and satisfaction: the share of tickets submitted through the portal and user ratings after a ticket is closed.
- Change quality: the share of changes implemented without a rollback, and the number of incidents caused by changes.
- Major incidents: how many there were, how long each one lasted, and whether they recurred for the same reason.
Results in these terms are reported by ITG Corporation, which grew its SimpleOne setup from ITSM to services across the whole group: request processing time in the connected departments dropped by 24%, and customer satisfaction rose by 35% thanks to standardized services and fixed SLAs.
How to take the "before" measurement
Use the same period and the same set of services that you will measure after launch. If you have no tracking, a 2–4 week sample is enough: tickets from email and phone, the time spent on each one, and who closed it. For changes and major incidents, pull the records for the past year: there are fewer of them, but each one is expensive. ISO/IEC 20000-1:2018 requires analyzing changes for effectiveness and reviewing them for trends at planned intervals (clause 8.5.1.3), and reporting and reviewing each major incident after it is resolved to identify opportunities for improvement (clause 8.6.1).
How to turn the impact into money
Multiply the number of tickets per year by the time saved per ticket and by the hourly cost of a specialist, separately for each support line. Then separately estimate:
- tickets that moved to the portal and knowledge base, without counting them a second time in the time savings;
- downtime hours that did not happen: fewer major incidents and fewer failures after changes.
Keep the calculation conservative and base it on your own ticket volumes and hourly costs: leadership trusts a number it can check.
How it works in SimpleOne ITSM
SimpleOne ITSM is an IT service management system built on the SimpleOne platform. For measurement, it provides:
- SLAs and service level targets for any task: the system calculates actual and business time for each ticket and flags SLA breaches automatically;
- closure codes that show whether the first or the second line resolved the ticket, so you can see the first-line share;
- a contact type field that shows where the ticket came from: a call, email, or the portal;
- user ratings for both the specialist's work and the service as a whole.
A major incident is marked with a flag: its impact becomes very high, and the system calculates the priority itself. To work on it, you can gather a team in a Telegram group, and a timeline of events is required at closure.
A change's risk is calculated with a matrix, and the risk determines who approves it: for high-risk changes, the change advisory board (CAB). When a change is completed, it gets a closure code: implemented, partially implemented, or not implemented with a rollback. An incident records which changes caused it. Reports and dashboards on these fields are built in the report designer, and metrics with thresholds in traffic light scorecards.
How to set up SLAs and quality metrics is covered in the SimpleOne ITSM documentation, and the processes the system covers are on the SimpleOne ITSM page.
