ITIL 4 Foundation Exam Power Prep

Service

A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.

Outcome

A result for a stakeholder enabled by one or more outputs. Outcomes are what customers actually want to achieve.

Output

A tangible or intangible deliverable produced by an activity (for example, a report, a completed transaction, or a piece of software).

Utility

The functionality offered by a product or service to meet a particular need; often described as "what the service does" or fitness for purpose.

Warranty

Assurance that a product or service will meet agreed requirements, such as availability, capacity, continuity, and security; often called fitness for use.

Incident

An unplanned interruption to a service, or reduction in the quality of a service, or a failure of a configuration item that has not yet affected a service.

Service

A means of enabling value co‑creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.

Value

The perceived benefits, usefulness, and importance of something.

Utility

The functionality offered by a product or service to meet a particular need. Often called fit for purpose (what the service does).

Warranty

The assurance that a product or service will meet agreed requirements. Often called fit for use (how well it works, e.g., availability, capacity, security, reliability).

Service Provider

An organization that provides services to consumers.

Service Consumer

A generic role that includes customers, users, and sponsors who consume services.

Service Value System (SVS)

A model that describes how all the components and activities of an organization work together as a system to enable value creation through IT-enabled services.

Opportunity and demand

The inputs to the SVS. Opportunity is a possibility to add value; demand is the need or desire for products and services.

Value (in the SVS)

The perceived benefits, usefulness, and importance of something. In ITIL 4, value is co-created through active collaboration between providers and consumers.

Guiding principles

Recommendations that guide an organization in all circumstances, regardless of changes in its goals, strategies, or type of work.

Governance (in ITIL 4)

The means by which an organization is directed and controlled, including policies, decision-making, and performance monitoring.

Service value chain

The central element of the SVS, providing an operating model with six activities (plan, improve, engage, design and transition, obtain/build, deliver and support) for creating, delivering, and improving services.

Organizations and People

Covers structure, roles, skills, culture, leadership, and communication. If neglected: resistance to change, unclear responsibilities, low morale, and good tools or processes fail in practice.

Information and Technology

Covers data, information, knowledge, applications, tools, and infrastructure. If neglected: poor data quality, security issues, tool failures, and inability to support or measure services.

Partners and Suppliers

Covers external providers and contracts. If neglected: unclear responsibilities, unmanaged risks, vendor lock-in, and services failing when suppliers fail.

Value Streams and Processes

Covers end-to-end workflows and processes. If neglected: bottlenecks, delays, rework, inconsistent outcomes, and wasted effort even with good people and tools.

Four Dimensions and the SVS

The four dimensions are applied to all parts of the Service Value System and every practice. Balanced attention across all four enables the Service Value Chain to convert demand and opportunities into value.

Focus on value

Always identify, understand, and focus on value for the customer and other stakeholders in everything the organization does.

Start where you are

Do not start from scratch and build something new without first considering what is already available.

Progress iteratively with feedback

Organize work into smaller, manageable sections that can be executed and completed in a timely manner, and use feedback before, during, and after each iteration.

Collaborate and promote visibility

Work together across boundaries to create value, and ensure that information is visible and understandable to those who need it.

Think and work holistically

Recognize that outcomes are delivered through the effective management and integration of information, technology, organization, people, practices, partners, and processes.

Keep it simple and practical

Always use the minimum number of steps needed to accomplish an objective, and eliminate anything that does not contribute to value.

Service Value Chain (SVC)

The central model in the ITIL 4 Service Value System that describes how an organization turns demand and opportunities into value through six interconnected activities.

Value stream

A series of steps an organization uses to create and deliver products and services to consumers, built by combining Service Value Chain activities and ITIL practices.

Plan (SVC activity)

Ensures a shared understanding of the vision, current status, and improvement direction for all products and services.

Improve (SVC activity)

Ensures continuous improvement of products, services, and all Service Value Chain activities.

Engage (SVC activity)

Provides a good understanding of stakeholder needs, transparent communication, and strong relationships with stakeholders.

Design and transition (SVC activity)

Ensures that products and services are designed and transitioned to meet stakeholder expectations for quality, cost, and time-to-market.

Continual improvement (practice) – simple definition

An ongoing organizational activity that identifies, prioritizes, and implements improvements to ensure services and practices stay aligned with changing business needs.

Continual Improvement Register (CIR)

A central log or list used to record and manage improvement opportunities and initiatives, including their priority, status, and ownership.

Key question: What is the vision?

First step of the continual improvement model; clarifies the high-level direction and desired value so improvements support the organization’s goals.

Difference: Incident vs continual improvement

Incident management restores normal service quickly after an unplanned interruption. Continual improvement focuses on preventing issues and enhancing value over time.

Difference: Project vs continual improvement

Projects are time-limited efforts with a defined output and end date. Continual improvement is an ongoing cycle of smaller changes that may never fully end.

Step: Did we get there?

