ITILFND-V5 Cheat Sheet

In ITIL (Version 5), digital product and service management is the set of specialized organizational capabilities for enabling value for customers and stakeholders in the form of digital products and services. It is the evolution of ITIL service management, broadening the focus from services alone to digital products and services managed together across their whole life.

Continual improvement is a recurring activity performed at all levels of an organization to ensure that its products, services, and practices continually meet stakeholders' expectations. In ITIL (Version 5) it is a key concept of digital product and service management, keeping value relevant as needs and conditions change.

In ITIL, a product is a configuration of an organization's resources designed to offer value for a consumer. Products are usually not consumed directly; instead, parts of a product are made available to consumers as services.

Trap A product (a configuration of resources) is not the same as a service (the means of enabling value from those resources for a consumer).

In ITIL, a service is a means of enabling value co-creation by facilitating outcomes that consumers want to achieve, without the consumer having to manage specific costs and risks. Products and services are the core key concepts of digital product and service management.

A digital product is a product that is made available or delivered through digital technology, and a digital service is a service enabled by information technology and delivered through digital channels. In ITIL (Version 5) both are key concepts of digital product and service management.

In ITIL, a good is a key concept of digital product and service management: a tangible or physical item that has value and whose ownership can be transferred to a consumer, who then becomes responsible for its future use (for example, a laptop or a mobile phone).

Trap A good is a tangible item that is owned once transferred; it is not the same as access to resources, where the provider keeps ownership.

In ITIL (Version 5), the ITIL Product and Service Lifecycle is a key concept of digital product and service management: an overarching, end-to-end model describing how a set of activities is applied iteratively and non-sequentially across a product or service's whole life, from identifying an opportunity through to retirement.

Trap The lifecycle is the whole-life model of activities; it is not the ITIL value chain and not a single value stream.

Utility is the functionality offered by a product or service to meet a particular need — 'what the service does', or fitness for purpose. A service provides utility when it supports the performance of the consumer or removes constraints on the consumer, or both.

Trap Utility (fit for purpose, what it does) is not warranty (fit for use, how it performs).

Warranty is the assurance that a product or service will meet agreed requirements — 'how the service performs', or fitness for use. Warranty is typically addressed through availability, capacity, security, and continuity.

Trap Warranty assures performance levels (availability, capacity, security, continuity); it does not describe the functionality, which is utility.

In ITIL (Version 5), sustainability is a value characteristic that assures a product or service continually meets requirements for environmental responsibility, as well as social progress and economic growth.

Trap Sustainability concerns ongoing environmental, social, and economic responsibility, not the agreed performance levels, which are warranty.

In ITIL (Version 5), user experience (UX) is a value characteristic describing the whole experience a user has when interacting with a product or service and its provider, including usability and how the user feels. Together, utility, warranty, user experience, and sustainability are the four characteristics that define a service's quality.

Trap The four value characteristics are utility, warranty, user experience, and sustainability; user experience and sustainability sit alongside utility and warranty, which alone are not enough.

For enterprises, ITIL provides a common framework and language to co-create value, improve the quality and consistency of digital products and services, align IT with business objectives, and manage cost and risk.

For managed service providers, ITIL offers proven best practice and a shared vocabulary that help deliver consistent, high-quality services across many clients, strengthen service relationships, and differentiate competitively.

For digital product vendors, ITIL helps integrate service management with product development to deliver value and improve customer experience; for digital product and service management professionals, it provides a globally recognized qualification, a common vocabulary, and practical career-building guidance.

In ITIL Experience, experience is the sum of how a person thinks and feels about their interactions with a product, service, or organization. Digital experience is that experience when the interactions take place through digital technology and channels.

In ITIL Experience, trust is the confidence one party has in the reliability, integrity, and ability of another — for example, a consumer's confidence in a service provider. Trust is built over time through consistent, positive experiences.

Human-centred design is an approach that focuses on the needs, contexts, and behaviours of the people who will use a product or service, involving their perspective throughout the design process to make the result usable, useful, and desirable.

An experience level agreement (XLA) is an agreement that sets targets for the experience users and customers actually have, focusing on outcomes and how people feel, rather than only on the technical service-level measures found in a Service Level Agreement.

Trap An XLA measures experience and outcomes, while an SLA measures technical service-level targets; they are not the same agreement.

In ITIL Experience, user experience (UX) is the experience a user has when interacting with a specific product or service and its provider — for example, the usability and satisfaction of using an application.

In ITIL Experience, customer experience (CX) is the sum of the functional and emotional interactions a customer has with a service provider across the entire relationship and all touchpoints — a broader view than the user-focused UX.

