ITIL® 5 Foundation Exam Prep: The Complete Study Guide

Why ITIL® 5 Foundation Exam Prep Is About Understanding, Not Memorizing

The ITIL® 5 Foundation exam rarely asks you to recite a definition word-for-word. Instead, it presents a short scenario and asks which concept applies, or asks you to tell two similar-sounding ideas apart — Incident vs Problem, Utility vs Warranty, Output vs Outcome.

That's why the most efficient ITIL® 5 Foundation exam prep focuses on relationships between concepts rather than isolated flashcard-style memorization. Once you understand how the pieces fit together, most exam questions become much easier to answer, even ones you haven't seen phrased that exact way before.

What's Covered on the ITIL® 5 Foundation Exam

At a high level, ITIL® 5 Foundation exam prep covers six broad areas. You don't need to master every management practice in depth for the Foundation level, but you should recognize the big ideas within each area below.

Key Concepts of Service Management

The foundational vocabulary everything else builds on:

• What a service is, and what ITIL® 5 Foundation actually teaches
• Utility vs Warranty
• Outputs vs Outcomes
• Customer vs User
• Cost and Risk as they relate to value

The Guiding Principles

Seven recommendations that apply regardless of role or organization — things like "Focus on Value," "Start Where You Are," and "Keep It Simple and Practical."

The Four Dimensions of Service Management

A reminder that services depend on more than technology — organizations, people, partners, suppliers, and value streams all shape whether a service actually succeeds.

The Service Value System

The overall framework connecting governance, guiding principles, management practices, the service value chain, and continual improvement into one system.

The Service Value Chain

Six interconnected activities — Plan, Improve, Engage, Design & Transition, Obtain/Build, and Deliver & Support — that transform demand into value.

Management Practices

Practical, day-to-day activities. The ones tested most often at Foundation level include:

• Incident Management
• Problem Management
• Change Enablement
• Service Request Management
• Continual Improvement

A Simple Way to Structure Your Study Time

You don't need weeks of study to prepare for ITIL® 5 Foundation. A focused, structured approach over a single weekend is realistic for most learners, especially if you build it around three phases:

• Learn the concepts — read through the core ideas once, focusing on how they connect rather than memorizing wording.
• See them applied — real-world examples make abstract definitions click, which is why every guide on this site includes one.
• Test yourself — realistic practice questions reveal which concepts still feel shaky before you sit the actual exam.

That three-phase structure is exactly what Pass The Foundation is built around — it's not a coincidence.

Common Mistakes That Cost Candidates Points

A few patterns show up across almost every topic on this exam:

• Memorizing definitions without understanding how concepts relate to each other.
• Assuming every management practice works in isolation, rather than as part of one connected system.
• Confusing similar-sounding concept pairs under exam time pressure (Incident vs Problem is the most common example).
• Treating ITIL as a rigid rulebook rather than a flexible set of practices meant to be adapted to context.

Free Ways to Start Preparing Right Now

You don't need to commit to anything to get a feel for where you stand. Take the free diagnostic quiz to see how you score on real exam-style questions, or browse the topic guides below to review any specific concept you want to double-check.

Explore Every ITIL® 5 Foundation Topic

• ITIL® 5 Foundation Exam Prep: What Is ITIL® 5 Foundation?

  ITIL® 5 Foundation is an entry-level certification that teaches the core concepts of modern IT service management. It provides a common language and framework for delivering technology services that create value for customers and the business.

• ITIL® 5 Foundation Exam Prep: Service Value System Explained

  The Service Value System (SVS) is the central operating model within ITIL® 5. It explains how all components of an organization work together to create value through services. Rather than focusing on individual processes, the SVS shows how governance, continual improvement, guiding principles, management practices, and the service value chain combine to help organizations consistently deliver value.

• ITIL® 5 Foundation Exam Prep: Service Value Chain Explained

  The Service Value Chain is the operating model within ITIL® 5 that describes how organizations transform demand into value. It consists of six interconnected activities that work together to design, build, deliver, support, and continually improve services.

