Automation in ITSM maturity: from manual toil to workflows you can trust
Automation is the fastest way to remove delay and error from service delivery, and the fastest way to scale a bad process. This domain measures how much repeatable work runs without human touch, and how safely and visibly it runs.
Automation raises the ceiling and the stakes at the same time
Google’s Site Reliability Engineering book defines toil as work that is manual, repetitive, automatable, tactical, without enduring value, and that grows in line with the size of the service. It sets a goal of keeping toil below half of an engineer’s time. The same definition fits much of a service desk and an operations floor.
Adoption is already widespread. Gartner’s 2022 survey of 304 infrastructure and operations leaders found that two out of three reported some high or full automation in their function. The harder part is doing it safely. Uptime Institute’s 2025 outage analysis reports that nearly 40% of organizations had a major outage caused by human error in the past three years, and that 85% of those incidents stem from staff failing to follow procedures or from flaws in the procedures themselves.
That second finding is the case for assessing automation as a maturity domain rather than a tool feature. Well-designed automation encodes the procedure so that it runs the same way every time. Poorly governed automation does the opposite: it hides failures, bypasses approvals and spreads a bad assumption across thousands of records at machine speed.
What sits behind human-error outages
Seven things we look at in the automation domain
We look at how much is automated, and just as closely at who owns each automation, how it is tested, and what happens when it fails.
- Workflow automationApprovals, notifications and state changes that run without manual nudging, and the exceptions that still need a person.
- Routing and assignmentWhether work reaches the right team automatically, and how often it has to be re-routed by hand.
- Self-service and fulfillmentCatalog items that complete without a human touch, and the share of requests that still queue for manual handling.
- Runbooks and orchestrationDocumented, executable procedures for common operational tasks, run from the platform rather than from someone’s laptop.
- Event correlation and remediationHow events are grouped and enriched, and where known fixes are applied automatically inside defined limits.
- Automation governanceNamed owners, testing, error handling, rollback and an audit trail for every automation in production.
- Measurement of manual toilWhether you can show hours spent on repetitive work before and after, so benefits are evidence and not opinion.
Three points on the scale for automation
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.
Manual work with ad hoc scripts. No one measures the time spent on repetitive tasks, and fixes depend on who remembers the steps.
Standard catalog items, routing rules and runbooks have named owners, are tested and logged, and manual effort is estimated.
Closed-loop remediation runs inside policy guardrails. Toil is a tracked KPI, automations are audited like production code, and savings are reinvested.
Three patterns we see again and again
Scattered scripts with no owner
Flows and scripts accumulate across teams with no testing, error handling or owner. Failures stay silent until a user notices.
No baseline, so no proof
Teams automate the easy tasks but never measured the manual hours before, so the benefit cannot be shown and the next investment is hard to justify.
Automating a broken process
Routing rules and catalog items are built on poor categorization and an untrusted CMDB. The automation works perfectly and sends work to the wrong place faster.
These are practitioner observations from assessment and implementation work, not survey findings. They are the reason automation is scored after process, tools and governance are understood.
One domain of six, scored on the same 0 to 5 scale
Automation is scored from questions on workflow coverage, self-service, orchestration, remediation, governance and measurement. It leans on process quality, tool configuration and governance, which is why the six domains are scored together. See how the numbers are produced on our scoring methodology page, or read the other domain guides.
Find out how much of your service delivery is genuinely automated.
No sales call required to get your first read, just the assessment.
Start free trial assessmentSources. Google, Site Reliability Engineering, Eliminating Toil (2016). Gartner, State of I&O Automation: 5 Survey Insights (2022 survey). Uptime Institute, Annual Outage Analysis 2025 (2025). Survey figures are reported as published by each source.