The operations ladder: five steps of maturity
The maturity of IT operations is not defined by the number of dashboards or the price of monitoring systems. It is defined by the culture of work with the service. The main test is what the team records and how it uses that data: are failures logged, are priorities set, are deadlines met, are root causes analysed. On the same Zabbix a team can stand on step two or on step four.
You cannot skip levels. With no recorded history there is nothing to count. With no priorities and SLA there is nothing to compare. With no recorded changes there is nothing to link a new outage to.
Tap a step to read what it is.
Your step by your answers
1. Reacting
Signs of the step: Failures are reported by users. No outage history is kept; incidents are solved in chats and by phone.
Limits: Talks about reliability rest on emotions and impressions, not on facts.
How to move up: Start recording every outage in one system: start time, end time, affected services.
Analytics available: None (there is nothing to count yet).
Your step by your answers
2. Recording
Signs of the step: Every outage is logged (start, end, scale). The Incident management practice is in place.
Limits: You see what breaks, but there are no priorities. All failures look equally important, and recovery times are not guaranteed to users.
How to move up: Define the key services and their owners. Set priorities by impact and urgency. Approve recovery times (SLA) and set up an on-call rota.
Analytics available: Recovery time (MTTR) and total downtime. Weak spots of the infrastructure, peak load hours, cycles of incidents and the chance of a long failure.
What the step is made of:
- every outage is recorded Incident management
Your step by your answers
3. Managing
Signs of the step: Services have owners, outages have a priority and SLA times. On-call duty follows set rules. The Service level management and Service desk practices are in place.
Limits: Outages are fixed fast but come back. Root causes are not investigated, and changes in the IT infrastructure are not recorded anywhere, so they cannot be linked to new failures.
How to move up: Look for the causes of repeat failures (RCA), log changes (type and result) and set up monitoring so that you learn about outages before users do.
Analytics available: The metrics of the step below, plus the split of incidents by priority and business impact.
What the step is made of:
- main services have owners Service level management
- priority is set by impact and urgency Incident management
- recovery times are promised Service level management
- an on-call rota and a hand-over order Service desk
Your step by your answers
4. Preventing
Signs of the step: Repeat failures are investigated, changes are recorded, monitoring works ahead of users. Problem management, Change enablement and Monitoring and event management are in place.
Limits: Improvements are made, but their final effect is not measured: the figures 'before' and 'after' are not compared.
How to move up: Give every improvement an owner and a KPI. Discuss the metrics directly with the consumers of the services. Record how services depend on equipment (a resource and service model).
Analytics available: The metrics of the steps below, plus the link between outage frequency and the changes made (a search for dependencies).
What the step is made of:
- repeats are investigated down to the cause Problem management
- changes are recorded with a type and a result Change enablement
- outages are known before the consumer notices Monitoring and event management
Your step by your answers
5. Improving
Signs of the step: The effect of improvements is measured, metrics are clear to the business, infrastructure dependencies are documented. Continual improvement, Measurement and reporting, Service configuration management are in place.
Limits: The infrastructure changes, and processes set up once go stale over time.
How to move up: Holding the level: a regular audit. Constant comparison of current metrics with past periods to check the effect of the solutions put in place.
Analytics available: The metrics of the steps below, plus a check of hypotheses: did the outage frequency change after a given improvement, and what is the forecast of failures for the coming periods.
What the step is made of:
- improvements have an owner and a measured effect Continual improvement
- measures are reviewed with the consumer Measurement and reporting
- service dependencies on equipment are known Service configuration management
What the ladder rests on
The ladder rests on the practices of ITIL 4, the ISO/IEC 33000 (CMMI) approach to process assessment and Gartner's principles of analytics. The assessment is built on confirmed data: what staff say gives the level 'declared', an export from the system gives 'confirmed', and a mismatch between them gives 'disputed'.
Find your step
Twelve questions, a few minutes. Your answers show the step in your own words; an export of your log shows it from your data.
What next with your step
Send an export of your outage log for 90 days or more: from it the engine computes what your step opens.