• ITIL® 5 Foundation Exam Prep: Utility vs Warranty Explained

  Utility and Warranty work together to define the value of a service. Utility answers: can the service do what I need? Warranty answers: can I depend on the service when I need it? A service needs both to deliver value.

• ITIL® 5 Foundation Exam Prep: Outputs vs Outcomes Explained

  Outputs and Outcomes are often confused, but they describe two very different things. An Output is what a service produces. An Outcome is the result the customer actually achieves. ITIL focuses much more heavily on Outcomes because customers ultimately care about results, not just deliverables.

• ITIL® 5 Foundation Exam Prep: Customer vs User Explained

  One of the most common ITIL® Foundation exam questions asks you to distinguish between a Customer and a User. A Customer defines requirements, agrees to the service, and is accountable for the outcomes. A User actually consumes or uses the service. Sometimes the Customer and User are the same person, but often they are not.

• ITIL® 5 Foundation Exam Prep: Incident Management Explained

  Incident Management is the ITIL® practice responsible for restoring normal service operation as quickly as possible after an interruption. The goal isn't necessarily to find the root cause. The goal is to get users working again as quickly as practical.

• ITIL® 5 Foundation Exam Prep: Incident vs Problem Explained

  Incidents and Problems are closely related, but they have different goals. An Incident is an interruption to a service that needs to be restored quickly. A Problem is the underlying cause of one or more incidents. Think of it like this: Incident = fix it now. Problem = prevent it from happening again.

• ITIL® 5 Foundation Exam Prep: Problem Management Explained

  Problem Management is the ITIL® practice responsible for identifying the underlying causes of incidents and reducing the likelihood of those incidents happening again. While Incident Management focuses on restoring service quickly, Problem Management focuses on preventing future disruptions.

• ITIL® 5 Foundation Exam Prep: Change Enablement Explained

  Change Enablement is the ITIL® 5 management practice responsible for ensuring that changes are implemented successfully while balancing risk, speed, and business value. Its goal is not to prevent change. Its goal is to enable beneficial change while minimizing unnecessary disruption.

• The Four Dimensions Model Explained (ITIL® 5)

  The ITIL® Four Dimensions Model helps organizations take a balanced approach to managing services. Rather than focusing only on technology, ITIL teaches that successful services depend on four interconnected dimensions: Organizations and People, Information and Technology, Partners and Suppliers, and Value Streams and Processes. Ignoring any one of these dimensions can reduce the effectiveness of a service.

• How to Study for the ITIL® 5 Foundation Exam (The Method That Actually Works)

  The single biggest predictor of passing the ITIL® 5 Foundation exam isn't how much you read — it's how many mock exams you take, with a full review of every wrong answer in between. Skim the material once for orientation, then shift almost immediately into a cycle of mock exam, review, mock exam, repeating until your score plateaus above 90%, with one final mock exam within 24 hours of the real thing. Most candidates who pass comfortably take 8 to 15 full mock exams before sitting the real exam.

• The Seven Guiding Principles Explained (ITIL® 5)

  The Seven Guiding Principles are universal recommendations that help organizations make better decisions regardless of the situation. Rather than following rigid rules, they provide practical guidance that can be applied to nearly every service management activity.

• Focus on Value: The ITIL® 5 Guiding Principle Explained

  Focus on Value reminds organizations that every activity should contribute toward creating value for customers and stakeholders. Before starting work, making changes, or improving services, ITIL encourages asking one simple question: "How does this create value?" If an activity doesn't contribute to value, it should be questioned.

• Continual Improvement Explained (ITIL® 5)

  Continual Improvement is the ongoing effort to make products, services, and ways of working better over time. Instead of waiting for major problems before making changes, ITIL encourages organizations to identify small improvements regularly and continuously increase the value they deliver.

• Service Request Management Explained (ITIL® 5)

  Service Request Management is the ITIL® practice responsible for handling predefined, user-initiated requests in a consistent and efficient way. Unlike incidents, service requests are not caused by service failures—they are routine requests for information, access, or standard services.

