Service management and the VeriSM model
Domain 2: Service management and the VeriSM model
This domain tests how VeriSM organizes service management. You need to know the model's components, what the management mesh does, and why VeriSM is described as flexible rather than a fixed lifecycle. Questions often ask where a practice belongs or what the model is trying to achieve.
Core rules and concepts
- The VeriSM model is a flexible service management model: it helps an organization choose and combine management practices to deliver value in a changing digital context.
- Governance sits above service management: it sets direction, risk appetite and accountability, while service management turns that direction into services.
- The management mesh is the flexible combination of practices, technologies, people, partners and culture used to deliver a service. It is assembled for the context, not bought as a fixed suite.
- Service management practices include areas such as incident management, problem management, change management and continual improvement, but VeriSM does not prescribe a single process lifecycle.
- Progressive practices and innovative technologies feed the mesh, allowing the organization to respond to new demand.
- The model is value-driven and integrated: practices are selected because they support outcomes, and they are joined up across teams.
Worked example
An e-commerce company launches a subscription delivery service. Governance approves the risk appetite and investment. Service management defines the service, the outcomes and the support arrangements. The management mesh then selects practices: incident management for delivery failures, problem management for repeated packing errors, change management for pricing changes, and continual improvement for monthly review. Cloud monitoring and automated alerts are technology elements in the mesh. Reasoning: the model does not say "implement every ITIL process". It asks what value is needed, what governance allows, and which combination of practices, technology and people will deliver it.
Traps that cost marks
- Treating the VeriSM model as a rigid lifecycle with mandatory stages.
- Confusing the management mesh with a software tool or a fixed process library.
- Putting governance inside day-to-day service management; governance sets direction and limits.
- Assuming one set of practices fits every service; the mesh changes with context.
- Ignoring progressive practices when selecting the mesh.