0 / 24

Model 33 of 74 · Technology & Data

IT Service Management Maturity Assessment

Evaluate ITSM capability across incident, change, problem, and service management.

Pillars & areas

Resolve

Respond to disruption

  1. 01Incident & Request Management
  2. 03Problem Management & Root Cause

Deliver

Deliver with consistency

  1. 02Change & Release Management
  2. 04Service Catalogue & Self-Service

Improve

Optimise over time

  1. 05Service Level Management & Reporting
  2. 06Continual Improvement & Governance

Levels

  1. 1Break-FixFirefighting & ad-hoc
  2. 2Process-LedRepeatable processes
  3. 3PredictiveData-driven & proactive

01 Incident & Request Management

How effectively does the organisation detect, respond to, and resolve service disruptions and user requests?

0/4 answered

IR-1How are incidents detected and reported in your organisation?

Think about whether your team finds out about outages from monitoring tools or from frustrated users calling in.

IR-2How does your team prioritise and categorise incoming incidents?

Consider whether every incident gets the same level of urgency or whether there is a clear system for deciding what gets worked on first.

IR-3How does your organisation handle major incidents that affect many users or critical services?

Think about the last time a critical system went down — was there a coordinated response, or did people scramble?

IR-4How does your organisation manage service requests from users?

Service requests are routine asks like password resets, access provisioning, or new equipment — not incidents.

02 Change & Release Management

How well does the organisation control and coordinate changes to production systems while minimising disruption?

0/4 answered

CR-1How are changes to production systems assessed before implementation?

Consider whether changes go through any review process, or whether individuals push changes whenever they are ready.

CR-2How does your organisation schedule and coordinate changes across teams?

Think about whether teams know what other teams are changing, and whether conflicting changes ever collide in production.

CR-3How does your organisation handle emergency changes?

Emergency changes bypass normal approval — think about whether there are guardrails or whether 'emergency' becomes a loophole.

CR-4How does your organisation measure change success and learn from failed changes?

Consider whether you track how many changes cause incidents, and whether that data actually changes how you work.

03 Problem Management & Root Cause

Does the organisation investigate recurring issues systematically and eliminate their underlying causes?

0/4 answered

PM-1How does your organisation identify problems that need investigation?

A problem is the underlying cause of one or more incidents — think about whether recurring incidents are noticed and grouped, or just fixed one at a time.

PM-2How does your team conduct root cause analysis?

Consider whether investigations dig deep enough to find the real cause, or whether they stop at the first plausible explanation.

PM-3How does your organisation track and resolve known errors?

A known error is a problem where you understand the root cause but have not yet fixed it permanently — think about whether these are tracked or just remembered informally.

PM-4How does problem management contribute to preventing future incidents?

Think about whether fixing problems actually reduces incident volume over time, or whether the same issues keep coming back in slightly different forms.

04 Service Catalogue & Self-Service

Can users find, request, and receive IT services without unnecessary friction or delay?

0/4 answered

SC-1Does your organisation maintain a service catalogue that users can access?

A service catalogue lists what IT offers, who can request it, and how long it takes — think about whether users know what they can ask for.

SC-2How effectively does your self-service portal reduce demand on the service desk?

Consider whether users actually use the portal, or whether they bypass it and contact the service desk directly.

SC-3How does your organisation manage its knowledge base for end users?

Think about whether users can find answers to common questions themselves, or whether every question requires a ticket.

SC-4How does your organisation gather and act on user satisfaction with IT services?

Consider whether you know how users feel about IT support, and whether that feedback actually changes anything.

05 Service Level Management & Reporting

Are service commitments clearly defined, measured, and used to drive accountability and improvement?

0/4 answered

SL-1How are service level targets defined and agreed with the business?

Think about whether IT and business stakeholders have jointly agreed on what 'good' looks like for each service.

SL-2How does your organisation track and report on service level performance?

Consider whether anyone regularly looks at whether SLAs are being met, and whether that information reaches the people who need it.

SL-3How does your organisation respond when service levels are consistently missed?

Think about what actually happens when a service keeps missing its targets — is there a structured response or just acceptance?

SL-4How well does your organisation use service management data to inform decisions?

Consider whether ticket volumes, resolution times, and incident trends actually influence staffing, investment, or architecture decisions.

06 Continual Improvement & Governance

Does the organisation systematically improve its service management practices and hold itself accountable for outcomes?

0/4 answered

CI-1How does your organisation identify opportunities to improve IT service management?

Think about whether improvement ideas come from a structured process or only from things going wrong.

CI-2How does your organisation prioritise and execute improvement initiatives?

Consider whether good improvement ideas actually get implemented, or whether they sit on a list indefinitely.

CI-3How does your organisation govern its service management processes?

Think about whether anyone is responsible for ensuring processes are followed consistently, or whether each team does things its own way.

CI-4How does your organisation develop the skills and capabilities of its service management team?

Consider whether service management staff receive structured development, or whether they learn purely through on-the-job experience.

Self-assessment report

IT Service Management

Answer the questions above and your report builds here: an overall score, a score and target for each area, and the three changes that matter most.

About this model

About the IT Service Management maturity model

IT service management exists to ensure technology reliably delivers value to the people and processes that depend on it. The best ITSM organisations do not measure success by how many tickets they close — they measure it by how rarely their users need to raise tickets in the first place. This model assesses whether your service management capability is trapped in a cycle of firefighting, or whether it has evolved into a disciplined practice that anticipates problems, empowers users, and continuously improves.

Great ITSM is invisible to the business. Services work. Changes go smoothly. Problems are fixed before they cause outages. Users can help themselves. When something does go wrong, the response is fast, coordinated, and followed by genuine learning. This maturity model helps organisations assess where they stand on that journey and identify the specific areas that need attention.