• What Is a Service Desk? (ITIL® 5 Explained)

  A Service Desk is the single point of contact between users and an organization's IT service provider. It helps users report incidents, request services, ask questions, and receive support while coordinating communication throughout the service lifecycle.

• Monitoring and Event Management Explained (ITIL® 5)

  Monitoring and Event Management is the ITIL® practice responsible for observing IT services, detecting events, and determining whether action is needed. By identifying unusual activity early, organizations can prevent incidents, improve service reliability, and respond more quickly when problems occur.

• Service Configuration Management Explained (ITIL® 5)

  Service Configuration Management is the ITIL® practice responsible for ensuring that accurate and reliable information about services and their supporting components is available when it's needed. It helps organizations understand what they have, how everything is connected, and how changes may affect other services.

• What Is Service Value? (ITIL® 5 Explained)

  Service Value is the benefit that customers and organizations receive from using a service. In ITIL®, value isn't created simply by delivering technology—it is created when services help customers achieve desired outcomes while balancing costs and risks.

• Release Management Explained (ITIL® 5)

  Release Management is the ITIL® practice responsible for making new and changed services and features available for use, at the right time, in a controlled way. It focuses on planning when and how approved changes actually reach users — separate from the decision to approve the change in the first place.

• Products vs Services in ITIL® 5: What's the Difference?

  A product is a configuration of an organization's resources designed to offer value to a consumer. A service is a means of enabling value co-creation by facilitating outcomes customers want to achieve, without the customer having to manage specific costs and risks. In short: a product is a thing you configure; a service is delivered through one or more products, plus everything around them.

• The Service Relationship Model Explained (ITIL® 5)

  The Service Relationship Model describes how a service provider and a service consumer establish a relationship through joint activities: service provision, service consumption, and service relationship management. Value is co-created through this ongoing relationship, not delivered as a one-time handoff.

• What Is Value Co-Creation? (ITIL® 5 Explained)

  Value co-creation is the ITIL® principle that value is never delivered by a provider alone — it's created jointly by the provider and the consumer working together. The provider enables the service, and the consumer contributes resources, engagement, and effort. Together, they produce the outcome.

• Service Level Management Explained (ITIL® 5)

  Service Level Management is the ITIL® practice responsible for setting clear, measurable targets for service quality, and making sure the organization actually meets them. It's built on ongoing monitoring and review — not just a signed agreement that sits in a drawer.

• Availability Management Explained (ITIL® 5)

  Availability Management is the ITIL® practice responsible for making sure services deliver the agreed levels of availability — proactively planning, measuring, and improving uptime, rather than just reacting when something breaks.

• Capacity and Performance Management Explained (ITIL® 5)

  Capacity and Performance Management is the ITIL® practice that ensures services meet current and future demand for capacity and performance in a cost-effective way — making sure there's enough resource to perform well, without paying for far more than is needed.

• IT Asset Management Explained (ITIL® 5)

  IT Asset Management is the ITIL® practice responsible for planning and managing the full lifecycle of IT assets — from purchase through retirement — tracking cost, value, contracts, licenses, and ownership, in order to maximize value and control risk and cost.

• Knowledge Management Explained (ITIL® 5)

  Knowledge Management is the ITIL® practice responsible for maintaining and improving the effective use of information and knowledge across an organization — making sure the right people have access to the right knowledge, in the right format, at the right time.

• Information Security Management Explained (ITIL® 5)

  Information Security Management is the ITIL® practice responsible for protecting the confidentiality, integrity, and availability of an organization's information — through policies, controls, and risk management — rather than reacting to individual disruptive events after they happen.

• Supplier Management Explained (ITIL® 5)

  Supplier Management is the ITIL® practice responsible for ensuring that an organization's suppliers and their performance are managed appropriately, to support the seamless provision of quality products and services.

• Progress Iteratively with Feedback Explained (ITIL® 5)

  Progress Iteratively with Feedback means breaking work into smaller, manageable pieces, gathering feedback after each piece, and using that feedback to guide what comes next — rather than attempting one large, all-at-once initiative.