Trap UX is a user's experience of using a specific product or service; CX is a customer's experience across the whole relationship and all touchpoints, so CX is broader than UX.

In ITIL Strategy, a strategy is a plan describing how an organization will achieve its objectives. A business strategy defines the organization's overall goals and how to reach them, while a digital strategy defines how the organization uses digital technology to achieve those business objectives.

In ITIL Strategy, mission is what an organization does and its reason for existing today; vision is the aspirational description of what it wants to become in the future; and purpose is what the organization does for its consumers and other stakeholders and why.

Trap Mission is what the organization does now, vision is the future it aspires to, and purpose is what it does for stakeholders and why; do not confuse the three.

VUCA stands for volatility, uncertainty, complexity, and ambiguity — the characteristics of the turbulent modern environment organizations operate in. Leadership is the ability to guide, influence, and inspire people toward achieving the organization's objectives.

In ITIL Transformation, change is the act of making something different: an addition, modification, or removal that alters a product, service, process, or way of working, and is often incremental in nature.

In ITIL Transformation, transformation is a profound and often radical change in how an organization operates, delivers value, or is structured — for example, digital transformation — going well beyond an incremental change.

Trap Transformation is a fundamental, large-scale reshaping; a change is a discrete alteration; business as usual is the normal ongoing operation, so keep the three distinct.

In ITIL Transformation, business as usual (BAU) refers to the normal, day-to-day execution of an organization's established, ongoing operations and services — the steady state that change and transformation act upon.

In ITIL, a service offering is a formal description of one or more services designed to meet the needs of a target consumer group. A service offering may include goods, access to resources, and service actions.

A service offering explains what a provider offers by combining goods, access to resources, and service actions in different proportions, tailoring the offering to the needs of each target consumer group.

In ITIL, service interactions are the ways in which service providers and service consumers engage with one another to co-create value, occurring across the touchpoints of the service relationship.

Service interactions can take the form of service actions, transfer of goods, or access to resources. For digital services, the main form of interaction is access to resources — for example, consumers using cloud environments, applications, storage, or networks that remain under the provider's control.

Service actions are activities performed by a service provider to address a consumer's needs — for example, user support provided by a service desk. They are one of the three components of a service offering.

Transfer of goods is a service-offering component in which ownership of a tangible item (a good) passes to the consumer, who then takes responsibility for its future use — for example, receiving a laptop or a mobile phone.

Trap In transfer of goods ownership passes to the consumer; in access to resources the provider keeps ownership.

Access to resources is a service-offering component in which the provider grants the consumer access to use resources (such as networks, storage, or applications) under agreed terms and conditions, while the provider retains ownership and control.

Trap Access to resources does not transfer ownership; the consumer may use the resources only during the agreed consumption period.

The three service-offering components are distinguished by ownership and effort: transfer of goods hands over ownership of an item, access to resources lets the consumer use provider-owned resources without transferring ownership, and service actions are tasks the provider actively performs for the consumer.

Trap Confusing the three components: goods transfer ownership, access to resources does not, and service actions are provider-performed tasks.

Many digital service providers aim to reduce or eliminate service actions by handling them through automation and self-service, which lowers cost and improves the consistency and reliability of service delivery.

In ITIL, value is the perceived benefits, usefulness, and importance of something. Value is subjective — it is defined and judged by the stakeholder who receives it, especially the service consumer.

Trap Value is judged by the consumer's perception, not by the provider's cost of delivery.

Value co-creation means that value is created jointly through the active collaboration of service providers and service consumers within a service relationship; neither party creates the value alone.

Value contributes to co-creation because the pursuit of value is the shared goal that directs the collaboration: providers apply resources and capabilities while consumers provide requirements and correct use, so that valued outcomes are realized together.

In ITIL, cost is the amount of money spent on a specific activity or resource. In value co-creation, a service can both remove costs from the consumer (costs the provider now bears) and impose costs on the consumer (the price of consumption).

In ITIL, risk is a possible event that could cause harm or loss, or make it more difficult to achieve objectives. Risk can also be defined as uncertainty of outcome and can be positive as well as negative.

Outcomes, costs, and risks contribute to value co-creation together: value is achieved only when desired outcomes are reached while the associated costs and risks are optimized. A provider takes on some costs and risks so the consumer can achieve outcomes more effectively than alone.

Trap Costs and risks are to be optimized, not driven to zero, and outcomes are not to be maximized regardless of the costs and risks they create.

