1.3Service lifecycle, value co-creation, and SLM

ITIL 4 holds that a service's value is not delivered one-way by the provider but is co-created with the consumer. The provider enables value through the service, but actual value materializes only when the consumer achieves their own outcome. Thus a service manager must evaluate operations by "what outcome the customer gained," not "what we delivered."

The core mechanism that protects agreed value is SLM (service level management). SLM agrees an SLA with the customer, continually measures and reviews achievement, and links shortfalls or improvement opportunities to a service improvement plan (SIP). The key point is that across the service lifecycle—strategy, design, transition, operation, continual improvement (or the ITIL 4 activities)—SLM keeps monitoring whether "the promised value is preserved." SLM is not a one-off signing of an SLA but an ongoing effort to keep value flowing.

Suppose a service manager notices that on a core service, response time stays within the SLA target yet customer satisfaction is falling. By the numbers alone, "SLA met, no problem," but from a value-co-creation view the consumer may not be getting the expected outcome (business running smoothly). In an SLM review, dialogue with the customer reveals that a monthly batch delay was disrupting period-close—something the average-response-time metric barely reflects. The manager then revises the SLA metric to fit the outcome (guaranteeing batch completion time) and folds the improvement into the SIP. The essence of SLM is re-measuring value around the customer's outcome, not around merely hitting a metric.

1.3.1Section summary

• A service's value is not delivered one-way but co-created through the consumer's outcome.
• SLM agrees an SLA, continually measures and reviews achievement, and links shortfalls to the SIP.
• Meeting an SLA metric differs from realizing value; revising metrics around the customer's outcome is the manager's judgment.