• Collaborate and Promote Visibility Explained (ITIL® 5)

  Collaborate and Promote Visibility means involving the right stakeholders in decisions and work, and making that work visible across the organization — so people can make better decisions with accurate, shared information instead of assumptions.

• Think and Work Holistically Explained (ITIL® 5)

  Think and Work Holistically means recognizing that no part of an organization or service operates in isolation. Changes in one area — people, process, technology, or a supplier — can ripple into others, so decisions should account for the whole system, not just the piece directly being changed.

• Keep It Simple and Practical Explained (ITIL® 5)

  Keep It Simple and Practical means using the minimum number of steps needed to accomplish an objective, and removing anything that doesn't add real value. It pushes organizations to judge processes by outcomes, not by how thorough or complex they appear.

• Optimize and Automate Explained (ITIL® 5)

  Optimize and Automate means maximizing the value of resources, technology, and people before applying automation — because automating a broken or inefficient process just makes the broken process run faster.

• Known Error vs Problem in ITIL® 5: What's the Difference?

  A Problem is the underlying cause of one or more incidents, and its cause may still be unknown. A Known Error is a specific type of Problem — one whose root cause has already been identified and documented, usually along with a workaround, even if a permanent fix hasn't been implemented yet.

• Priority vs Impact vs Urgency in ITIL® 5: What's the Difference?

  Impact measures how much damage or disruption an issue causes. Urgency measures how quickly it needs to be resolved. Priority is calculated from the two together — it determines the order in which issues get worked on, based on their combined impact and urgency.

• Major Incident Management Explained (ITIL® 5)

  Major Incident Management is a separate, accelerated process within Incident Management, used specifically for incidents with the highest impact and urgency — usually involving a dedicated response team, more frequent communication, and a faster escalation path than standard incidents.

• ITIL vs DevOps: What's the Difference? (ITIL® 5 Explained)

  ITIL is a framework for managing IT services end-to-end, covering everything from strategy to support. DevOps is a culture and set of practices focused on breaking down silos between development and operations teams to deliver software faster and more reliably. They address different scopes and can be — and often are — used together.

• ITIL® 4 vs ITIL® 5: What Actually Changed?

  ITIL® 5 is an evolution of ITIL® 4, not a replacement or reset. According to PeopleCert, roughly 40% of ITIL® 5 content is retained from ITIL® 4, 36% is completely new, and 24% is changed or enhanced. The biggest shifts are a scope expansion from "service management" to "digital product and service management," the replacement of the Service Value Chain with an eight-activity Product and Service Lifecycle Model, and built-in AI governance guidance. The seven guiding principles and all 34 management practice names carry over unchanged.

• What's New in ITIL® 5? ITIL® 5 Changes Explained

  ITIL® 5's biggest concrete additions are: a renamed ITIL® Value System (formerly the Service Value System), a new Product and Service Lifecycle Model with eight activities replacing the six-activity Service Value Chain, explicit AI governance guidance including an AI Capability Model, a simplified two-category practice structure, and new terminology reflecting "digital product and service management" instead of just "service management." The seven guiding principles and 34 management practice names are unchanged.

• ITIL® 5 vs ITIL® 4 Foundation: What's the Difference?

  Per PeopleCert's official exam details, both the ITIL® 5 Foundation exam and the ITIL® 4 Foundation exam use the same core format: 40 multiple-choice questions, 60 minutes (75 minutes if the exam isn't taken in your working language), closed book, with a 65% pass mark (26 out of 40 correct). The exams aren't harder or easier than each other in structure — the real difference is syllabus content, since ITIL® 5 Foundation covers the new Product and Service Lifecycle Model, updated terminology, and AI-related content that didn't exist in the ITIL® 4 Foundation syllabus.