In value co-creation, a service removes some risks from the consumer (the provider takes them on), but consuming a service can also introduce new risks to the consumer - for example, dependence on the provider or a security breach at the provider affecting the consumer. Like costs, risks are considered in both directions: removed from and imposed on the consumer.

Trap Assuming a service only ever reduces consumer risk; consumption itself introduces new risks that must be weighed.

In ITIL, an output is a tangible or intangible deliverable produced by an activity — the thing that is created, such as a report or a provisioned server.

In ITIL, an outcome is a result for a stakeholder, enabled by one or more outputs. Outcomes are what the consumer actually wants to achieve with the support of a service.

The difference between output and outcome is that an output is a deliverable the service produces, whereas an outcome is the result the consumer achieves because of that output. A service can deliver its outputs and still fail to produce the desired outcome.

Trap An output (for example, a monthly report) is not the same as an outcome (for example, better-informed decisions); delivering outputs does not guarantee the outcome.

The four value characteristics contribute to co-created value together: utility makes a service fit for purpose, warranty makes it fit for use, user experience shapes how people feel using it, and sustainability assures ongoing environmental, social, and economic responsibility.

Trap All four characteristics contribute to value; utility and warranty alone are not sufficient, because user experience and sustainability also shape perceived value.

Feedback contributes to value co-creation by giving providers and consumers information about how well outcomes are being achieved, so that products and services can be adjusted and continually improved to keep co-creating value.

In ITIL, an organization is a person or a group of people that has its own functions with responsibilities, authorities, and relationships to achieve its objectives. Organizations can take the role of service provider, service consumer, or both.

A service provider is an organization (or part of one) that takes on the role of providing services, while a service consumer is an organization or role that receives and uses services. The same organization can be a provider in one relationship and a consumer in another.

Trap Provider and consumer are roles, not fixed identities; one organization can be a provider in one relationship and a consumer in another.

A digital product vendor is an organization that develops and supplies digital products, such as software, for others to use. Unlike a service provider, a vendor primarily provides the product itself rather than continuously co-creating value in an ongoing service relationship with the consumer.

Trap A digital product vendor supplies the product; a service provider engages in an ongoing service relationship to co-create value, so they are different roles.

A service consumer receives and uses services to achieve outcomes, whereas a digital product vendor supplies digital products to others. The consumer is on the receiving side of value, while the vendor is a source of the products used to enable that value.

Trap Confusing the service consumer (who uses services to get outcomes) with the digital product vendor (who supplies products).

A service relationship is a cooperation between a service provider and a service consumer through which value is co-created. It is the umbrella concept within which the relationship types, consumer roles, service interactions, and the service journey all operate.

In ITIL, a basic service relationship is transactional, with the provider simply delivering a standard service; a cooperative relationship adds coordination and shared information toward common goals; and a collaborative relationship is a close partnership in which both parties actively work together and share risks and rewards.

The difference between the three relationship types is the depth of engagement: basic relationships are transactional and low-integration, cooperative relationships involve coordinated joint working, and collaborative relationships are the most integrated, with shared objectives, risks, and rewards.

Trap The increasing order of integration is basic then cooperative then collaborative; collaborative is the closest partnership, not the most transactional.

In ITIL, the three service consumer roles are the sponsor, who authorizes the budget for service consumption; the customer, who defines the requirements for a service and takes responsibility for the outcomes of consumption; and the user, who actually uses the service.

Trap Sponsor authorizes the budget, customer defines requirements and owns outcomes, and user uses the service; one person may hold more than one role, but the roles are distinct.

In ITIL, the service journey is the complete, end-to-end experience a service consumer has with a service provider across all of their touchpoints and interactions over the course of the relationship.

Trap The service journey is the whole experience across all touchpoints; it is not a single value stream or a lifecycle activity.

In ITIL, service quality is the totality of a service's characteristics that are relevant to its ability to satisfy stated and implied needs — a holistic measure of how well the service meets both explicit requirements and unspoken expectations.

Trap Service quality is the totality of characteristics; it is not any single element such as warranty or an SLA.

In ITIL, a service level is one or more metrics that define or measure the expected or achieved performance of a service against agreed targets.

In ITIL, a Service Level Agreement (SLA) is a documented agreement between a service provider and a customer that identifies the required services and the expected service levels. It is the tool used to set and monitor targets, not the definition of service quality itself.

Trap An SLA is the documented agreement of targets, while service quality is the overall fitness of the service; they are not the same thing.