This assessment covers six core areas of IT service management capability: how incidents and requests are handled, how changes are controlled, how recurring problems are eliminated, how services are presented to users, how performance is measured and reported, and how the organisation governs and improves its practices over time.

The model contains 24 questions across 6 areas, with 3 maturity levels per question. Each question describes concrete, observable behaviours at each level — not aspirational statements, but things you can verify by looking at how your team actually works today.

Who this assessment is for

This model is designed for IT service managers, service desk leads, infrastructure managers, and technology directors who want an honest assessment of their ITSM maturity. It is equally useful for organisations that are just getting started with formalising their service management as it is for mature teams looking to identify their remaining gaps. Business stakeholders who depend on IT services will also find value in understanding where their technology partner sits on this maturity spectrum.

The three maturity levels

  • Level 1 — Break-Fix: Service management operates in firefighting mode. Incidents are detected by users, not monitoring. Changes are uncontrolled. Problems recur because root causes are never investigated. There is no service catalogue, no meaningful SLAs, and no structured improvement activity. The team is busy, but busy does not mean effective — effort is consumed by preventable work.
  • Level 2 — Process-Led: Repeatable processes are in place for the core service management disciplines. Incidents are prioritised consistently, changes go through a review process, problems are investigated when they recur, and service levels are documented and tracked. The team follows defined workflows, uses shared tooling, and can demonstrate compliance with its own standards. This is where most organisations first achieve predictability.
  • Level 3 — Predictive: The organisation uses data and automation to anticipate demand, prevent failures, and continuously optimise service delivery. Monitoring detects issues before users notice. Change risk is assessed automatically. Problem management reduces incident volume proactively. Self-service handles routine interactions without analyst involvement. Service level reporting drives investment decisions. Improvement is systematic, not opportunistic. The team spends more time preventing problems than fixing them.

The 6 areas assessed

1. Incident & Request Management

The front line of IT service management — how disruptions are detected, prioritised, communicated, and resolved, and how routine user requests are fulfilled. This area assesses whether your organisation is reactive (waiting for users to report problems) or proactive (detecting and resolving issues before users are affected), and whether service requests are handled with the same rigour and efficiency as incidents.

2. Change & Release Management

The discipline of controlling modifications to production systems so that improvements are delivered without causing new problems. This area examines whether changes are assessed for risk, coordinated across teams, and tracked for outcomes — or whether changes are an uncontrolled source of incidents. It also looks at how emergency changes are governed and whether the organisation learns from change failures.

3. Problem Management & Root Cause

The investigative discipline that sits behind incident management — identifying why incidents happen and eliminating their root causes so they do not recur. This area assesses whether your organisation simply fixes symptoms one ticket at a time, or whether it systematically identifies patterns, investigates underlying causes, tracks known errors, and demonstrates a measurable reduction in repeat incidents over time.

4. Service Catalogue & Self-Service

How IT services are presented to users and how easily users can request and receive what they need. This area evaluates whether users know what IT offers, whether they can help themselves through a portal and knowledge base, and whether the organisation measures and acts on user satisfaction. A strong service catalogue and self-service capability reduces demand on the service desk and improves user experience simultaneously.

5. Service Level Management & Reporting

The practice of defining, measuring, and reporting on the commitments IT makes to the business. This area assesses whether service level targets are meaningful and jointly agreed, whether performance is tracked and reported transparently, whether breaches trigger genuine corrective action, and whether service management data is used to inform strategic decisions about staffing, investment, and architecture.

6. Continual Improvement & Governance

The meta-capability that determines whether service management practices get better over time or stagnate. This area examines how improvement opportunities are identified and prioritised, whether improvement work is actually executed and measured, how processes are governed and enforced, and whether the service management team itself is developing the skills and capabilities it needs.

How this model relates to other frameworks

  • ITIL (Information Technology Infrastructure Library) — the most widely adopted ITSM framework globally, covering service lifecycle management
  • ISO/IEC 20000 — the international standard for IT service management systems
  • COBIT (Control Objectives for Information and Related Technologies) — governance and management framework for enterprise IT
  • FitSM — a lightweight, open-source ITSM standard designed for federated organisations
  • VeriSM — a service management approach for the digital age, integrating multiple frameworks

Frequently asked questions

What is the IT Service Management maturity model?

Evaluate ITSM capability across incident, change, problem, and service management. It is an original, simplified model with three maturity levels (Break-Fix, Process-Led and Predictive), assessed through 24 questions across 6 areas: Incident & Request Management, Change & Release Management, Problem Management & Root Cause, Service Catalogue & Self-Service, Service Level Management & Reporting and Continual Improvement & Governance.

How long does the IT Service Management assessment take?

Most people finish in 10–14 minutes. Each of the 24 questions has three concrete answer options. Your progress is saved in the page URL, so you can bookmark it and come back later.

How is the score calculated?

Each answer scores 1 (Break-Fix), 2 (Process-Led) or 3 (Predictive). An area's score is the average of its answered questions, and the overall score is the average of the area scores, so every area counts equally. Scores run from 1.0 to 3.0.

Is my data stored or shared?

No. Your answers are never sent to a server. They are stored only in the page URL, which you control. Copy the link to share results with colleagues, or export a PDF or CSV report.

How should I use the results?

Start with "Where to focus" in your report. It lists the questions with the biggest gap to the target you set for each area, and shows what the next level looks like in practice. For a fuller picture, ask several people from different teams to complete the assessment and compare their links. Differences in perception are often as revealing as the scores themselves.