Metric definitions and formulas reference
This appendix lists every metric defined in the content topics, grouped by part and topic. Each entry carries the definition, formula, unit, data source, related ITIL practice, agile counterpart, and cadence from the home topic, together with the gaming vector and the paired guardrail. It is generated from the "Metric definitions" and "Gaming vectors and guardrails" sections of each topic, so the home topic is the authority: where an entry here differs from its topic, the topic wins, and this appendix is regenerated.
How to use this reference
- Look up before you adopt. Before adding a metric to a dashboard, read its entry, including the gaming vector and the guardrail, and adopt the guardrail with it (see topic 1.3, Outcomes over output: choosing what to measure).
- Measure teams, services, and systems. No entry is meant for ranking individuals (see topic 1.2, Goodhart's law and the psychology of metrics).
- Prefer the home topic for judgment. The formulas here are short. The definitions of terms, the caveats on sampling, and the worked examples are in the home topic.
- Record your own variations. If your organization changes a definition, record the change and the reason in your metric catalog (see topic 1.4, Metrics governance and ownership). Metric cards help (see topic 12.4, Templates).
- Illustrative figures are marked. This appendix contains no benchmark values. Any number comes from your own baseline.
Part 1: Foundations of Measurement
1.1 Why measure agile ITIL
Home topic: (see topic 1.1, Why measure agile ITIL).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Decision-linked metric share | Share of reported metrics that have a written question and a named decision they inform | metrics with a recorded question and decision / metrics reported on the dashboard at quarter end | percent | Metric register (see topic 1.4, Metrics governance and ownership) | Measurement and reporting; continual improvement | Retrospective actions; working agreements | Quarterly | Writing a plausible question and decision for every metric after the fact to raise the percentage | Sample the decision log: ask what changed because of the metric, and check the date the entry was written against the date the metric first appeared |
| Baseline coverage | Share of in-scope services and teams that have a recorded starting value for each of the agreed core measures | service-and-measure pairs with a baseline recorded in the last 12 months / all in-scope service-and-measure pairs; services outside the catalog are excluded | percent | Service catalog and metric register | Service level management; measurement and reporting | Stakeholder review; team dashboards | Quarterly | Recording a baseline once and never refreshing it, or choosing a convenient quiet period | Require a stated date range and sample size with each baseline; review baselines after major changes to the service |
| Measurement effort | Staff time spent collecting, cleaning, and reporting metrics by hand | hours logged to manual collection and reporting during the month, excluding time spent acting on findings | hours per team per month | Time notes or a short team survey | Measurement and reporting | Retrospective time budget | Quarterly | Moving collection work off the books by doing it unlogged, or by shifting it to a supplier | Compare with a short survey of how long people say reporting takes; include supplier effort in the review |
| Data age at review | How old the newest data point is when the group meets to discuss it | review meeting timestamp minus timestamp of the latest data point on the dashboard; computed per metric, reported as median and 85th percentile | days | Dashboard refresh log | Measurement and reporting | Stakeholder review | Per review | Refreshing the dashboard just before the meeting while the underlying records are still stale | Report the age of the newest record in the source system as well as the refresh time |
| Improvement follow-through | Share of improvement actions raised from metric reviews that are completed or deliberately closed within the agreed window | actions completed or closed with a reason within 90 days of being raised / actions raised in the period, counted from the date logged in the improvement register | percent | Continual improvement register or backlog | Continual improvement | Retrospective action items | Quarterly | Closing actions with a reason of "no longer relevant" to hit the percentage, or splitting actions into trivial pieces | Review the reasons given for closed actions each quarter, and track whether the measure the action targeted moved |
1.2 Goodhart's law and the psychology of metrics
Home topic: (see topic 1.2, Goodhart's law and the psychology of metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Guardrail coverage | Share of reported metrics that have a named, tracked guardrail | metrics with a guardrail / metrics reported | percent | Metric register (see topic 1.4, Metrics governance and ownership) | Measurement and reporting; continual improvement | Retrospective of working agreements | Quarterly | Naming a guardrail on paper without ever tracking it | Review the register: a guardrail only counts if its latest value appears on the same dashboard |
| Reopen rate | Share of closed tickets or work items reopened within a stated window | items reopened within 14 days / items closed in the period | percent | ITSM tool or issue tracker status history | Incident management; problem management | Definition of done; escaped defects | Monthly | Closing the ticket and raising a new one instead of reopening; lengthening the window until reopenings fall outside it | Duplicate and linked-ticket rate; recurrence of the same cause across tickets |
| Definition change count | Number of changes to metric definitions or status workflows in a period, with reasons | count of entries in the definition change log | count | Metric register change log | Measurement and reporting | Working agreements | Quarterly | Not logging changes so the count stays low; changing a workflow without telling anyone | Compare the status model in the tool with the register at each review |
| Metric use rate | Share of reported metrics that were cited in a decision during the period | metrics cited in a recorded decision / metrics reported | percent | Decision log or review notes | Continual improvement | Retrospective actions | Quarterly | Citing every metric in a decision log as a formality | Ask what changed because of the citation; sample the log |
| Perception gap | Difference between a satisfaction survey result and a ticket-derived service level for the same service | survey-derived rate minus tracker-derived rate | percentage points | Survey tool and ITSM tool | Service level management | Stakeholder review feedback | Quarterly | Surveying only satisfied users; steering surveys to times after a good interaction | Survey response rate and respondent mix; open comments read aloud in a review |
1.3 Outcomes over output: choosing what to measure
Home topic: (see topic 1.3, Outcomes over output: choosing what to measure).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Outcome coverage | Share of reported metrics that are linked in the metric register to a written outcome for a named customer or service | metrics with a written outcome link / metrics reported in the period. Counts only metrics shown on a regular report; excludes working-view measures kept by a single team | percent | Metric register (see topic 1.4, Metrics governance and ownership) | Measurement and reporting; continual improvement | Product goal and delivery goal | Quarterly | Writing a vague outcome sentence ("improve service") for every metric so the link exists on paper | Sample the register: a sentence must name a person or service and a change; check that a decision was taken because of the measure |
| Feature adoption rate | Share of eligible users who use a new or changed capability within a stated window after release | distinct eligible users who used the capability within 30 days of release / distinct eligible users in that period. Clock starts at general availability; excludes internal test accounts and users who could not reach the capability | percent | Product analytics, service catalog usage logs | Service design; release management | Stakeholder review feedback; product outcome measure | Monthly for 3 months after release, then quarterly | Counting a forced or automatic first use as adoption; shrinking the eligible user group; making the capability the default so it is "used" without being chosen | Task completion or satisfaction among users of the capability; retention of use after 30 and 90 days; read open comments |
| Repeat contact rate | Share of contacts from a user about the same service within a stated window after an earlier contact was closed | new contacts from the same user about the same service within 14 days of a closed contact / closed contacts in the period. Clock starts at closure; excludes contacts opened as planned follow-ups | percent | ITSM tool contact and ticket history | Service desk; incident management | Escaped defects; definition of done | Monthly | Telling users to raise a new request through another channel; closing the contact as a duplicate of an unrelated one; lengthening the closure to avoid recontact inside the window | Contacts by channel for the same service; sampled review of closure notes; user-reported "problem solved" rate |
| Leading indicator validation rate | Share of leading indicators in use whose movement has preceded the movement of their linked lagging indicator in the review period | leading indicators with a confirmed lead over their lagging indicator / leading indicators in use. Judged by the team in a documented review, on at least four periods of data; excludes indicators with fewer than four periods | percent | Metric register and trend history | Continual improvement | Retrospective actions on experiments | Twice a year | Declaring leading indicators valid after an informal look; choosing indicators that trivially move with the outcome | Written review record with the plotted data; invite someone outside the team to challenge one result per cycle |
| Benefit review completion rate | Share of funded changes or improvements whose intended outcome was reviewed against its measure after the agreed delay | changes with a completed outcome review within 90 days of the planned review date / changes whose review date fell in the period. Excludes changes withdrawn before release | percent | Change record, improvement register, review notes | Continual improvement; change enablement | Stakeholder review; product increment review | Quarterly | Holding a review in name only, or setting the intended outcome after the fact so it is always met | Compare the outcome in the review with the statement made when the change was funded; track the share of reviews that led to a change in plan |
1.4 Metrics governance and ownership
Home topic: (see topic 1.4, Metrics governance and ownership).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Ownership coverage | Share of reported metrics with a named, current owner | reported metrics with an owner who still holds the role at period end / reported metrics at period end; excludes metrics used only inside one team's private board | percent | Metric register | Measurement and reporting | Working agreements | Quarterly | Naming a manager or a mailing list as owner to reach 100 percent, with no one who can explain or change the metric | Ask each owner to explain one recent movement in the number; track questions that went unanswered for more than a week |
| Definition currency | Share of reported metrics whose definition was reviewed within the agreed interval | metrics with a review date within the last 6 months / reported metrics; clock starts at the last recorded review and stops at the period end | percent | Metric register change log | Measurement and reporting; continual improvement | Retrospective actions | Quarterly | Touching the review date without reading the definition | Sample three entries each quarter and compare the written definition with the tool's actual configuration |
| Source conformance | Share of reported metrics computed from exactly one named source | metrics with one authoritative source and no known parallel calculation / reported metrics; parallel calculations are found by sampling dashboards and reports | percent | Register plus a sample of dashboards and reports | Measurement and reporting; service level management | Definition of done for a metric | Quarterly | Declaring a source authoritative while spreadsheets still circulate and disagree | Count distinct figures for the same metric found in a sample of reports; reconcile differences in the review |
| Retirement rate | Number of metrics retired or merged in a period relative to those reported | metrics retired or merged in the period / metrics reported at period start; a metric moved to a private team view counts as retired from the reported set | percent | Metric register change log | Continual improvement | Retrospective actions | Quarterly | Retiring trivial or unused metrics to look disciplined, or renaming a metric so it counts as new | Review the retirement log for what was removed; track the total reported count and the decision linkage figure alongside |
| Access review currency | Share of restricted metric views whose audience list was reviewed within the interval | restricted views with an audience review in the last 6 months / restricted views; views open to the whole organization are excluded | percent | Access list or BI tool permissions export | Information security management; measurement and reporting | Working agreements | Semi-annually | Approving the existing audience list without reading it | Compare the list with current team membership and roles; report the number of removals found |
| Decision linkage | Share of reported metrics linked in the register to a decision they inform | metrics with a recorded decision or question / reported metrics; a link counts only if the decision was taken in the last 12 months | percent | Metric register and decision log | Continual improvement | Stakeholder review and improvement outcomes | Quarterly | Writing a vague decision such as "improve service" to satisfy the field | Require a dated decision or question, and sample the decision log for whether the metric was actually consulted |
1.5 Data sources and instrumentation
Home topic: (see topic 1.5, Data sources and instrumentation).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Source coverage | Share of in-scope services and teams whose events reach the metrics store automatically | services or teams with an automated feed / services or teams in scope; "in scope" is listed in the metric register | percent | Metric register and pipeline configuration | Measurement and reporting; service configuration management | Team working agreement on tooling | Quarterly | Counting a service as covered after a feed is connected, even if it carries almost no events; leaving hard services out of scope | Event volume per covered service compared with its known activity; review the scope list against the service catalog |
| Timestamp completeness | Share of closed work items that carry every timestamp needed for the clocks of the metric | closed items with all required state-change timestamps / items closed in the period; items still open are excluded | percent | ITSM tool or issue tracker history | Incident management; service request management | Board or workflow history | Monthly | Filling required timestamps with the closing time to satisfy validation | Distribution of gaps between consecutive states; sample closed items to see whether the times are plausible |
| Backdating rate | Share of state changes recorded after the fact, measured by the gap between the event time and the time it was entered | state changes entered more than 24 hours after the event time / state changes in the period; clock starts at the event, stops at the entry | percent | Audit trail of the tracker, or pipeline event time versus entry time | Change enablement; incident management | Definition of done | Monthly | Entering changes just inside the threshold; widening the threshold; recording all changes through one bulk update | Entry-time pattern by hour; share of changes made by automation versus by hand; audit of bulk edits |
| Data freshness | How old the newest data on a dashboard is when it is viewed | view time minus the newest event time loaded; report the median and the 95th percentile | hours | Pipeline run log and dashboard load log | Measurement and reporting | Stakeholder review preparation | Weekly | Showing the time of the last refresh instead of the time of the newest event | Newest event time displayed on the dashboard; alert when a feed delivers no new events |
| Reconciliation variance | Disagreement between two sources for the same count | absolute difference between the two counts / the source of record count, for a fixed period and scope | percent | Source of record and the reporting layer | Service level management; financial management | Release report checks | Monthly | Choosing the period or scope that reconciles; adjusting the reporting layer to match the source without finding the cause | Fix the scope and period in advance; record each cause found and review the causes quarterly |
| Status model drift | Number of distinct status names or transitions in use compared with the documented model | undocumented statuses or transitions observed in the period (count); documented ones are excluded | count | Tracker workflow configuration and event history | Continual improvement | Working agreements on workflow | Quarterly | Reusing an existing status for a new meaning to avoid being flagged; adding statuses without logging them | Compare workflow configuration with the register at each review; read a sample of items in unusual states |
| Survey response rate | Share of invited people who completed a survey | completed responses / invitations delivered; bounced invitations are excluded | percent | Survey tool | Service level management; customer experience | Stakeholder review and improvement feedback | Per survey wave | Inviting only people likely to respond; sending reminders to satisfied users; offering rewards that bias answers | Respondent mix compared with the user population; distribution of answers by wave; open comments read in the review |
1.6 Statistical literacy for service metrics
Home topic: (see topic 1.6, Statistical literacy for service metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Median resolution time | The middle resolution time of incidents resolved in the period | 50th percentile of (resolved timestamp minus created timestamp) over incidents resolved in the period; the clock starts at ticket creation and stops at resolution; pauses are reported separately, not subtracted; canceled and duplicate tickets are excluded | hours or days | ITSM tool status history | Incident management; measurement and reporting | Median cycle time | Weekly or monthly | Closing quick tickets first and leaving hard ones open; splitting a ticket into several easy ones; pausing the clock in a customer-wait state | High-percentile resolution time and oldest open item age; share of time in pause states; linked-ticket rate |
| High-percentile resolution time | The time within which most incidents are resolved, with the percentile named | 85th (or 95th) percentile of the same elapsed time as above; computed only if at least 20 items resolved, otherwise the raw items are listed | hours or days | ITSM tool status history | Incident management; service level management | Cycle time percentile forecast | Weekly or monthly | Choosing a percentile that flatters the result, or changing it between reports; excluding long cases as "outliers" or reclassifying them | Percentile fixed in the register; a list of excluded items with reasons; oldest open item age |
| Oldest open item age | Age of the oldest item still open, plus the count of items older than the high percentile | now minus created timestamp for open items, no pause subtracted; counts all open items in the service queue including those waiting for the customer | days | ITSM tool or issue tracker | Incident management; problem management | Work item age | Weekly | Closing or merging the oldest item without resolving it; moving it to a different queue or category | Reopen rate; sample audit of the oldest closed items; queue transfer count |
| Rate reporting coverage | Share of reported rates that show the numerator, denominator, and a minimum-count check | rates reported with counts and a sample flag / rates reported; counts only rates published in the period's review pack | percent | Metric register (see topic 1.4, Metrics governance and ownership) | Measurement and reporting | Working agreements | Quarterly | Attaching a count in small print while headlines still lead with the percentage; setting the minimum count so low that it never triggers | Review the actual dashboard, not the register; minimum count reviewed with the interval width |
| Control chart signal rate | Share of points on a measure's control chart that signal special-cause variation under the team's written rules | points flagged under the rules / points plotted, over the last 20 or more points; the rules are fixed in advance and logged | percent | Control chart tool or spreadsheet | Continual improvement | Retrospective inspection of the process | Monthly | Widening the limits, adding rules, or restarting the baseline so signals disappear; moving points by changing the measure | Rules and limits stored in the register with change history; compare against the raw histogram |
| Interval width | Width of the stated uncertainty range on a headline rate | upper bound minus lower bound of the interval, using the method named in the register, for the period's headline rate | percentage points | Calculated from ITSM counts | Service level management | Forecast range in planning | Monthly | Choosing a method or window that produces a narrow range; pooling dissimilar services to enlarge the sample | Method named in the register; breakdown by service available on request; pooled and unpooled results compared |
1.7 Measurement frameworks
Home topic: (see topic 1.7, Measurement frameworks).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Goal traceability | Share of reported metrics that trace to a written goal and question | metrics with a recorded goal and question / metrics reported | percent | Metric register (see topic 1.4, Metrics governance and ownership) | Measurement and reporting; continual improvement | Delivery goal; product goal | Quarterly | Writing a goal and question after the metric already exists, to make the record look complete; vague goals that justify any metric | Sample five entries each quarter and ask whether the question could have led to a different metric; check that the audience and decision are named |
| Key result score distribution | Spread of end-of-period scores for key results, shown as the share in each band | key results in each score band (for example 0.0 to 0.3, 0.4 to 0.6, 0.7 to 1.0) / key results scored in the period; excludes key results dropped with a recorded reason | percent per band | OKR tracking tool or team document | Continual improvement; service level management | Quarterly planning; review | Quarterly | Writing easy key results so scores cluster near 1.0; rescoring generously; dropping key results that are going badly without recording why | Count of key results dropped with their reasons; compare key results with the previous period's outcomes; review the median ambition with leadership |
| Perspective coverage | Share of the four balanced scorecard perspectives that have at least one measure with a current value | perspectives with a measure reported in the last period / four | percent | Scorecard or dashboard | Measurement and reporting; service value system governance | Stakeholder review (customer and learning views) | Quarterly | Adding a token measure to a perspective so it counts as covered; choosing measures that cannot move | Check that each perspective measure has changed value in the last year and has a written decision attached |
| Indicator review age | Time since each KPI's definition and target were last reviewed | review date minus the date of the last review; the clock starts on the last recorded review and stops on the reporting date; report the median and the oldest | days | Metric register change log | Continual improvement; measurement and reporting | Retrospective actions | Quarterly | Recording a review without reading the indicator; changing the date only | Require a written outcome (kept, changed, retired) with each review, and sample the log |
| CSF-to-KPI coverage | Share of critical success factors with at least one KPI that is currently reported | CSFs with a current KPI / CSFs defined for the service or practice | percent | Practice or service documentation; metric register | The CSF and KPI approach in ITIL practice guides | Definition of done; working agreements | Quarterly | Assigning a KPI that is unrelated to the CSF to reach full coverage; choosing a KPI that cannot reveal a failure | Ask for each pair what reading would show the CSF is failing; look for KPIs that have never been red |
Part 2: Flow and Continuous Delivery Metrics
2.1 Flow measures
Home topic: (see topic 2.1, Flow measures).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Work in progress (WIP) | Work items started but not finished | Count of items whose started timestamp is set and whose finished timestamp is empty, at a stated moment (for example the end of each day); backlog items not yet started and finished items are excluded | items | Issue tracker or ITSM tool state history | Incident management; service request management; change enablement | WIP limit; team backlog in progress | Daily snapshot, reviewed weekly | Keeping items in the backlog or in a "ready" column until the last moment, so they are not counted as started; closing and reopening items; hiding work off the board | Reconcile board items with requests received; sample the board against the team's actual work; track the age of items in the first column |
| Throughput | Work items finished per unit of time | Count of items whose finished timestamp falls in the period (for example a calendar week, Monday to Sunday); items finished and then reopened count again only if they are new items | items per week | Issue tracker or ITSM tool state history | Incident management; service request fulfillment | Throughput; completed items | Weekly | Splitting items into tiny pieces; closing items before they are done; choosing easy items first | Look at item size distribution and reopen rate; count escaped defects and incidents tied to recent items; review the mix of work types finished |
| Work item age | Elapsed time an unfinished item has been in progress | Current time minus the started timestamp, for items still in progress; clock runs through blocked time; items not yet started are excluded | days | Issue tracker or ITSM tool state history | Incident management; problem management | Work item age; daily team check-in | Daily, reviewed at each team check-in | Moving a stale item to "done" or a new state to reset the clock; canceling old items quietly; creating a fresh copy of an old item | Audit state moves backward and canceled items; report canceled items and their age; check for duplicates created near the age limit |
| Cycle time | Elapsed time from start to finish of a finished item | Finished timestamp minus started timestamp, in calendar days, inclusive; clock starts at the first move into a started state and stops at the move into a finished state; report the median and the 85th and 95th percentiles | days | Issue tracker or ITSM tool state history | Incident management; service request fulfillment; change enablement | Cycle time; item duration | Weekly, with a rolling 8 to 12 week window | Starting the clock late by moving items to "in progress" only when work is nearly done; ending it early by marking items done before review or release | Compare start time with first commit or first activity; report the time between "done" and release; sample finished items for true completion |
| SLE attainment | Share of finished items that met the team's service level expectation | Finished items with cycle time at or below the SLE / all items finished in the window; items still open are excluded | percent | Derived from cycle time | Service level management | Service level expectation | Monthly | Setting a generous SLE; excluding hard items as "special"; closing items to stay under the limit | Keep the SLE at a percentile of past data and review it each quarter; report excluded items and the reason; read the 95th percentile and the oldest open items |
| Blocked time share | Share of in-progress days that items spent flagged as blocked | Item-days in a blocked state / item-days in progress, over the window; the clock for both starts at the started timestamp | percent | Issue tracker flags or a blocked status in the ITSM tool | Incident management; problem management; supplier management | Blockers; impediments raised in daily team check-ins | Weekly | Never flagging blocks, so the share looks low; flagging everything as blocked to explain delay | Compare blocked share with the age of in-progress items; review block reasons by category; sample blocked items to check each reason |
2.2 Lead time, cycle time, and flow efficiency
Home topic: (see topic 2.2, Lead time, cycle time, and flow efficiency).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Lead time | Elapsed time from the arrival of a request to its delivery to the requester | delivery timestamp minus request arrival timestamp, per work item; clock starts when the request is recorded, stops when the requester can use the result; items still open and items canceled before delivery are excluded and counted separately | days or hours | ITSM tool or issue tracker history | Service request management; incident management; change enablement | Lead time on the team board; request-to-release time | Weekly, reviewed monthly | Delaying the creation of the request record so the clock starts late; closing and reopening items to restart the clock; splitting one request into many tiny ones | Compare request records with the first contact in email or chat on a sample; track reopen rate; track the size and count of items per request |
| Cycle time | Elapsed time from the moment the team starts the work to the moment it is finished | finished timestamp minus started timestamp, per work item; clock starts at the first move into an active working state, stops at the first move into a done state; time before the start and after the done state is excluded | days or hours | Tracker or board state history | Incident management; service request management; change enablement | Cycle time (see topic 2.1, Flow measures) | Weekly | Starting the clock late by moving items to "in progress" only at the end; leaving items out of the board until almost done; slicing work into pieces that do not deliver value on their own | Work item age for open items (see topic 2.1, Flow measures); check that done items are usable by the requester; compare lead time with cycle time |
| Touch time | Time in which a person or an automation is actively working on the item | sum of the intervals the item spends in states classed as active work; waiting states, blocked states, and queue states are excluded | hours | Tracker state history, with each state classed as active or waiting | Incident management; service request management | Process time in a value stream map | Monthly sample | Classifying waiting states as active, or logging activity to look busy | Review the state classification with the team each quarter; sample items and compare logged activity with commits, comments, and calendars |
| Wait time | Time in which the item is in a queue, blocked, or paused | cycle time minus touch time, per work item; n/a for items without a recorded start | days or hours | Tracker state history | Incident management; service level management | Wait time or blocked time on a board | Monthly | Creating new statuses so waiting time falls into an unmeasured gap; moving waiting items into a status outside the workflow | Count undocumented statuses and transitions (see topic 1.5, Data sources and instrumentation); confirm that cycle time equals touch time plus wait time on a sample |
| Flow efficiency | Share of cycle time spent in active work | sum of touch time / sum of cycle time, for items finished in the period; items with a missing state history are excluded and counted separately | percent | Tracker state history | Continual improvement; service request management | Flow efficiency from lean practice | Monthly | Reclassifying waiting as active; selecting only fast items for the sample; finishing easy items first to lift the ratio | Fixed state classification with a change log; compute it on all finished items; report it with the 85th percentile cycle time and the age of open items |
| Clock pause share | Share of cycle time during which the formal service clock was paused | sum of pause durations / sum of cycle time, for items finished in the period; pauses are the statuses defined in the written clock rules | percent | ITSM tool status history | Service level management; incident management | Blocked or on-hold column time | Monthly | Pausing the formal service clock for reasons that do not depend on the customer, such as internal handoffs, to meet the SLA | Audit the pause reasons on a sample; report elapsed time and SLA time side by side; review the customer's own view of resolution time (see topic 5.1, SLA, OLA, and XLA metrics) |
2.3 Work in process and queueing
Home topic: (see topic 2.3, Work in process and queueing).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Work in process | Number of items started and not finished inside the agreed boundary | Count of items in "in process" statuses at the snapshot time; items in the backlog or "ready" queue before the first work status and items already done are excluded | items | Issue tracker or ITSM tool status history | Incident management; service request management | WIP count on the board | Daily snapshot, reviewed weekly | Moving items to a "parked" or "on hold" status to stay under the limit; splitting items to look smaller; starting work off the board | Count of items in parked statuses and their age; sample the board against the real work; report the oldest item in process |
| Queue length | Number of items waiting for work to begin or waiting between stages | Count of items in waiting statuses (for example "new," "awaiting triage," "awaiting review") at the snapshot time; blocked items are reported separately, not added | items | Tracker or ITSM status history | Incident management; change enablement | Ready column and queue columns on a board | Daily snapshot, reviewed weekly | Closing and reopening items; rejecting new items at the door; renaming waiting statuses so they fall outside the count | Reopen rate and rejection rate beside queue length; review of status definitions at each metrics review |
| Queue time | Elapsed time an item spends waiting before work starts, per stage | Clock starts when the item enters a waiting status and stops when it enters the next active status; time in a status marked "blocked on customer" is excluded and reported as its own figure; report the median and the 85th percentile | hours or days | Status transition timestamps in the tracker or ITSM tool | Service desk; incident management; change enablement | Wait time in a value stream; time in queue columns | Weekly | Starting the clock late by creating the record after work is ready; pausing the clock through blocked or customer-wait statuses; marking an item as in progress when it has only been opened | Distribution of time in blocked and pause statuses; share of items created after they were started; requester-reported wait from a short survey |
| Arrival and departure rate | Items entering and leaving the system per period, and their difference as net queue growth | Arrivals = items that enter the boundary in the period; departures = items that complete in the period; net growth = arrivals minus departures; reopened items count as arrivals only if the team defines them so | items per week | Tracker or ITSM creation and resolution timestamps | Monitoring and event management; incident management | Throughput and cumulative flow diagram | Weekly | Closing items quickly to raise departures; splitting one request into many to raise both counts; counting duplicates as arrivals | Quality and reopen measures on closed items (see topic 3.3, Incident response and resolution time); size distribution of items; customer outcome check |
| Team load ratio | Share of team capacity that planned and expected work would consume | Hours of demand expected in the period (arrivals times average effort per item) / hours of capacity available after leave and fixed commitments; the team states how it estimates effort; individuals are never reported | percent | Capacity plan, tracker effort history, rota | Capacity and performance management; workforce and talent management | Team capacity in planned work | Monthly, and at each planning event | Underestimating effort to show spare capacity, or overstating demand to justify headcount; reporting a ratio for a favorable period | Compare estimated and actual effort per item; show the ratio with its trend and the interrupt share; peer review of the estimation method |
| WIP limit breach rate | Share of days a stage or the system exceeds its agreed WIP limit | Days with WIP above the limit / working days in the period; days when the team recorded a deliberate exception with a reason are reported separately | percent of days | Daily WIP snapshots and the exception log | Continual improvement; incident management | WIP limit working agreement | Weekly | Raising the limit to stop breaches; hiding breaches by moving items off the board; granting exceptions freely | Number and reasons for exceptions; history of limit changes with dates; cycle time percentile alongside breach rate |
| Little's law consistency ratio | Check that the three flow numbers agree with each other | Average WIP over the period / (departures per day times mean cycle time in days) for the same boundary and period; a ratio near 1 means the definitions are consistent, a ratio far from 1 means a boundary or clock is inconsistent | ratio | Same tracker data as the other flow metrics | Measurement and reporting | Flow metric sanity check in a retrospective | Monthly | Adjusting the boundary or period until the ratio approaches 1; excluding long-lived items as outliers | Fix boundary and period in advance; publish the excluded items and their count; review changes to the boundary with a reason |
2.4 Value stream metrics
Home topic: (see topic 2.4, Value stream metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Value stream lead time | Elapsed time from the customer's request to the customer being able to use the result | time of delivery confirmation minus time the request was logged; items canceled or withdrawn are excluded; report the median and the 85th and 95th percentiles | days | ITSM tool records joined with delivery events from the pipeline or fulfillment system | Service request management; change enablement | Lead time on the team board | Monthly | Starting the clock later, for example at triage instead of the request; closing items before the customer can use them; splitting one request into several small ones | Fixed clock rules written in the metric register; customer confirmation of delivery; count of reopened items and linked child items |
| Process time | Time an item is being actively worked, per stage and for the stream | sum of the intervals in which the item is in an active state, per stage; queue, approval wait, and blocked states are excluded | hours or days | Tracker status history; time records where states are too coarse | Incident management; service request management | Cycle time in "in progress" columns | Monthly | Recording idle or blocked states as active so process time rises and the stream looks efficient; or recording waits as work to look busy | Observation of a sample of items; process time compared with time records where they exist; the state definitions reviewed with the team |
| Wait time | Time an item sits between active work, per stage and for the stream | stage elapsed time minus the process time of that stage; includes queues, approvals, handoffs, and blocked time | days | Tracker status history and ITSM tool state changes | Change enablement; service desk | Time in queue columns; blocked time | Monthly | Moving waiting into an untracked state, such as a side conversation, a spreadsheet, or a "pending" status that stops the clock | Report the use of pause and blocked statuses; compare ticket age with stage timestamps; sample items for off-system waits |
| Process efficiency | Share of the lead time that is process time | sum of process time across stages / value stream lead time for the same items; items still open are excluded | percent | Derived from process time and lead time | Continual improvement | Flow efficiency | Quarterly | Shrinking the lead time with expedited handling for the measured items, or inflating process time to raise the ratio | Show lead time and process time beside the ratio; report the expedited share; never set a target for the ratio itself |
| Percent complete and accurate (stage) | Share of items a stage receives that it can use without correction, completion, or return | items accepted as received / items received in the period; items returned for any reason count as not accepted | percent | Return and reopen events in the tracker or ITSM tool; sampled acceptance reviews | Service request management; change enablement; problem management | Definition of ready; rework rate | Monthly | The receiving stage lowers its acceptance bar so fewer items are returned, or the sending stage pushes work through by informal workarounds | Written acceptance condition; downstream defect and rework counts; sample of accepted items reviewed by a third party |
| Rolled percent complete and accurate | Share of items that pass every stage cleanly | product of the stage %C/A values for one stream and period (for example 0.90 x 0.85 x 0.95); stages outside the stream are excluded | percent | Derived from the stage values | Continual improvement | Escaped defect and rework rate across a pipeline | Quarterly | Merging stages so that returns happen inside a stage and disappear from the handoff count; choosing a favorable stage list | Fix the stage list in advance; report stage changes in the decision log; compare with the rework rate for the whole stream |
| Handoff count | Number of times an item passes between teams or queues | count of changes of owning team or queue from request to delivery, per item; report the median and 85th percentile | count | Assignment history in the ITSM tool or tracker | Service desk; service request management | Dependencies between teams | Quarterly | Reassigning items to a shared queue or a catch-all owner to avoid counted changes of owner; hiding handoffs in a single "team" that spans several | Count by queue and by role; read the assignment history of sampled items; track the number of reassignments per item |
| Takt time ratio | Whether the stream's pace matches demand | median observed interval between completions / takt time, where takt time is available working time divided by items demanded in the same period; a ratio above 1 means the stream is slower than demand | ratio | Demand count from the intake queue and completion events | Capacity and performance management; service level management | Throughput against demand; forecast | Quarterly | Counting deferred or rejected demand as not demanded; counting partial completions as completions | Report demand, rejected demand, and backlog age beside the ratio; count completions only when the customer confirms |
2.5 Delivery forecasting and planning metrics
Home topic: (see topic 2.5, Delivery forecasting and planning metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Forecast hit rate | Share of forecasts where the actual result fell inside the stated range | forecasts whose actual outcome was within the stated range / forecasts made | percent | Forecast log and delivery records | Capacity and performance management; continual improvement | Forecasting accuracy in planning conversations | Monthly | Stating very wide ranges so that every forecast hits; re-forecasting after the fact | Forecast range width; keep the original forecast in the log; compare ranges with peers' history |
| Forecast range width | How wide the stated range was, relative to the median forecast | (upper bound minus lower bound) / median forecast | ratio | Forecast log | Capacity and performance management | Cone of uncertainty narrowing | Monthly | Narrowing ranges to look confident | Forecast hit rate; require the range to be built from recorded history |
| Delivery goal success | Share of stated delivery goals that were met for the period, judged by outcome | goals met / goals set | percent | Goal records agreed with stakeholders | Service level management; continual improvement | Outcome review with stakeholders | Monthly or per release of a goal | Setting easy goals; redefining a goal after the fact; counting output as outcome | Stakeholders judge the outcome; goal wording kept in a log; check usage data for the delivered change |
| Scope change rate | Share of committed work that was added, removed, or re-sized after the forecast was made | items added or removed after forecast / items in the original forecast | percent | Work tracker change history | Change enablement; service level management | Backlog adaptation to feedback | Monthly | Freezing scope by refusing valid changes; hiding scope change by re-sizing items | Satisfaction of stakeholders with responsiveness; change reasons recorded |
| Capacity allocation | Share of team capacity spent on change, operational work, and improvement | completed items or hours in each category / all completed items or hours | percent | Work tracker with work type | Capacity and performance management; incident management | Work type distribution | Monthly | Mislabeling operational work as improvement; hiding operational load by working off the board | Reconcile with incident and request records; sample items for type |
| Throughput stability | Variation in weekly throughput | standard deviation of weekly throughput / mean of weekly throughput | ratio | Work tracker | Capacity and performance management | Predictability of flow | Monthly | Splitting items into trivial pieces to raise the count; closing items without finishing them | Item size distribution; reopen rate; sample for value delivered |
| Local velocity | A single team's finished work in its own sizing unit per planning period | sum of estimates for items meeting the definition of done in the period | team-defined points | Work tracker | Capacity and performance management | Team capacity planning aid | Per planning period | Inflating estimates; splitting stories to claim points; comparing teams | Keep it team-private; compare with throughput and cycle time; never set a target |
2.6 Backlog and refinement metrics
Home topic: (see topic 2.6, Backlog and refinement metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Backlog size | Number of open items in a named backlog at a point in time | Count of items with status open or ready on the snapshot date; excludes items in progress and closed items | items | Issue tracker or ITSM tool snapshot | Incident management; service request management; problem management | Product backlog; Input queue | Weekly | Closing items in bulk as obsolete, splitting items to look busy, or hiding work in side lists and spreadsheets | Backlog discard rate with leave reasons; periodic comparison of the tool to the real list of requests; customer feedback on dropped items |
| Backlog age | Distribution of how long open items have waited | For each open item, snapshot date minus the date it entered the backlog; report the median, 85th percentile, and oldest item | days | Issue tracker or ITSM creation and status history | Incident management; problem management; continual improvement | Backlog health; aged item review | Weekly | Resetting the entry date by cloning or re-creating old items; moving items between backlogs; re-opening instead of re-raising to change the clock | Audit of cloned and moved items; oldest-item review; age measured from first creation across linked records |
| Ready work depth | How far ahead the team has ready work | Items meeting the definition of ready / average items finished per week over the last six periods | weeks | Issue tracker ready flag and throughput history | Business analysis; service request management | Definition of ready; refinement | Per planning period | Marking items ready without checking them; inflating depth by writing detailed items for low-value work | Sample of ready items read against the definition; rework or return-to-refinement rate when work starts |
| Refinement coverage | Share of the near-term window that is ready | Items in the next two fortnights of expected work (or the top N by order) that meet the definition of ready / items in that window | percent | Issue tracker order, ready flag, and planned work | Business analysis; change enablement (for planned change) | Product backlog refinement | Per planning period | Ticking the ready flag to meet the number; narrowing the window so fewer items count | Count of items sent back after planning; delivery goal success and mid-period scope change (see topic 2.5, Delivery forecasting and planning metrics) |
| Backlog inflow-outflow ratio | Whether items arrive faster than they leave | Items added in the period / items removed from the backlog by completion or discard in the same period; a ratio above 1 means growth | ratio | Issue tracker or ITSM created and resolved events | Incident management; service request management; capacity and performance management | Arrival and departure rates | Weekly | Closing quickly the easy items to push outflow, or refusing new items at the door to hold inflow down | Age of the oldest items; discard rate; share of requests rejected without a reason; customer-reported unmet needs |
| Backlog discard rate | Share of leaving items removed without delivery | Items closed as will not do, duplicate, or obsolete / all items leaving the backlog in the period; excludes items closed as done | percent | Issue tracker resolution field | Continual improvement; problem management (known error review) | Backlog pruning; product owner ordering | Monthly | Discarding items that users still want, to shrink size; or avoiding discards so the number looks gentle | Review of a sample of discarded items with the requester; reopen and re-raise rate for discarded items |
| Service backlog past target | Share of open service items older than their agreed response or resolution window | Open items whose elapsed time exceeds the service target / all open items in the queue; the clock runs from logging and pauses only in states the written definition allows | percent | ITSM tool with service level clock | Service level management; incident management; service request management | Expedite lane; service level expectation | Daily or weekly | Pausing the clock with a waiting-for-customer state, downgrading priority, or closing and reopening to reset the window | Share of time in pause states; reopen rate (see topic 1.2, Goodhart's law and the psychology of metrics); user satisfaction on closed tickets |
2.7 Pull request and code review metrics
Home topic: (see topic 2.7, Pull request and code review metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Time to first review | Wait between a pull request becoming ready for review and the first substantive human response | Clock starts when the pull request leaves draft status or is opened ready, stops at the first review comment, change request, or approval by someone other than the author; bot and author comments and pure label changes are excluded. Report the median and 85th percentile in working hours | working hours | Version control platform event history | Software development and management; change enablement | Working agreement on review responsiveness; flow of work in progress | Weekly | Posting a quick "looks good" or an emoji as the first response; assigning a bot or a friendly reviewer; marking a pull request ready only after someone has pre-agreed to look | Post-merge fix rate; sample of approvals with no comments; require that first responses be substantive in the working agreement |
| Review cycle time | Total time from ready for review to merge | Clock starts when the pull request is ready for review, stops at merge; pull requests closed without merging are excluded and counted separately. Report the median and 85th percentile in working hours | working hours | Version control platform event history | Deployment management; change enablement | Cycle time of the review stage on the team board | Weekly | Merging without waiting for review; splitting a change into tiny pieces to pass faster; closing and reopening a pull request to reset the clock | Count closed-and-reopened pull requests; review rounds; post-merge fix rate; protected branch rules that require approval |
| Pull request size | Amount of change in a pull request | Lines added plus lines deleted, excluding generated files, lock files, vendored code, and pure renames, as listed in the repository's ignore rules. Report the median and 85th percentile per merged pull request | lines changed | Version control platform diff statistics | Software development and management | Small batch size; slicing of stories | Weekly | Excluding files from the count; splitting a single change into pieces that cannot be understood separately; padding size with generated code | Review the ignore rules each quarter; check that split pieces build and pass tests alone; read a sample of the smallest and largest |
| Review rounds | Number of loops of author push and reviewer response before merge | Count of distinct "changes requested" or comment-then-push cycles per merged pull request; the first submission is round zero and automated check failures are excluded. Report the median and 85th percentile | count | Version control platform review and push events | Continual improvement; software development and management | Rework signal in the review stage; Definition of Done | Weekly | Approving on the first pass to keep the count low; moving discussion to chat so it leaves no trace; authors pushing many fix-ups in one commit to hide rounds | Post-merge fix rate; sample of zero-round pull requests; keep the discussion in the pull request |
| Review load concentration | How unevenly review work is spread across a team | Share of the team's completed reviews handled by the two busiest reviewers over a rolling 4 weeks; reviews of one's own pull request and bot reviews are excluded. Reported for the team, never by name | percent | Version control platform review events, aggregated to team | Continual improvement; knowledge management | Shared code ownership; collective ownership | Monthly | Splitting reviews into many small approvals to spread the count; assigning reviews to those with spare time but no knowledge | Review the knowledge of the reviewer for risky areas; watch post-merge fix rate by area; keep the metric at team level |
| Stale pull request count | Pull requests open longer than the team's agreed limit | Pull requests still open and not in draft whose age since ready for review exceeds the team limit, counted at snapshot time; drafts are excluded | count | Version control platform open pull request list | Change enablement; continual improvement | Work item age; WIP limit | Weekly | Closing stale pull requests without merging; converting them to drafts to hide them; raising the stale limit | Count of pull requests closed unmerged; count of long-running drafts; review the limit with the team each quarter |
| Post-merge fix rate | Share of merged pull requests followed by a corrective change soon after | Merged pull requests followed within 14 days by a fix, revert, or hotfix linked to the same change / merged pull requests in the period; planned follow-up work labeled as such is excluded | percent | Version control history, linked issues, and incident or change records | Change enablement; incident management | Quality built in; Definition of Done | Monthly | Recording fixes under a new work item with no link; labeling corrective work as planned follow-up; avoiding the metric by delaying the fix past the window | Compare with incident and change failure data; sample of follow-up items; audit of the labels used |
2.8 DORA metrics
Home topic: (see topic 2.8, DORA metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Change lead time | Time for a committed change to reach production | Clock starts at the first commit of the change (or its merge to the main branch, if stated in the definition) and stops when the deployment to production completes successfully; report the median and the 85th percentile of changes deployed in the period; changes never deployed are excluded and reported separately as work in progress | Hours or days | Version control joined to the deployment pipeline | Deployment management; release management; change enablement | Cycle time; Lead time to production | Weekly or per release, reviewed monthly | Moving the start of the clock later, such as starting at merge instead of first commit; merging early to a long-lived branch; excluding hard changes as "not code"; shipping trivial changes through the pipeline to drag the median down | Percentile and age of work in progress; a fixed written start of clock; sample of the slowest 10 percent of changes each quarter; change size distribution |
| Deployment frequency | How often a team deploys to production | Count of successful production deployments of the application in the period / days in the period; failed or rolled back deployments are excluded from the success count; deployments to test environments are excluded | Deployments per day or per week | Deployment pipeline event log | Deployment management; release management | Continuous delivery; releasing at the end of each increment | Weekly | Splitting one change into many trivial deployments; redeploying unchanged builds; counting deployments to staging or empty configuration changes | Change size per deployment; share of deployments that contain user-visible change; change fail rate and rework rate beside it |
| Failed deployment recovery time | How long it takes to recover when a deployment causes a production failure | Clock starts when the failure is detected or reported (the same rule every time) and stops when service is restored for users; report the median and the 85th percentile for failed deployments in the period; incidents not caused by a deployment are excluded | Minutes or hours | Incident record joined to deployment events and monitoring alerts | Incident management; service continuity management | Time to recover; restoration work | Per failure, reviewed monthly | Starting the clock late or closing incidents early; reclassifying a failure as a new incident after a partial fix; raising the severity threshold for "failure" | Recurrence of the same incident within a stated window; clock start taken from monitoring alerts; customer-reported impact duration |
| Change fail rate | Share of production deployments that cause a failure needing remediation | Deployments that required a hotfix, rollback, patch, or incident response / all production deployments in the period; the rule that links a failure to its deployment is written down and applied the same way each time | Percent | Deployment events joined to incidents, rollbacks, and hotfix deployments | Change enablement; incident management | Definition of done; escaped defects | Monthly | Not linking incidents to deployments; counting only failures that cause a full outage; widening the window so failures fall outside it; fixing forward and calling it a new change | Review a sample of incidents against the deployment log each quarter; track the proportion of incidents with a deployment link recorded; deployment rework rate |
| Deployment rework rate | Share of production deployments that were unplanned and made to fix a user-facing problem | Unplanned deployments made in response to a production issue / all production deployments in the period; planned deployments that happen to contain a fix are excluded; the rule for "unplanned" is written down | Percent | Pipeline log tagged by deployment reason, linked to incident or defect records | Change enablement; problem management | Unplanned work; bug fix released outside the plan | Monthly | Labeling fixes as planned work; bundling a fix into a scheduled release; avoiding fix deployments by delaying the fix | Defect and escaped-defect counts from the tracker; age of open production defects; the tag audit on a sample of deployments |
2.9 Operational work and unplanned work
Home topic: (see topic 2.9, Operational work and unplanned work).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Unplanned work ratio | Share of completed work items, by count, that were not in the plan at the start of the period | items completed in the period that entered the board or backlog after the period began / all items completed in the period; clock starts at the planning event, stops at the end of the period; canceled items and items still open are excluded | percent | Issue tracker with item creation time and the planning snapshot | Incident management; service request management | Scope change; Work item types | Monthly | Adding items to the planning snapshot late so they count as planned; leaving urgent work untracked so it never counts; tagging planned items as unplanned to excuse a missed plan | Frozen planning snapshot with a timestamp; unclassified count; a sample of closed items read each quarter to compare the tag with what happened |
| Capacity allocation adherence | How closely actual effort matches the stated split between change work, run work, and improvement work | for each category, absolute difference between actual share and agreed share, summed and halved; actual share is completed items (or logged effort where the team records it) in that category / all completed items; items with no category are reported separately and not dropped | percent points | Issue tracker work type field, and time records where they exist | Continual improvement; capacity and performance management | Capacity allocation or capacity planning | Monthly | Moving items between categories to match the agreed split; splitting one item into several to shift the shares; choosing a split the team already hits | Fixed category definitions written in the working agreement; a sample of item descriptions against their category; planned commitment reliability |
| Interrupt rate | How often demands outside the plan reach the team and reach the people doing planned work | interrupts received by the team in the period / working days in the period, where an interrupt is any ticket, page, message request, or ask logged to the team's intake channel and not already on the plan; duplicates of the same underlying demand are counted once | interrupts per working day | Intake channel log, ITSM queue, alert system, and team interrupt log | Incident management; service request management; monitoring and event management | Interruption log or team working agreement | Weekly | Turning interrupts into silent favors that never reach the log; combining several demands into one entry; discouraging people from asking | Compare the log with intake channel traffic and the alert history; ask the team in the retrospective whether the log matches their experience |
| Expedite rate | Share of completed items that used the expedite lane | items completed in the period that entered the expedite lane / all items completed in the period; the clock starts when the item is marked expedite and stops at completion; items downgraded out of the lane before work began are counted separately | percent | Board lane history or priority field history | Incident management; change enablement (emergency change) | Expedite class of service | Monthly | Keeping urgent work out of the lane to look disciplined, or putting everything in it to get speed; redefining expedite to mean "important" | Lane limit with an entry test; share of expedite items that met the test on review; planned work displacement |
| Planned work displacement | Number of planned items pushed out or abandoned to make room for unplanned work | planned items removed from the period, postponed, or left unfinished with a recorded reason of "displaced by unplanned work" in the period (count); items removed because the goal changed are excluded | count of items | Board change history, with the reason field | Change enablement; continual improvement | Delivery goal protection; scope negotiation | Monthly | Recording displacement as a scope change by choice; letting planned items fail quietly without a reason; avoiding planned items likely to be displaced | Reason field required on every removed or unfinished item; planned commitment reliability; review of reasons at the retrospective |
| Repeat unplanned work share | Share of unplanned items whose cause matches an earlier unplanned item in the lookback window | unplanned items completed in the period that link to the same problem record, alert rule, or cause tag as an earlier item within the lookback window (for example 90 days) / all unplanned items completed in the period; items without a cause tag are reported as a separate unclassified count | percent | ITSM incident and problem records, tracker cause tags | Problem management; known error management | Retrospective action items; recurring defect tags | Monthly | Using a coarse cause tag so repeats are hidden, or a fine one so nothing repeats; closing the problem record to remove the link | Cause tag taxonomy reviewed quarterly; unclassified count; recurrence check after a problem record closes |
| Planned commitment reliability | Share of the items the team planned for the period that it finished in the period | planned items finished in the period / planned items at the start of the period; items added after the start are excluded from both counts | percent | Planning snapshot and tracker completion history | Service level management; change enablement | Forecast reliability | Monthly | Planning small to finish everything; padding estimates; counting a partial item as done; dropping hard items before the period begins | Size and value of items planned compared over time; outcome check on the delivery goal; unplanned work ratio, so a high value is not read as health when the plan was timid |
Part 3: Service Desk, Incident, and Request Metrics
3.1 Service desk metrics
Home topic: (see topic 3.1, Service desk metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Contact volume | Number of contacts received by the desk, by channel and period | count of contacts created in the period, by channel; internal test contacts, duplicate email auto-replies, and outbound calls the desk placed are excluded | count | Telephony or chat platform log; ITSM tool contact records | Service desk | Demand signal in backlog refinement | Weekly | Agents discourage logging by redirecting users to channels that are not counted, or split one contact into several to make a queue look busy; managers target a lower volume | Contact rate per 100 users and a periodic reconciliation of telephony counts with ticket counts; a fixed rule that every channel is counted |
| Contact rate | Contacts relative to the size of the population served, so growth is not mistaken for a problem | contacts in the period / active users or active accounts in the period, scaled to 100 users; the user count is taken from the same period and the definition of "active" is written down | contacts per 100 users | Contact records and the identity or license system | Service desk; service level management | Usage-adjusted demand in product review | Monthly | The denominator is chosen after the fact (for example a broad definition of "active") so the rate looks better | A written, dated definition of "active users" and the raw counts shown beside the rate |
| Time to answer | Wait from the moment a contact enters the queue until a person or an automated answer engages | clock starts when the contact is queued and stops at first human response; abandoned contacts are excluded from this measure and counted in abandonment; report the median and 85th percentile | seconds (phone, chat); minutes or hours (email, portal) | Telephony platform; chat platform; ITSM tool timestamps | Service desk | Responsiveness working agreement | Daily during review windows, weekly in trend | Contacts are answered by an auto-greeting or a transfer to a quiet queue, or the call is picked up and put on hold; email gets an automatic reply that counts as an answer | Define the clock as first human response, and track abandonment and recontact beside it |
| Abandonment rate | Share of contacts that end before anyone engages, by the user | contacts ended by the user before first human response / contacts queued; contacts ended within a short grace period (stated in the definition, for example five seconds) are excluded as accidental | percent | Telephony platform; chat platform | Service desk | Cost-of-delay signal in service review | Weekly | Callers are dropped before they are queued, the grace period is stretched, or a callback offer is counted as an answered contact | Time to answer percentiles, callback completion rate, and a published grace period |
| Handle time | Time the desk spends on a contact | clock starts when a person engages and stops when they finish the contact, including after-contact documentation work; waiting for the user is included only if the definition says so; report the median and 85th percentile, split by contact type | minutes | Telephony platform; chat platform; ITSM tool work log | Service desk; incident management | Effort signal in refinement and capacity planning | Weekly | Calls are rushed, transferred early, or ended before the problem is solved; notes are left thin; work is moved to after-contact time that the clock excludes | First contact resolution, recontact rate, and a sample review of documentation quality by the team |
| First contact resolution rate | Share of contacts resolved at first contact with no later contact on the same matter | contacts resolved during the contact and not followed by a recontact on the same issue by the same user within the recontact window / contacts eligible; calls where only a referral is required and calls the desk is not expected to resolve are excluded | percent | ITSM tool resolution and linkage fields; user confirmation where collected | Service desk; incident management | Definition-of-done check, resolved at first touch | Monthly | Tickets are closed during the call regardless of the result, "same matter" is read narrowly, or hard contacts are classified as "not expected to resolve" | Recontact rate, a one-question user confirmation, and periodic audits of exclusions by the team |
| Recontact rate | Share of resolved contacts followed by another contact on the same matter | contacts followed within the recontact window (for example seven days, set in the definition) by another contact from the same user on the same service or issue / contacts resolved in the earlier period; contacts about a new issue are excluded | percent | ITSM tool linkage and reopen history; contact records | Service desk; incident management | Escaped defect rate | Monthly | Users are asked to open a new ticket for a follow-up, or follow-ups are logged under a different category so they do not link | Linking rules in the tool, a sample audit of unlinked repeat contacts, and user-reported resolution |
3.2 Incident volume and priority
Home topic: (see topic 3.2, Incident volume and priority).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Incident volume by service | Count of incidents opened for a service in a period | incidents with an opening time inside the period, attributed to the affected service; service requests, duplicates merged into a parent record, and records canceled as raised in error are excluded | count | ITSM tool incident records | Incident management | Production defects or unplanned work items per team | Weekly, reviewed monthly | Logging incidents as requests, merging unrelated tickets, discouraging users from reporting, or closing duplicates as "no fault found" | User-reported contact volume and request volume beside incident volume; satisfaction and abandonment from the service desk; sample of requests that read like faults |
| Normalized incident rate | Incidents relative to the usage of the service | incidents opened in the period / usage measure for the same period and scope (active users, sessions, or transactions, chosen and recorded per service) x 1,000; the usage measure must come from a source other than the incident tool | incidents per 1,000 usage units | ITSM tool plus usage data from analytics or monitoring | Incident management; service level management | Defect density per release or per user | Monthly | Choosing the denominator that gives the best figure, or changing the usage definition between periods | Fixed usage measure per service, recorded in the register; raw counts shown beside the rate |
| Priority mix | Share of opened incidents at each priority level | incidents at the priority recorded at opening / all incidents opened in the period, shown for each level; reclassified incidents counted at the opening priority and shown again at the closing priority | percent by level | ITSM tool, including the history of priority changes | Incident management | Severity distribution of defects; class-of-service mix | Monthly | Lowering priorities to look calm or raising them to get attention; assigning a low priority to avoid a response target | Priority reclassification rate; monthly sample review against the impact and urgency matrix; customer-reported impact |
| Priority reclassification rate | Share of incidents whose priority changed between opening and closing | incidents closed in the period whose closing priority differs from the opening priority / incidents closed in the period | percent | ITSM tool audit trail | Incident management | Re-triage rate on the defect backlog | Monthly | Not changing priority when it should change, so the rate looks stable; changing it only at closing to fit the target | Sample of records where impact changed during the incident; reviews of incident timelines |
| Category concentration | Share of incident volume held by the largest categories | incidents in the top five categories by count / all categorized incidents in the period; uncategorized incidents are reported separately as their own share | percent | ITSM tool category and service fields | Incident management; problem management | Defect clusters by component or epic | Monthly | Using a catch-all category, or splitting a big category into several to hide concentration | Share of uncategorized and "other" records; periodic review of the category list; checks of categories against resolution notes |
| Repeat incident rate | Share of incidents that recur for the same service, configuration item, and category within a stated window | incidents in the period with an earlier closed incident for the same service, CI, and category in the preceding window (for example 30 days, set once and recorded) / incidents opened in the period; a reopened record counts as a reopen, not a repeat | percent | ITSM tool and CMDB links | Incident management; problem management | Regression or escaped-defect rate | Monthly | Opening a new incident with different wording or CI to avoid the link; closing early to avoid a reopen | Review of near-duplicate records by text and service; reopen rate; link rate to problem records |
| Reopen rate | Share of closed incidents that were reopened | incidents closed in the period that were later reopened within a stated window (for example 7 days) / incidents closed in the period | percent | ITSM tool status history | Incident management | Reopened defects; rework | Monthly | Asking users to open a new ticket instead of reopening; closing tickets late to avoid reopens | Count of new tickets that reference a recent closed one; customer confirmation of resolution; time-to-close distribution |
| Monitoring-detected share | Share of incidents first raised by monitoring before a user reported them | incidents whose first event is an automated alert / all incidents opened in the period; incidents opened by a person from an alert are counted by the alert time | percent | ITSM tool, monitoring integration | Monitoring and event management; incident management | Alert-driven versus customer-reported defects | Monthly | Creating noisy alerts that open incidents automatically, or letting people re-label user reports as alerts | Alert quality measures such as actionable alert share (see topic 5.5, Monitoring and alert quality metrics); incident source audit |
3.3 Incident response and resolution time
Home topic: (see topic 3.3, Incident response and resolution time).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Time to detect | How long a fault affected users before the organization knew | Clock starts at the first moment of user impact (taken from monitoring data or the confirmed impact start recorded in the review); stops at the first alert or user report. Reported as median and 95th percentile per service. Incidents with no known start are counted and reported separately, not dropped | minutes | Monitoring and alerting platform; incident record with an impact-start field | Incident management; monitoring and event management | Observability and alert quality work (see topic 5.5, Monitoring and alert quality metrics) | Monthly | Setting the impact start later than it was; widening alert thresholds so fewer faults count as incidents; counting only incidents the monitor caught | Share of incidents first reported by users rather than monitoring; periodic review of impact-start estimates against monitoring data |
| Time to acknowledge | How long a raised alert or ticket waits before a person owns it | Clock starts when the alert fires or the ticket is logged; stops when a named person or team accepts it. Auto-assignment does not stop the clock. Reported as median and 95th percentile by priority | minutes | Paging tool; ITSM tool assignment history | Incident management; service desk | On-call response in an SRE rotation | Monthly | Auto-assigning or auto-acknowledging to stop the clock; acknowledging the alert and then doing nothing | Time to first response and time to restore for the same incidents; sample of acknowledged alerts with no later activity |
| Time to first response | How long the user waits for a first human, useful reply | Clock starts when the incident is logged; stops at the first human message or action that addresses the report. Auto-acknowledgements and templated receipts are excluded. Business-hours clock stated | minutes or business hours | ITSM tool communication log | Service desk; incident management | Timely feedback to the user, as in a working agreement | Weekly | Sending a templated or one-word reply to stop the clock | Review a sample of first replies for substance; repeat contact and survey comments |
| Time to restore | How long users were without a working service | Clock starts at the start of user impact; stops when users can again use the service, including by workaround or rollback. Cause fixed later does not extend it. Reported as median and 95th percentile by priority and service | minutes or hours | Incident record with impact start and restore timestamps; monitoring | Incident management | Mean time to restore in DORA terms, read as a distribution (see topic 2.8, DORA metrics) | Monthly | Declaring service restored before users can use it; restoring by suppressing the symptom; logging outages as planned maintenance | Recurrence within a window; user-reported impact after the restore time; share of incidents relabeled after the fact |
| Time to resolve | How long the incident record was open until closed | Clock starts when the incident is logged; stops when it is closed after restoration and user confirmation or a fair wait. Time in "waiting for customer" is shown as a separate, reported share and not subtracted from the headline. Reported as median and 95th percentile by priority | hours or business hours | ITSM tool status history | Incident management | Cycle time for unplanned work (see topic 2.2, Lead time, cycle time, and flow efficiency) | Monthly | Moving tickets into "waiting for customer" or "on hold"; closing after one contact attempt; splitting an incident into children to close the parent early | Share of time in pause states; reopen rate; oldest open incident age; read a sample of closing notes |
| Oldest open incident age | How long the longest-standing open incident has been open | Now minus logged time, for each open incident, listing the oldest few by priority. Pause states are not subtracted | days | ITSM tool open-incident list | Incident management | Work item age on the team board (see topic 2.1, Flow measures) | Weekly | Closing and re-raising the oldest ticket; reclassifying it as a problem or a request to remove it from the list | Link duplicates to originals and report linked age; count of incidents converted to problems or requests each period |
| Active-time share | The proportion of an incident's elapsed time spent in active work rather than waiting | Sum of time in active states / total time from logged to closed, for incidents closed in the period. Active states are those where a person is working the incident; waiting states are listed in the definition | percent | ITSM tool status history | Incident management | Flow efficiency (see topic 2.2, Lead time, cycle time, and flow efficiency) | Quarterly | Logging brief, meaningless work to mark time as active; moving to active states without effort | Compare active time with outcomes such as restore time; sample of work notes |
| Reassignment count | How many times an incident changes owning team before restoration | Count of assignment-group changes from logged to restored, summarized as the median and share of incidents with three or more. Counted per service and priority, never per agent | count | ITSM tool assignment history | Incident management; service desk | Handoff count (see topic 9.3, Collaboration and handoff metrics) | Monthly | Reopening under the same team instead of passing on; passing work by a side channel so the tool shows no handoff | Time to restore and user satisfaction; periodic observation of how work moves between teams |
3.4 Major incident metrics
Home topic: (see topic 3.4, Major incident metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Major incident count | Major incidents declared in a period, by service | Count of incidents that met the declaration criteria and were declared in the period, by declaration time; incidents downgraded within the first hour are listed separately and excluded | count per quarter | ITSM tool incident records with the major incident flag | Incident management | Team or service health review | Monthly report, quarterly trend | Raising the declaration threshold, keeping incidents at "high" priority so they are never declared, splitting one event into several records, or merging several into one | Fixed, versioned criteria; quarterly sample of high-impact ordinary incidents; customer impact and time to declare tracked beside the count |
| Major incident duration | Time that customers were affected | Service restored time minus impact start time, per incident. Impact start is the earliest evidence in monitoring or the first user report, whichever is earlier. Partial restoration is recorded as its own event, and the full restore stops the clock | minutes, per incident | Monitoring timeline, incident timeline in the ITSM tool | Incident management; service level management | Time to recover in delivery metrics (see topic 2.8, DORA metrics) | Per incident; long-window median and maximum quarterly | Restoring the clock to a later impact start, declaring "restored" while users still fail, or closing and reopening a new record | Impact start taken from monitoring; restoration confirmed by a user-facing indicator; reopened and linked records counted as one incident |
| Time to declare | Delay between the start of impact and the declaration of a major incident | Declaration time minus impact start time, per incident. Incidents never declared are found by a quarterly review of ordinary high-impact incidents and are included with a declaration time of n/a (never declared) | minutes, per incident | Monitoring timeline, ITSM tool audit trail | Incident management; monitoring and event management | Definition of ready for escalation in team working agreements | Per incident | Declaring early on everything to look fast, or backdating the declaration to the impact start | Share of declared incidents later downgraded; audit trail of the declaration time; sample of timelines against raw monitoring |
| Customer impact | How many users and how much usage were affected | Affected users (or failed requests) multiplied by minutes affected, per incident. Count only users who attempted to use the service during the impact window. Planned maintenance is excluded | user-minutes, or failed requests | Service telemetry, support contact records | Service level management; incident management | User-facing service level indicators (see topic 5.2, SLIs, SLOs, and error budgets) | Per incident | Narrowing the definition of "affected", counting only users who raised a ticket, or measuring a dependency that stayed up | Impact derived from telemetry as well as contacts; a plain-language impact statement reviewed at the incident review |
| Communication timeliness | Whether affected parties were told on time | Share of major incidents where the first customer-facing notice went out within the target after declaration, and share of scheduled updates sent within the agreed interval. Clock starts at declaration. Internal-only messages are excluded | percent of incidents; percent of updates | Status page history, communication log in the ITSM tool | Incident management; service level management | Stakeholder communication in the team working agreement | Per incident; quarterly summary | Posting a vague notice to start the clock, sending updates with no content, or counting internal messages | Content check of a sample of updates; customer feedback on clarity; only customer-facing notices counted |
| Review completion timeliness | Whether a review took place soon enough to be useful | Share of major incidents with a published review within the agreed number of working days after restoration. Clock stops at publication, not at the first draft. Incidents still inside the window are excluded | percent | Review repository, ITSM tool | Continual improvement; problem management | Improvement follow-up | Quarterly | Publishing a thin document to meet the date, or declaring a review "not needed" | Review quality read by a peer on a sample (see topic 4.2, Postmortem and learning metrics); share of reviews waived is shown |
| Action item follow-through | Whether review actions are completed | Review actions completed by their due date / review actions due in the period. Actions closed as "won't do" are counted separately with a reason, not hidden | percent; count of overdue | Issue tracker linked to the review | Continual improvement; problem management | Backlog items from retrospectives | Monthly | Writing vague or trivial actions that are easy to close, closing actions without doing the work, or relabeling as "won't do" | Action quality sampled; closed actions verified against the system change; "won't do" share and reasons reviewed |
| Repeat major incident rate | Recurrence of the same cause | Major incidents in the period whose recorded cause matches that of an earlier major incident in the previous twelve months / major incidents in the period. Matching is by the cause field, reviewed by hand | percent, with the count shown | Review records, problem records | Problem management | Prevention work in the backlog | Quarterly | Recording each cause as new by choosing different wording, or attributing everything to "human error" | A short cause taxonomy with definitions; cause fields reviewed by someone outside the incident; "human error" as a cause not accepted without a system explanation |
3.5 Service request fulfillment metrics
Home topic: (see topic 3.5, Service request fulfillment metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Request fulfillment time | Elapsed time to deliver a request, shown as a median and a 95th percentile per catalog item | clock starts when the user submits the request, stops when the user confirms delivery or the delivery is recorded; requests canceled by the user are excluded; time waiting for the user is reported separately, not removed | working days or hours | ITSM tool request history | Service request management | Cycle time on the team board (see topic 2.2, Lead time, cycle time, and flow efficiency) | Weekly, trended monthly | Pausing the clock for "waiting for user" whether or not the user is the cause; closing requests before delivery and reopening them as new ones; splitting one request into several small ones | Paused-time share by item, with a sample audit of pause reasons; reopen rate; user confirmation of delivery before closure |
| Fulfillment within target | Share of requests delivered within the target agreed for their catalog item | requests fulfilled within target / requests fulfilled in the period; clock as above, items still open are excluded and counted in backlog age instead | percent | ITSM tool request history; catalog item target table | Service level management | Service level expectation | Monthly | Redefining the target to be easier; counting only requests that finish and ignoring the old open ones; cherry-picking quick items for the target set | Backlog age for open requests; changes to targets logged in the metric register with a reason; the target set covers all items by volume |
| Request backlog and age | Number of open requests and how old the oldest are, by catalog item | open requests at the end of the period (count); age of each open request = report date minus submission date; report the count, the median age, and the oldest age | count and days | ITSM tool open request queue | Service request management | Work in progress and aging work items (see topic 2.3, Work in process and queueing) | Weekly | Closing old requests as "no response" or "stale"; moving requests to a different queue or category so they leave the counted queue | Count of requests closed without delivery, by reason; category and queue transfers reviewed in the monthly meeting |
| Approval wait time | Time a request spends waiting for an approval | clock starts when the approval is requested, stops when it is granted or declined; requests with no approval step are excluded | hours | ITSM tool approval log | Service request management; change enablement | Blocked time or a "waiting" column on the board | Monthly | Approvers approve without reading to keep their time low; requesters chase approvers outside the system so the logged wait is short | Sample review of approved requests against policy; reopen rate and security exceptions for approved items; approval step count per item |
| Request volume by catalog item | Number of requests submitted for each item, with its share of all requests | requests submitted per item in the period; requests resubmitted as duplicates, if identified, are excluded; report the count and the share of total | count and percent | ITSM tool request records | Service catalog management | Demand analysis for backlog shaping | Monthly | Reducing volume by making the catalog harder to find or by discouraging requests; reclassifying requests as incidents or as "general inquiries" | User satisfaction for the catalog; share of contacts classified as "other"; adoption data for the service (see topic 6.3, Service adoption and catalog metrics) |
| Automation share | Portion of requests fulfilled with no manual step after submission | requests fulfilled end to end by automation / requests fulfilled in the period; a request touched by a person for any fulfillment step is counted as manual; approvals by a person do not count as manual fulfillment steps if the policy requires them | percent | ITSM tool fulfillment records and automation platform logs | Service request management; automation within the service value chain | Automation in the definition of done | Monthly | Automating the trivial items to raise the percentage; counting a scripted request that a person still checks by hand as automated; hiding manual steps in a separate ticket | Share weighted by request volume and by hands-on time removed; failed automation and fallback-to-manual rate; sample of "automated" requests traced end to end |
| Request reopen rate | Share of fulfilled requests that the user reopens or re-raises because the result was wrong or incomplete | requests reopened or re-raised for the same item by the same user within 7 days of fulfillment / requests fulfilled in the period; the 7-day window is an example the team writes down | percent | ITSM tool request history | Service request management | Rework rate; defect escape | Monthly | Discouraging reopening by making it hard; telling users to open a new request, which resets the counter | Repeat requests from the same user for the same item within the window; user satisfaction by item; reopening allowed from the notification |
3.6 Knowledge management metrics
Home topic: (see topic 3.6, Knowledge management metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Knowledge link rate | Share of resolved cases that have at least one knowledge article attached at the moment of resolution | cases resolved in the period with at least one linked article / cases resolved in the period. Counts resolution date; excludes major incidents, cases closed as duplicates, and cases auto-closed with no human work | percent | ITSM tool: case and article link tables | Knowledge management; incident management | Definition of done includes capturing what was learned | Weekly for the team; monthly for review | Attaching any article, often a generic or very popular one, to every case before closing; linking after the fact in bulk | Monthly relevance sample of linked cases; share of links that go to the same few articles; link timestamp against resolution timestamp |
| Reuse ratio | Share of article links that point to an existing article rather than to one created during that case | links to articles that existed before the case opened / all article links made on resolved cases in the period. Excludes links added after the case closed | percent | ITSM tool: article creation date against case open date | Knowledge management; continual improvement | Reuse over rework; shared ownership of the codebase and its docs | Monthly | Creating a new article for every case then immediately linking it so it counts as reuse next time; or never creating at all so the ratio looks perfect | Duplicate article rate found by a periodic search; share of cases closed with the reason "no article existed" |
| Article freshness | Share of in-use articles that have been reviewed, or used and confirmed correct, within a stated review window | in-use articles with a review or confirmed-use date inside the window / in-use articles. An article is in use if it was linked to a case or viewed by a reader in the last 12 months (a team choice); drafts and retired articles are excluded | percent | Knowledge base metadata and view log | Knowledge management; service desk | Backlog refinement of documentation; retrospective actions | Monthly | Marking articles as reviewed without checking them; resetting the review date through trivial edits; counting only the articles easy to review | Sample of recently reviewed articles tested against the real service; helpfulness rate and written comments on the same articles |
| Zero-result search rate | Share of knowledge searches that return no article | searches with zero results / all searches. Excludes searches by bots and automated checks; counts each search once even if repeated within a minute | percent | Knowledge base or portal search log | Knowledge management; service desk; service request management | Discovery of unmet user need; backlog input | Weekly | Adding vague or catch-all articles that match any query; stuffing keywords; excluding awkward search terms from the log | Click-through followed by a contact on the same topic within a short window; helpfulness rate; manual read of top search terms |
| Helpfulness rate | Share of reader feedback that says the article helped, shown with the response rate | helpful votes / (helpful votes + not-helpful votes) for articles in the period; response rate = feedback votes / article views | percent, with response rate | Knowledge base feedback widget and view log | Knowledge management; customer experience | Stakeholder review feedback on documentation | Monthly | Prompting only satisfied readers to vote; hiding the not-helpful option; voting from within the team | Response rate and respondent mix shown with the rate; written comments; contact rate after reading the article |
| Time to publish | Elapsed time from when an article draft is created to when it is reviewed and visible to its audience | clock starts at draft creation, stops at publication (or at first approved visible state). Excludes time in a state of "on hold, awaiting product release"; reported as median and 85th percentile | days (median and 85th percentile) | Knowledge base workflow history | Knowledge management | Lead time of a work item from start to done (see topic 2.2, Lead time, cycle time, and flow efficiency) | Monthly | Publishing a thin stub to stop the clock; splitting an article into pieces; moving drafts to a state the clock excludes | Relevance and helpfulness of recently published articles; count and age of drafts in excluded states |
| Contribution breadth | Spread of article creation and improvement across the team, measured without naming people | distinct contributors who created or improved an article in the period / members of the team who resolved cases in the period. Reported for a team only, never as a list of names | percent | Knowledge base edit history joined to team membership | Knowledge management; continual improvement | Collective ownership; pairing and swarming | Quarterly | Making trivial edits so everyone appears as a contributor; asking people to add a sentence to meet a quota | Size and substance of edits sampled; reuse and helpfulness of the articles contributed; no names in the report |
3.7 Self-service and automation metrics
Home topic: (see topic 3.7, Self-service and automation metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Self-service success rate | Share of self-service sessions where the user's need was met without staff contact | Sessions that ended in a completed outcome (request submitted and fulfilled, article marked helpful, reset completed) with no staffed contact about the same need within 7 days, divided by all sessions that started a task. Clock starts at the first meaningful action in the portal, stops at completion or abandonment. Excludes bot traffic, test accounts, and pure browsing | Percent | Portal and identity logs, ticket system, session analytics | Service request management; knowledge management | Customer feedback loop; outcome-based acceptance criteria | Monthly | Counting any completed form or any page view as success; removing the "did this help" prompt when scores fall; excluding hard topics from the denominator | Fall-through rate and a sample of closed sessions read by a person; report the denominator rules |
| Estimated deflection rate | Estimated share of demand resolved at level 0 that would otherwise have reached staff | Compare contact rate per 1,000 active users for a service before and after a self-service change, or against a holdout group, adjusted for known demand shifts. Stated as an estimate with the method named. Excludes contacts that moved to another channel | Percent (estimate) | Ticket system, user population counts, experiment or cohort data | Service desk; incident management | Experiment with a control group; A/B test | Quarterly | Hiding the contact route; adding steps before contact; classifying all fewer tickets as deflection regardless of cause | Contacts per 1,000 active users, user satisfaction on the affected service, and the method written beside the number |
| Fall-through rate | Share of failed self-service attempts that end in a staffed contact on the same need | Staffed contacts opened within 7 days of an abandoned or unsuccessful self-service session by the same user on the same topic, divided by unsuccessful sessions. Clock starts at the end of the session. Excludes unrelated contacts | Percent | Portal logs joined to ticket system on user and topic | Service desk; knowledge management | Escalation path in a definition of done; feedback from support | Monthly | Defining the matching window so short that returns fall outside it; closing the follow-up contact as a duplicate | Repeat contact rate across all channels; review of a sample of returned contacts |
| Self-service adoption (portal-first share) | Share of eligible requests and incident reports raised through self-service channels | Items created via portal, bot, or API, divided by all items for catalog entries that offer a self-service route. Excludes items for which no self-service route exists | Percent | Ticket system channel field, catalog configuration | Service request management; service catalog management | Adoption tracking after a release | Monthly | Forcing all requests into the portal regardless of fit; re-labeling phone-created tickets as portal tickets | Self-service success rate and user effort; share of requests that have no workable portal route |
| Automation coverage | Share of eligible repeatable work completed by automation with no manual step | Items completed by an automated flow end to end, divided by all items of types judged automatable. Counts the type as automatable only if a written candidate list names it. Excludes one-off work and items automation rejected | Percent | Ticket system, automation platform logs, candidate list | Service request management; deployment management | Automation of the definition of done; pipeline-as-code | Monthly | Choosing easy items for the candidate list; growing the denominator with trivial tasks; counting partly manual flows as automated | Written candidate list reviewed each quarter; automation failure and rework rate; manual touch time of the remaining items |
| Automation failure and rework rate | Share of automated runs that failed, needed manual repair, or produced an outcome later corrected | Automated runs that errored, were rolled back, or were followed by a manual fix within 7 days, divided by all automated runs. Clock starts at run start. Excludes planned dry runs | Percent | Automation platform logs, ticket system, change records | Change enablement; incident management | Change fail rate; build and test stability | Weekly | Excluding manual repairs from the count; letting failed runs retry silently until they succeed; labeling failures as "planned dry runs" | Incident and alert records linked to flows; time to detect a failed run; sampled audit of outcomes |
| Manual touch time per request type | Staff effort spent on a request type that is a candidate for automation | Hands-on minutes recorded by staff on items of the type in the period, summarized as median and 85th percentile per item. Estimated by sampling where time is not logged. Excludes waiting time | Minutes per item | Time sampling, ticket work logs | Service request management | Toil tracking; value stream waste | Quarterly | Not logging time for items that look manual; assigning the time to another category; sampling only quiet days | Sampling plan written and reviewed; compare with cycle time and queue age for the same type |
| Level distribution (shift-left share) | Where in the support chain items get resolved | Items resolved at each level (0, 1, 2, 3) divided by all resolved items for the period. Level is the highest tier that did hands-on work. Excludes items canceled before triage | Percent by level | Ticket system resolver group and assignment history | Incident management; service desk | Swarming and escalation patterns; cross-functional teams | Monthly | Raising the share resolved at level 1 by reclassifying escalations, or by closing items at level 1 and reopening at level 2 as new items | Reopen rate and linked-ticket rate; resolution quality sample; customer satisfaction by level |
Part 4: Problem, Change, and Release Metrics
4.1 Problem management metrics
Home topic: (see topic 4.1, Problem management metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Problems opened and closed | Flow of problem records into and out of the open state, by service | Count opened in the period and count closed in the period, each by closing code (fixed, accepted risk, duplicate, cannot reproduce); duplicates are shown but excluded from the "fixed" count | count per period | ITSM problem records | Problem management | Backlog intake and throughput | Monthly | Opening many trivial records; splitting one problem into several; closing records as duplicates or "cannot reproduce" to clear the list | Closing code mix; post-fix recurrence rate; a sample of closed records read each quarter |
| Problem backlog age | How long open problems have been waiting | For each open problem, snapshot date minus the creation date of the record; report the median and 85th percentile of open problems and the oldest, by priority | days | ITSM problem records | Problem management | Work item age on the board | Monthly | Closing the oldest records without a fix; reopening as a new record to reset the clock; reclassifying a problem as a request | Link new records to their originals and report age from the first record; list of closures by reason; review of accepted risks |
| Incident-to-problem link rate | Share of incidents that point at a problem or known error where one is expected | Incidents in the period with a linked problem or known error / incidents in the period with a priority of high or above, or reopened, or in a repeat category; incidents closed as user error or duplicates are excluded | percent | ITSM incident and problem records | Incident management; problem management | Retrospective pattern spotting | Monthly | Linking every incident to a vague catch-all problem to raise the rate | Share of links pointing at the five largest problems; sample of links checked for a real match; recurrence of linked symptoms |
| Time to root cause | How long a diagnosed problem takes to reach a recorded cause | Clock starts when the problem record is created and stops when the cause is recorded and a second person has reviewed it; problems closed without a cause are excluded and counted separately; report the median and 85th percentile | days | ITSM problem records and their audit trail | Problem management | Spike or investigation time-box | Monthly | Recording a quick, shallow cause to stop the clock; naming "human error"; skipping the second reviewer | Post-fix recurrence rate; the cause taxonomy with "human error" not accepted alone; review of a sample of causes against the evidence |
| Known error reuse rate | How often a known error is used when an incident arrives | Incidents resolved with a linked known error or its workaround / incidents in the period whose symptom matches a known error that existed at the time; incidents with no matching known error are excluded | percent | ITSM incident links; knowledge article use | Knowledge management; problem management | Team runbook or playbook use | Monthly | Counting a link added after the incident closed; adding a known error to every incident of a service | Time between incident closure and the link; responder feedback on whether the entry helped; review of entries not used in 90 days |
| Time to permanent fix | How long a problem is exposed from diagnosis to the fix running in production | Clock starts when the cause is recorded and stops when the linked fix change is implemented and confirmed; problems closed as accepted risk are excluded and counted separately; report the median and 85th percentile | days | Problem records; change records or pipeline deployment events | Problem management; change enablement | Cycle time of the fix item | Monthly | Marking the change implemented before the fix is verified; closing as accepted risk to avoid the work | Post-fix recurrence rate; accepted-risk list with owner and review date; verification step before the clock stops |
| Post-fix recurrence rate | Share of fixed problems whose linked symptoms returned | Problems closed as fixed in a cohort quarter with a new matching incident within 90 days of the fix going live / problems closed as fixed in that quarter; the 90-day window is an example and is stated on the chart | percent | ITSM incident and problem records; deployment events | Problem management; continual improvement | Escaped defect or regression rate | Quarterly | Defining symptoms narrowly so that recurrences do not match; widening the closing window so fixes fall in earlier cohorts; delaying linking | Cause taxonomy reviewed by someone outside the owning team; incident link rate; fixed window stated in advance |
| Workaround-only share | Share of known problems protected only by a workaround | Open problems in the known error state with no fix scheduled / open problems in the known error state; accepted-risk problems with a named owner and review date are shown as a separate group | percent | ITSM problem records | Problem management; risk management | Technical debt register | Monthly | Scheduling a placeholder fix with no real date; moving problems to accepted risk; lowering the problem's priority | Age of scheduled fixes that have slipped; accepted-risk list reviewed with a named executive owner; repeat incident cost by problem |
4.2 Postmortem and learning metrics
Home topic: (see topic 4.2, Postmortem and learning metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Review coverage | Share of qualifying events that received a completed review | Qualifying events with a published review within the agreed window / qualifying events closed in the period. Qualifying events are those meeting the written triggers. Events inside the window still open at period end are excluded. | percent | ITSM tool incident records joined to the review repository | Incident management; problem management | Regular team reflection; team working agreements | Monthly | Narrowing the triggers; downgrading severity so events fall outside them; filing a one-line "review" to tick the box | Review quality score; compare incident severity counts to customer-reported impact; audit downgrades |
| Review quality score | Whether a published review meets a short written standard | Reviews in a sample that meet at least [agreed number] of the checklist items / reviews in the sample. The sample is a fixed number of reviews drawn at random each quarter, scored by someone outside the owning team. | percent | Quarterly sample of the review repository with a scoring sheet | Continual improvement; problem management | Definition of done for a review | Quarterly | Writing to the checklist with boilerplate; scoring by the owning team; a predictable sample | Outside scorer; random sample; read two reviews aloud each quarter; track whether actions from high-scoring reviews finish |
| Action closure rate | Share of review actions completed by their due date | Actions completed or formally declined (with a reason) by due date / actions due in the period. The clock starts when the review is published and stops when the owning team marks the action done and a reviewer confirms it. Actions closed as "won't do" are counted separately and reported. | percent | Team backlog or ITSM improvement register, linked to the review | Continual improvement; problem management | Team backlog; improvement actions | Monthly | Setting due dates far out; splitting actions into trivial pieces; closing actions without verification; declaring "won't do" to clear the list | Open action age; declined share with reasons; reviewer confirmation that the change works; cause recurrence rate |
| Open action age | Age of review actions still open | For each open action, today minus publication date of its review. Report the median, the 85th percentile, and the oldest. | days | Team backlog or improvement register | Continual improvement | Work item age; aging work in progress | Monthly | Closing and reopening or recreating an action to reset its age; moving actions to a separate "ideas" list | Link new actions to the originating review and keep the first date; count of actions moved to ideas |
| Cause recurrence rate | Share of events whose cause class matches an earlier event for the same service | Events in the period whose primary cause class matches a review closed in the previous twelve months for the same service / events with a recorded cause class in the period. Events without a recorded cause class are excluded and counted separately. | percent | Review repository cause class field joined to incident records | Problem management; incident management | Escaped defect analysis; retrospective themes | Quarterly | Recording vague or ever-changing cause classes so that nothing matches; using a broad "other" class; linking a repeat to a different class | Share of events in "other"; a periodic reread of reviews by class; a review of the class list itself |
| Near-miss reporting rate | Volume of near misses and weak signals that people choose to report | Near misses logged in the period / active services, shown as a trend per service and never per person. The rate is meant to rise early in a healthy program and then level off. | count per service | Near-miss log, or a tagged field in the issue tracker | Incident management; risk management | Team health check; impediment board | Monthly | Asking for reports in order to hit a number; logging trivial events; or, in the other direction, reading the number as a failure and suppressing reports | Share of near misses that led to a change; no targets on the count; feedback from the safe-to-speak pulse |
| Learning reach | How far a review travels beyond the team that wrote it | Reviews presented or discussed outside the owning team (a shared forum, a cross-team session, or a documented read by a dependent team) within [agreed number] days of publication / reviews published in the period | percent | Forum or meeting records and the review repository | Continual improvement; knowledge management | Stakeholder review; communities of practice | Quarterly | Adding names to a distribution list; presenting at poorly attended sessions; counting a link as a read | Attendance or actual discussion notes; ask dependent teams what they changed after the last review |
| Retrospective action carry-over | Share of team retrospective actions that were finished by the next retrospective | Retrospective actions completed before the next retrospective / retrospective actions agreed at the previous one. Actions deliberately dropped with a reason are removed from both counts. | percent | Retrospective notes or board, kept in the team backlog | Continual improvement | Regular team reflection | Per review period, reviewed quarterly | Agreeing only to trivial actions that are easy to finish; skipping the retrospective; marking items complete | Impact of the actions as judged by the team; retrospective held rate; whether the same theme appears for several weeks |
| Safe-to-speak pulse | Whether people believe they can describe mistakes without blame | Share of responses at or above [agreed level] on a short anonymous question set (for example "I can describe a mistake in a review without fear of blame") / responses received. The pulse is reported only for groups large enough to protect anonymity. | percent | Anonymous pulse survey | Continual improvement; organizational change | Team health check; psychological safety check | Quarterly | Pressuring respondents; surveying only the confident; reporting an average that hides a low-scoring group | Response rate and respondent mix; minimum group size; open comments read in full; whether review language changes |
4.3 Change enablement metrics
Home topic: (see topic 4.3, Change enablement metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Change volume by type | Number of changes completed, split by standard, normal, and emergency | Count of change records that reached implemented status in the period, grouped by type at time of approval; canceled and withdrawn changes are excluded and reported separately; report per service, not per person | Changes per week or month, by type | Change records in the ITSM tool, joined to pipeline deployment events | Change enablement | Throughput of finished work items; release content per increment | Weekly, reviewed monthly | Splitting one change into many small records to look busy, merging many into one to look calm, or leaving informal changes off the books | Reconcile counts against pipeline deployment events each month; track the share of deployments with no matching change record |
| Standard change share | Share of completed changes that took the pre-authorized path | Standard changes completed in the period / all changes completed in the period; a change reclassified after the fact counts under its final type and the reclassification is logged | Percent | Change records with type and reclassification history | Change enablement | Routine work covered by the team's working agreement and definition of done | Monthly | Reclassifying risky work as standard to reach a target, or writing broad standard procedures that cover anything | Quarterly sample review of classification; change failure rate by type (see topic 4.4, Change failure and rework); a log of reclassifications |
| Approval lead time | Time a change waits for an authorization decision | Clock starts when the request is submitted as ready for assessment and stops when the authorization decision is recorded; time spent waiting for the requester to supply information is excluded and shown separately; report the median and the 85th percentile for normal changes in the period; standard changes with no approval step are excluded | Hours or working days | Timestamps on change records or approval events in the pipeline | Change enablement | Wait time in a workflow; time in a review column | Weekly, reviewed monthly | Starting the clock late, stopping it early, pausing it for questions that did not need asking, or approving without reading | The 85th percentile beside the median; sampled review of approvals for substance; change failure rate by approver group, never by individual |
| Automated approval share | Share of authorization decisions made and recorded by pipeline controls or pre-authorized policy | Changes whose approval was granted by a recorded automated check or recorded peer review under a written policy / all changes completed in the period; manual sign-off by a board or manager counts as not automated | Percent | Pipeline logs, code review records, and change records | Change enablement; deployment management | Automated quality gates; peer review as part of the definition of done | Monthly | Adding automated checks that always pass, or counting a peer review with no comments as assurance | Sampled review of automated and peer approvals; escaped defects and failure rate for automatically approved changes; bypass count |
| Approval queue age | How long pending requests have been waiting right now | Age of each change currently awaiting a decision, measured from submission to the moment of the snapshot; report the oldest item and the 85th percentile of the open queue; completed approvals are excluded | Hours or working days | Change records with open approval status | Change enablement | Work item age; aging work in progress | Daily snapshot, reviewed weekly | Closing or withdrawing old requests so the queue looks short, or moving them to a new request with a fresh timestamp | Count of withdrawn and resubmitted requests; request age measured from the first submission |
| Change record completeness | Share of completed changes whose record can answer who, what, why, when, and which service | Changes with all required fields populated and linked to the affected service or configuration item / all changes completed in the period; the required fields are listed in the definition; records created after the change was implemented are flagged | Percent | Change records, version control links, configuration data | Change enablement; service configuration management | Traceability from commit to ticket to deployment | Monthly | Filling required fields with placeholder text, or creating records after the change to satisfy a report | Flag records created after implementation; sample quality review of free text; link-to-commit rate |
4.4 Change failure and rework
Home topic: (see topic 4.4, Change failure and rework).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Change fail rate | Share of changes to production that cause degraded service or need remediation | changes that required a rollback, hotfix, roll-forward fix, or linked incident within the failure window / all changes to production completed in the period; the window starts at completion of the change and stops after a fixed number of days (for example 7), written in the metric register; changes still inside the window are reported separately and excluded from the rate until the window closes | percent | Change records or deployment log joined to the incident tool and the hotfix list | Change enablement; incident management | Definition of done; escaped defects | Monthly, on a rolling window of 90 days | Narrowing the failure window; not linking incidents to changes; classifying a bad change as a "service request" or "maintenance"; fixing forward and calling it a new change; bundling many edits into one change so one failure covers them | Change-to-incident link rate; quarterly sample audit against the incident list; failure-definition agreement; lead time and deployment frequency beside it |
| Emergency change share | Share of changes made through the emergency path | changes recorded as emergency / all changes completed in the period; emergency means the normal assessment was bypassed or shortened on urgency, and pre-authorized standard changes are excluded from both counts | percent | Change record type field | Change enablement | Unplanned work and expedite class of service | Monthly | Routing urgent work through the standard path with a false risk rating; routing ordinary work as emergency to avoid approval; splitting an emergency into several normal changes | Quarterly read of all emergency changes; reasons sorted and reviewed; standard change share and approval lead time (see topic 4.3, Change enablement metrics) |
| Rollback rate | Share of changes that were reversed to a previous version | changes reversed after reaching production / all changes to production in the period; a rollback made before the change reached any users (for example a canary stopped at its first step) is counted separately | percent | Deployment log and release tool | Release management; deployment management | Pipeline and release practices | Monthly | Fixing forward to avoid recording a rollback; keeping a broken version live; holding changes back from production so there is nothing to reverse | Hotfix rate and rework rate beside it; recovery time distribution; sample of incidents against the deployment log |
| Hotfix rate | Share of changes that are urgent patches applied outside the normal release flow | changes tagged or branched as hotfix / all changes to production in the period; the denominator includes the hotfixes themselves | percent | Version control branches or tags and the deployment log | Change enablement; incident management | Unplanned work; expedite | Monthly | Not tagging hotfixes; pushing them through the normal branch; calling a hotfix "a small improvement" | Deployment rework rate; branch and tag audit; unplanned work share (see topic 2.9, Operational work and unplanned work) |
| Deployment rework rate | Share of deployments that were unplanned fixes for a problem in an earlier deployment | deployments to production that fix a defect or failure in a recent earlier deployment, within the same failure window / all production deployments in the period; planned follow-up work from the roadmap is excluded | percent | Deployment log with a "fixes" link or tag, and the work tracker | Change enablement; continual improvement | Rework; escaped defects; failure demand | Monthly | Not linking fixes to the originating deployment; labeling a fix as "planned"; bundling the fix with new features | Required "fixes" link on corrective deployments; sample review of deployments labeled planned; change fail rate beside it |
| Change-to-incident link rate | Share of resolved incidents that record whether a change caused them, and which one | incidents with a completed "caused by change" field (yes or no, plus the change identifier when yes) / incidents resolved in the period; clock stops when the incident is closed | percent | Incident tool and change records | Incident management; change enablement | Post-incident review; definition of done | Monthly | Completing the field with "no" without checking; letting the field default to "no"; closing incidents in bulk to raise the percentage | Sample check of "no" answers in the post-incident review; no default value; reviewer comments on a sample |
| Failure-definition agreement | Agreement between two reviewers about whether a sample of changes failed | sampled changes where two independent reviewers reach the same failure verdict using the written definition / sampled changes; a sample of at least 20 changes drawn at random each quarter | percent | Sample review sheet kept with the metric register | Continual improvement; measurement and reporting | Retrospective | Quarterly | Choosing easy examples for the sample; reviewers who are the people being measured; relaxing the definition so everyone agrees | Random sample drawn by someone outside the team; include borderline cases on purpose; publish disagreements and fix the definition |
4.5 Release and deployment metrics
Home topic: (see topic 4.5, Release and deployment metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Deployment frequency | How often a service receives a successful deployment to production | Count of successful production deployments of the service in the period / days in the period; deployments to test or staging environments, failed or rolled-back deployments, and redeployments of an unchanged build are excluded; configuration-only deployments are counted in a separate series | Deployments per day or per week | Deployment pipeline event log | Deployment management | Continuous delivery; shipping a working increment | Weekly | Splitting one change into trivial deployments; redeploying unchanged builds; counting deployments to staging; counting configuration-only deployments with the main series | Release batch size and the share of deployments with a user-visible change; the separate configuration series; change fail rate beside it |
| Release frequency | How often users receive a change they can reach | Count of release events in the period / days in the period; a release event is the moment a change, or a group of changes, becomes reachable by its intended users (a flag turned on for all users, a final stage of a progressive rollout, or a deployment of a change with no flag); a dark launch, a rollout stopped at a partial stage, and a flag change that only affects internal users are excluded | Releases per week or per month | Flag service audit log joined to the pipeline log and the release calendar | Release management | Releasing at the end of each increment; a potentially shippable increment made available | Weekly, reviewed monthly | Relabeling deployments as releases; counting a flag switched on for internal staff as a release; releasing empty or cosmetic changes to meet a target; counting each stage of a rollout as a separate release | A written definition of release; sample of releases each quarter checked against user-visible changes; batch size and customer-facing change counts |
| Release lead time | How long a finished change waits before users can reach it | Clock starts when the change is merged to the main line and has passed its automated checks (or, if your team writes it so, at the first commit) and stops when the change is released as defined above; report the median and the 85th percentile of changes released in the period; changes not yet released are excluded and reported as an age of work waiting | Hours or days | Version control joined to the pipeline and the flag audit log | Release management; deployment management | Lead time from done to delivered; Lead time to customer | Weekly, reviewed monthly | Starting the clock later, for example at approval instead of merge; excluding changes that waited long as "blocked"; releasing a trivial change first to pull down the median; ending the clock at deployment | The 85th percentile and the age of the oldest waiting change; a fixed written start; a quarterly review of the slowest 10 percent of changes |
| Deployment-to-release gap | How long deployed code stays dark before users can reach it | Clock starts when the change is deployed to production and stops when it is released; report the median and the 85th percentile; changes released at the moment of deployment have a gap of zero and are included; changes deployed and later removed without release are excluded and counted separately | Hours or days | Pipeline log joined to the flag audit log | Release management; deployment management | Dark launch; decoupling deployment from release | Monthly | Turning a flag on for a token user to record the release early; leaving long-dark code out of the sample by calling it "not a release"; deleting dark code to avoid a long gap | Exposure share at release (a threshold for what counts as released); count of changes deployed and removed without release; stale flag count |
| Release batch size | How much change ships together in one release | Median and 85th percentile of the number of merged changes (pull requests or work items) per release in the period; the unit of change is written down; each change is counted once, in the release that made it reachable | Changes per release | Version control and the issue tracker joined to the release event | Release management; change enablement | Small batches; vertical slices of work | Per release, reviewed monthly | Splitting work into artificial pull requests; merging unrelated changes into one to lower the number of releases; counting only the large change in a bundle | Median change size in lines or files as a context measure; review of a sample of releases for unrelated bundling; frequency beside size |
| Feature flag coverage | The share of user-visible changes that were released behind a flag | User-visible changes released in the period that had a flag at the time of release / all user-visible changes released in the period; infrastructure changes and defect fixes that cannot be flagged are excluded, and the rule for "user-visible" is written down | Percent | Flag service joined to the issue tracker and release log | Release management; change enablement | Progressive delivery; experiment-driven development | Monthly | Adding flags to trivial changes to raise the rate; flagging only the safe changes and shipping risky ones unflagged; creating a flag with no way to turn it off in practice | Flag-off test results for a sample of flags; the stale flag count; incident causes that had no flag |
| Stale flag count | How many flags have outlived their purpose | Number of release flags still present in code or configuration more than a stated number of days after the change they guard reached all users; permanent operational flags (kill switches, entitlement flags) are tagged and excluded; the age limit is written down per flag type | Flags, and the median age of release flags in days | Flag service inventory joined to the code search | Release management; knowledge management | Technical debt cleanup; the done criterion of removing a flag | Monthly | Re-tagging release flags as permanent to leave the stale count; deleting the flag record while leaving it in code; extending expiry dates without review | A periodic code search against the register; review of every change of flag type; the age of the oldest release flag |
4.6 Technical debt and known errors
Home topic: (see topic 4.6, Technical debt and known errors).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Known error backlog age | How long open known errors have waited for a permanent fix | Clock starts when the problem record is marked "known error"; stops when the permanent fix is released to production; items closed as "accepted risk" are reported separately and excluded. Report count, median age, and 85th percentile age, by service | days (distribution) | ITSM tool problem and known error records, release records | Problem management | Aging work item chart; bug backlog age | Monthly | Closing old records as "accepted risk" or "will not fix"; splitting one old record into new young ones; resetting the clock by re-registering | Accepted-risk count and age reported on the same page; review of closures by someone outside the owning team; record lineage kept |
| Workaround coverage | Share of open known errors that have a documented, tested workaround an agent can follow | open known errors with a workaround reviewed within the last 6 months / open known errors; closed and accepted-risk items excluded | percent | Knowledge base linked to known error records | Problem management; knowledge management | Runbook or definition of done for operability | Monthly | Writing a vague workaround to satisfy the field; counting a workaround that no agent has ever tried | Workaround use and failure rate in linked incidents; periodic test of a sample of workarounds |
| Incidents linked to open known errors | Incidents whose cause is an open known error, a direct measure of the interest paid in service disruption | incidents in the period linked to a known error that was open when the incident started / all incidents in the period; incidents with no cause link are reported as unlinked, not counted | percent, plus count | ITSM tool incident-to-problem links | Incident management; problem management | Escaped defects; production bug inflow | Monthly | Leaving incidents unlinked, or linking them to a different cause, so the share falls | Unlinked incident share reported beside it; sample review of closed incidents for missed links |
| Debt stock | Number and estimated size of registered technical debt items that remain open | open items in the debt register at period end; size is the sum of coarse effort bands (hours, days, weeks) assigned at registration; unregistered or suspected debt is excluded | count, and effort bands | Debt register in the tracker, tagged by service | Continual improvement; service design | Product backlog items labeled as debt | Monthly | Not registering debt, so the stock looks small; merging many items into one large item; registering trivia to look diligent | Register review against a sample of code reviews and incident postmortems; item size and specificity checks |
| Debt interest | Extra work caused by open debt and known errors, in team time | hours logged in the period against work items tagged with a debt or known error reference (workarounds, manual steps, rework, and extra effort on affected changes) / total team working hours in the period; the repair work itself is excluded and counted under capacity share | percent of working time | Time or effort tags on work items, kept at team level | Continual improvement; problem management | Unplanned work and rework share | Monthly | Under-tagging the work to avoid scrutiny, or over-tagging to win a repair budget; reading the figure as a rating of a team | Sample audit of tagged and untagged items; team-level view only, with no comparison between teams; interest read together with incident links |
| Debt capacity share | Share of delivery capacity spent on retiring debt and known errors | capacity (item count or effort) of completed work items tagged as debt repair or known error fix / all completed work items in the period; items with no tag are excluded | percent | Tracker, completed items by tag | Continual improvement; change enablement | Capacity allocation | Per planning period, reviewed monthly | Tagging ordinary feature work as repair; choosing easy cosmetic items to fill the share | Outcome check: age of the oldest high-interest items and incident links falling; review of what was fixed against the ranking |
| Debt net change | Whether the ledger is growing or shrinking | debt and known error items registered in the period minus items resolved in the period; resolved means fix released, not merged; items closed as "will not fix" are counted in a separate line | count (signed) | Debt register and known error records | Continual improvement | Backlog change by category | Monthly | Resolving many tiny items to offset a few large ones; closing items as "will not fix" to make the count fall | Net change shown by size band and by interest; "will not fix" line reported; recurrence check on resolved items |
Part 5: Service Level, Availability, and Reliability Metrics
5.1 SLA, OLA, and XLA metrics
Home topic: (see topic 5.1, SLA, OLA, and XLA metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| SLA attainment rate | Share of measured items (incidents, requests, or time windows) that met a stated SLA target in the period | Items that met the target divided by items that were measured. Clock starts at the logged time defined in the agreement (for example ticket creation) and stops at the defined stop event (for example restoration confirmed). Excluded: items canceled as duplicates and time inside agreed exclusions such as scheduled maintenance. Report the count beside the share | Percent, with n | ITSM tool timestamps; monitoring data for time-based targets | Service level management; incident management; service request management | Service level objective attainment over a rolling window (see topic 5.2, SLIs, SLOs, and error budgets) | Monthly, with a weekly internal view | Choosing the target to be easy; closing tickets early and reopening later; reclassifying priority downward; excluding hard cases as "out of scope" | Reopen rate and priority reclassification rate; sample of closed tickets read with the customer; review of the exclusion list each quarter |
| Near-miss share | Share of items that met the target but finished inside the last tenth of the allowed time | Items finished at 90 percent or more of the target time and still within it, divided by items that met the target. Same clock as the SLA. n/a for time windows (it applies to time-to-target measures only) | Percent | ITSM tool timestamps | Service level management | Proportion of work close to the service level expectation on a flow chart (see topic 2.1, Flow measures) | Monthly | Stopping the clock a minute before the limit, then continuing the work off the record; splitting a ticket into two shorter ones | Time from last customer contact to confirmed restoration; count of linked or child tickets per incident |
| Clock pause share | Share of total elapsed ticket time spent in states that pause the SLA clock | Total pause time divided by total elapsed time from start to stop, for items in scope. Excludes items with no pause state used. Report by pause state | Percent | ITSM tool status history | Service level management; incident management | Blocked time and wait time in a flow view (see topic 2.4, Value stream metrics) | Monthly | Using pause states on tickets that are not waiting for the customer; moving work into a state that is not counted | Pause reasons audited on a sample; share of pauses reversed by the customer; experience score for paused tickets |
| OLA attainment rate | Share of internal hand-offs that met the OLA target between two teams | Hand-offs completed within the OLA target divided by hand-offs received. Clock starts when the receiving team is assigned and stops when it returns or closes the item. Excluded: items reassigned in error, counted separately | Percent, with n | ITSM tool assignment history | Service level management; incident management | Hand-off wait time and blocked work between teams (see topic 9.3, Collaboration and handoff metrics) | Monthly | Rejecting hand-offs back to the sender to restart the clock; marking items as accepted without starting work | Bounce count per item and total time to restoration across teams; the end-to-end SLA outcome |
| Hand-off wait time (85th percentile) | Time an item waits in a receiving team's queue before work begins | 85th percentile of the time between assignment to the receiving team and the first logged action by that team. Excluded: items waiting on the customer | Hours or minutes | ITSM tool assignment and activity history | Service level management; incident management | Queue time in a flow view (see topic 2.3, Work in process and queueing) | Weekly | Assigning to a person rather than the team queue to hide the wait; logging a token first action | First action quality sampled; time from assignment to the first customer-visible update |
| Experience score by journey | Customer or user rating of how the service supported a defined journey, such as getting a new laptop or recovering from an outage | Mean and distribution of survey ratings on a fixed scale for completed journeys in the period. Report the response rate and respondent mix. Excluded: partial surveys. Not a single average, so show the distribution | Rating scale, with response rate | Short post-interaction survey; journey events from the ITSM tool | Service level management; customer satisfaction practices (see topic 6.1, Customer satisfaction metrics) | Customer feedback and outcome measures | Monthly, with each wave shown | Sending surveys only to satisfied users; asking leading questions; coaching responders to give high ratings | Respondent mix against the population; response rate shown beside the score; open comments read in the review |
| Watermelon gap | Share of reporting periods or services where the SLA reads as met while the experience measure or a user-impact measure reads as poor | Services (or periods) with SLA attainment at or above target and experience below its agreed level, divided by services (or periods) with SLA attainment at or above target. The experience level must be agreed before the period is scored | Percent of green services | SLA attainment and experience score together | Service level management; continual improvement | Retrospective of results against outcomes | Quarterly | Setting the experience level low so the gap stays small; changing the experience measure when it dips | Experience level agreed in advance and changes logged with reasons; trend of the whole distribution |
| Agreement coverage and currency | Share of live services whose SLA, OLAs, and supplier contracts exist and were reviewed within the agreed interval | Services with all three layers documented and reviewed within the interval, divided by live services in the service catalog. Interval is set by the organization. Excluded: services in retirement | Percent | Service catalog (service catalog in ITIL's own spelling) and agreement register | Service level management; service catalog management; supplier management | Working agreements and team charters reviewed on a regular cadence | Quarterly | Marking an agreement as reviewed without a real review; counting a stub document as an SLA | Evidence of the review (attendees, changes, decisions); sample of agreements read for actual content and customer sign-off |
5.2 SLIs, SLOs, and error budgets
Home topic: (see topic 5.2, SLIs, SLOs, and error budgets).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| SLI attainment | The share of valid events that were good, for one indicator of one service | good events / valid events, for the window from the start to the end of the reporting period; events excluded by the SLO document (load tests, planned maintenance announced in advance, if the SLO says so) are removed from both numerator and denominator | percent | Load balancer, application, or synthetic probe telemetry; the monitoring or observability platform | Service level management; monitoring and event management | Definition of done for operability; stakeholder review of service health | Continuous, reported daily and per window | Narrowing "valid" events until the failures drop out, such as excluding retried requests or whole error classes; measuring only the healthiest component; probing only from a favorable location | Publish the SLI definition and exclusions in the SLO document with a change log; compare the SLI with support contacts and user complaints; a regular review of excluded events and their volume |
| SLO compliance | Whether the SLI met the objective over the SLO window, and for how many recent windows | windows in which SLI attainment was at or above the objective / windows evaluated, over the last 12 months; a window that is still open is excluded | percent of windows | SLI attainment history | Service level management; continual improvement | Team goal or working agreement on reliability | Monthly, with a quarterly trend | Setting the objective low enough to always pass; changing the window length after a bad period; redefining a breach as a maintenance period | Objective set with user input and reviewed on a schedule; window fixed in the document; count of exclusions and unplanned changes to the window reported alongside compliance |
| Error budget remaining | The part of the budget not yet spent in the current window | 1 - (bad events so far / allowed bad events for the whole window), where allowed bad events = (1 - SLO) x expected valid events for the whole window; the clock starts at the window start and stops at the window end | percent of budget | SLI attainment and the volume forecast | Service level management; risk management | Release readiness check; planned work input | Daily, reviewed weekly | Reclassifying bad events as excluded; inflating the expected volume so the allowed bad count looks larger; resetting the window early | Allowed bad events computed from the actual volume at the window end; excluded event volume shown beside the budget; window dates fixed in advance |
| Burn rate | The speed at which the budget is being spent relative to the even-spend rate | (bad events / valid events over a look-back period) / (1 - SLO); the look-back period is stated, for example 1 hour or 6 hours | ratio (1 means exactly on budget) | SLI telemetry at fine time resolution | Monitoring and event management; incident management | On-call alerting rules; swarming trigger | Continuous, evaluated in alert rules | Tuning alert thresholds so burn never triggers; using a look-back so long that fast burns average out | Alert coverage test using past incidents ("would this rule have paged?"); actionable alert rate and missed-detection count (see topic 5.5, Monitoring and alert quality metrics) |
| Budget policy adherence | How often the agreed consequence was applied when a trigger in the error budget policy was hit | triggers in the period where the policy action was taken within the agreed time / triggers hit in the period; triggers that were formally waived with a recorded reason are counted separately, not removed | percent | Policy document, decision log, and backlog history | Service level management; change enablement | Working agreement; retrospective follow-through | Quarterly | Granting exceptions routinely; writing a policy with triggers that are never reachable; counting a token reliability ticket as the policy action | Exceptions counted and reviewed separately; share of exceptions in the period; reliability work completed (see topic 4.1, Problem management metrics) |
| SLO coverage | The share of critical user journeys, or of services in scope, that have a current SLO and a working SLI | services or journeys in scope with at least one SLO whose SLI data arrived in the last 7 days / services or journeys in scope; "in scope" is listed in the service catalog (service catalog in ITIL terms) | percent | Service catalog, SLO register, and monitoring configuration | Service catalog management; service level management | Team service ownership list | Quarterly | Adding a trivial SLO to every service to raise the percentage; counting a journey as covered when no data flows | SLI data freshness check (data arrived in the last 7 days); review of whether the SLO covers a critical journey, not a secondary endpoint |
5.3 Availability metrics
Home topic: (see topic 5.3, Availability metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Time-based availability | Share of in-scope time in which the service met the written definition of "up" | (in-scope minutes in window minus unplanned downtime minutes) / in-scope minutes in window. Clock starts at the first failed probe that is later confirmed as user impact, or at the confirmed impact start recorded in the incident review; stops when the service again meets the definition. Planned downtime inside agreed service hours is shown separately, and time outside agreed service hours is excluded from the denominator | percent | Synthetic monitoring results; incident record with impact start and restore timestamps | Availability management; service level management | A time-based SLI for a single system (see topic 5.2, SLIs, SLOs, and error budgets) | Monthly | Probing a trivial page that stays up while the real journey fails; lengthening the probe interval so short outages fall between checks; shrinking the in-scope hours; counting outages as degradation | User-weighted availability and real user monitoring; probe interval stated beside the figure; sample incidents against the monitoring record |
| Request-based availability | Share of valid requests that succeeded | successful valid requests / total valid requests in the window. Valid requests exclude malformed requests and client errors caused by the caller; failures caused by the service, including timeouts, are counted as failures. Reported per service and per user journey | percent | Load balancer, gateway, or application logs and metrics | Availability management; monitoring and event management | Success-rate SLI with an SLO and error budget (see topic 5.2, SLIs, SLOs, and error budgets) | Daily trend, monthly report | Counting easy requests (health checks, cached assets) in the denominator to dilute failures; classifying server errors as client errors; excluding retries that users experienced as failures | Success rate per critical journey, not per request; review the exclusion list; compare with user-reported incidents |
| User-weighted availability | Availability weighted by the users or journeys affected, so an outage at peak counts for more than one overnight | 1 minus (failed user sessions or failed journeys / total user sessions or journeys) in the window. A session counts as failed if a defined critical step failed; partial success is reported as a separate degradation share, not folded in | percent | Real user monitoring; application session logs; analytics events | Availability management; service level management | Journey-based SLI and the experience measures in topic 6.2 (see topic 6.2, Experience level agreements) | Monthly | Choosing the weighting so peak failures matter little; defining a "successful" session so loosely that broken steps still pass | Publish the weighting rule and the journey list; compare with complaint volume and support contacts during outages |
| Unplanned downtime | Minutes in which the service was unavailable without prior approved notice | Sum of outage durations in the window, from confirmed impact start to confirmed restore, for outages not announced and approved through change enablement before they began. Overlapping outages on the same service are merged, not summed. Reported as total minutes, outage count, and the median and 95th percentile of outage duration | minutes | Incident record with impact start and restore timestamps | Incident management; availability management | Time to restore read as a distribution (see topic 3.3, Incident response and resolution time) | Monthly | Reclassifying outages as planned after the fact; delaying the confirmed impact start; splitting one outage into two to look shorter | Planned downtime share, with the rule that an outage announced after it began is unplanned; compare impact start with monitoring data |
| Planned downtime share | Proportion of all downtime that was announced and approved in advance | planned downtime minutes / (planned plus unplanned downtime minutes) in the window. An outage counts as planned only if it was approved through a change record before it began and its start and end times were communicated to users; an overrun beyond the approved window is reclassified as unplanned from the moment the window ended | percent | Change record with approved window; incident record; status page history | Change enablement; availability management | Release and maintenance practices that favor zero-downtime deployment (see topic 4.3, Change enablement metrics) | Monthly | Booking changes as approved windows so that overruns and failures count as planned; inflating the planned share by scheduling needless maintenance | Overrun minutes reclassified as unplanned; change fail rate and emergency change share (see topic 4.4, Change failure and rework) |
| Outage frequency and spacing | How often outages start and how long the service runs between them | Count of outages starting in the window; and for each pair of consecutive outages, the minutes of uptime between the restore of the first and the start of the second, summarized as the median and the 5th percentile. Not reported as a single mean when fewer than ten intervals exist | count; minutes | Incident record; monitoring history | Incident management; problem management | Stability signal alongside change fail rate (see topic 4.4, Change failure and rework) | Monthly | Merging incidents, or opening a new incident only after a long gap, to keep the count low; suppressing alerts so short outages go unrecorded | Alert and incident sampling against raw monitoring events; monitoring coverage and alert quality (see topic 5.5, Monitoring and alert quality metrics) |
| Degradation share | Time in which the service worked but below an agreed quality | Minutes in which the latency, error, or correctness indicator breached its threshold, excluding minutes already counted as downtime / in-scope minutes. Threshold stated per service, for example in the SLO | percent | Monitoring and SLI measurements | Availability management; capacity and performance management | Latency SLI (see topic 5.4, Capacity and performance metrics) | Monthly | Setting the threshold so loose that slow service never breaches it; declaring degraded time as up | Latency percentiles and user-reported slowness reviewed beside the figure (see topic 5.4, Capacity and performance metrics) |
| Measurement coverage | How much of the service's user-facing behavior the availability measurement actually observes | Critical user journeys with an active probe or real user measurement / critical user journeys listed in the service definition | percent | Service definition; monitoring configuration | Monitoring and event management; availability management | Observability coverage and alert quality (see topic 5.5, Monitoring and alert quality metrics) | Quarterly | Listing only the journeys that are easy to probe, so coverage reads as 100 percent; counting a journey as covered by a probe that never runs | Journey list agreed with the service owner and users; probe run history sampled each quarter |
5.4 Capacity and performance metrics
Home topic: (see topic 5.4, Capacity and performance metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Resource utilization | Share of a resource's capacity in use over an interval, reported as a high percentile of the interval series | busy capacity / total capacity, per interval of 1 to 5 minutes; report the median and the 95th percentile over the review window; maintenance windows with the resource drained are excluded | percent | Infrastructure monitoring and cloud platform metrics | Capacity and performance management; monitoring and event management | Operational acceptance criteria in the definition of done; SRE resource signals | Weekly | Averaging over long intervals to hide peaks; counting idle reserved capacity as "used"; reporting only the quietest resources | Peak-hour 95th percentile beside the average; saturation measure; list of resources in scope reviewed against the service map |
| Saturation | Amount of work waiting for a resource that is fully used | queue length, run queue, pending requests, or throttled requests, per interval; report the 95th percentile and the share of intervals with any waiting; intervals with no demand are excluded | count, or percent of intervals | Application and infrastructure telemetry | Capacity and performance management; monitoring and event management | SRE saturation signal; work in process limit on a service queue | Weekly | Raising queue limits so nothing is reported as rejected or throttled; moving the wait into another queue that is not measured | Latency percentile and error rate for the same operation; end-to-end queue time, not one stage; review of all queues in the path |
| Latency percentile | Time taken to answer a request for one user-facing operation, reported at the median, p95, and p99 | response time from request received at the edge to last byte sent, per successful request; failed requests are reported as errors, not as fast responses; measure over a rolling window | milliseconds | Load balancer or gateway logs, tracing, real user monitoring | Service level management; capacity and performance management | SRE latency indicator and service level objective | Continuous, reviewed weekly | Reporting the mean or the median only; dropping slow or failed requests from the sample; measuring from a fast internal location; excluding "outliers" | p95 and p99 always shown; error and timeout rate shown beside latency; real user monitoring compared with server-side timing; raw sample size shown |
| Headroom | Remaining load a service can carry before it breaches its objectives | (tested or modeled breaking load - current peak load) / current peak load; peak is the busiest hour in the window; the breaking load is the load at which the latency objective is first breached in a test, not the hardware maximum | percent, or days at current growth | Load test results and traffic telemetry | Capacity and performance management; service level management | Non-functional requirements and performance tests in the pipeline | Monthly, and before major launches | Choosing a gentle test workload; testing a larger environment than production; defining the breaking point as the hardware maximum | Test workload reviewed against production traffic shape; written list of differences between test and production; headroom retested after relevant changes |
| Forecast error | Difference between forecast demand and actual demand for a period | absolute (forecast peak - actual peak) / actual peak, for a stated horizon; the forecast is frozen at the start of the horizon and not revised afterwards; unforecast one-off events are listed, not removed | percent | Forecast register and traffic telemetry | Capacity and performance management; demand-related planning in service financial management | Release and roadmap forecasting; SRE demand forecasting | Quarterly | Revising the forecast after the fact; setting very wide ranges so that every outcome is "in range"; removing months with surprises as "unforecast events" | Forecast frozen and dated in the register; range width reported with the error; every excluded event listed and reviewed |
| Capacity lead time | Time needed to bring new capacity into service once the need is accepted | clock starts when the capacity request is approved, and stops when the capacity carries production traffic; report the median and the 85th percentile; requests canceled are excluded | days | Request records in the ITSM tool, change records, provisioning logs | Capacity and performance management; service request management; change enablement | Lead time for a platform backlog item (see topic 2.2, Lead time, cycle time, and flow efficiency) | Quarterly | Starting the clock later by delaying approval records; closing requests when the order is placed instead of when capacity carries traffic; splitting requests | Clock defined from approval to carrying traffic; sample of closed requests compared with provisioning logs; count of requests reopened |
| Performance test coverage | Share of critical services with a recent, realistic load test | critical services with a passing load test less than a stated age old, on a representative environment and workload / critical services in the register; the age limit is written down | percent | Test results store and service register | Capacity and performance management; release management | Non-functional tests in the continuous delivery pipeline | Quarterly | Running a trivial test to claim coverage; shrinking the list of critical services; keeping an old passing test on the books | Test age and workload realism recorded; critical service list reviewed against the service catalog and incident history; failed tests reported as well as passes |
5.5 Monitoring and alert quality metrics
Home topic: (see topic 5.5, Monitoring and alert quality metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Alert volume | Number of alerts that notified a human, split into pages and tickets | Count of distinct notifications delivered to a rotation or queue in the period; repeats of the same open alert are grouped into one; alerts handled entirely by automation with no human notification are excluded; report per rotation per week, and the out-of-hours share separately | alerts per rotation-week | Paging and alert-routing tool | Monitoring and event management | Team working agreement on on-call | Weekly | Raising thresholds, adding long delays, or moving alerts from pages to a silent queue so the count falls while problems go unseen; splitting or merging alerts to change the count | Monitored detection share and time to detect; a rule that every demotion is recorded with its reason and reviewed after one quarter |
| Actionable alert rate | Share of alerts after which a person took a useful action | Alerts with a recorded action (fix, mitigation, escalation, or a change to the alert rule) / alerts reviewed in the period; alerts auto-resolved before any acknowledgement are counted as not actionable; unreviewed alerts are reported as a separate count, not dropped | percent | Alert record joined to the review label, ticket, or incident | Monitoring and event management; incident management | Team improvement action on operations | Weekly review, monthly trend | Labeling alerts as actionable after the fact, or taking a trivial action (a comment, an acknowledgement) to qualify; leaving noisy alerts unreviewed so they never enter the denominator | The count of unreviewed alerts shown beside the rate; a sample check by someone outside the rotation; a definition of "useful action" written down |
| False positive rate | Share of alerts that fired when no problem existed | Alerts labeled false positive in review / alerts reviewed in the period; "false positive" means the condition was not a fault and no one would want to be told; a real problem that is too minor to act on is not a false positive | percent | Alert review labels | Monitoring and event management | Retrospective noise review | Monthly | Defining false positives narrowly so that "real but pointless" alerts count as true; closing noisy alerts without a label | Actionable alert rate and the "real but not worth a page" label tracked separately; periodic sampling of closed alerts |
| Detection coverage | Share of in-scope services that have at least one tested alert on a user-facing symptom | Services with a symptom alert that was exercised by a test or a real event in the last 12 months / services in the service catalog scope; the list of in-scope services is fixed at the start of the period | percent | Service catalog, alert rule inventory, test records | Service configuration management; monitoring and event management | Definition of done for a new service | Quarterly | Adding a trivial alert (a ping) to every service to claim coverage; counting alerts that have never been tested | The requirement that the alert watches a user-facing symptom and has been exercised in the last 12 months; monitored detection share |
| Monitored detection share | Share of incidents that monitoring detected before a user or colleague reported them | Incidents whose first signal was an alert / incidents in the period; the clock is the incident open time, and incidents with no recorded first signal are reported as unknown, not as detected | percent | Incident record with first-signal field, alert timeline | Incident management | Incident review (post-incident learning) | Monthly | Recording every incident as "detected by monitoring" even when a user reported it first; creating an alert after the fact and then citing it; leaving the first-signal field empty to avoid a bad number | The unknown count shown beside the share; first-signal evidence taken from the alert timeline, not from memory; customer-reported incidents linked from the support record |
| Time to detect (TTD) | Elapsed time between the start of user impact and the first alert that notified a human | First human-notifying alert time minus impact start time, where impact start is the earliest time the service level indicator breached, as established in the incident review; report the median and the 95th percentile; incidents with no alert are excluded and counted separately | minutes | Incident review, alert timeline, service level indicator history | Incident management; monitoring and event management | Post-incident review | Monthly, per incident | Declaring the impact start later than it was; excluding incidents with no alert; reporting the mean to hide the tail | Impact start taken from the service level indicator history; the no-alert incidents counted and shown; median and 95th percentile reported together |
| Alert concentration | Share of alert volume produced by the noisiest few alert rules | Alerts from the five rules with the most alerts / all alerts in the period; the same alert grouped once; rule count of five is a convention a team may change if it states why | percent | Alert rule inventory and paging record | Continual improvement; monitoring and event management | Retrospective improvement backlog | Monthly | Splitting one noisy rule into several so none of them is in the top five; renaming rules | Report concentration by the underlying fault or service as well as by rule; track total volume and actionable alert rate beside it |
| Alert rule currency | Share of paging rules that have an owner, a runbook link, and a review within the agreed interval | Paging rules meeting all three conditions / all paging rules; rules disabled in the period are excluded | percent | Alert rule inventory | Knowledge management; monitoring and event management | Working agreement on operational readiness | Quarterly | Adding placeholder owners, empty runbook links, or a rubber-stamp review to meet the condition | A spot check that the runbook link resolves and was used in a real response; the practice of testing the runbook in game days |
5.6 Service continuity metrics
Home topic: (see topic 5.6, Service continuity metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| RTO met rate | Share of recovery exercises in which the service was restored within its stated RTO | exercises with restore time <= RTO / exercises run. Clock starts at the declared start of the exercise failure (injection time or scenario declaration) and stops when the service passes its agreed health check for real or synthetic users. Tabletop exercises and exercises with no timed restoration are excluded and counted separately | percent, with the number of exercises shown | Exercise report, timeline from monitoring, service register with RTO | Service continuity management; availability management | Game day outcome; time to recover in delivery metrics | Per exercise; rolled up quarterly | Choosing a small test dataset, an easy scenario, or a rehearsed script; starting the clock late, after the team has begun; loosening the health check so "restored" arrives sooner; setting a generous RTO so every test passes | Record data size, scenario surprise, and health check definition with each result; compare the RTO with the BIA; show each exercise as its own row, including failures |
| RPO met rate | Share of recovery exercises in which data loss stayed within the stated RPO | exercises with measured data loss span <= RPO / exercises that restore data. Data loss span is the time between the last write present after recovery and the moment of failure. Exercises that restore no state are excluded | percent, with the number of exercises shown | Exercise report, comparison of restored data to source or write log | Service continuity management; information security management | Restore drill as part of definition of done | Per exercise; rolled up quarterly | Measuring loss only for the primary table and not for all state; testing a replica that is in sync because no load is running; redefining the RPO after a missed result | Verify data loss against the write log across all data stores in scope; test under realistic write load; keep a change log of objectives with reasons |
| Tested recovery coverage | Share of tier-1 and tier-2 services that had a hands-on recovery test within their agreed test interval | services with a qualifying test inside the interval / services in scope. A qualifying test is hands-on (not tabletop only) and restores the service in the test or production environment. The interval is set per tier | percent, by tier | Service register, exercise calendar and reports | Service continuity management; service catalog management | Game day schedule | Monthly | Counting tabletop discussions as tests; testing a trivially small service to raise the percentage; shrinking the in-scope list by reclassifying services to a lower tier | Require hands-on tests for the tier-1 count; report coverage weighted by service criticality; audit tier changes against the BIA |
| Days since last successful recovery test | Age of the most recent passing recovery test for each critical service | report date minus date of the latest test that met both RTO and RPO. A failed test does not reset the clock. Services never tested are shown as "never" and not as zero | days, per service, with the oldest highlighted | Exercise reports, service register | Service continuity management | Game day schedule; work item age | Monthly | Re-running an easy test to reset the age; labeling a partial test as passed; resetting the date after a paper review | Show the scope of the last passing test; show the oldest age and the services never tested; require both RTO and RPO to have been met |
| Backup restore success rate | Share of attempted restores from backup that completed with verified, usable data | restores that completed and passed a data verification check / restores attempted, over automated and manual restore tests. Backup job success alone is excluded, because a job that ran is not a restore that worked | percent, by data tier | Backup system logs, automated restore verification results | Service continuity management; infrastructure and platform management | Restore drill; operability criteria in definition of done | Weekly for automated tests; monthly in review | Reporting backup job success as restore success; testing only the backups that are known to be good; verifying with a check that cannot fail | Track restores of randomly sampled backups; require a data verification result; review the check itself at each audit |
| Exercise finding closure rate | Share of findings from recovery exercises closed within their agreed time, split by severity | findings closed within target / findings that came due in the period. Clock starts when the finding is recorded in the exercise report and stops at verified fix, which means a re-test or review that confirms it. Findings accepted as risks by a named owner are counted separately | percent, with the count of overdue findings | Exercise report, issue tracker | Service continuity management; continual improvement | Retrospective action items; backlog item age | Monthly | Closing findings without a fix; downgrading severity to relax the due date; splitting one finding into many easy ones; recording few findings in the first place | Verify closure by re-test; report findings per exercise next to the closure rate, since a falling count can mean gentler exercises; review severity changes |
| Plan currency | Share of continuity plans and runbooks reviewed after the last material change to their service, or within their review interval | plans with a review date later than the last material change and inside the interval / plans in scope. Material change means a change record flagged as altering architecture, data stores, dependencies, or suppliers | percent, with oldest unreviewed plan age | Plan repository (version control), change records, service register | Service continuity management; change enablement | Definition of done includes runbook update | Quarterly | Updating a review date without reading the plan; marking changes as non-material; stuffing the plan with generic text that never goes stale | Sample plans and walk through them with someone who did not write them; compare the material-change flag rate with the architecture change history; link currency to test results |
5.7 Toil and on-call metrics
Home topic: (see topic 5.7, Toil and on-call metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Pages per shift | Number of pages delivered to a rotation during one shift | Count of pages delivered between shift start and shift end, one count per shift, after merging duplicate pages for the same alert group within 5 minutes (the merge window is a team setting). Test pages and pages sent in error are excluded. Report the median and 90th percentile across shifts, plus the busiest shift | pages per shift | Paging tool; on-call schedule | Incident management; monitoring and event management | Unplanned work policy; sustainable pace | Weekly review, monthly trend | Raising alert thresholds or silencing alerts so the count falls; merging unrelated alerts into one page; moving pages to a ticket queue that nobody watches | Detection coverage and customer-reported incidents that the monitoring missed (see topic 5.5, Monitoring and alert quality metrics); time to detect (see topic 3.3, Incident response and resolution time) |
| Out-of-hours page share | Share of pages that arrive outside the written working window | Pages delivered outside the working window / all pages delivered, over the period. Window is set per rotation in local time; holidays count as outside the window | percent | Paging tool; rotation calendar | Incident management; monitoring and event management | Working agreement on availability | Monthly | Redefining the working window to be wider; rescheduling jobs and deployments so pages shift into office hours without reducing them; reclassifying pages as "low urgency" | Total page volume next to the share; written working window under change control; a review of what moved |
| Night interruption rate | How often a shift includes at least one page in the protected sleep window | Shifts with at least one page in the protected sleep window (for example 22:00 to 07:00 local, set by the team) / all shifts in the period. A page that is acknowledged automatically with no human response is excluded | percent of shifts | Paging tool; acknowledgement log | Incident management; workforce and talent management | Sustainable pace; team health check | Monthly | Delaying acknowledgement until morning; auto-acknowledging pages; counting only pages that reached a human | Time to acknowledge by hour (see topic 3.3, Incident response and resolution time); pages with no human response reported separately; customer impact at night |
| Toil share of time | Share of a rotation's working time spent on toil | Hours the rotation records against work classified as toil / total working hours recorded by the rotation, over a month. Meetings, training, and leave are excluded from both numerator and denominator. Classification follows the six characteristics of toil, applied by the team | percent of time | Time sampling or task labels in the work tracker; team classification review | Continual improvement; deployment management; service request management | Unplanned work share; capacity allocation in planned work | Monthly, with a quarterly review of the classification | Reclassifying toil as "engineering" or "project work"; recording less than was spent; labeling only what is easy to describe | A periodic audit of classified items by someone outside the rotation; the team's own view of how the week felt; the share of time spent on planned improvement work |
| Toil by source | Distribution of toil hours across named sources such as manual restarts, access requests, certificate renewals, and ticket triage | Toil hours for each source / total toil hours, listing the top five sources and an "other" group. Same exclusions as toil share of time | percent of toil hours by source | Time sampling or task labels in the work tracker | Problem management; service request management | Backlog of improvement items | Quarterly | Splitting a large source into several small ones so none stands out; leaving a source unnamed in "other" | A cap on the "other" group (for example under a fifth of toil hours, a team setting); sampling of the "other" items each quarter |
| Repeat page rate | Share of pages caused by a condition that has paged the rotation before within a stated window | Pages whose alert group or cause code matches an earlier page within 30 days / all pages in the period. A cause code is set by the responder at close; unset codes are reported separately | percent | Paging tool; incident record cause codes | Problem management; incident management | Retrospective actions; technical debt backlog | Monthly | Closing pages with a new cause code each time so matches are missed; widening cause codes until everything is distinct; lengthening or shortening the window | Cause-code audit on a sample; recurrence of the same alert group across incidents (see topic 4.1, Problem management metrics) |
| Rotation depth | How many qualified responders share the pager compared with the number of roles to fill | Number of people who completed on-call readiness and are available for shifts / number of shift positions per rotation cycle. Leave and secondment reduce availability. Report as a ratio per rotation, never per person | ratio | Rotation schedule; readiness checklist | Workforce and talent management | Cross-functional team; skills matrix | Quarterly | Counting people who have not completed readiness; counting people who are rarely available; padding the roster | Share of shifts actually covered by the nominal pool; actual shift count by slot, reported without names; readiness checklist completion |
| Toil removed | Recurring toil hours taken out of the rotation's work by an automation or design change | Estimated monthly toil hours of a source before the change minus the same after the change, measured over at least two cycles after delivery. Hours saved by a one-off cleanup are excluded | hours per month | Time sampling before and after; improvement ticket | Continual improvement; problem management | Improvement item delivered | Quarterly | Counting one-off cleanups as recurring savings; ignoring the effort of building and maintaining the automation; claiming savings without a before-and-after | Before-and-after hours measured over two cycles; maintenance effort of the automation; toil share of time over the following quarters |
Part 6: Customer and Experience Metrics
6.1 Customer satisfaction metrics
Home topic: (see topic 6.1, Customer satisfaction metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| CSAT | Share of responses that are satisfied, for a defined interaction type | responses rated 4 or 5 on a five-point scale / valid responses | percent | Post-interaction survey tied to the ticket or release | Service desk; incident management; service level management | Stakeholder review feedback | Weekly or monthly | Agents coach users to give top marks; surveys sent only after easy tickets; difficult tickets closed without a survey | Automatic survey to every eligible ticket; response rate and respondent mix; reopen rate |
| NPS | Promoters minus detractors for a defined service and audience | percent answering 9 or 10 minus percent answering 0 to 6 | points, range -100 to 100 | Relationship survey, sent at a fixed interval | Continual improvement; service level management | Product outcome review | Quarterly | Surveying only friendly users; timing the survey after a good event; asking face to face; relabeling scale points | Fixed audience and schedule in the register; respondent coverage; read the comments of detractors |
| CES | Average or share-favorable rating of how easy it was to get something done | favorable responses / valid responses, or mean rating | percent or mean | Post-interaction survey tied to the ticket, request, or release | Service request management; service desk | Usability feedback in refinement | Monthly | Removing steps from the form in a way that moves the work elsewhere; asking only after smooth requests | Count of contacts per issue; request fulfillment time and rework (see topic 3.5, Service request fulfillment metrics) |
| Survey response rate | Share of invited users who responded | responses received / surveys delivered | percent | Survey tool and ticket system | Measurement and reporting | Feedback participation in reviews | Monthly | Inviting only people likely to answer; sending the survey to a different list each time | Invitation rule written down; compare invitees with the user population |
| Respondent coverage | How closely the respondent mix matches the user population on agreed dimensions | share of respondents in each group compared with share of users in that group, per group | percentage points | Survey tool joined to the user directory or ticket data | Measurement and reporting | Stakeholder map | Quarterly | Dropping hard-to-reach groups from the comparison; reweighting without saying so | Publish the dimensions and the method; show the unweighted result beside the weighted one |
| Comment theme share | Share of free-text comments assigned to each theme | comments in theme / comments coded | percent | Coded survey comments | Continual improvement | Retrospective themes | Monthly | Coding comments to avoid bad themes; merging themes so none looks large | Second person codes a sample; keep the theme list stable and log changes |
| Detractor follow-up time | Time from a low rating to a documented contact with the user | timestamp of follow-up note minus timestamp of low rating, median and 85th percentile | hours or days | Survey tool and ticket system | Incident management; continual improvement | Feedback loop in the working agreement | Monthly | Logging a note without contacting the user; contacting the user to ask for a better score | Check follow-up notes for content; ask the user in the next survey whether anyone contacted them |
6.2 Experience level agreements
Home topic: (see topic 6.2, Experience level agreements).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Experience score | Average rating of an agreed experience statement, for a service and audience | mean rating across valid responses to one statement on a fixed scale | scale points | Short pulse survey, sent on a schedule | Service level management; continual improvement | Stakeholder review feedback; product outcome review | Monthly | Surveying satisfied users only; timing the survey after good events; rewording the statement so it is easier to agree with | Response rate and respondent mix; stable wording log; read comments |
| Sentiment trend | Direction of tone in free-text comments for a service | share of comments coded positive minus share coded negative, per period | percentage points | Coded survey comments and ticket comments | Continual improvement | Retrospective themes | Monthly | Tuning the tool or the theme list until the trend rises; excluding negative channels | Human check of a monthly sample; keep a fixed coding guide and log changes |
| Friction events per user | Count of signals that a user hit trouble, normalized by active users | (repeat contacts + reopened items + failed logins beyond a set number + abandoned requests) / active users | events per user | Ticket system, identity logs, request portal | Service desk; incident management | Defects found in use | Monthly | Redefining events so fewer count; discouraging repeat contacts by making the desk hard to reach | Contact volume by channel; abandonment rate at the service desk (see topic 3.1, Service desk metrics) |
| Time lost to IT issues | Estimated time users lose to service problems in a period | self-reported minutes lost per user, or measured time in degraded state weighted by users affected | minutes per user | Pulse survey; monitoring joined to user counts | Availability management; incident management | Cycle time lost to blockers | Quarterly | Asking in a way that anchors low estimates; counting only major incidents | Compare self-reported time with measured degraded time; survey wording review |
| Journey completion rate | Share of users who finish a defined journey without abandoning or seeking help | users completing journey without a help contact / users starting journey | percent | Portal analytics; ticket links | Service request management; service catalog management | Task success in usability tests | Monthly | Defining the journey so narrowly that failure is out of scope; steering hard cases to a different channel | Journey definition in the register; help-contact rate and escalations |
| XLA attainment | Share of agreed experience targets met in the period | targets met / targets agreed | percent | The XLA register | Service level management | Delivery goal achievement | Quarterly | Setting targets that are already met; defining a very small set of targets | Review target-setting with users; show attainment with trend and target history |
| Experience gap | Difference between SLA attainment and experience score for the same service | SLA attainment rank minus experience score rank across services, or a written comparison | rank difference or note | SLA reports and pulse survey | Service level management | Definition of done versus user feedback | Quarterly | Choosing the services or periods that look best; changing which SLAs are compared | Fixed comparison set agreed in advance; show all services |
6.3 Service adoption and catalog metrics
Home topic: (see topic 6.3, Service adoption and catalog metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Adoption rate | Share of eligible users who used a service at least once in the period | distinct eligible users with at least one completed use / eligible users | percent | Service usage logs joined to the user directory | Service catalog management; service level management | Feature adoption; product outcome review | Monthly | Mandating use; counting logins or page views as use; narrowing "eligible users" to those who already use it | Completed-outcome definition; compare with satisfaction and effort ratings; publish the eligible-user rule |
| Active use rate | Share of adopters still using the service over time | users active in the period who also used the service in the prior period / users active in the prior period | percent | Usage logs; cohort tables | Continual improvement | Retention in product analytics | Monthly | Auto-enrolling users so they appear active; sending notifications that count as activity | Count only user-initiated completed actions; sample interviews with lapsed users |
| Catalog coverage | Share of requests that arrive through the catalog instead of ad hoc channels | requests created via catalog / all requests, from all channels | percent | Request management tool; mailbox and chat tags | Service request management; service catalog management | Backlog items that carry a written definition | Monthly | Forcing every request into a generic catalog item; closing email requests with "please use the portal" | Request abandonment rate and satisfaction; count how many requests are re-raised by another channel |
| Request abandonment rate | Share of started requests that the user does not submit | requests started but not submitted within 24 hours / requests started | percent | Portal analytics | Service request management | Task abandonment in usability tests | Monthly | Removing form fields that are needed, which shifts work to fulfillment; counting abandoned requests only after a long window | Rework and clarification rate at fulfillment (see topic 3.5, Service request fulfillment metrics) |
| Search success rate | Share of catalog searches that end in a request or a viewed answer | searches followed by a request or knowledge view within the session / searches | percent | Portal search logs | Knowledge management; service catalog management | Findability in user research | Monthly | Counting any click as success; adding irrelevant articles that match every query | Check that the result was used (request made, article rated helpful); read zero-result searches |
| Stale item share | Share of catalog items past their review date or with no use in a set period | items overdue for review or with zero requests in 12 months / items in the catalog | percent | Catalog register | Service catalog management | Backlog age and pruning | Quarterly | Marking items as reviewed without reading them; resetting review dates in bulk | Sample reviewed items for accuracy; show last real change date |
| Request concentration | Share of requests accounted for by the most requested items | requests for the top five items / all catalog requests | percent | Request management tool | Service request management | Pareto of work by type | Quarterly | Splitting popular items into many; merging unrelated items to hide long-tail demand | Fixed item taxonomy with change log; look at the tail by category |
6.4 User and employee experience
Home topic: (see topic 6.4, User and employee experience).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Day-one readiness rate | Share of new starters whose devices, accounts, and access are complete and working at their start time | new starters with all agreed items working at start / new starters in the period | percent | Onboarding requests, identity system, new starter confirmation | Service request management; service catalog management | Team working agreement for onboarding | Monthly | Shortening the agreed list; marking items ready before they work; delaying the official start date | Written list in the register; new starter confirmation; time to productive |
| Time to productive | Elapsed time from start date to the point where a new starter has everything needed for their first real task | median and 85th percentile of days from start date to confirmation from the new starter and their manager | days | Onboarding tracker; short confirmation question | Service request management; continual improvement | Time for a new team member to make a first change | Monthly | Marking the start of the clock later; closing the onboarding record early | Clock definition in the register; manager and new starter both confirm |
| Workaround prevalence | Share of surveyed staff who use unapproved tools or manual steps to get around an official service | respondents reporting a workaround for the service / valid respondents | percent | Pulse survey; sanctioned-tool discovery reports | Service level management; continual improvement | Impediments raised in daily team check-ins | Quarterly | Discouraging honest answers by hinting at consequences; asking only satisfied groups | Anonymity statement; response rate and respondent mix; privacy safeguard compliance |
| Forced-disruption minutes | Time people are interrupted by planned IT actions such as forced restarts, updates, and sign-in prompts | total disruption minutes caused by planned actions / active users in the group | minutes per person per month | Endpoint management logs, aggregated by group | Change enablement; release and deployment management | Interruption-free working time | Monthly | Counting only some kinds of interruption; moving disruptions to the group not measured | Define all planned interruption types; report by group including remote and shift staff |
| Accessibility request resolution time | Time to resolve requests related to accessibility needs | median and 85th percentile of hours from request to confirmed working solution | hours | Request system with an accessibility tag | Service request management; incident management | Inclusive definition of done | Monthly | Closing requests with a partial fix; tagging requests as something else to avoid the clock | Confirmation from the requester that the solution works; review of untagged requests |
| Tool pulse score | Rating of one named tool or service on a short agreed question | mean rating or share favorable across valid responses, per tool | scale points or percent | Pulse survey, rotating tools | Service level management; continual improvement | Feedback from team members on their tools | Quarterly | Surveying only happy users; changing the question; training staff to answer well | Stable wording log; response rate and mix; read comments |
| Privacy safeguard compliance | Share of experience reports that meet the suppression and aggregation rules | reports meeting the rules / reports published | percent | Review of published reports against the privacy rules | Information security management; measurement and reporting | Working agreement on data use | Quarterly | Reporting compliance without independent review; widening groups to hide issues | Periodic review by someone outside the team; publish the rules (the value of k and suppression) |
6.5 Value realization and business outcomes
Home topic: (see topic 6.5, Value realization and business outcomes).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Benefit realization rate | Share of expected benefits that were observed at the agreed review date | benefits with measured result at or above the agreed threshold / benefits expected with a review date in the period | percent | Benefits register with owners, baselines, and review dates | Continual improvement; service value system governance | Outcome review with stakeholders | Quarterly | Setting low thresholds; moving the review date; redefining the benefit after the fact | Threshold and date fixed at approval; evidence quality share; owner outside the delivery team |
| Time to first value | Time from the start of work to the first measurable benefit for users | days from first work started to the first date the benefit indicator moved as expected | days | Work tracker and benefit indicator | Service design; release and deployment management | Continuous delivery of value | Per initiative | Choosing an early indicator that moves for the wrong reason; starting the clock late | Indicator and clock defined in the register; confirm with the benefit owner |
| Hypothesis check rate | Share of released changes whose stated value hypothesis was checked after release | changes with a recorded post-release check / changes released that carried a hypothesis | percent | Hypothesis log linked to release records | Continual improvement; change enablement | Learning from released work | Monthly | Writing vague hypotheses that always pass; checking only successful changes | Sample hypotheses for testability; include null and failed results in the review |
| Evidence quality share | Share of claimed benefits that have a baseline and a stated method of comparison | benefit claims with baseline and method / benefit claims reported | percent | Benefits register review | Measurement and reporting | Honest reporting of outcomes | Quarterly | Backfilling baselines; describing any comparison as a method | Baseline dated before the change; review by someone outside the team |
| Outcome indicator movement | Change in a chosen outcome indicator compared with its baseline and with a comparison where available | (indicator after minus indicator before) with the comparison group's change reported alongside | indicator units | Product analytics, service data, finance | Service level management; continual improvement | Key result progress | Monthly | Picking a favorable period or group; ignoring confounders | Pre-registered period and group; list of confounders considered |
| Business-impact hours | Hours in which a business process was degraded or stopped because of service issues | hours of degraded or stopped process attributed by process owners to IT service causes | hours | Incident records joined with process owner confirmation | Incident management; availability management | Business impact review | Monthly | Process owners inflating or deflating attributions; incidents reclassified to avoid attribution | Attribution rules written and logged; compare with incident and availability records |
| Outcome-linked capacity share | Share of team capacity spent on work linked to a stated outcome | capacity on items linked to a recorded outcome / total capacity | percent | Work tracker with outcome field | Service value system; portfolio governance | Work aligned to the product goal | Quarterly | Tagging all work with a generic outcome; inventing outcomes for routine work | Outcome list reviewed with stakeholders; sample items for link quality |
Part 7: Asset, Configuration, and Financial Metrics
7.1 IT asset management metrics
Home topic: (see topic 7.1, IT asset management metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Inventory accuracy | Share of sampled assets whose record matches what is found | sampled assets where the record matches physical or technical evidence on all agreed fields / assets sampled | percent | Audit sample compared with the asset register and discovery data | IT asset management; configuration management | Definition of done includes registering the asset | Quarterly | Sampling the easy assets; auditing only after a clean-up; counting a match on fewer fields | Random sample drawn by someone outside the team; fixed field list; sample from both directions |
| Discovery coverage | Share of expected assets seen by discovery in the period | assets seen by at least one discovery source in the last 30 days / assets in the register that discovery can see | percent | Discovery tool reports joined to the register | IT asset management; monitoring and event management | Infrastructure as code state matches reality | Monthly | Narrowing "expected assets" to what discovery can see; excluding hard-to-scan networks | Document exclusions; compare with procurement and cloud billing |
| Reconciliation rate | Share of assets matched across independent sources | assets matched in both register and a second source (for example procurement, identity, or cloud billing) / assets in either source | percent | Register, procurement, identity, cloud billing exports | IT asset management; supplier management | Single source of truth for environments | Monthly | Choosing a second source that is derived from the first; auto-matching on weak keys | Use truly independent sources; spot-check matches by hand |
| Ownerless asset share | Share of assets with no named, valid owner | assets with no owner or an owner who has left / assets in the register | percent | Register joined to the people directory | IT asset management; information security management | Clear ownership of services and components | Monthly | Assigning a catch-all team as owner; entering a placeholder person | Count of assets owned by catch-all teams; owner confirmation sample |
| Lifecycle stage completeness | Share of assets with a current lifecycle stage and the dates that stage requires | assets with stage and required dates recorded / assets in the register | percent | Register | IT asset management; release and deployment management | Environment lifecycle tracked in the pipeline | Monthly | Filling in default dates; setting every asset to "in use" | Compare stage with evidence in the audit; look at the age distribution |
| Time to record | Delay between an asset change and its update in the register | median and 85th percentile of hours or days from the change event to the register update | days | Change, procurement, or pipeline events compared with register timestamps | IT asset management; change enablement | Automated registration in the pipeline | Monthly | Backdating change events; recording the event time as the record time | Compare with source system timestamps; audit trail on edits |
| Unaccounted asset rate | Share of expected assets that cannot be located or explained at audit | assets expected but not found, and not explained by an approved disposal / assets expected | percent | Audit results | IT asset management; information security management | Retrospective finding on lost items | Per audit | Writing assets off without approval; reclassifying them as disposed | Disposal approval and evidence rate; compare write-offs with finance records |
7.2 Software asset and license metrics
Home topic: (see topic 7.2, Software asset and license metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Effective license position | Comparison of entitlements held with usage found, per product, in the license's own counting unit | entitlements held minus deployments or users found, per product | units (surplus positive, shortfall negative) | Entitlement records, discovery tool, identity system | IT asset management; supplier management | Visible catalog and usage data for teams | Monthly for key products; quarterly for others | Counting in a favorable unit; leaving shadow deployments out of discovery | Count in the license's own unit; compare with expense and identity data; legal review of the counting rule |
| License utilization rate | Share of paid entitlements that are in active use | entitlements with activity in the last 90 days / entitlements paid for | percent | Vendor usage reports, identity logs, entitlement records | IT asset management; financial management | Retrospective on tool value | Monthly | Shortening the activity window; counting logins by bots or service accounts as use | Fixed window in the register; exclude non-human accounts; compare with vendor usage report |
| Shelfware cost | Annual cost of entitlements that are paid for and unused | sum of (unused entitlements times unit cost) | currency per year | Entitlement records, usage data, invoices | IT asset management; financial management | Waste reduction in the toolchain | Quarterly | Renegotiating or canceling just before the review to reduce the number; ignoring subscriptions on cards | Include all spend sources; track cost at the start of the notice window |
| Unsanctioned application count | Number of software applications in use that are not in the approved catalog | applications seen in expense data, single sign-on logs, or network data that are not in the catalog | count | Expense reports, identity provider, network and endpoint data | IT asset management; information security management | Teams choosing tools with visible support | Monthly | Approving everything into the catalog to reduce the count; hiding usage by using personal accounts | Catalog review criteria; look at spend and identity data; ask teams what they need |
| Renewal readiness | Share of renewals that had a usage review before the notice date | renewals with a completed usage review at least 90 days before notice date / renewals due in the period | percent | Contract register and review records | Supplier management; financial management | Planning ahead for change | Quarterly | Holding a perfunctory review; setting the notice date later | Review checklist with required inputs; contract dates held by procurement |
| SBOM coverage | Share of production services with a current software bill of materials | services with an SBOM generated in the last release cycle / production services | percent | Build pipeline outputs, service catalog | IT asset management; information security management | Definition of done includes dependency visibility | Monthly | Generating SBOMs that omit transitive dependencies; counting build output that is not released | Define depth in the register; spot-check an SBOM against the deployed artifact |
| Open-source review coverage | Share of components in production with a recorded license identification and policy decision | components with license and decision recorded / components found in SBOMs | percent | Software composition analysis tool, policy register | IT asset management; supplier management | Dependency review in the pipeline | Monthly | Marking components as reviewed without a decision; accepting "unknown" licenses | Count components with unknown license; review a sample of decisions |
7.3 Hardware asset lifecycle metrics
Home topic: (see topic 7.3, Hardware asset lifecycle metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Age profile | Distribution of device age by class, and share beyond the planned life | median age and 85th percentile age; share of devices older than the planned life for the class | years; percent | Asset register purchase and deployment dates | IT asset management; capacity and performance management | Technical health review | Quarterly | Replacing healthy devices to lower the average; excluding old devices by reclassifying them as spares | Failure rate by age band; idle device share; review of reclassification |
| Refresh on-time rate | Share of devices reaching planned replacement that were replaced within the planned window | devices replaced within the window / devices that reached planned replacement in the period | percent | Asset register and refresh plan | IT asset management; service request management | Planned maintenance of the working environment | Quarterly | Widening the planned window; deferring planned dates by editing the plan | Plan changes logged with reasons; compare with failure and user feedback |
| Failure rate by model | Failures per 100 devices per year, by model and age band | hardware failures in the period / average devices in service, scaled to a year, times 100 | failures per 100 per year | Incident and repair records joined to the register | Incident management; IT asset management | Defects in the working environment | Quarterly | Coding failures as user damage or software faults; delaying repair records | Sample failure coding; compare repair records with incident records |
| Idle device share | Share of issued devices with no activity in a set period | devices with no sign-in or network activity in 60 days / devices issued | percent | Endpoint management logs, aggregated by class | IT asset management; financial management | Waste reduction | Monthly | Counting scheduled background activity as use; reassigning idle devices to ghost users | Use human sign-in as the activity signal; spot-check assignments |
| Replacement lead time | Time to replace a failed or lost device with a working one | median and 85th percentile of hours or days from report to the user having a working device | days | Incident and request records | Incident management; service request management | Time to unblock a team member | Monthly | Stopping the clock at dispatch; closing the request before the user has a working device | Clock ends at user confirmation; survey of recent replacements |
| Secure disposal completion | Share of retired devices with recorded evidence of data erasure or destruction | retired devices with evidence of erasure or destruction / devices retired | percent | Disposal records and wipe certificates | Information security management; IT asset management | Definition of done for retiring equipment | Monthly | Recording erasure without evidence; certificates not matched to serial numbers | Match certificates to serial numbers; audit a sample with the disposal partner |
| Reuse and recycling rate | Share of retired devices that were reused, refurbished, or recycled through an approved channel | devices reused, refurbished, or recycled through an approved channel / devices retired | percent | Disposal and partner records | IT asset management; supplier management | Sustainability goal in planning | Quarterly | Counting devices sent to a broker with unknown downstream handling as recycled | Require certified partners and downstream reporting; sample audits |
7.4 Configuration and CMDB quality metrics
Home topic: (see topic 7.4, Configuration and CMDB quality metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| CI completeness | Share of in-scope CIs with all required attributes populated with valid values | in-scope CIs with every required attribute valid / in-scope CIs | percent | CMDB, attribute rules | Service configuration management; IT asset management | Definition of done includes service description | Monthly | Filling required attributes with defaults or placeholders; narrowing the required list | Count default and placeholder values; fixed required list; accuracy sample |
| CI accuracy | Share of sampled CIs whose record matches evidence on the required attributes | sampled CIs matching on all required attributes / CIs sampled | percent | Audit sample compared with the live system | Service configuration management | Infrastructure as code state matches reality | Quarterly | Sampling easy classes; auditing after a clean-up | Random sample drawn independently from both directions; fixed method |
| Dependency coverage | Share of critical services whose upstream and downstream dependencies are mapped and reviewed | critical services with a dependency map reviewed in the last 90 days / critical services | percent | CMDB relationships and review records | Service configuration management; availability management | Architecture and service ownership review | Quarterly | Marking maps as reviewed without reading them; mapping only trivial dependencies | Impact prediction hit rate; spot-check a map against live traffic |
| Impact prediction hit rate | Share of incidents and changes where the services actually affected were in the CMDB's predicted impact | incidents or changes where all affected services were predicted / incidents or changes reviewed | percent | Post-incident reviews and change records compared with CMDB queries | Incident management; change enablement | Blameless review finding on missing dependencies | Quarterly | Choosing incidents that went well; recording affected services narrowly | Review all significant incidents; reviewers outside the owning team |
| Duplicate CI rate | Share of CIs that duplicate another CI | CIs flagged as duplicates by matching rules and confirmed in review / CIs in scope | percent | CMDB matching report and review sample | Service configuration management | Single source of truth | Monthly | Merging distinct CIs to lower the rate; loosening matching rules | Sample merges for correctness; log merge rules |
| Update latency | Delay between a change to a CI in the real world and its update in the CMDB | median and 85th percentile of hours or days from change event to CMDB update | hours or days | Change events and pipeline events compared with CMDB timestamps | Service configuration management; change enablement | Automated registration in the pipeline | Monthly | Backdating change events; counting only automated updates | Compare event and update timestamps from source systems; audit trail |
| CMDB use rate | Share of incidents and changes that reference CIs, and of those, share where users report the record helped | records referencing a valid CI / incidents and changes in the period; plus share of reviewed records where the CI data helped | percent | ITSM tool, short feedback prompt | Incident management; change enablement | Teams using the shared record in their work | Monthly | Adding CI references as a formality; making the field mandatory with any value | Check that referenced CIs are relevant; the feedback question on helpfulness |
7.5 Service cost and unit economics
Home topic: (see topic 7.5, Service cost and unit economics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Cost per service | Fully loaded annual cost of a named service, using documented allocation rules | direct costs + allocated shared costs for the service in the period | currency per year | General ledger, cost center data, cloud and license bills, time or activity data | Service financial management; service catalog management | Cost of a persistent product team and its platforms | Quarterly | Shifting costs to other services through the allocation rule; leaving unfavorable costs unallocated | Allocation coverage; rules published and reviewed by owners; compare totals with the ledger |
| Unit cost | Cost per unit of something users value, such as per active user, per transaction, or per resolved request | cost per service in the period / units delivered in the period | currency per unit | Cost per service and volume data | Service financial management; service level management | Cost to serve per outcome | Quarterly | Raising the denominator with low-value units; cutting quality to cut cost; changing the unit | Quality companion measure; fixed unit definition; outcome checks |
| Allocation coverage | Share of IT spend attributed to a named service or declared as shared overhead | spend attributed to services or declared overhead / total IT spend | percent | General ledger and allocation model | Service financial management | Visible cost of each team's work | Quarterly | Declaring large amounts as shared overhead to avoid attribution | Overhead share reported; review of what is declared overhead and why |
| Run, change, and improvement split | Share of spend or capacity going to running services, changing them, and improving them | spend or capacity in each category / total | percent | Ledger tags, work tracker work types | Service financial management; continual improvement | Capacity allocation by work type | Quarterly | Relabeling run work as improvement or change; tagging at the end of the period | Tag at intake; sample items for type; compare with incident and request data |
| Forecast variance | Difference between forecast and actual cost, by service | (actual minus forecast) / forecast | percent | Forecast log and ledger | Service financial management | Forecast accuracy | Monthly | Padding forecasts; revising the forecast late in the period | Forecast logged at the start; compare forecast ranges with actuals over time |
| Showback dispute rate | Share of showback or chargeback line items that service owners challenged and that were changed | line items changed after challenge / line items issued | percent | Showback system and dispute log | Service financial management | Retrospective on shared costs | Quarterly | Discouraging disputes; changing line items without a rule change | Review disputes and outcomes; check whether rules changed after repeated disputes |
| Persistent-team funding share | Share of delivery and operations spend funded as stable team capacity for a service | spend on persistent service teams / total delivery and operations spend | percent | Ledger and organization chart | Service financial management; organizational change | Teams built around services and motivated people | Annual | Renaming projects as persistent teams without changing funding or ownership | Check team stability and ownership over time; service health measures |
7.6 FinOps and cloud cost metrics
Home topic: (see topic 7.6, FinOps and cloud cost metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Allocation coverage | Share of cloud spend attributed to an owning team or a declared shared pool | spend with a valid owner and service tag, or in a declared shared pool / total cloud spend | percent | Cloud billing export, tag policy | Service financial management; IT asset management | Team ownership of what it runs | Weekly | Tagging everything to a catch-all owner; declaring large amounts as shared | Share of spend owned by catch-alls; shared pool size and review; owner confirmation sample |
| Cloud unit cost | Cost of cloud resources per unit of something users value | cloud cost for the service in the period / units delivered in the period | currency per unit | Billing data joined to service volume | Service financial management; service level management | Cost to serve per outcome | Monthly | Choosing a unit that grows cheaply; cutting reliability to cut cost | Fixed unit definition; reliability and quality companions |
| Waste rate | Share of spend on resources that are idle or clearly oversized | spend on idle or oversized resources, per agreed rules / total spend on the scoped resources | percent | Utilization metrics and billing | Capacity and performance management; financial management | Waste reduction in the toolchain | Weekly | Narrowing the definition of idle; moving waste to an account out of scope | Rules in the register; scan all accounts; sample resources the rules exclude |
| Commitment coverage | Share of eligible steady usage covered by discounted commitments | eligible usage covered by commitments / eligible usage | percent | Billing and commitment reports | Service financial management; supplier management | Planning for predictable demand | Monthly | Committing to inflated baselines to chase a high percentage | Commitment utilization; check the baseline against usage history |
| Commitment utilization | Share of purchased commitments that were used | commitment hours used / commitment hours purchased | percent | Commitment reports | Service financial management; supplier management | Value from planned investment | Monthly | Adding eligible usage that is not needed to fill commitments | Compare with growth in real demand; unit cost |
| Forecast variance | Difference between forecast and actual cloud spend, by team and in total | (actual minus forecast) / forecast | percent | Forecast log and billing data | Service financial management | Forecast accuracy | Monthly | Padding forecasts; revising them late | Log the forecast at the start; track range width and hit rate |
| Anomaly acknowledgement time | Time from a cost anomaly alert to a recorded decision by the owner | median and 85th percentile of hours from alert to owner response | hours | Anomaly alerts and ticket records | Monitoring and event management; incident management | Responsiveness to a production signal | Monthly | Acknowledging alerts without looking; closing alerts automatically | Record a decision and outcome; sample alerts for quality of response |
7.7 Return on investment and business case
Home topic: (see topic 7.7, Return on investment and business case).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Return on investment | Net gain relative to cost over a stated period | (total benefits minus total costs) / total costs over the period | percent | Business case, ledger, benefits register | Service financial management; continual improvement | Outcome review against funding | At decision and at each review | Choosing a long period or counting soft benefits; leaving out operating cost | Fixed rules for period and cost scope; benefit evidence quality; independent review |
| Total cost of ownership | Whole-life cost of a service or asset over a stated period | acquisition + operation + support + change + training + disposal costs over the period | currency | Ledger, cost models, supplier contracts | Service financial management; IT asset management | Cost of a persistent team and its platforms | At decision and annually | Omitting support, training, change effort, or disposal; using optimistic volumes | Checklist of cost categories; compare with actual TCO of similar past work |
| Payback period | Time for cumulative net benefits to equal the initial investment | time at which cumulative benefits minus cumulative costs reaches zero | months | Business case cash flows | Service financial management | Time to first value, extended to cost recovery | At decision and at each review | Defining the start late; counting benefits that are not realized | Clock definition fixed; compare with realized benefit accuracy |
| Net present value | Present value of expected benefits minus present value of costs, at a stated discount rate | sum over periods of (benefit minus cost) / (1 + discount rate) to the power of the period | currency | Business case cash flows, finance policy on the discount rate | Service financial management | Value-based prioritization | At decision | Choosing a low discount rate; extending the horizon | Discount rate set by finance policy; sensitivity analysis shown |
| Cost estimate accuracy | Ratio of actual to estimated cost for completed initiatives | actual cost / estimated cost at approval, per initiative and as a distribution | ratio | Business case records and ledger | Service financial management; continual improvement | Forecast accuracy | Quarterly | Revising the baseline estimate after the fact; excluding overruns as scope changes | Estimate frozen at approval; log scope changes with approval; show total cost to complete |
| Benefit estimate accuracy | Ratio of realized to expected benefit for completed initiatives, using the evidence rules for benefits | realized benefit / expected benefit at approval, per initiative and as a distribution | ratio | Business case records and benefits register | Continual improvement; service value system governance | Outcome review with stakeholders | Quarterly | Counting benefits that were not measured; redefining the benefit | Benefits register rules; owner outside the delivery team confirms |
| Evidence-based stop rate | Share of funded initiatives that were stopped or reshaped at a stage gate because evidence changed the picture | initiatives stopped or reshaped on evidence at a gate / initiatives reaching a gate | percent | Stage gate decision log | Continual improvement; portfolio governance | Learning from released work | Quarterly | Stopping low-value work to inflate the rate; never stopping anything | Read with accuracy measures; review reasons for stops and continues |
Part 8: Security, Risk, Compliance, and Supplier Metrics
8.1 Security incident and vulnerability metrics
Home topic: (see topic 8.1, Security incident and vulnerability metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Exposure window | Time a known vulnerability remains open on in-scope assets, by priority band | median and 85th percentile of days from the date it was known to apply to the asset to the date a fix or accepted mitigation is verified | days | Vulnerability scanner, ticket system, change records | Information security management; problem management | Time to fix a defect in the backlog | Weekly | Closing findings without verification; changing the start date; reclassifying severity | Verification step by someone outside the fixing team; start-date rule in the register; severity change log |
| Patch compliance | Share of in-scope assets that meet the patch policy window for their class | assets patched within the policy window / assets in scope that required a patch in the period | percent | Endpoint and server management tools, asset register | Information security management; release and deployment management | Dependencies kept current in the pipeline | Weekly | Excluding hard-to-patch assets from scope; counting a patch as applied when the system was not restarted | Scope changes logged; verify installed version from the asset, not the ticket |
| Overdue critical findings | Count and age of critical-priority findings past their policy deadline | number of critical findings beyond deadline; age of the oldest | count; days | Vulnerability management system | Information security management; risk management | Security defects exceeding the agreed limit | Weekly | Splitting findings or merging them; downgrading severity | Count by unique vulnerability and asset; review all severity changes |
| Scan coverage | Share of in-scope assets assessed within the required interval | assets scanned successfully in the last interval / assets in scope | percent | Scanner reports joined to the asset register | Information security management; IT asset management | Pipeline checks run on every build | Weekly | Scanning a narrower set; counting a scan that failed to authenticate | Coverage against the asset register; scan quality (authenticated, complete) |
| Time to contain | Time from detection of a confirmed security incident to containment | median and 85th percentile of hours from detection to containment | hours | Incident records | Incident management; information security management | Time to restore service after a failure | Per incident, reviewed monthly | Starting the clock later; declaring containment early | Clock starts at first detection signal; verify containment with evidence |
| Risk exception age | Age of accepted-risk exceptions, and the share past their review date | days since approval; exceptions past review date / open exceptions | days; percent | Exception register | Risk management; information security management | Technical debt review | Monthly | Renewing exceptions automatically; splitting exceptions to reduce age | Review exception renewals with a reason; cap renewals without new evidence |
| Security report rate | Share of staff-reported suspicious events relative to confirmed security events, as an indicator of reporting culture | reports from staff in the period / suspicious events confirmed in the period, with group-level trend | ratio | Security mailbox, incident records | Information security management; incident management | Raising impediments openly | Monthly | Encouraging low-value reports; discouraging reports to improve other numbers | Quality of reports; read the comments; survey on whether people feel safe reporting |
8.2 Risk and control metrics
Home topic: (see topic 8.2, Risk and control metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Risk review currency | Share of open risks reviewed by their owner within the agreed interval | risks reviewed within the interval / open risks | percent | Risk register review dates | Risk management; continual improvement | Risks reviewed in planning and review conversations | Monthly | Marking risks as reviewed without discussion; changing the interval | Sample reviews for substance; fixed interval in the register |
| Owner coverage | Share of open risks with a named, current owner who accepted ownership | risks with a confirmed current owner / open risks | percent | Risk register joined to the people directory | Risk management | Team-owned risks on the backlog | Monthly | Assigning owners without their knowledge; naming a senior person with no authority | Owner confirmation; check that owners can act on the response |
| Control test coverage | Share of key controls tested for operation within the required cycle | key controls tested in the cycle / key controls | percent | Control register and test records | Risk management; information security management | Automated checks in the pipeline | Quarterly | Testing the easy controls; counting design reviews as operating tests | Key control list fixed by a second party; test type recorded |
| Control effectiveness rate | Share of tested controls found to operate as designed | controls found effective / controls tested | percent | Test results | Risk management; continual improvement | Automated tests passing for the right reasons | Quarterly | Testing small samples; choosing samples that pass | Sample method independent of the owner; sample size recorded |
| KRI breach response time | Time from a key risk indicator crossing its threshold to a recorded decision | median and 85th percentile of hours or days from breach to decision | hours or days | KRI monitoring and decision log | Risk management; monitoring and event management | Reaction to a production signal | Monthly | Changing the threshold after a breach; recording a decision with no content | Threshold change log; decision content sample |
| Treatment plan timeliness | Share of risk treatments completed by their committed date | treatments completed by date / treatments due in the period | percent | Risk register and action tracker | Risk management; continual improvement | Improvement actions delivered | Quarterly | Setting easy dates; redefining completion | Dates agreed with the owner at approval; check that the risk rating moved |
| Risk-based change share | Share of changes approved through risk-based routes with the control evidence attached | changes approved by a risk-based route with required evidence / changes in the period | percent | Change records | Change enablement; risk management | Changes delivered continuously with automated checks | Monthly | Classifying changes as low risk to avoid review; attaching evidence that was not produced by controls | Sample classification against rules; automated evidence from the pipeline |
8.3 Compliance and audit metrics
Home topic: (see topic 8.3, Compliance and audit metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Obligation coverage | Share of applicable obligations mapped to a control with an owner and a source of evidence | obligations mapped to at least one control with owner and evidence source / applicable obligations | percent | Obligations register and control register | Governance; information security management; risk management | Definition of done includes control evidence | Quarterly | Mapping obligations to weak or irrelevant controls; defining obligations narrowly | Review of control relevance by a second party; test the controls (see topic 8.2, Risk and control metrics) |
| Evidence automation rate | Share of in-scope control evidence collected automatically from systems of record | control evidence items collected automatically / evidence items required | percent | Control register, pipeline and system logs | Information security management; change enablement | Pipeline records review, test, and deployment automatically | Quarterly | Counting screenshots or exports as automatic; automating low-value evidence first | Define automatic as system-generated and tamper-resistant; rank by risk |
| Evidence turnaround | Time to supply evidence requested by an auditor or assessor | median and 85th percentile of days from request to accepted evidence | days | Audit request tracker | Governance; information security management | Responsiveness to a stakeholder question | Per audit | Providing partial evidence quickly; negotiating the request wording | Count accepted evidence only; track follow-up requests |
| Finding closure time | Time to close audit findings by severity | median and 85th percentile of days from finding issued to verified closure | days | Findings tracker | Continual improvement; risk management | Time to fix a defect | Monthly | Closing findings without verification; reclassifying severity | Independent verification; severity change log |
| Repeat finding rate | Share of findings that recur from a previous audit or review | findings matching an earlier closed finding in substance / findings in the period | percent | Findings tracker with cause links | Continual improvement; problem management | Recurring defect after a fix | Per audit cycle | Rewording findings so they do not match; closing the earlier finding as a different type | Match by cause with a recorded rule; review by internal audit |
| Segregation-of-duties conflicts | Count of access or approval combinations that violate segregation rules, and time to resolve | conflicts detected; median days to resolve | count; days | Identity and access management tools, change records | Information security management; change enablement | Independent review of changes | Monthly | Moving conflicts to systems not in scope; granting temporary access that is never recorded | Cover all systems with sensitive processes; review temporary access |
| Audit effort | Person-hours the organization spends preparing for and supporting an audit cycle, per scope unit | hours logged to audit preparation and support / scoped controls or systems | hours per unit | Time records or effort estimates | Governance; continual improvement | Cost of non-delivery work | Per audit cycle | Not logging hours; moving effort to other budgets | Sample time records; compare with team surveys |
8.4 Supplier and contract metrics
Home topic: (see topic 8.4, Supplier and contract metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Supplier service level attainment | Share of contracted service level measures met by a supplier, paired with an experience measure for the same service | measures met in the period / measures contracted; reported beside the user experience score for the service | percent | Supplier reports, your own monitoring, survey data | Supplier management; service level management | Review of a partner's contribution to goals | Monthly | Supplier excludes events from measurement; clock pauses; narrow definitions | Own monitoring; experience measure; audit of exclusions |
| Supplier-attributed incident time | Hours of service impact attributed to a supplier's component or action | sum of impact hours of incidents where a supplier's failure was a confirmed cause | hours | Incident records with cause analysis, supplier incident reports | Incident management; supplier management | Time lost to external blockers | Monthly | Disputing attribution; classifying supplier faults as customer-side | Joint cause review; neutral reviewer for disputes; track disputed share |
| Contract register coverage | Share of suppliers with a current contract, a named internal owner, and a scheduled review | suppliers with all three / suppliers in scope | percent | Contract register, procurement records | Supplier management; financial management | Clear ownership of external dependencies | Quarterly | Naming owners who do not know; listing contracts without dates | Owner confirmation; check review meetings are held |
| Due diligence currency | Share of critical suppliers whose risk assessment is within its review cycle | critical suppliers assessed within the cycle / critical suppliers | percent | Supplier risk assessments | Supplier management; risk management; information security management | Regular review of risks | Quarterly | Assessments by questionnaire only; suppliers self-certify | Evidence requirement for critical suppliers; sample verification |
| Exit readiness | Share of critical suppliers with a documented exit plan that has been tested within the agreed period | critical suppliers with a tested exit plan / critical suppliers | percent | Exit plans and test records | Supplier management; service continuity management | Practiced recovery of a dependency | Annual | Writing a plan and calling it tested; exercises without real steps | Record what was exercised; independent review of exercise |
| Concentration | Share of critical services that depend on a single supplier with no tested alternative | critical services with a single-supplier dependency and no tested alternative / critical services | percent | Dependency map, supplier register | Supplier management; risk management | Avoiding a single point of failure | Quarterly | Splitting one supplier into several legal entities on paper | Dependency map to the ultimate provider; review shared platforms |
| Joint action closure rate | Share of actions agreed in joint reviews with suppliers that were closed by their due date | joint actions closed by date / joint actions due | percent | Review minutes and action tracker | Supplier management; continual improvement | Retrospective actions delivered | Quarterly | Setting easy actions; closing without effect | Review action quality; check that the intended issue improved |
8.5 Regulated and government reporting
Home topic: (see topic 8.5, Regulated and government reporting).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Reporting obligation coverage | Share of reporting obligations with a named owner, a stated definition, a data source, and a calendar entry | obligations with all four / reporting obligations in scope | percent | Obligations register | Measurement and reporting; governance | Working agreement with stakeholders on information needs | Quarterly | Treating obligations narrowly; listing the owner without agreement | Review of the register by compliance or internal audit; confirmation from owners |
| Report timeliness | Share of required reports submitted by their due date | reports submitted on or before due date / reports due in the period | percent | Reporting calendar and submission records | Measurement and reporting | Commitments to stakeholders met | Monthly | Submitting incomplete reports to meet the date; counting drafts as submissions | Completeness check on submission; count only accepted reports; restatement rate |
| Restatement rate | Share of submitted reports or figures later corrected | reports or figures corrected after submission / reports or figures submitted | percent | Submission log and correction log | Measurement and reporting; continual improvement | Escaped defects | Quarterly | Suppressing corrections; making corrections quietly | Correction log reviewed by an independent reader; a low rate is read with traceability |
| Traceability coverage | Share of reported figures that can be traced to a system of record through documented steps | figures with documented lineage to a system of record / figures reported | percent | Lineage documentation, report specifications | Measurement and reporting; knowledge management | Reproducible builds | Quarterly | Documenting lineage superficially; including only simple figures | Sample lineage by reperforming a calculation from the source |
| Definition alignment | Share of reported measures for which the statutory definition and the internal definition are documented and reconciled | measures with documented reconciliation / reported measures with a statutory definition | percent | Metric register | Measurement and reporting; service level management | Shared definition of done | Quarterly | Declaring definitions aligned without reconciliation; adopting the statutory definition only in the report | Reconciliation document reviewed; show both figures side by side |
| Reporting effort | Person-hours spent producing a recurring report | logged hours per report cycle, with the share that is manual extraction and assembly | hours | Time estimates, effort logs | Measurement and reporting; continual improvement | Cost of non-delivery work | Per report cycle | Not logging hours; moving work to other teams | Compare with team feedback; include all contributors in the estimate |
| Published accessibility conformance | Share of published reports and datasets that meet the required accessibility standard | published items passing an accessibility check / published items | percent | Accessibility test results | Measurement and reporting; knowledge management | Inclusive definition of done | Quarterly | Running a checker that finds only some issues; publishing a separate accessible version that lags | Manual testing with assistive technology; check for parity between versions |
Part 9: People, Teams, and Improvement Metrics
9.1 Team health and developer experience
Home topic: (see topic 9.1, Team health and developer experience).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Feedback loop time | Time for a person to get the result of a common action, by loop type | median and 85th percentile of minutes or hours for build, test run, code review wait, and deployment, per team | minutes or hours | Pipeline and review tool timestamps, aggregated by team | Release and deployment management; continual improvement | Fast feedback in continuous delivery | Weekly | Excluding slow cases; measuring a fast path that most work does not take | Report 85th percentile; define each loop's start and end in the register |
| Focus time share | Share of working time in uninterrupted blocks of an agreed minimum length, as reported by the team | team-reported hours in focus blocks / working hours, collected in a short pulse | percent | Team pulse; calendar data only if the team opts in and it is aggregated | Continual improvement; knowledge management | Protected time for deep work | Monthly | Blocking calendar time without focusing; reporting inflated focus to please managers | Team-owned pulse; compare with interruption causes; no individual reporting |
| Cognitive load rating | Team rating of how hard it is to understand and change a named system or process | mean rating and spread on a short agreed scale, per system | scale points | Short pulse linked to a system or process | Service design; knowledge management | Shared understanding of the work | Quarterly | Rating systems low to avoid scrutiny; picking easy systems to rate | Rate a fixed list of systems; compare with onboarding time and incident patterns |
| Obstacle resolution time | Time from an obstacle being raised by the team to its removal or a recorded decision not to remove it | median and 85th percentile of days from raised to resolved or decided | days | Impediment list or tracker | Continual improvement; problem management | Impediments removed | Monthly | Closing obstacles without fixing them; refusing to log obstacles | Team confirms resolution; rate of reopened obstacles |
| Team health check trend | Team's own rating on dimensions it chose, tracked over time | change in team-chosen dimension ratings between checks | scale points | Team health check, owned by the team | Continual improvement | Team reflection on how to become more effective | Monthly or quarterly | Managers pressing for good scores; teams adjusting scores to avoid attention | Team owns results; trends shared only with team consent |
| Tool and process satisfaction | Team rating of satisfaction with the tools and processes they use daily | mean rating or share favorable for each named tool or process | scale points or percent | Short pulse | Service level management; continual improvement | Fit of the environment to the work | Quarterly | Surveying happy users; training staff to answer well | Response rate and mix; read comments; tie to system measures |
| Dimension coverage | Number of SPACE dimensions covered by the measures a team actually uses | count of the five dimensions with at least one measure in use | count (0 to 5) | Metric register | Measurement and reporting; governance | Balanced measures | Annual | Counting a dimension with a token measure | Check that each counted measure is used in a decision |
9.2 Satisfaction and well-being metrics
Home topic: (see topic 9.2, Satisfaction and well-being metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Sustainable pace rating | Team rating of whether the current pace could be kept up indefinitely | mean rating and spread on an agreed scale for the statement "we could keep working at this pace indefinitely" | scale points | Anonymous team pulse | Continual improvement; workforce and talent management | Constant pace indefinitely | Monthly | Managers pressing for good scores; teams reporting what is expected | Anonymity and group-size rules; compare with workload facts; read comments |
| Psychological safety rating | Team rating of how safe it is to raise problems and take interpersonal risks | mean rating on a short validated set of statements, per team | scale points | Anonymous team pulse | Continual improvement; workforce and talent management | Trust and open reflection | Quarterly | Surveying only safe teams; wording changes that raise scores | Fixed wording log; response rate and mix; compare with reporting rates for incidents and mistakes |
| Needs-support rating | Team rating of autonomy, competence, and relatedness at work | mean rating for each of three statements, per team | scale points | Anonymous team pulse | Workforce and talent management; continual improvement | Motivated individuals with the environment they need | Quarterly | Redefining statements; coaching answers | Stable wording; team-owned interpretation; comments |
| Workload strain rating | Team rating of how demanding the workload is relative to capacity | mean rating and share rating the workload as unsustainable | scale points; percent | Anonymous team pulse | Capacity and performance management; workforce and talent management | Sustainable development | Monthly | Lowering reported strain to avoid scrutiny; adjusting scope on paper | Compare with unplanned work and rotation load; check for hidden work |
| Sustained extended-hours weeks | Share of weeks in which the rotation or team worked well beyond its normal hours, counted at rotation or team level | weeks in the period with extended hours at team level / weeks in the period | percent | Rotation records and on-call logs aggregated by team; team-reported, opt-in | Incident management; capacity and performance management | Overtime as a signal of overload | Monthly | Not logging hours; moving work out of the rotation records | Compare with incident logs and team comments; allow reporting without penalty |
| Voluntary attrition and exit themes | Share of team members leaving voluntarily in a period, with themes from exit conversations | voluntary leavers / average headcount; theme counts from consenting leavers | percent; counts | Human resources records, exit conversations | Workforce and talent management | Retention of experienced people | Quarterly | Reclassifying resignations as involuntary; steering exit conversations | Clear classification rules; independent exit conversations; look at long periods |
| Time to act on well-being feedback | Time from a team raising a well-being concern to a recorded response | median and 85th percentile of days from concern to recorded decision or action | days | Team feedback log | Continual improvement | Prompt response to team reflection | Quarterly | Recording a response with no action; closing concerns quickly | Team confirms the response is meaningful; track whether ratings change |
9.3 Collaboration and handoff metrics
Home topic: (see topic 9.3, Collaboration and handoff metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Handoff count | Number of times a work item changes owning team before completion | median and 85th percentile of team-to-team transfers per completed item, by item type | transfers per item | ITSM or tracker assignment history, aggregated by team | Incident management; service request management; change enablement | Cross-functional teams carrying work end to end | Monthly | Keeping items assigned to one team while others do the work; reassigning to a shared queue to avoid counting | Check actual activity by team; count handoffs by activity, not assignment alone |
| Handoff wait share | Share of an item's elapsed time spent waiting after a handoff before work resumes | time between handoff and first action by the receiving team / total elapsed time, median across items | percent | Assignment and activity timestamps | Incident management; service request management | Flow efficiency; queue time | Monthly | Recording a first action that is only an acknowledgement; assigning to the right team late | Define "first action" as a substantive step; compare with satisfaction and resolution time |
| Reassignment rate | Share of items passed between teams more than twice or returned to a previous team | items reassigned more than twice or returned / completed items | percent | Assignment history | Incident management; problem management | Rework and bouncing work | Monthly | Refusing to reassign even when wrong; closing and reopening items under another team | Resolution quality and reopen rate; sample bounced items |
| Dependency delay | Time items spend blocked waiting on another team | median and 85th percentile of days in a blocked-by-another-team state, with the dependency named | days | Tracker blocked state and dependency field | Change enablement; release and deployment management | Blocked work item age | Monthly | Not recording blocked state; naming the wrong dependency | Compare with cycle time and item age; review the dependency field with teams |
| Collaborative resolution rate | Share of incidents resolved by people from several teams working together in real time without sequential escalation | incidents with a recorded real-time collaboration (for example a shared channel or call) that resolved without further handoff / incidents of eligible priority | percent | Incident records with collaboration tag | Incident management; major incident management | Swarming on problems | Monthly | Tagging every incident as collaborative; creating shared channels with no real work | Check that the call or channel included the resolving people; resolution time and outcomes |
| Knowledge coverage | Share of critical components with at least a stated number of team members able to operate and change them | critical components with at least the target number of people able to operate and change / critical components | percent | Team-maintained skills and ownership map | Knowledge management; service continuity management | Shared ownership and collective code ownership | Quarterly | Listing people who could in theory do the work; inflating the map | Pairing or drill evidence; ask who actually performed the last change |
| Stakeholder response time | Time from a team's question to a stakeholder until a usable answer | median and 85th percentile of hours from question logged to answer recorded | hours | Question log or tracker field for open questions | Service level management; business relationship management | Continuous stakeholder involvement | Monthly | Logging questions late; marking an answer as received when it is not usable | Stakeholder confirms the answer is usable; sample questions |
9.4 Skills and learning metrics
Home topic: (see topic 9.4, Skills and learning metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Protected learning time share | Share of team capacity set aside and actually used for learning | hours or capacity share used for learning in working time / total working capacity, at team level | percent | Team capacity plan and work tracker work type | Workforce and talent management; continual improvement | Time for reflection and technical excellence | Monthly | Logging ordinary work as learning; scheduling time that is then canceled | Count only time used; compare with work type records and team comments |
| Cross-training depth | Share of critical tasks performed by at least two people in the last period | critical tasks performed by two or more people in the period / critical tasks | percent | Team task and ownership map, validated by recent work | Knowledge management; service continuity management | Collective ownership of the work | Quarterly | Listing people who have never done the task; counting a single observation | Evidence of recent work; drill results |
| Time to first contribution | Time for a new team member to complete their first real change or resolved case | median and 85th percentile of days from start date to first completed real work item in production | days | Onboarding tracker and work tracker | Workforce and talent management; knowledge management | Time for a new team member to make a first change | Per hire, reviewed quarterly | Counting trivial changes; starting the clock late | Define "real" work in the register; ask the new member and their buddy |
| Community participation | Share of team members taking part in a community of practice in the period, as chosen by them | members who attended, contributed, or presented in the period / team members, at team level | percent | Community records, voluntary | Knowledge management; continual improvement | Communities of practice | Quarterly | Mandating attendance; counting sign-ups | Voluntary only; ask what the community produced |
| Training application rate | Share of training experiences where the learner or their team reports using the learning in work within 90 days | learning experiences reported as applied / learning experiences completed | percent | Short follow-up question to learner, anonymized to team | Workforce and talent management; continual improvement | Learning applied to the work | Quarterly | Pressuring learners to say they applied it; asking only enthusiasts | Anonymous aggregate; follow-up at team level; look at observable changes |
| Relevant certification coverage | Share of roles that require a certification for legal, contractual, or entry reasons where the requirement is met | roles with required certification held / roles requiring certification | percent | Role requirements register, certificate records | Workforce and talent management; governance | Meeting contractual or regulatory entry requirements | Annual | Collecting certificates for roles that do not need them; treating certification as competence | Scope to genuine requirements; check practical capability by other evidence |
| Lessons shared across teams | Number of lessons from incidents or improvements that were shared outside the originating team and used by another team | shared lessons with a recorded use by another team in the period | count | Lessons register and review notes | Knowledge management; continual improvement | Learning shared across teams | Quarterly | Sharing trivial lessons; counting posts | Require a recorded use by another team; review quality |
9.5 Continual improvement metrics
Home topic: (see topic 9.5, Continual improvement metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Action follow-through rate | Share of improvement actions agreed in reviews that were completed by their agreed date | actions completed by date / actions due in the period | percent | Improvement register or team backlog | Continual improvement | Reflection actions delivered | Monthly | Agreeing trivial actions; moving due dates; closing without doing | Review the size and value of actions; date changes logged; effect check rate |
| Improvement backlog age | Age of open improvement items, with attention to the oldest | median and 85th percentile age in days of open items; age of the oldest | days | Improvement register | Continual improvement | Backlog age | Monthly | Closing old items as "won't do" without a decision; splitting items to reset age | Record reasons for closure; track items closed without action; review the oldest |
| Effect check rate | Share of completed improvements whose effect was checked against a baseline | completed improvements with a recorded before-and-after check / completed improvements | percent | Improvement register with baseline and result fields | Continual improvement; measurement and reporting | Learning from experiments | Quarterly | Recording a check with no baseline; checking only successes | Baseline dated before the change; include null and negative results |
| Time from idea to trial | Time from an improvement idea being raised to the first trial in the real work | median and 85th percentile of days from raised to first trial | days | Improvement register | Continual improvement | Fast feedback on changes | Monthly | Calling a plan a trial; trialing trivial variations | Define a trial as a change in the real work; look at the importance of trialed ideas |
| Frontline idea share | Share of improvement ideas raised by people who do the work, counted at team level | ideas raised by team members doing the work / ideas raised | percent | Improvement register | Continual improvement | Self-organizing teams | Quarterly | Managers filing ideas under staff names; mandatory idea quotas | Ideas by author recorded at team level; no quotas; ask the team |
| Repeat issue rate | Share of issues that recur after an improvement intended to remove their cause | issues recurring within a stated period after a related improvement closed / improvements closed with a related cause | percent | Incident, problem, and improvement records linked by cause | Problem management; continual improvement | Escaped defect after a fix | Quarterly | Recording different causes for the same problem; closing the earlier record under another type | Match by cause with a recorded rule; review by someone outside the team |
| Improvement capacity share | Share of team capacity spent on improvement work | capacity or completed items tagged as improvement / total capacity or completed items | percent | Work tracker work types | Continual improvement; capacity and performance management | Time for reflection and technical excellence | Monthly | Tagging ordinary work as improvement; scheduling time that is then used for delivery | Sample items for type; compare with time actually spent |
9.6 Organizational change and adoption metrics
Home topic: (see topic 9.6, Organizational change and adoption metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Aim clarity | Share of team members who can state the aim of a practice in their own words and a way they would tell if it were working | members giving a clear aim and indicator in a short, anonymous check / members asked, at team level | percent | Short anonymous check, aggregated by team | Organizational change management; continual improvement | Team understanding of why it works this way | Quarterly | Coaching people to recite the aim; asking leading questions | Anonymous check; ask for an example of how they would tell; compare with outcome movement |
| Practice adoption breadth | Share of teams using a defined practice, as defined by observable behavior, not attendance | teams showing the defined behavior in the last period, confirmed by the team and an observer / teams in scope | percent | Team self-assessment confirmed by observation | Organizational change management | Spread of a practice | Quarterly | Counting boards and meetings; teams performing for the observer | Define by behavior and purpose; observation by someone outside the team; outcome movement |
| Outcome movement against comparison | Change in an outcome measure for adopting teams compared with similar non-adopting teams over the same period | change in outcome for adopters minus change for comparison teams | outcome units | Outcome measures per team (flow, stability, experience) | Continual improvement; measurement and reporting | Learning from experiments | Quarterly | Choosing a favorable comparison group or period; leaving out other changes | Choose comparison and period in advance; list other changes; show the uncertainty |
| Change load | Number of significant changes concurrently affecting a team | count of significant change initiatives that ask a team to change how it works in the period, per team | count | Change portfolio and team input | Organizational change management; change enablement | Sustainable pace | Quarterly | Splitting an initiative into small pieces; not counting changes that arrive informally | Count by effect on the team's work; ask teams to list what they are absorbing |
| Stakeholder involvement rate | Share of change initiatives in which the affected people took part in design and review | initiatives with recorded involvement of affected people / initiatives | percent | Initiative records and affected-team confirmation | Organizational change management; stakeholder engagement | Continuous stakeholder involvement | Quarterly | Inviting people to a briefing and calling it involvement; recording attendance only | Affected-team confirmation that they influenced the design; record changes made in response |
| Voluntary uptake share | Share of adopting teams that chose the practice, as opposed to being directed | adopting teams that report choosing the practice / adopting teams | percent | Team reports | Organizational change management | Self-organizing teams | Annual | Presenting a mandate as a choice; teams saying they chose when they felt they had to | Anonymous report; ask what would have happened if they declined |
| Reversion rate | Share of teams that dropped a practice within a year of adopting it | teams that stopped within 12 months / teams that adopted | percent | Team records over time | Organizational change management; continual improvement | Practices abandoned as unhelpful | Annual | Making dropping a practice costly or hidden; renaming the dropped practice | Review reasons for dropping; allow safe withdrawal |
Part 10: Metrics in the Age of AI
10.1 AI in service management measurement
Home topic: (see topic 10.1, AI in service management measurement).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Baseline completeness | Share of planned AI use cases that have a recorded pre-adoption baseline for their main indicators | use cases with dated baseline / planned use cases | percent | Use case register | Continual improvement; measurement and reporting | Baseline before an experiment | Quarterly | Recording baselines after the fact; using convenient indicators | Date-stamped baselines; independent review of baseline method |
| AI use coverage | Share of eligible work items or tasks where AI was used, by use case | items where AI assistance was used / eligible items, from tool logs or user tags, at team level | percent | Tool usage logs, tags | Service desk; incident management; release and deployment management | Adoption of a tool by willing teams | Monthly | Mandating use; counting trivial or automatic invocations | Never a target; compare with outcome movement; count meaningful use |
| Suggestion acceptance and override rate | Share of AI suggestions accepted as is, edited, or rejected | suggestions in each category / suggestions offered | percent | Tool logs aggregated by team | Service desk; knowledge management | Review of machine suggestions | Monthly | Rewarding acceptance; making rejection cumbersome | No targets; reviewed output accuracy; ask users about their experience |
| Reviewed output accuracy | Share of sampled AI outputs judged correct and fit for purpose by a qualified reviewer | outputs judged correct / outputs sampled | percent | Sampled review records | Quality assurance; knowledge management | Definition of done for the output | Monthly | Sampling easy outputs; lenient reviewers | Random sample by independent reviewers; written standard; reviewer rotation |
| Task time against baseline | Time to complete a defined task with AI compared with the baseline or a comparison group | median and 85th percentile of task time with AI minus the same for baseline or comparison | minutes or hours | Timed tasks, ticket timestamps | Service desk; incident management | Cycle time for a task | Quarterly | Timing only generation; choosing easy tasks | Time to checked result; sample tasks randomly; include review and rework |
| Cost per AI-assisted task | Total cost of AI-assisted work per task, including review and rework | (license and usage cost + review and rework time cost) / tasks completed with AI | currency per task | Vendor invoices, time estimates, work tracker | Service financial management | Cost to serve per outcome | Quarterly | Leaving out review time or governance cost | Full-cost checklist; compare with time studies |
| Outcome movement against comparison | Change in the outcome indicator for AI-assisted work compared with similar non-assisted work | change in indicator for AI-assisted group minus change for comparison group | indicator units | Outcome measures per use case (quality, satisfaction, reopen rate, defects) | Continual improvement | Learning from experiments | Quarterly | Choosing favorable groups or periods; ignoring other changes | Pre-agreed comparison and period; list of other changes |
10.2 Measuring AI-assisted work
Home topic: (see topic 10.2, Measuring AI-assisted work).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Retention rate | Share of AI-assisted changes that remain substantially unchanged after a stated period | AI-assisted changes with less than a set share modified or reverted after 30 days / AI-assisted changes merged 30 days ago | percent | Version control history joined to assistance tags, at team level | Release and deployment management; change enablement | Work that sticks; low rework | Monthly | Avoiding needed changes to keep the number up; tagging only successful changes as assisted | Tag by tool logs, not by author choice; pair with escaped defects and rework |
| Post-merge rework | Share of changes needing a follow-up fix within a short period, for assisted and comparison changes | changes with a linked follow-up fix within 14 days / changes merged, per group | percent | Version control, issue tracker, change records | Change enablement; problem management | Escaped defects; rework | Monthly | Fixing in a different ticket or a new change not linked; delaying fixes beyond the window | Linking rule in the register; look at a longer window; production defects |
| Review load | Reviewer effort per change, for assisted and comparison changes | median and 85th percentile of review time and review rounds per change, per group | hours; rounds | Review tool timestamps, aggregated by team | Release and deployment management | Review as feedback and learning | Monthly | Rushed reviews that lower measured time; approvals without comments | Review depth sample; escaped defects; reviewer survey |
| Escaped defect rate | Defects found in production per change, for assisted and comparison changes | defects found after release attributed to a change / changes released, per group | defects per change | Defect tracker linked to changes | Incident management; problem management | Quality of what is released | Quarterly | Not attributing defects to changes; reclassifying defects as enhancements | Attribution rule; independent sample of defect classification |
| Explanation check pass rate | Share of sampled AI-assisted changes whose author can explain the approach and its trade-offs in review | sampled changes where the author explained to the reviewer's satisfaction / sampled changes | percent | Sampled review notes | Knowledge management; change enablement | Shared understanding of the code | Quarterly | Authors rehearsing for the check; lenient reviewers | Random, unannounced samples; rotate reviewers; focus on design reasons |
| Assisted support quality | Reopen rate and user satisfaction for AI-assisted support responses compared with unassisted ones | reopened assisted tickets / assisted tickets, and favorable ratings / ratings, per group | percent | ITSM tool, survey | Service desk; incident management | Quality of service outcomes | Monthly | Assisting only easy tickets; coaching users to rate highly | Match tickets by type and difficulty; response rate and mix; read comments |
| Unaided confidence rating | Team rating of confidence to do key tasks without the tool | mean rating and spread on an agreed scale, per team | scale points | Anonymous team pulse | Workforce and talent management; knowledge management | Team capability and learning | Quarterly | Inflated ratings to avoid scrutiny; low ratings to argue for more tools | Anonymity; compare with observed practice in drills; read comments |
10.3 AI agent and chatbot metrics
Home topic: (see topic 10.3, AI agent and chatbot metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Verified resolution rate | Share of bot conversations in which the user confirmed that the issue was resolved, or did not return within a stated period | conversations with confirmed resolution or no return contact within 7 days / conversations that started with a resolvable intent | percent | Conversation logs, user confirmation, ticket and contact data | Service desk; knowledge management | Working outcome for the user | Weekly | Counting any end of conversation as resolved; asking leading confirmation questions | Define confirmation neutrally; return contact rate; sample conversations |
| Return contact rate | Share of bot-ended conversations followed by a contact about the same issue through any channel | conversations followed by a related contact within 7 days / conversations ended without handoff | percent | Conversation logs joined to ticket and contact records | Service desk; incident management | Escaped defects | Weekly | Measuring only through one channel; short windows | Join all channels; use a longer window as a check; sample returns |
| Handoff context completeness | Share of handoffs to a person in which the person had the information needed without asking the user to repeat it | sampled handoffs judged complete by the receiving agent / handoffs sampled | percent | Sampled handoffs, agent feedback | Service desk; knowledge management | Smooth collaboration across the boundary | Monthly | Passing a long transcript instead of a summary; sampling easy handoffs | Receiving agent rating; random sample; time to resolution after handoff |
| Time to human | Time from the user asking for a person, or the bot deciding to hand off, to a person taking over | median and 85th percentile of minutes | minutes | Conversation logs, queue data | Service desk; incident management | Responsiveness when the user needs help | Weekly | Starting the clock after menus; counting a queue acknowledgment as takeover | Clock starts at the request; takeover means a person is active in the conversation |
| Answer accuracy | Share of sampled bot answers judged correct, complete, and safe by a qualified reviewer | answers judged correct / answers sampled | percent | Sampled review | Knowledge management; quality assurance | Definition of done for an answer | Monthly | Sampling easy conversations; lenient reviewers | Random sample by independent reviewers; adversarial test cases |
| Bot satisfaction and effort | User rating of satisfaction and ease after a conversation, with comments | favorable ratings / ratings; mean effort rating | percent; scale points | Short post-conversation survey | Service desk; customer experience | Feedback on working software | Weekly | Surveying only completed conversations; placing the survey where only happy users reach it | Survey also abandoned conversations; response rate and mix; read comments |
| Agent action reversal rate | Share of actions taken by an AI agent that had to be corrected, undone, or escalated | actions reversed or corrected / actions taken, by action type and risk class | percent | Action audit log, change records | Change enablement; incident management | Rework and rollback | Weekly | Not logging reversals; reclassifying corrections as new work | Audit log tamper-resistant; link reversals to actions; incident review |
10.4 Metric inflation and quality dilution
Home topic: (see topic 10.4, Metric inflation and quality dilution).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Output-to-outcome ratio | Volume of output relative to the outcome it was meant to produce | output count (tickets, articles, changes) / outcome measure (resolved problems, used articles, retained changes), over the same period, tracked as a trend | ratio | Work tracker, knowledge base, outcome measures | Continual improvement; measurement and reporting | Working software over documentation volume | Monthly | Choosing an outcome measure that rises with volume; changing the period | Outcome fixed in the register; compare with satisfaction and reopen rate |
| Useful-item share | Share of sampled items judged useful by a qualified reviewer | sampled items judged useful (correct, relevant, non-duplicate) / items sampled | percent | Random sample review | Knowledge management; quality assurance | Definition of done for content | Monthly | Sampling easy items; lenient rubric; reviewers influenced by the producer | Random sample; written rubric; independent, rotating reviewers |
| Verification burden | Human time spent checking and correcting generated work per unit of output | review and correction hours / units of output, tracked as a trend | hours per unit | Time estimates, review tool data | Service financial management; continual improvement | Review capacity as a constraint | Monthly | Not logging review time; shifting checking to downstream teams | Include downstream rework; ask reviewers about load |
| Content redundancy rate | Share of knowledge items that duplicate or substantially overlap another | items flagged duplicate or overlapping in review or by matching / items in the knowledge base | percent | Knowledge base review, matching reports | Knowledge management | Single source of truth | Quarterly | Narrow matching rules that miss duplicates; merging distinct items | Sample duplicates by hand; log merge rules |
| Reviewed share of generated knowledge | Share of AI-generated knowledge items that a qualified person has reviewed and approved before publication | generated items published with approved review / generated items published | percent | Knowledge base metadata | Knowledge management; change enablement | Review before release | Monthly | Marking review as complete without reading; reviewing in bulk | Sample reviews for substance; time per review; error rate in published items |
| Backlog inflow against resolution | Growth of work arriving relative to growth of work resolved, for queues affected by AI | (change in items created) / (change in items resolved), compared with the pre-AI baseline | ratio | Ticket and tracker history | Incident management; service request management | Flow balance | Monthly | Auto-closing items; splitting items | Check resolution quality; reopen rate; sample closed items |
| Metric drift flags | Number of metrics whose definition or distribution shifted noticeably after AI was introduced, reviewed and annotated | metrics flagged in review / metrics in the register | count; percent | Metric register review, distribution checks | Measurement and reporting | Retrospective on measurement | Quarterly | Not flagging to avoid work; flagging everything | Review all metrics each quarter; require a decision for each flag |
10.5 AI governance and risk metrics
Home topic: (see topic 10.5, AI governance and risk metrics).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| AI use register coverage | Share of AI uses found by independent means that are on the register with an owner and a risk class | uses on the register with owner and risk class / uses found by independent discovery (procurement, expense, identity, network, and staff reports) | percent | Register, procurement and expense data, identity logs, surveys | Governance; IT asset management; risk management | Visible work and clear ownership | Quarterly | Registering trivial uses to raise the percentage; denominators limited to what is registered | Independent discovery for the denominator; sample register entries for quality; amnesty for unregistered uses |
| Risk assessment currency | Share of medium and high-risk uses with a risk assessment within the required cycle | uses assessed within cycle / medium and high-risk uses | percent | Risk assessments | Risk management; information security management | Regular reflection on risks | Quarterly | Light-touch assessments that always pass; assessing low-risk uses | Review assessment depth; check that risk class matches the criteria |
| Change control coverage | Share of changes to models, prompts, tools, and data sources in production that went through change control with required tests | changes with change record, tests, and approval proportional to risk / changes detected | percent | Change records compared with version history and vendor release notes | Change enablement; release and deployment management | Small, controlled, reversible changes | Monthly | Not detecting vendor changes; recording changes after the fact | Detection through version history and vendor notices; change records timestamped before release |
| Evaluation currency | Share of production uses with a current evaluation (accuracy, safety, and fairness where relevant) and results within tolerance | uses with an evaluation within the cycle and results acceptable / production uses in scope | percent | Evaluation records | Quality assurance; risk management | Definition of done for behavior | Quarterly | Evaluations on easy cases; choosing tolerances after seeing results | Test sets reviewed by independent party; thresholds set in advance |
| Human oversight evidence rate | Share of sampled consequential outputs or decisions with a recorded, substantive human review | sampled items with documented review that could have changed the outcome / items sampled | percent | Sampled decision records | Risk management; governance | Review before release | Monthly | Clicking approve without reading; documenting review that could not change the outcome | Sample reviews for substance; seeded known errors; reviewer load |
| AI incident rate and time to contain | Incidents involving AI (harmful output, data exposure, unsafe action) per use and the time to contain them | incidents per production use per quarter; median and 85th percentile of hours from detection to containment | incidents; hours | Incident records tagged AI | Incident management; information security management | Blameless response and learning | Quarterly | Not reporting incidents; narrowing the definition | Easy, blame-free reporting; compare with user complaints and audit findings |
| Supplier AI due diligence currency | Share of suppliers providing AI features in critical services whose AI-specific assessment is current | suppliers with current AI assessment / critical suppliers with AI features | percent | Supplier assessments | Supplier management; risk management | Regular review of dependencies | Quarterly | Questionnaires answered by marketing; assessments without evidence | Evidence requirements for critical suppliers; independent verification |
Part 11: Building a Metrics Program
11.1 Designing a service metrics dashboard
Home topic: (see topic 11.1, Designing a service metrics dashboard).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Question coverage | Share of listed audience questions that the dashboard can answer with a defined measure | questions with a measure and a definition / questions listed by the audience | percent | Question list from stakeholder sessions; metric cards | Continual improvement; service level management | Continuous stakeholder involvement | Quarterly | Writing narrow questions that existing measures already answer; leaving out hard questions | Include stakeholders from outside the program team; review unanswered questions explicitly |
| Definition completeness | Share of displayed measures with a current written definition, data source, owner, and known limits | measures with all four / measures displayed | percent | Metric cards or catalog | Information and technology management; knowledge management | Shared understanding; visible work | Quarterly | Filling fields with boilerplate; definitions nobody reads | Sample definitions for clarity with someone outside the team; check that the definition matches the actual calculation |
| Data freshness | Share of displayed measures updated within their expected interval | measures updated on time / measures displayed | percent | Pipeline logs; dashboard metadata | Monitoring and event management | Fast feedback | Weekly | Refreshing a stale source with unchanged data; counting a refresh as success when the source feed failed | Check source timestamps as well as refresh times; compare with record counts and expected volume |
| Decision linkage | Share of reviewed measures where a recent review led to a recorded decision, action, or deliberate choice to do nothing | measures with a linked decision in the period / measures reviewed | percent | Review notes; improvement register | Continual improvement | Regular reflection | Quarterly | Recording decisions after the fact to fill the field; inventing action to avoid a blank | Accept "chose to do nothing" as a recorded decision; sample links for a real prior discussion |
| Display size | Number of measures on each audience view | count per view | measures | Dashboard configuration | Continual improvement | Simplicity | Quarterly | Hiding measures on secondary tabs; splitting one view into many | Count measures per audience across all tabs; ask the audience how many numbers they actually use |
| Retirement rate | Measures removed or replaced in the period because they stopped informing decisions | measures retired / measures displayed at start | percent | Change log of the dashboard | Continual improvement | Ongoing evolution | Annual | Retiring inconvenient measures that show poor results | Review the retired list for measures with unfavorable trends; require a stated reason |
| Audience reach (descriptive) | Share of intended teams or roles that opened their view in the period | distinct teams or roles that viewed / intended teams or roles | percent | Dashboard access logs, aggregated to team or role | Information and technology management | Continuous stakeholder involvement | Quarterly | Opening the page to raise the count; mandatory viewing at meetings | Keep it descriptive; read with decision linkage; do not report individual views |
11.2 Tooling landscape
Home topic: (see topic 11.2, Tooling landscape).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Source coverage | Share of the systems of record needed for the agreed measures that feed the metrics store automatically | sources connected and tested / sources needed for agreed measures | percent | Source inventory; pipeline configuration | Information and technology management; service configuration management | Continuous delivery of the pipeline | Quarterly | Connecting easy or irrelevant sources; counting a connection that carries no usable data | Count by agreed measures; check data completeness per source |
| Pipeline reliability | Share of scheduled data loads that complete on time with passing checks | loads on time with passing checks / loads scheduled | percent | Pipeline logs and test results | Monitoring and event management | Automated tests and fast feedback | Weekly | Loosening checks so loads always pass; scheduling fewer loads | Review the checks for strength; track reconciliation and source row counts |
| Time to a new measure | Elapsed time from an approved request for a new measure to its availability with a definition card | days from approval to published, median and 85th percentile | days | Request and release records | Service request management; change enablement | Small increments of value | Quarterly | Publishing without definitions or tests; narrowing what counts as a new measure | Require the definition card and a reconciliation check for completion |
| Reconciliation rate | Share of key figures that match between the metrics store and the source system on a sampled check | figures matching within tolerance / figures checked | percent | Reconciliation checks | Information and technology management | Trustworthy feedback | Monthly | Choosing easy figures to check; widening the tolerance after a miss | Choose samples before the check; fix tolerance in advance; include difficult figures |
| Manual effort share | Share of effort on recurring reports spent on manual collection and cleaning | hours on manual steps / total hours on recurring reports | percent | Time estimates; team survey | Continual improvement | Eliminating toil | Quarterly | Understating manual work; hiding effort in other budgets | Ask the people who do the work; compare with time spent late in each reporting cycle |
| Exit readiness | Whether the definitions, history, and dashboards can be exported in a documented, usable form | exports tested and complete / export tests planned | percent | Export test records | Supplier management; service continuity management | Sustainable choices | Annual | Testing a partial export; counting a documented plan as readiness | Run a full restore into a different tool on a sample; verify definitions and history |
| Tooling cost per team supported | Full annual cost of the program's tooling divided by the teams it serves | (licenses + infrastructure + upkeep effort) / teams served | currency per team | Finance and effort records | Service financial management | Sustainable pace | Annual | Excluding upkeep effort; adding teams on paper | Include staff time; count teams that actively use their views |
11.3 Rolling out metrics without breeding fear
Home topic: (see topic 11.3, Rolling out metrics without breeding fear).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Use charter coverage | Share of participating teams that have agreed a written statement of what their measures are used for and never used for | teams with an agreed charter / participating teams | percent | Charters held with the program | Governance; organizational change management | Working agreements | Quarterly | Signing charters as a formality; leaders ignoring them | Check charter use in practice; report individual-use incidents; review charters with the teams |
| Team ownership share | Share of a team's displayed measures whose definitions the team helped write or has approved | measures with team approval / measures displayed to the team | percent | Metric catalog; approval records | Continual improvement | Self-organizing teams | Quarterly | Teams approving definitions they did not read; the program presenting finished definitions for sign-off | Sample how definitions were developed; track changes teams requested and made |
| Candor signal | Whether reporting of problems and near-misses holds steady or rises after measures are introduced | near-miss or problem reports per team per quarter, before and after; trend | reports | Incident, near-miss, and postmortem records | Incident management; continual improvement | Blameless reflection | Quarterly | Pressuring teams to report more or fewer problems; renaming categories | Read with severity and the content of postmortems; compare with customer-reported issues |
| Challenge turnaround | Time from a person or team challenging a number to a resolution that is visible to them | median and 85th percentile of days from challenge to resolution | days | Challenge log | Continual improvement; knowledge management | Responding to feedback | Quarterly | Closing challenges without a visible resolution; discouraging challenges | Require a visible response; survey challengers; track repeat challenges |
| Perceived safety of measurement (survey) | Team-level survey agreement with statements such as "the data about our work is used to help us" | percent agreeing on the team survey; response rate shown | percent | Anonymous team survey, aggregated | Organizational change management | Trust and motivated individuals | Twice a year | Coaching respondents; low response rates hiding unhappy teams | Anonymity and minimum group size; show response rates; talk to teams directly |
| Individual-use incidents | Instances where data was shown or used to rank or evaluate individuals, against the charter | count of reported instances per quarter, with outcomes | count | Reports to the program; review of dashboards and reviews | Governance | Respect for people | Quarterly | Not reporting; reclassifying incidents as something else; blaming those who report | Easy anonymous reporting; protection for reporters; review of reviews and dashboards for individual data |
| Voluntary adoption | Share of eligible teams that chose to take up the program in a period, before any mandate | teams that opted in / eligible teams invited | percent | Program records | Organizational change management | Pilots and learning | Quarterly | Pressure framed as invitation; counting teams that joined to avoid scrutiny | Ask teams why they joined; check use in practice; keep the period free of mandate |
11.4 Maturity model for metrics programs
Home topic: (see topic 11.4, Maturity model for metrics programs).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Assessment participation | Share of participating teams that completed a self-assessment with their own discussion | teams that completed and discussed / participating teams | percent | Assessment records | Continual improvement | Reflection and retrospectives | Twice a year | Completing forms to meet a quota; one person filling for the team | Require a team discussion; ask for the evidence behind each claim |
| Profile by dimension | The distribution of teams' self-assessed levels in each dimension, shown as a range and not a single score | count of teams at each level, per dimension | teams per level | Self-assessments, aggregated | Continual improvement; governance | Visible work | Twice a year | Inflating levels to look good; sandbagging to receive help | Do not link to funding or standing; ask for evidence; calibrate openly |
| Improvement actions from assessments | Share of agreed next steps that were completed, dropped with a reason, or still under way | actions closed or reasoned out / actions agreed | percent | Improvement register | Continual improvement | Small experiments | Quarterly | Choosing trivial steps to close; closing without doing | Review step size and value; check outcomes at the next assessment |
| Decision evidence | Share of sampled measures where the team can name a decision or deliberate choice that the measure informed in the last quarter | measures with a named decision / measures sampled | percent | Team interviews; review notes | Continual improvement | Evidence over ceremony | Quarterly | Inventing decisions after the fact; listing decisions of no consequence | Ask for the date and the people involved; accept "chose to do nothing" as a decision |
| Definition and data trust | Team-level agreement that the definitions are clear and the data is correct | percent agreeing on a short team survey; response rate shown | percent | Anonymous team survey | Knowledge management; information management | Shared understanding | Twice a year | Coaching respondents; low response hiding discontent | Anonymity and minimum group size; show response rates; talk with teams directly |
| Time-to-next-level (descriptive) | Elapsed time for a team to move a dimension up one level where it chose to | median months from agreed step to the team's reassessment | months | Assessment history | Continual improvement | Sustainable pace | Annual | Rushing claims of progress; hiding regression | Keep descriptive; read with evidence; record regressions without penalty |
| Assessment burden | Hours the assessment takes per team | median hours per team | hours | Time estimates from teams | Continual improvement | Sustainable pace | Twice a year | Skipping the discussion to cut hours | Track hours together with participation and the quality of evidence |
11.5 An incremental adoption roadmap
Home topic: (see topic 11.5, An incremental adoption roadmap).
| Metric | Definition | Formula | Unit | Data source | ITIL practice | Agile counterpart | Cadence | Gaming vector | Guardrail |
|---|---|---|---|---|---|---|---|---|---|
| Time to first useful result | Elapsed time from the start of the program to the first measure that a pilot team says helped it make a change | days from kickoff to the first team-confirmed helpful use | days | Program log; team confirmation | Continual improvement | Early and continuous delivery of value | Once, then per new team | Declaring a trivial change useful; rushing a showpiece | Ask the team what changed; check that the change persisted |
| Teams actively using measures | Share of invited teams that used their measures in a review in the period, by their own account | teams that used measures in a review / invited teams | percent | Team confirmation; review notes | Organizational change management | Continuous stakeholder involvement | Monthly | Reviews held to tick a box; claiming use that did not happen | Ask for the decision made; sample review notes; talk with teams |
| Improvements traced to measures | Number of changes teams made that they attribute, with reasons, to what a measure showed | count of team-reported changes with a stated link to a measure | count | Improvement register | Continual improvement | Evidence-informed experiments | Quarterly | Inventing links to reach a count; claiming credit for unrelated changes | Keep it descriptive; ask the team for the reasoning; accept uncertain links as such |
| Retired measures and reports | Measures or reports stopped because they stopped informing decisions | count retired per quarter | count | Catalog change log | Continual improvement | Ongoing evolution | Quarterly | Retiring inconvenient measures; retiring and reintroducing under new names | Review the retired list for unfavorable trends; require a stated reason |
| Baseline coverage | Share of agreed measures that have a recorded baseline of at least a few months | measures with a baseline / agreed measures | percent | Metric catalog | Service level management; continual improvement | Evidence over opinion | Quarterly | Fabricating history; using a period that flatters later results | Record the source and period; keep raw data; choose baselines before changes |
| Program effort share | Share of participating teams' time spent on measurement tasks | hours on collection, reporting, and review / total team hours, by estimate | percent | Team time estimates | Continual improvement | Sustainable pace | Quarterly | Understating effort; moving work to people outside the count | Ask the people who do the work; compare with late-cycle overtime |
| Stage review completion | Share of planned stage reviews held with teams, with changes recorded | reviews held with recorded changes / reviews planned | percent | Program records | Continual improvement | Regular reflection | Per stage | Short, perfunctory reviews; recording changes that never happen | Check that changes are carried out; ask teams if the review was worth their time |