• Should You Take ITIL® 4 or ITIL® 5?

  For most first-time candidates in 2026, ITIL® 5 Foundation is the more forward-looking choice, since it's the current version PeopleCert is actively promoting and it covers the newest content, including AI governance and the updated lifecycle model. That said, ITIL® 4 Foundation remains fully available with no announced retirement date, and PeopleCert has committed to at least a 12-month coexistence period — so if your employer specifically requires ITIL® 4, or you need to align with a team or project still running on ITIL® 4 language, that's a legitimate reason to take it instead.

• ITIL® 4 Bridge vs ITIL® 5 Foundation: Which Should You Take?

  If you already hold an ITIL® 4 certification, per PeopleCert's official exam details you're eligible for the ITIL® Foundation Bridge exam: 20 questions, 30 minutes, closed book, 65% pass mark, covering only the updates introduced in ITIL® 5. It costs roughly a third of the full exam bundle. The eligibility requirement is any ITIL® 4 certification, excluding ITIL® 4 Specialist: Acquiring and Managing Cloud Services and ITIL® 4 Specialist: Sustainability in Digital and IT. If you don't hold a qualifying certification, or want the full syllabus depth, retaking the complete ITIL® 5 Foundation exam is the other route.

• The ITIL® Product and Service Lifecycle Explained (ITIL® 5)

  The ITIL® Product and Service Lifecycle is the model ITIL® 5 uses to describe how digital products and services are planned, built, delivered, and supported across eight connected activities: Discover, Design, Acquire, Build, Transition, Operate, Deliver, and Support. It replaces the Service Value Chain from ITIL® 4 and treats product management and service management as one unified, non-linear lifecycle rather than two separate disciplines.

• Discover (Lifecycle Activity) Explained (ITIL® 5)

  Discover is the lifecycle activity focused on identifying business needs, opportunities, and demand — understanding what customers, users, or the market actually require before any design work begins. It formalizes the front end of the lifecycle, making sure work starts from a real, understood need rather than an assumption.

• Design (Lifecycle Activity) Explained (ITIL® 5)

  Design is the lifecycle activity focused on turning a confirmed need into a solution — creating specifications, architectures, and prototypes that describe what will be built, before any actual building happens. It comes after Discover confirms the need is real, and before Acquire and Build turn the design into something real.

• Acquire (Lifecycle Activity) Explained (ITIL® 5)

  Acquire is the lifecycle activity focused on obtaining whatever is needed to bring a design to life — people, technology, and suppliers — whether that means building something in-house, buying it, or hiring outside expertise. It sits between Design, which specifies what's needed, and Build, which assembles it.

• Build (Lifecycle Activity) Explained (ITIL® 5)

  Build is the lifecycle activity focused on coding, configuring, assembling, and testing the components acquired for a solution — turning a design and its sourced resources into a working product or service component. It comes after Acquire has obtained what's needed, and before Transition moves the finished work into live use.

• Transition (Lifecycle Activity) Explained (ITIL® 5)

  Transition is the lifecycle activity focused on moving a built and tested solution from a development environment into live use. It's one of the two "bridge" activities — alongside Operate — that connect the earlier, more Product-focused activities to the later, more Service-focused ones.

• Operate (Lifecycle Activity) Explained (ITIL® 5)

  Operate is the lifecycle activity focused on keeping a live service running day to day — managing infrastructure, monitoring performance, and handling the routine work required to keep things functioning as expected. It's the second of the two "bridge" activities, alongside Transition, connecting Product-leaning work to Service-leaning work.

• Deliver (Lifecycle Activity) Explained (ITIL® 5)

  Deliver is the lifecycle activity focused on making sure value actually reaches the customer or user — not just that a service exists and runs, but that people can access it, use it, and get real benefit from it. It leans toward Service thinking, alongside Support, in the later half of the lifecycle.

• Support (Lifecycle Activity) Explained (ITIL® 5)

  Support is the lifecycle activity focused on addressing issues and requests that arise once a product or service is in active use. It's where customers and users get help when something goes wrong or when they need something new — and it's frequently the source of fresh signals that feed back into Discover.

