Creating, Delivering and Supporting Services
What the exam asks
This domain tests how teams and workflows actually create, deliver and support services: structures, culture, swarming, shift left, service desk models, service integration and the mechanics of incident, problem, change and request handling.
Core rules
- Shift left moves work to the earliest sensible point and the closest capable resource: self-service, knowledge articles, first-line resolution. It should reduce cost and lead time without lowering quality.
- Swarming assembles a collaborative group with the right competencies to resolve an incident, instead of escalating it through tiers.
- Service desk models include local, centralized, virtual and follow-the-sun. The service desk is a practice, not merely a team.
- Service integration and management (SIAM) coordinates multiple suppliers so the customer experiences one seamless service.
- Culture matters: blameless learning, collaboration, and continual improvement as everyone's responsibility.
- A support value stream runs detect, diagnose, resolve, recover, learn.
Worked example
A P1 payment failure occurs at 02:00. Instead of tier 1 to tier 2 escalation, the on-call coordinator opens a swarm with the payment platform engineer, the database specialist and the supplier contact. Reasoning: swarming shortens time to restore because expertise is engaged in parallel; the coordinator maintains stakeholder communication, and a problem record is opened afterwards to find the root cause.
Traps
- Treating shift left as pure cost-cutting; it must preserve capability and quality.
- Confusing swarming with escalation; swarming is collaborative, escalation is hierarchical.
- Forgetting that problem management follows the incident but is not part of restoring service.