Measurement, engagement and underpinning agreements

A target with no service behind it

An organisation that agrees a target for the average response time of the order-entry transaction, where that measure attaches to no service in the catalogue, has produced an individual metric with no purpose behind it. The practice warns against this because a number that is not tied to a defined service cannot be judged: there is nothing to say whether hitting it means anything for anybody.

It is also how organisations accumulate dashboards nobody acts on. The requirement is that targets relate to a defined service, and through that service to what the customer is trying to achieve.

The capability the practice actually runs on

Beyond producing reports, service level management depends most on listening to and engaging with customers so their real needs and priorities are understood. Reporting is the visible output; engagement is what makes the reported things the right things.

That is why the practice is often described as relationship work rather than measurement work, and why the wrong options here — better dashboards, more frequent reporting, automated data collection — all improve the machinery without improving what the machinery is pointed at.

Three commitments, sorted by the other party

An SLA is with the customer. An operational level agreement is with another part of the SAME organisation — an internal IT department agreeing with its own network team that network faults affecting payroll are picked up within fifteen minutes has an operational level agreement, and the giveaway is that no external party is involved. An underpinning contract is with an external supplier, and it exists so that a commitment made to the customer is actually deliverable.

The pattern the exam likes is a provider that has promised four-hour restoration to a customer while delivery depends on an outside hosting company. The right answer is an underpinning contract with terms that support the four-hour commitment: you cannot promise the customer something your supplier has not promised you.

A fourth term rounds this out and is not an agreement at all. A service level requirement is a stated need, expressed before anything is negotiated. If a question describes what the customer says they need, with nothing settled, that is a requirement rather than an agreement.

What "performing acceptably" is judged from

No single source answers whether a service is performing acceptably. The practice draws on engagement with the customer, operational metrics, business metrics and what customers say back, all TOGETHER, and the correct option is always the one that combines them rather than the one that nominates a best single source.

The reason is the watermelon again: operational metrics alone produce the green-report failure, and feedback alone produces an impression with no evidence behind it. Each source covers a blind spot in the others.