ITIL 4 MP key terms

The series of steps an organization uses to turn demand into products and services for consumers, combining value-adding activities so customers receive what they need quickly and with as little waste as possible.

A cap on how many items may sit in one stage of a workflow at the same time. It exposes bottlenecks, shortens lead time and pushes teams to finish work before starting more.

An automated sequence that builds, tests and deploys code changes. Continuous integration merges work frequently; continuous delivery keeps the software always in a state that can be released.

Moving testing and quality checks earlier in the lifecycle so that defects are found by the people creating the work, before they reach later stages where correcting them costs far more.

A collaborative way of working in which several specialists focus together on an incident or task until it is resolved or passed on, instead of handing it sequentially between separate queues.

A problem that has been analysed and now has a documented root cause and workaround, letting support staff restore service faster while a permanent fix is planned and delivered.

A pre-authorised, low-risk change with a documented procedure that can be applied repeatedly without fresh approval each time, cutting administrative effort and delay for routine work.

A management approach that coordinates multiple internal and external service providers so that, from the consumer's point of view, they behave as one seamless supplier.

A structured review held after an incident that looks at systemic causes and learning rather than individual fault, encouraging honest reporting and reducing the likelihood of recurrence.

A technique for visualising the steps, queues and handoffs in a workflow so that time lost to waiting and waste becomes visible and flow can be improved.

A visual story of a customer's experience over time, showing actions, touchpoints, emotions and pain points at each stage from first awareness through use to exit.

A diagram of a service that maps customer-facing interactions alongside the front-stage and back-stage activities, systems and processes required to deliver them consistently.

Any point of interaction between a service provider and a consumer, such as a website, phone call, chat session or invoice, where the customer forms an impression of the service.

A critical interaction in which the customer judges service quality and forms a lasting impression, often at first contact, during service recovery or at the end of an engagement.

The principle that value emerges from interaction between provider and consumer rather than being delivered one-way, so customers and other stakeholders actively help shape the outcomes they receive.

A tool that identifies the individuals and groups affected by or able to influence a service, recording their interests, level of influence and preferred form of engagement.

A loyalty metric based on asking customers how likely they are to recommend the service; the percentage of promoters minus the percentage of detractors gives a score from -100 to +100.

A model describing three levels of relationship between provider and consumer - basic, cooperative and partnership - reflecting how closely they work together and how much responsibility each accepts.

The planned process of welcoming and equipping a new customer or employee so they can use services effectively and reach the point where they gain value as quickly as possible.

An acronym for volatility, uncertainty, complexity and ambiguity. It describes the turbulent conditions in which digital organizations must make decisions and deliver services.

The ability not merely to withstand shocks but to improve because of them, so that stress, failure and change leave the system or organization stronger than before.

The accumulated future cost of shortcuts taken in design or code, which makes later change slower and riskier, much like interest payments on a loan.

The degree to which the internal state of a system can be inferred from its outputs, such as logs, metrics and traces, so teams can locate the cause of problems quickly.

Treating a new feature as an experiment with a stated assumption and success measure, so that work is validated with real users before more investment is committed.

Deliberately injecting controlled failures into a system to observe how it responds, building confidence in resilience before real incidents occur in production.

A configuration switch that turns functionality on or off without redeploying code, separating release from deployment and allowing risky changes to be limited or quickly reversed.

A stable, cross-functional group holding end-to-end responsibility for a product or service and its outcomes, empowered to decide how best to meet user and business needs.

The capacity of a system or organization to absorb disruption, keep delivering acceptable service and recover quickly, adapting to change instead of simply breaking under strain.

The means by which an organization is directed and controlled, covering decision rights, accountability, and the policies and practices that ensure value is created and risk managed.

One of the few things that must go well for a strategy or service to succeed; CSFs focus attention and give a basis for choosing measures that actually matter.

A goal-setting format that pairs a qualitative objective with a small set of measurable key results, aligning teams around outcomes rather than volume of activity.

A documented justification for an investment setting out expected benefits, costs, risks and timescales, used to support a decision to proceed, pause or stop the work.

An ongoing activity of aligning services with changing business needs by identifying and implementing improvements, typically through a repeated cycle of plan, do, check and act.

A responsibility assignment matrix that records, for each activity, who is responsible, accountable, consulted and informed, clarifying roles and exposing gaps or duplication.

The practices used to prepare people for change by addressing communication, training, resistance and adoption, so that new ways of working are actually taken up and sustained.

The economic value lost by not delivering a feature or outcome sooner; it supports prioritisation by making the timing of delivery an explicit, comparable factor.

Seven recommendations that shape decisions and actions in any circumstance: focus on value, start where you are, progress iteratively with feedback, collaborate and promote visibility, think and work holistically, keep it simple and practical, optimise and automate.