VeriSM Professional cheat sheet

Service value is co-created by provider and consumer; the consumer determines value through outcomes, not through the provider's output alone.

A service is a means of enabling value co-creation by facilitating outcomes the customer wants, without the customer owning specific costs and risks.

Output is the tangible or intangible deliverable of an activity; outcome is the result for the consumer enabled by one or more outputs. The distinction is a frequent exam discriminator.

Utility = fit for purpose (the service supports the consumer's performance or removes constraints); warranty = fit for use (assurance of availability, capacity, security, continuity). A service needs both.

Four dimensions of service management: organizations and people, information and technology, partners and suppliers, value streams and processes. All four apply to every service.

Cost and risk shift between provider and consumer; the provider typically absorbs some risks (e.g., infrastructure failure) in exchange for the value it captures.

Service management is a set of specialized organizational capabilities for enabling value to customers in the form of services.

Processes transform inputs into outputs; functions are teams with tools and specialized roles. A process may span multiple functions and organizational boundaries.

VeriSM is a service management approach that helps organizations adopt emerging technologies and progressive ways of working; it is product-agnostic and not a prescriptive process framework.

VeriSM definition of service management: 'the application of a set of specialized organizational capabilities that enable the delivery of value to customers in the form of services.'

The VeriSM model is a cyclical, iterative loop with these stages: Define, Produce, Provide, Respond. Governance sits at the center and informs every stage.

Define: identify consumer needs, outcomes, and the service promise; Produce: build or assemble the service using the management mesh; Provide: deliver and support the service; Respond: react to feedback and changing demand.

The management mesh is the combination of resources (people, technology, information, partners) brought together to create and deliver a product or service; it is configured per service rather than fixed.

Mesh elements are grouped as: resources (people, technology, information, partners), management practices (from multiple frameworks), environment (culture, structure, governance) and emerging technologies.

Practices are selected from any suitable framework (ITIL, Agile, Lean, DevOps, COBIT, SIAM) and blended into the mesh; VeriSM does not mandate one framework over another.

Governance provides direction and control: it sets principles, policies, and decision rights, and it defines the boundaries within which the mesh can be configured.

The model is driven by consumer needs and is iterative: output from Respond feeds back into Define, so the loop repeats as needs and technology change.

Start from the consumer and the desired outcome, then design the service promise; do not start from an existing process catalogue.

Service blueprinting maps consumer-facing interactions against supporting back-stage activities; use it in Define and Produce to expose dependencies and failure points.

Mesh configuration decision rule: choose the lightest combination of resources and practices that delivers the required outcome at acceptable risk; avoid over-engineering.

Progressive practices are selected by context, not by popularity; the Professional role justifies each practice against the outcome, risk profile, and organizational culture.

Agile delivers iterative increments with consumer feedback; Lean removes waste and improves flow; DevOps integrates development and operations for fast, reliable delivery; SIAM coordinates multi-provider service integration.

Measure outcomes and consumer experience, not only process compliance; define success criteria in Define so Respond has something objective to evaluate.

Feedback loops must be short and explicit: instrument the service, capture consumer feedback, and route it into the next Define cycle.

When integrating multiple providers, define the service integration role, shared end-to-end SLAs, and a single point of accountability for the consumer experience.

Culture and change management are part of the mesh environment: adopting new practices requires skills, communication, and leadership support, not just tooling.

Governance sets direction through principles, policies, and decision rights; management executes within those boundaries. Confusing the two is a common error.

Governance bodies evaluate, direct, and monitor: they evaluate options and stakeholder needs, direct through strategy and policy, and monitor performance and conformance.

The mesh is configured inside governance boundaries; escalation to governance occurs when a decision exceeds delegated authority or risk appetite.

Risk appetite defines how much risk the organization accepts; the mesh configuration must keep residual risk within that appetite.

Organizational structure shapes the mesh: siloed structures need explicit cross-functional coordination; product-oriented structures delegate more authority to teams.

Regulatory and contractual obligations (data protection, industry regulation, customer contracts) are hard constraints on mesh design and cannot be traded away for speed.

Decision rights must be explicit - who approves a new service, who accepts risk, who owns the end-to-end service - otherwise accountability gaps appear under pressure.

Governance is not a one-time gate: it monitors outcomes continuously and adjusts policy as the environment, technology, or consumer needs change.

Emerging technology adoption is a governance decision as much as a technical one; it requires assessment of value, risk, compliance, and organizational readiness.

Common emerging technology categories in VeriSM: cloud, big data and analytics, IoT, AI and machine learning, robotics and automation, blockchain, mobile, and social/collaboration platforms.

Cloud shifts spend from capital to operating expenditure and changes the provider's responsibility boundary (IaaS, PaaS, SaaS); it does not remove the need for service management.

Automation and AI change the mesh by replacing or augmenting human resources; they require new controls for quality, bias, and exception handling.

IoT moves the point of service interaction to connected devices, generating continuous data streams that enable proactive and predictive service delivery.

Analytics supports evidence-based decisions in Define and Respond: demand forecasting, experience measurement, and predictive failure detection.

Blockchain provides distributed, tamper-evident records; its service management relevance is trust and verification in multi-party transactions, not general storage.

Technology adoption is assessed against value, risk, cost, skills, and regulatory compliance; the technology is an enabler of outcomes, not an outcome itself.

New technology changes the skills and roles in the mesh; the Professional must plan competence development and adjust the mesh configuration accordingly.

A decision rule: adopt emerging technology when it materially improves an outcome or reduces risk within governance boundaries; pilot before scaling.

Context factors that shape practice selection: organization size, sector and regulation, culture, maturity, existing frameworks, technology landscape, and consumer expectations.

There is no single 'best practice' configuration; VeriSM treats practices as a toolbox to be selected and blended for the specific service and context.

Progressive practices include Agile, Lean, DevOps, SIAM, continuous improvement, design thinking, and value stream mapping; each addresses a distinct problem.

Value stream mapping identifies where value is created and where delay and waste occur; it is used to redesign flow rather than to document current process for its own sake.

Design thinking (empathize, define, ideate, prototype, test) supports the Define stage by grounding the service promise in real consumer needs.

Continuous improvement is a repeating cycle: measure, analyse, improve, and re-measure; improvements feed back into the mesh configuration.

Adoption is incremental: pilot, measure outcomes, then scale; scaling without evidence of outcome improvement increases risk without proven value.

Adaptation must preserve governance requirements: tailoring practices never waives regulatory, contractual, or risk-appetite constraints.

Maturity is a context factor, not a target for its own sake; the right level of formality is the one that delivers the outcome at acceptable risk.