• What Is a Service Offering? (ITIL® 5)

  A service offering is a formal description of one or more services designed to address the needs of a target consumer group. It's made up of some combination of three elements: goods (transferred to the consumer), access to resources (provided under agreed terms, but not owned by the consumer), and service actions (activities the provider performs, like support or maintenance).

• Service Actions Explained (ITIL® 5)

  Service actions are the activities a service provider performs on behalf of the consumer as part of a service offering — things like support, maintenance, and incident resolution. Unlike goods, service actions are typically intangible: there's no physical item changing hands, just work being done.

• Transfer of Goods Explained (ITIL® 5)

  Transfer of goods refers to the component of a service offering where ownership of a physical or tangible item passes from the provider to the consumer, who then takes responsibility for its future use. It's distinguished from access to resources by that transfer of ownership — goods become the consumer's property; accessed resources do not.

• Access to Resources Explained (ITIL® 5)

  Access to resources refers to the component of a service offering where a provider grants a consumer the right to use specific resources — like software, infrastructure, or facilities — under agreed terms, while the provider retains ownership and control. Unlike goods, access to resources does not transfer ownership to the consumer.

• Service Journey Explained (ITIL® 5)

  A service journey is the end-to-end path a customer or user takes through their interactions with a service provider — from first recognizing a need, through every touchpoint along the way, to actually realizing the value the service provides. ITIL® 5 gives this concept dedicated attention through its new focus on experience, building on ideas already present in earlier ITIL® versions.

• Basic vs Cooperative vs Collaborative Service Relationships (ITIL® 5)

  A basic service relationship is a reactive "order taker" arrangement. A cooperative service relationship blends service delivery with elements of advice, where both parties work toward their own goals somewhat independently. A collaborative (partnership) service relationship involves the provider and consumer working closely together to actively co-create value.

• Service Provider vs Service Consumer in ITIL® 5: What's the Difference?

  A service provider is the party that delivers a service, absorbing the costs and risks involved in running it. A service consumer is the party that receives and uses that service to achieve outcomes. The relationship between the two — who delivers, who consumes — is the basic building block that every other service relationship concept in ITIL® builds on.

• Digital Product Vendor Explained (ITIL® 5)

  A digital product vendor is a party that supplies a digital product without necessarily running an ongoing service or co-creating value through a continuing relationship. It's distinct from a service provider, which runs a service and absorbs the ongoing costs and risks of delivering it. The same organization can act as a vendor in one relationship and a provider in another.

• Value Stream Mapping Explained (ITIL® 5)

  Value stream mapping is a Lean management technique used to visualize the steps needed to convert demand into value, in order to identify opportunities for improvement. A value stream map shows the flow of work, information, and resources from an initial trigger through to the value actually being delivered.

• Core Value Stream vs Enabling Value Stream (ITIL® 5)

  A core value stream directly creates and delivers value to external customers — like fulfilling a customer order. An enabling value stream supports the core value streams without directly touching the customer — like onboarding new staff or maintaining infrastructure. Neither outranks the other; an organization needs both, and a failing enabling stream can eventually damage the core streams that depend on it.

• AI in ITIL® 5 Explained: How AI Fits Into the Framework

  ITIL® 5 treats AI as a capability that assists and automates work across the entire product and service lifecycle — from discovering demand through to supporting live services — and across the value chain activities that make up an organization's operating model. AI's role is broad, not limited to one technical stage like build or operate, and its use still has to follow the "optimize and automate" guiding principle: automating a bad process with AI just produces bad results faster.

• AI Governance Explained (ITIL® 5)

  AI governance is the system of directing and controlling an organization's use of artificial intelligence to ensure it is responsible, ethical, transparent, and aligned with organizational objectives and legal requirements. It addresses accountability, transparency, risk, and compliance in how AI is used — it is not about how technically capable or accurate the AI itself is.

• The ITIL® AI Capability Model Explained (ITIL® 5)

  The ITIL® AI Capability Model is a model for understanding and assessing an organization's readiness to adopt, use, and govern AI effectively. It frames that readiness across the four dimensions of service management — people and skills, information and technology, partners and suppliers, and value streams and processes — helping an organization see where it's ready to use AI more heavily and where it still needs to build capability first.

