ITIL Metrics and Measurement 5 — Questions and Answers
Question 1: An ITIL practitioner is designing a measurement framework. Which principle should guide the NUMBER of KPIs selected for a given process?
- More KPIs always provide better visibility and should be maximized
- KPIs should be limited to a manageable set that drives the right behaviors without creating reporting overload (Correct answer)
- The number of KPIs must match the number of team members responsible for the process
- KPIs should only be added when a process is underperforming
Correct answer: KPIs should be limited to a manageable set that drives the right behaviors without creating reporting overload
A focused, manageable set of KPIs ensures teams can act on the data without being overwhelmed by measurement overhead.
Question 2: What does the ITIL concept of 'metric cascade' describe?
- A process for automatically escalating incidents when SLA thresholds are breached
- The translation of strategic goals into operational metrics at successively lower organizational levels (Correct answer)
- A waterfall reporting model where data flows from operations to executives monthly
- The practice of using one metric to trigger measurement of a secondary metric
Correct answer: The translation of strategic goals into operational metrics at successively lower organizational levels
Metric cascading ensures that high-level strategic goals are broken down into actionable metrics at each organizational level, maintaining alignment.
Question 3: A service team is measuring 'number of changes deployed per sprint.' This is BEST classified as which type of metric?
- Outcome metric
- Technology metric
- Throughput metric (Correct answer)
- Financial metric
Correct answer: Throughput metric
A throughput metric measures the volume of work completed in a period, indicating productivity rather than the quality or business value of the output.
Question 4: Which scenario BEST demonstrates the ITIL principle of 'focusing on value' as applied to metrics?
- Tracking every possible system event to ensure comprehensive data collection
- Measuring only the metrics that directly inform decisions improving customer or business outcomes (Correct answer)
- Automating all metric collection to reduce manual effort
- Reporting metrics weekly to all stakeholders regardless of their relevance to each audience
Correct answer: Measuring only the metrics that directly inform decisions improving customer or business outcomes
Focusing on value means collecting and reporting only the metrics that enable better decisions linked to customer or business outcomes.
Question 5: An organization is implementing Operational Level Agreements (OLAs) between internal teams. What role do metrics play in OLAs?
- Metrics are irrelevant to OLAs as they only apply to external SLAs
- Metrics define and verify the performance commitments each internal team makes to support overall SLA delivery (Correct answer)
- OLA metrics are set exclusively by senior management without input from the teams
- Metrics in OLAs track financial chargebacks between departments
Correct answer: Metrics define and verify the performance commitments each internal team makes to support overall SLA delivery
OLA metrics quantify internal team commitments, ensuring each group's performance can be tracked and linked to the broader service level targets.
Question 6: When presenting metrics to senior business stakeholders, which format is MOST aligned with ITIL best practice?
- Raw data tables showing every measurement point collected during the period
- A concise dashboard highlighting outcomes, trends, and areas requiring attention (Correct answer)
- Detailed technical logs proving system uptime calculations
- A list of all incidents and changes processed during the reporting period
Correct answer: A concise dashboard highlighting outcomes, trends, and areas requiring attention
Business stakeholders need outcome-focused summaries that support decisions, not raw technical data or exhaustive logs.
Question 7: In ITIL, what is the PRIMARY reason for distinguishing between 'activity metrics' and 'outcome metrics' when measuring a service?
- Activity metrics are mandatory for compliance while outcome metrics are optional
- Activity metrics measure work done by IT teams while outcome metrics measure results experienced by customers (Correct answer)
- Outcome metrics are easier to automate than activity metrics
- Activity metrics require senior approval while outcome metrics can be set by team leads
Correct answer: Activity metrics measure work done by IT teams while outcome metrics measure results experienced by customers
The distinction ensures organizations do not mistake busyness for value delivery — customers experience outcomes, not activities.
An ITIL practitioner is designing a measurement framework.
Which principle should guide the NUMBER of KPIs selected for a given process?