Service Request Management measurement, metrics, and continual improvement
Domain 4: Measurement, metrics, and continual improvement
This domain tests whether you can select balanced measures, interpret them end to end, and turn the results into improvement.
Core rules
- Measure the whole request-to-fulfil value stream, including waiting for approval and user confirmation-not just the time a fulfiller spends on a ticket.
- Use a balanced set: volume by request type; fulfilment lead time; SLA and OLA achievement; approval cycle time; first-time fulfilment; backlog and ageing; reopen and rework rate; self-service and automation adoption; catalogue coverage; cost per request; user satisfaction.
- Segment by request type and channel; averages can hide a slow, high-volume item.
- Link measures to outcomes: speed, quality, compliance, user experience, and cost.
- Continual improvement uses request data to automate, shift left to self-service, rationalize the catalogue, improve request models, add knowledge, and reduce avoidable demand.
Worked example
Access requests average four days against a two-day target. Analysis shows fulfilment takes one hour but manager approval waits three days. The improvement is not to tell fulfillers to work faster; it is to pre-authorize role-based access for standard roles, automate approval routing, and set an approval target. The team baselines the change, pilots it, then measures lead time and satisfaction again.
Traps that cost marks
- Measuring only ticket closure speed or agent productivity.
- Ignoring wait time and approval delay.
- Using too many metrics with no decision purpose.
- Setting targets without a baseline or segmentation.
- Treating improvement as a one-off project rather than a repeating cycle.