• Complexity Thinking Explained (ITIL® 5)

  Complexity thinking is an approach that treats organizations and their work as complex adaptive systems, where outcomes emerge from many interacting parts and can't be fully predicted or controlled through linear, top-down management. It calls for observing how the system actually behaves, running small experiments, and adapting — rather than assuming a single detailed master plan will play out exactly as designed.

• Product Specification vs Product Prototype (ITIL® 5)

  A product specification is a documented description of what a product or service should do — its functionality, user experience, and operating model requirements. A product prototype is a working model or tangible representation of the product used to demonstrate and validate the design before full development. Both are outputs of the Design lifecycle activity, but a specification documents requirements in writing, while a prototype demonstrates them in a testable form.

• Continuous Integration vs Continuous Delivery vs Continuous Deployment (ITIL® 5)

  Continuous Integration (CI) is the practice of developers frequently merging code into a shared repository, where automated builds and tests catch problems early. Continuous Delivery extends CI by automating the entire path to a release-ready build, but still requires a human decision to actually deploy to production. Continuous Deployment goes one step further and removes that human approval step entirely — any change that passes all automated tests is deployed to production automatically. These are DevOps and software delivery concepts, not official ITIL® terms, though they relate closely to ITIL®'s Release Management practice and the "optimize and automate" guiding principle.

• Site Reliability Engineering (SRE) Explained (ITIL® 5)

  Site Reliability Engineering (SRE) is a discipline, born at Google, that applies software engineering approaches to IT operations problems, with the goal of improving the availability, performance, and reliability of production systems. SRE is not an ITIL® term or practice, but it overlaps conceptually with ITIL®'s Availability Management and reliability concepts, and it shares ITIL®'s emphasis on automation, though the two frameworks approach these goals from different traditions.

• Observability Explained: How It Relates to ITIL® 5

  Observability is the ability to understand a system's internal state by examining its external outputs — typically metrics, logs, and traces — so teams can ask new questions about unexpected problems without shipping new code to investigate them. Monitoring, by contrast, checks whether a system is behaving within expected, predefined bounds using known metrics and alerts. Observability is not an ITIL® term, but it relates closely to ITIL®'s Monitoring and Event Management practice, which is concerned with systematically observing services and recording meaningful changes of state.

• Reliability in ITIL® 5 Explained

  Reliability is the measure of how long a service, component, or configuration item can perform its agreed function without interruption. It's one of three key aspects that determine availability, alongside maintainability (how quickly a failed service can be restored) and serviceability (how effectively third-party suppliers deliver their part of a service). Reliability specifically concerns freedom from interruption, not overall uptime or how fast a fix happens.

• Sustainability in ITIL® 5 Explained

  Sustainability, in ITIL® 5, is the service's broader impact — ensuring it meets environmental, social, and economic requirements, not just technical or functional ones. It's one of four service quality dimensions alongside utility, warranty, and experience, and ITIL® 5 is explicit that none of the four is inherently more important than the others.

• Event vs Incident in ITIL® 5: What's the Difference?

  An event is any change of state that has significance for the management of a service or configuration item — it's simply something detectable happening, tracked by the Monitoring and Event Management practice. An incident is specifically an unplanned interruption to a service, or a reduction in the quality of a service. Every incident typically starts life connected to one or more events, but most events never become incidents at all.

• Release vs Deployment in ITIL® 5: What's the Difference?

  A release is a set of one or more changes to a service that are made available for use together. A deployment is the technical act of moving a component or change into a specific environment. Put simply: release is about making something available to users; deployment is about the technical work of getting it into place. A deployment often happens before a release goes live, and multiple deployments can feed into a single release.

• Service Level vs SLA in ITIL® 5: What's the Difference?

  A service level is a single measurable target for some aspect of a service — like 99.9% uptime, or a four-hour response time. A Service Level Agreement (SLA) is the documented agreement between a provider and a customer that contains one or more of those service level targets, along with the responsibilities of each party. In short: a service level is a specific measurable commitment; an SLA is the broader agreement that packages multiple service levels together.

