🌐
VeriSM — Value-driven, Evolving, Responsive, Integrated Service Management
IFDC / EXIN · Modern Service Management Approach · Digital Organisation Focus
Interactive study manual covering the VeriSM model, Management Mesh, four elements, progressive model, governance, and 36 flash cards.
VeriSM Model Management Mesh 4 Elements Progressive Stages Governance 36 Flash Cards
VeriSM is a service management approach designed for the digital organisation. Unlike ITIL which prescribes specific practices, VeriSM is deliberately flexible — it describes principles and a model for how organisations can manage services effectively by consuming, producing, and evolving a Management Mesh of practices tailored to their unique context.
4
VeriSM Elements
1
Management Mesh
4
Progressive Stages
2019
Published
EXIN
Certification body
🔤 What VeriSM Stands For
V
Value-driven
Everything the service provider does must create value for consumers and the organisation. Value is the north star.
e
Evolving
The approach evolves continuously — what worked yesterday may not work tomorrow. Embrace change, not stability.
ri
Responsive
Respond to consumer and business needs quickly. Agility over rigidity. Speed of response is a service differentiator.
SM
Integrated Service Management
Integrate multiple management practices — ITIL, DevOps, Agile, Lean — into a cohesive approach, not competing frameworks.
Why VeriSM was created: Traditional ITSM frameworks like ITIL were designed for stable, process-driven IT organisations. Digital organisations work differently — faster, more agile, with blurred boundaries between IT and business. VeriSM was designed specifically for this context: organisations where technology is the product, not just the support function.
💡 VeriSM Core Philosophy — 5 Principles
1
Focus on value — every activity must justify itself through the value it creates for consumers
2
Use what works — don't be dogmatic about frameworks; combine ITIL, DevOps, Agile, Lean as needed
3
Keep it simple — complexity without purpose is waste; simplify processes wherever possible
4
Respond to change — build service management that adapts rather than resists change
5
Deliver outcomes — measure success by outcomes delivered to consumers, not by process compliance
The VeriSM Model shows how a service provider organisation operates — from governance at the top, through the Management Mesh, to the production and delivery of services. It is a layered model where each layer shapes what is possible below it.
🏗 The VeriSM Model — Full Stack
Governance
Sets direction, defines organisational principles, establishes boundaries for the Management Mesh · Ensures accountability and oversight
↓
Management Mesh
The flexible combination of resources, environment, emerging technologies, and management practices available to the service provider
🏢 Organisational Environment
Culture, structure, size, risk appetite, capabilities, funding model
🔧 Resources
People, technology, processes, partners, information, finance
🚀 Emerging Technologies
AI, cloud, IoT, blockchain, automation, analytics — shaping what is possible
📚 Management Practices
ITIL · DevOps · Agile · Lean · COBIT · ISO 20000 · SIAM · SRE · any others
↓
Produce
Define, create, and test the service
Provide
Deploy, run, and support the service
↓
Respond
Handle incidents, requests, and feedback — feeding learning back into the mesh
↓
Consumer
Uses the service and provides feedback — the source of value definition and improvement signals
⚡ The key insight: The Management Mesh is not fixed. It evolves as the organisation grows, as new technologies emerge, and as consumer needs change. VeriSM explicitly designs for this evolution — unlike frameworks that assume a fixed process model.
VeriSM is built on four elements that work together to enable effective service management. These are not sequential steps — they interact continuously, with each element influencing the others.
G
Governance
The system by which the service provider organisation is directed and controlled. Sets the constraints and direction within which service management operates.
→ Organisational strategy and direction
→ Risk appetite and compliance boundaries
→ Accountability and decision rights
→ Stakeholder requirements
→ Policies that shape the Management Mesh
SM
Service Management Principles
The organisation's defined approach to service management — the principles, standards, and practices selected from the Management Mesh to guide how services are delivered.
→ Selected management practices
→ Service management standards
→ Defined ways of working
→ Consumer focus principles
→ Continual improvement approach
MM
Management Mesh
The flexible combination of resources, environment, technologies, and management practices available to the service provider. Not prescriptive — tailored to the organisation's context.
→ Organisational environment (culture, structure)
→ Resources (people, technology, finance)
→ Emerging technologies
→ Management practices (ITIL, DevOps, Agile etc.)
→ Evolves as context changes
SO
Service Offering
What the service provider delivers to consumers — defined in terms of outcomes and value, not just technical components. The service offering is what the consumer experiences.
→ Consumer-defined value
→ Outcome-based definition
→ Service catalogue items
→ SLA commitments
→ Continually refined based on feedback
The Management Mesh is VeriSM's defining concept — a flexible toolkit of management practices that the service provider selects and combines based on their context. VeriSM does not prescribe which practices to use. It provides a framework for selecting and integrating them intelligently.
The practices available in the mesh span multiple disciplines. VeriSM explicitly includes practices from other frameworks rather than replacing them — enabling organisations to stop debating "ITIL vs DevOps" and start combining them purposefully.
🔧 Service Management
ITIL 4
Practices for IT service management — incident, change, problem, SLM, and the service value system. A key input to the mesh for most organisations.
🔧 Service Management
ISO/IEC 20000
International SMS standard providing certifiable requirements for service management. Used to structure and certify the mesh's service management practices.
🔧 Service Management
SIAM
Service Integration and Management — used when the mesh needs to coordinate multiple service providers in the environment.
🔧 Service Management
SRE (Site Reliability Engineering)
Google's approach to reliability engineering — SLOs, error budgets, toil reduction. Increasingly used alongside ITIL for digital-native services.
🔧 Service Management
Customer Experience Management
Practices focused on understanding and improving the end-to-end experience of service consumers — beyond technical SLA metrics.
⚡ Development
DevOps
Cultural and technical practices that unite development and operations — CI/CD, infrastructure as code, automation, and collaborative ownership.
⚡ Development
Agile (Scrum / Kanban)
Iterative, value-driven development and delivery practices. Scrum sprints, Kanban flow, and agile ceremonies as selected from the mesh.
⚡ Development
Lean
Waste elimination and flow optimisation principles applied to service management — reducing unnecessary process steps and handoffs.
⚡ Development
Design Thinking
Human-centred approach to service design — deeply understanding consumer needs before defining solutions. Increasingly used in digital service design.
⚡ Development
SAFe / Disciplined Agile
Scaled agile frameworks for enterprises — applying agile principles at portfolio and programme level, not just team level.
🏛 Governance
COBIT 2019
IT governance and management framework — providing governance objectives and design factors to shape how the mesh is structured and controlled.
🏛 Governance
CMMI
Process maturity model — used to assess and improve the maturity of specific practice areas within the management mesh.
🏛 Governance
Risk Management (ISO 31000)
International risk management standard — providing principles and guidelines for managing risk across the service management environment.
✅ Quality
ISO 9001 Quality Management
Quality management system standard — providing quality assurance principles applicable to service delivery processes within the mesh.
✅ Quality
Six Sigma
Data-driven quality improvement methodology — DMAIC (Define, Measure, Analyse, Improve, Control) applied to service management processes.
✅ Quality
Continual Service Improvement
Systematic approach to identifying, prioritising, and implementing improvements across all elements of the management mesh.
VeriSM describes a progressive model for how organisations evolve their service management capability. Unlike maturity models with rigid level requirements, VeriSM's progressive model describes common patterns of evolution — helping organisations understand where they are and what comes next.
🌱
Survive
Basic service management. Reactive. Keeping the lights on. Minimal process. Success depends on individual heroics. No formal Management Mesh.
🏗
Build
Establishing core service management practices. Beginning to form a Management Mesh. Some consistency emerging. Governance being defined.
🚀
Thrive
Well-functioning Management Mesh. Consistent service delivery. Consumer focus embedded. Practices integrated and evolving. Proactive improvement culture.
⭐
Optimise
Continuously optimising management mesh and service delivery. Data-driven decisions. Consumer experience measured and improved systematically. Benchmark-leading.
🔄 The VeriSM Service Model Cycle
🎯
Define
Consumer needs & service requirements
🏗
Produce
Design, build, and test the service
🚀
Provide
Deploy, run, and support live
🔄
Respond
Handle events and improve
VeriSM is often positioned as a modern alternative to ITIL, but the relationship is more nuanced. Understanding how it differs from — and complements — ITIL 4 and SIAM helps IT leaders decide when VeriSM adds value.
DimensionVeriSMITIL 4SIAM
Primary focusFlexible, value-driven service management for digital orgsBest practices for IT service managementMulti-supplier coordination and integration
ApproachPrinciple-based — select and combine what worksPractice-based — 34 defined practicesMethodology — specific roles and governance model
PrescriptivenessVery low — describes a model, not specific processesModerate — defined practices with guidanceModerate — defined layers, roles, and governance
Relationship to other frameworksExplicitly includes ITIL, DevOps, Agile, Lean in the meshIntegrates with Agile, DevOps, LeanUses ITIL practices at each layer
CertificationEXIN VeriSM Foundation and ProfessionalITIL 4 Foundation through to MasterEXIN / BCS Foundation and Professional
Certification typeIndividual practitionerIndividual practitionerIndividual practitioner
Best forDigital-native orgs, startups scaling service management, orgs frustrated with heavy ITIL implementationAny IT organisation establishing or improving ITSMLarge enterprises with 3+ service providers
Maturity assumptionWorks at any maturity level — designed to evolve with the orgCan be applied at any maturityRequires existing ITSM foundations
Tooling guidanceMinimal — choose tools that fit the meshStrong — ITSM tools well understoodStrong — shared toolset is core to SIAM
Governance modelGovernance as one of four elementsGovernance within SVSThree-layer ecosystem governance
When to choose VeriSM: If your organisation is digital-first, has outgrown rigid process frameworks, or is struggling to reconcile ITIL with DevOps and Agile — VeriSM provides a unifying model. It works best as an overarching philosophy that includes ITIL practices rather than replacing them.
36 flash cards covering VeriSM key concepts, the Management Mesh, and exam-relevant knowledge. Click a card to flip it.
Card 1 of 36
Question
Tap to reveal answer
Answer