VeriSM Professional flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

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. VeriSM presents this as a broad, technology-inclusive discipline.

Output versus outcome

Output is the deliverable produced by an activity. Outcome is the result the consumer experiences from using that output. Value is judged on outcomes, so providers must measure beyond deliverables.

Utility and warranty

Utility means fit for purpose: the service supports the consumer's performance or removes a constraint. Warranty means fit for use: assured availability, capacity, security, and continuity. Both are required.

Four dimensions of service management

Organizations and people, information and technology, partners and suppliers, and value streams and processes. Every service must be considered across all four dimensions, which interact and constrain each other.

Value co-creation

Value is created jointly by provider and consumer through interaction; the consumer determines value in use. A provider cannot unilaterally declare a service valuable without evidence of consumer outcomes.

Cost and risk shift

In a service relationship the provider takes on some costs and risks the consumer would otherwise bear, in exchange for value returned. The balance of transferred risk shapes the service agreement.

Process versus function

A process transforms inputs into outputs toward a defined objective. A function is a team with specialized roles, tools, and responsibilities. Processes often cross several functions and organizational boundaries.

VeriSM model stages

A repeating loop of Define, Produce, Provide, and Respond, with governance at the center. Define captures consumer needs; Produce builds the service; Provide delivers it; Respond handles feedback and change.

Management mesh definition

The combination of resources brought together to create and deliver a product or service. It is configured per service rather than fixed, and can draw on people, technology, information, and partners.

Mesh composition elements

Resources (people, technology, information, partners), management practices drawn from multiple frameworks, the environment (culture, structure, governance), and emerging technologies. These are blended as needed for each service.

Role of governance in VeriSM

Governance sits at the center of the model and provides direction and control through principles, policies, and decision rights. It sets the boundaries within which the management mesh may be configured.

Framework-agnostic practice selection

VeriSM does not mandate a single framework. Practices are selected from ITIL, Agile, Lean, DevOps, COBIT, SIAM or others and blended into the mesh according to the service and context.

Iterative feedback in the model

Respond feeds back into Define, so the loop repeats as consumer needs, technology, and performance data change. The model is cyclical and iterative rather than a linear project lifecycle.

Define stage purpose

Identify consumer needs and desired outcomes, then articulate the service promise. Success criteria established here give Respond an objective basis for later evaluation.

Produce stage purpose

Build or assemble the service using an appropriate management mesh, selecting the resources and practices needed to deliver the promised outcome within governance boundaries.

Provide and Respond stages

Provide delivers and supports the service to consumers. Respond reacts to feedback, incidents, and changing demand, and routes learning back into the next Define cycle.

Service blueprinting

A technique mapping consumer-facing interactions against supporting back-stage activities and systems. It exposes dependencies, handoffs, and failure points, supporting Define and Produce decisions.

Lightest sufficient mesh rule

Choose the least complex combination of resources and practices that delivers the required outcome at acceptable risk. Over-engineering adds cost and delay without improving the consumer outcome.

Agile practice contribution

Iterative delivery in short increments with frequent consumer feedback. It suits uncertain requirements and enables early value, but needs governance to manage scope and cumulative risk.

Lean practice contribution

Focus on removing waste and improving flow through value streams. Lean identifies delays, rework, and non-value-adding steps, supporting redesign rather than documentation of existing process.

DevOps practice contribution

Integrates development and operations to deliver changes quickly and reliably through automation, shared ownership, and continuous feedback. It reduces handoff delay between build and run.

SIAM and multi-provider integration

Service Integration and Management coordinates multiple service providers around a single consumer experience, with shared end-to-end targets and one accountable integration role.

Outcome-based measurement

Measure consumer outcomes and experience rather than only process compliance. Metrics defined during Define allow Respond to judge whether the service promise was actually met.

Governance versus management

Governance sets direction through principles, policies, and decision rights. Management plans and executes within those boundaries. Confusing the two produces either stalled delivery or unmanaged risk.

Evaluate, direct, monitor

The governance cycle: evaluate options and stakeholder needs, direct through strategy and policy, and monitor performance and conformance. Monitoring closes the loop back into evaluation.

Risk appetite as constraint

The amount of risk the organization is willing to accept. Mesh configurations must keep residual risk within that appetite; exceeding it requires escalation to the governing body.

Explicit decision rights

Named authority for approving services, accepting risk, and owning end-to-end service performance. Without clarity, accountability gaps appear under pressure and escalate into disputes.

Regulatory obligations as hard limits

Data protection, sector regulation, and contractual commitments constrain mesh design and cannot be traded for speed. Tailoring practices never waives these obligations.

Cloud responsibility boundary

Under IaaS, PaaS, and SaaS the split of responsibility between provider and consumer changes, but service management duties on the consumer side remain and must be defined explicitly.

Automation and AI in the mesh

These replace or augment human resources in service delivery. They introduce new controls for quality, bias, and exception handling, and change the skills required in the mesh.

IoT effect on service delivery

Connected devices move the point of interaction to the consumer's environment and generate continuous data, enabling proactive and predictive service rather than reactive support.

Technology adoption decision rule

Adopt emerging technology when it materially improves an outcome or reduces risk within governance boundaries. Pilot at limited scale, measure outcomes, then scale only on evidence.