• Goods vs Services in ITIL® 5: What's the Difference?

  Goods are physical or digital items where ownership transfers to the consumer, who then takes responsibility for their own future use of them. A service is the means of enabling value co-creation, without the consumer having to manage specific costs and risks themselves. The key test is ownership and ongoing responsibility: goods are handed over and owned; a service is provided and managed on the consumer's behalf.

• User Experience in ITIL® 5 Explained

  User experience is the sum of the functional and emotional interactions a user has with a service — covering things like ease of use, interface design, and how valuable the service feels to the person actually using it. In ITIL® 5, user experience is treated as one of four service quality dimensions alongside utility, warranty, and sustainability, and none of the four is considered inherently more important than the others.

• Governance in ITIL® 5 Explained

  Governance is the means by which an organization is directed and controlled. In ITIL®, it's exercised through a continuous cycle of three activities — Evaluate, Direct, and Monitor (EDM) — carried out by a governing body, and it sits alongside guiding principles, practices, and continual improvement as a core element of the ITIL® Service Value System.

• What Is an Operating Model in ITIL® 5?

  An operating model is the conceptual representation of how an organization runs to create and deliver value — how its resources, activities, and value chain fit together. The Service Value Chain is the specific set of interconnected activities that support that operating model in practice. In short: the operating model is the bigger-picture "how we run" concept, and the value chain is the concrete set of activities that carries it out.

• Metric vs Critical Success Factor (CSF) in ITIL® 5: What's the Difference?

  A metric is a measurement or calculation that's monitored or reported for management and improvement — a quantified indicator, like average resolution time. A critical success factor (CSF) is a necessary precondition for the achievement of an intended result — something that must be true or in place for a practice or service to succeed, like "users can reach support easily." Metrics are typically defined to track progress toward CSFs; a CSF without a metric can't be tracked, and metrics without CSFs measure activity blindly.

• What Are ITIL® Practice Guides?

  ITIL® Practice Guides are detailed guidance documents, one for each Management Practice, kept separate from the core ITIL® publication so they can be updated independently. Each guide follows a consistent structure covering the practice's purpose, key terms, the value chain activities it contributes to, how the four dimensions apply, and practical guidance. Their benefits include faster onboarding, consistency across an organization, reuse of proven approaches, and the ability to update individual practices without reissuing the whole framework.

• PESTLE Analysis in ITIL® 5 Explained

  PESTLE stands for Political, Economic, Social, Technological, Legal, and Environmental factors — six categories of external influence, outside an organization's direct control, that affect all four dimensions of service management. An organization scans these factors to anticipate constraints and opportunities. PESTLE factors are external; anything within the organization's own control, like employee skills, belongs to a dimension itself, not PESTLE.

• Value Stream Management Explained (ITIL® 5)

  Value stream mapping visualizes a value stream to identify opportunities for improvement — it's a snapshot and analysis tool. Value stream management is the broader, ongoing discipline of actively managing and improving the flow of value through an organization, on a continuing basis rather than as a one-time exercise. Mapping shows you the road; management is actively driving the car, using that map to keep improving the journey over time.

• General Management Practices vs Product & Service Management Practices (ITIL® 5)

  ITIL® 5 organizes its Management Practices into two categories: Product and Service Management Practices (22 practices), which focus on the delivery and management of digital products and services across their lifecycle, and General Management Practices (12 practices), which provide the broader organizational and governance capabilities that support those delivery activities. This replaces ITIL® 4's three-category structure, folding the old Technical Management Practices category into the other two.

• ITIL® vs PRINCE2: What's the Difference?

  PRINCE2 provides structured project governance for delivering change — clear stages, defined roles, controlled risk and scope. ITIL® provides service management for the ongoing products and services that result from that change. PRINCE2 governs the project; ITIL® governs the ongoing service. A project delivered under PRINCE2 hands its output into the service lifecycle that ITIL® then governs — neither framework replaces the other.