IT Service Management Fundamentals and Governance
This domain tests whether you can use service management vocabulary precisely and explain how governance differs from management. Expect definitions of service, product, service offering, service relationship, utility and warranty, plus the components of a service value system and the role of a governing body.
Core rules and concepts
- A service enables value co-creation by facilitating outcomes the customer wants without the customer managing specific costs and risks.
- Utility is fit for purpose: what the service does. Warranty is fit for use: availability, capacity, continuity and security. Both are needed for value.
- A service value system links demand and opportunity to value through guiding principles, governance, the service value chain, practices and continual improvement.
- Governance evaluates, directs and monitors. Management plans, executes and controls within the boundaries the governing body sets.
- Accountability cannot be delegated. Use RACI to separate responsible, accountable, consulted and informed roles.
Worked example
A platform team wants to bypass the change advisory board for a low-risk patch. The reasoning is not that the team is busy. First ask whether the change fits a pre-authorized standard model with defined risk criteria. If it does, the governing body has already delegated that authority; the team records the change and proceeds. If it does not, it is a normal change and needs assessment and approval. Governance sets risk appetite; management applies it. Skipping the model without that decision is a control failure, not agility.
Traps
Confusing governance with day-to-day management; defining a service by its technology rather than customer outcomes; mixing utility and warranty; treating a framework as a mandatory checklist; assigning accountability to a group rather than a named role.