ITIL (Version 5) defines four dimensions of product and service management: organizations and people; partners and suppliers; information and technology; and value streams and processes. All four must be considered to effectively and efficiently facilitate value through products and services.

Trap The four dimensions are not the components of the ITIL Value System (guiding principles, governance, value chain, management practices, continual improvement); that is a separate model.

Every one of the four dimensions applies to all of an organization's products and services and to service management as a whole. Each dimension represents a perspective that is essential to creating value, so none can be ignored without weakening the others.

The four dimensions must be addressed holistically, balanced and coordinated together, because they are interconnected. Failing to give adequate attention to any one dimension can lead to sub-optimal or unfit products and services.

Trap Optimizing a single dimension (for example, buying advanced technology) while neglecting another (such as people's skills) undermines the overall value delivered.

The four dimensions are cross-cutting perspectives applied across all activities, whereas the ITIL Value System is the operating model itself. The value chain is a component of the Value System, not one of the four dimensions.

Trap A common error is to list 'value chain' or a guiding principle as one of the four dimensions.

ITIL (Version 5) refers to them as the four dimensions of product and service management. This is the current naming; the four areas themselves (organizations and people, partners and suppliers, information and technology, value streams and processes) are unchanged.

Trap Mislabeling them as only 'service management' dimensions, or inventing additional dimensions.

The organizations and people dimension addresses the human side of an organization: its roles and responsibilities, formal organizational structures, culture, staffing, and the required competencies and skills. It ensures the organization is structured and managed so that people can support its objectives.

For this dimension to support value creation, an organization needs a culture that supports its objectives and the right levels of capacity and competency among its people. Clear roles, effective leadership, and good communication are essential.

Organizational structures, management and leadership, team culture, and staff training or competencies all belong to the organizations and people dimension. It concerns the service provider's own people.

Trap Relationships with third parties or supplier contracts belong to partners and suppliers, not organizations and people.

The information and technology dimension includes the information and knowledge required to manage products and services, and the technologies used both within the services themselves and to support service management. It also covers how components relate and how information is exchanged.

When selecting technology for this dimension, an organization considers factors such as compatibility with existing systems, compliance with policies and regulations, security, and alignment with its strategy. Information management also addresses the security and confidentiality of data.

Examples of this dimension include the applications, databases, and communication systems that make up a service, as well as tools such as workflow, AI, and cloud platforms that support service management.

Trap The way work flows through these tools is value streams and processes; the tools and information themselves are information and technology.

The partners and suppliers dimension encompasses an organization's relationships with the other organizations involved in the design, development, deployment, delivery, support, and continual improvement of its services. It includes the contracts and agreements that govern those relationships.

An organization's use of partners and suppliers is shaped by factors such as cost, expertise, and the availability of resources, and is formalized through contracts and service level agreements. Service integration and management (SIAM) coordinates multiple suppliers so they act as a coherent whole.

When external organizations help design, deliver, or support a service, they fall under the partners and suppliers dimension, positioning them as co-creators of value alongside the organization.

Trap Third-party contributions are partners and suppliers, not organizations and people, which concerns the provider's own workforce.

The value streams and processes dimension is concerned with how the various parts of the organization work in an integrated and coordinated way to create and deliver products and services. It defines the activities the organization performs and how they are organized to enable value creation efficiently.

In the value streams and processes dimension, a value stream is a series of steps an organization uses to create and deliver products and services, while a process is a set of activities that transforms inputs into outputs. Together they describe how work is sequenced and performed.

This dimension focuses on how the organization's internal activities flow and are coordinated. Which third parties are involved is covered by partners and suppliers, not by value streams and processes.

Trap Confusing this dimension with value stream mapping, which is a separate topic about analysing and improving a specific value stream.

The four dimensions (organizations and people, partners and suppliers, information and technology, and value streams and processes) are the internal factors, or perspectives, that an organization must balance to facilitate value through its products and services. Each must be given adequate attention.

Internal factors, such as an organization's structure, culture, resources, and processes, can be shaped and managed by the organization. External factors, analysed with PESTLE, arise from the wider environment and are usually beyond the organization's direct control.

Trap A new data-protection law or an economic downturn is an external factor, not something the organization can manage as an internal factor.

Because the four dimensions are interconnected, they are managed holistically rather than separately, and always within the constraints imposed by external factors. Balancing them together, under those constraints, is what keeps products and services fit for purpose and use.

The four dimensions are affected by external factors that are often beyond the organization's control, such as government regulation or economic conditions. These external factors can be analysed using the PESTLE model.

Trap External factors influence every dimension, not just one; for example, a new law can affect people, technology, suppliers, and processes at once.

PESTLE is the model used to categorize external factors influencing the four dimensions: political, economic (economical), social, technological, legal, and environmental. Each letter represents a type of external influence on the organization.

Trap PESTLE covers external factors only; the four dimensions themselves are internal and are not part of PESTLE.

Factors such as new legislation, government policy, market and economic conditions, and social trends originate outside the organization and are treated as external factors. The organization must respond to them but cannot directly control them.

Trap Staffing levels or an internal process are internal factors; do not classify them under PESTLE.

Political factors include government policy, political stability, taxation, and trade or labour regulation. Economic factors include economic growth, interest rates, inflation, and exchange rates that affect costs and demand.

Social factors include demographics, cultural attitudes, and lifestyle or population trends. Technological factors include innovation, automation, and the rate of technological change that can create opportunities or make capabilities obsolete.

Legal factors include employment law, data protection, health and safety, and other compliance requirements. Environmental factors include climate, ecological concerns, and environmental regulations or sustainability expectations.

Trap A data-protection statute is a legal factor, whereas climate or emissions targets are environmental factors.

Correctly classifying an external factor means matching it to the right PESTLE category; for example, interest rates and inflation are economic factors, while political stability is a political factor. This helps an organization analyse how each type of influence affects its four dimensions.

Trap Interest rates are economic, not political; a new privacy law is legal, not merely technological.

In ITIL (Version 5), the Product and Service Lifecycle is the overarching, end-to-end model that shows how a common set of key activities applies to every product and service. It represents the shared lifecycle of digital products and services, which are managed together with a single, integrated approach.

Trap Confusing the lifecycle model with the value chain; the value chain is the operating model of interconnected activities that an organization arranges into value streams, not the whole-life model itself.

The Product and Service Lifecycle is not the same as the value chain, a value stream, or the continual improvement model. The value chain is the operating model of interconnected activities; a value stream is a situation-specific series of steps for one particular product or service; the continual improvement model is a repeatable guide for improvement work.

Trap Selecting 'a set of interconnected activities arranged into value streams' (the value chain) or 'a series of steps for one product' (a value stream) as the definition of the lifecycle.

ITIL (Version 5) treats digital products and services as two perspectives of the same technology-based solution, so they share the same lifecycle and should be managed together. The model adopts a holistic, ecosystem approach rather than a siloed way of working.

The ITIL Product and Service Lifecycle consists of eight activities: discover, design, acquire, build, transition, operate, deliver, and support. Every product and service is managed through these same eight activities.

Trap Listing an ITIL 4 six-activity service value chain (plan, improve, engage, design & transition, obtain/build, deliver & support) or a different count; Version 5 names eight lifecycle activities.

The eight lifecycle activities are the same eight activities that make up the Version 5 value chain. The lifecycle shows how they apply across a product or service's whole life, while the value chain arranges them into value streams to respond to demand.

Trap Assuming the lifecycle and the value chain use different sets of activities; they share the identical eight.

The eight lifecycle activities redefine the five ITIL v3 lifecycle stages (service strategy, service design, service transition, service operation, and continual service improvement) into a more holistic, non-linear set. This reflects the shift away from separate, sequential stages.

Trap Naming the v3 stages (strategy, design, transition, operation, CSI) as the Version 5 lifecycle activities.

The lifecycle activities apply across the entire life of a product or service, from the initial opportunity or idea through to its eventual retirement. This gives a consistent, end-to-end way to manage a product or service rather than covering only its development.

Trap Thinking the lifecycle covers only creation or build; it spans the whole life, including running, supporting, and retiring the product or service.

Because the model is holistic rather than a single moving pipeline, different versions of the same product or service can exist in several lifecycle activities at the same time. For example, one version can be live and operating while a newer version is still being designed.

The lifecycle applies to every product and service, giving the organization a consistent, end-to-end way to manage quality, risk, and compliance throughout their life. This whole-life view is what makes the model an ecosystem rather than a one-off project.

The lifecycle activities are not performed in a fixed sequence or a straight line. An organization can move backwards or forwards between any of the activities as its needs require, and a transition can happen between any two activities.

Trap Treating the eight activities as a linear, one-way plan-build-run or waterfall pipeline that must be followed in order.

The activities can be used iteratively, being repeated and revisited many times over a product or service's life as needs and conditions change. For instance, feedback while a service is live can send work back to 'design' and then forward again.

The non-linear, iterative model replaces the traditional sequential plan-build-run way of working. Teams can collaborate across several activities at the same time instead of handing work down a fixed line.