A check in the continual improvement model where results are measured against the target state to see whether the improvement was successful.

Service level management (purpose)

To set clear business-based targets for service performance and ensure that delivery of services is properly assessed, monitored, and managed against those targets.

Incident management (purpose)

To minimize the negative impact of incidents by restoring normal service operation as quickly as possible.

Problem management (purpose)

To reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents and managing workarounds and known errors.

Incident (ITIL 4)

An unplanned interruption to a service, a reduction in the quality of a service, or a failure of a configuration item that has not yet affected a service.

Problem (ITIL 4)

A cause, or potential cause, of one or more incidents.

Known error

A problem that has been analyzed and has a documented root cause and a workaround (or a planned permanent fix).

Change enablement (purpose)

To maximize the number of successful changes by ensuring risks are properly assessed, authorizing changes, and managing the change schedule.

Standard change

A low-risk, pre-authorized change that is well understood and follows a documented, repeatable procedure.

Normal change

A change that must be assessed and authorized individually because its risk and impact can vary.

Emergency change

A change that must be implemented as soon as possible, often to resolve a major incident or security issue, using streamlined assessment and authorization.

Release management (purpose)

To make new and changed services and features available for use in a controlled way, focusing on what is released and when.

Deployment management (purpose)

To move new or changed components to live or other environments, focusing on how the rollout is executed.

Service desk (purpose)

To capture demand for incident resolution and service requests, and to be the single point of contact for the service provider and its users.

Service request

A user’s request for something that should normally be available, often pre-approved and handled via a standard workflow (request model).

Service request management (purpose)

To support the agreed quality of a service by handling all predefined, user-initiated service requests in an effective and user-friendly manner.

Incident (ITIL 4)

An unplanned interruption to a service, a reduction in the quality of a service, or a failure of a configuration item that has not yet impacted a service.

Monitoring and event management (purpose)

To observe services and service components, record and report events, and determine the appropriate response to those events.

Event (ITIL 4)

Any change of state that has significance for the management of a service or other configuration item.

Information security management (purpose)

To protect the information needed by the organization to conduct its business.

Three core security goals (CIA)

Confidentiality, Integrity, Availability.

Relationship management (purpose)

To establish and nurture the links between the organization and its stakeholders at strategic and tactical levels.

Supplier management (purpose)

To ensure that the organization's suppliers and their performance are managed appropriately to support the seamless provision of quality products and services.

Customer (ITIL 4 role)

The role that defines requirements for a service and takes responsibility for the outcomes of service consumption.

User (ITIL 4 role)

The role that uses services on a day-to-day basis.

Architecture management – simple purpose?

Provides a big-picture understanding of all organizational elements and how they relate, so the organization can achieve current and future objectives. Image: city map of business, data, apps, and tech.

Strategy management – simple purpose?

Defines goals and chooses courses of action and resource allocation to achieve them. Image: compass setting long-term direction.

Portfolio management – simple purpose?

Manages the mix of programs, projects, products, and services to support strategy. Image: investment fund of initiatives.

Risk management – key idea?

Identifies, assesses, and treats risks to objectives (threats and opportunities). Image: umbrella before it rains.

Business analysis – key focus?

Understands business needs and defines requirements, recommending value-creating solutions. Image: translator between business and IT.

Service design – key focus?

Designs products and services that are fit for purpose and fit for use, and can be delivered. Image: service blueprint.

Service Value Chain: Six activities

Plan, Improve, Engage, Design and transition, Obtain/build, Deliver and support.

Value stream

A specific sequence of activities (a path through the Service Value Chain) that creates value for a particular product or service.

Which SVC activity? "Interact with customers, users, or suppliers"

Usually **Engage**.

Which practice? "Restore service as quickly as possible"

**Incident management**.

Which practice? "Identify and remove the causes of recurring incidents"

**Problem management**.

Guiding principle: "Use what you already have"

**Start where you are**.

Incident management vs problem management

**Incident management**: Restore normal service as quickly as possible and minimize impact. **Problem management**: Reduce likelihood and impact of incidents by identifying causes and workarounds.

Change enablement vs release management

**Change enablement**: Ensure changes are assessed, authorized, and scheduled to balance value and risk. **Release management**: Make new and changed services and features available for use.

Service request management vs incident management

**Service request management**: Handle user requests (information, access, standard changes, service delivery). **Incident management**: Handle unplanned interruptions or reduction in service quality.

Guiding principle: Focus on value

Everything the organization does should directly or indirectly create value for customers and stakeholders. Understand who the customers are, what they value, and how they measure success.

Guiding principle: Progress iteratively with feedback

Do not attempt everything at once. Organize work into smaller, manageable pieces, and use feedback at each iteration to guide and adjust further work.

Guiding principle: Think and work holistically

Recognize that services and value streams are complex systems. Consider all dimensions and SVS components, not isolated parts, when making decisions.