Reporting, Metrics, and Continual Improvement
What the exam tests
Reporting, Metrics, and Continual Improvement tests whether you can define meaningful measures, build trustworthy reporting, and use the results to change behavior.
Core rules
- A metric needs a definition, a data source, an owner, a target, and a review cadence. Without these, numbers drift and debate replaces action.
- Useful ITAM measures include inventory accuracy verified by sample audit, license compliance percentage, hardware utilization, cost per asset, percentage of assets with a named owner, and open data-quality defects.
- Data quality is a precondition for every other metric. Report it explicitly rather than hiding it.
- Continual improvement follows a plan, do, check, act cycle; each improvement needs a baseline, an intervention, and a measured result.
- Dashboards serve different audiences: executives need trend and risk, operations need exceptions and queues.
Worked example
Inventory accuracy is claimed at 98%. A random sample of 100 assets finds 91 with correct serial, location, and owner - accuracy is 91%, not 98%. The gap comes from transfers processed in the service desk but never synchronized to the register. The team sets a 95% target, adds a nightly sync, and re-samples after 60 days at 96%. The lesson: state the method, because a metric without a sampling method is an opinion.
Traps that cost marks
- Vanity metrics that look good but change no decisions.
- Measuring tool uptime instead of asset outcomes.
- No baseline, so improvement cannot be demonstrated.
- Redefining a metric mid-year and breaking trend comparability.