ITIL 4... as fast as possible

The ITIL 4 Foundation syllabus compressed into interactive diagrams

Lord have mercy

Disclaimers

  1. Opinions expressed in this post do not reflect the views/positions of no affiliated group.

  2. Unto Caesar what is Caesar's: Claude helped beautify all the diagrams used in this article.



Hook

My hierarchy asked me to take the ITIL v4 Foundation certification. I have had a genuinely hard time seeing how this exam would help me do my job better. It has been due for days, and I kept pushing it back; now I am against the wall: tomorrow, July 13th, is the final deadline.

This certification is apparently requested by companies all over the world. Yet nobody around me has ever mentioned ITIL. Maybe I don't have the right friends. Shoutout to "GeekStation... πŸΈπŸΉπŸΊπŸ§‹πŸ§ƒπŸ₯€" lol

From where I stand, I doubt the exam will bring much to me or to the company I work for to be honest. But skepticism is only worth something once it has been put to the test. So I will sit the exam, honestly try to pass it, and find out whether I am wrong.

This will not be an article. This is a constellation of diagrams. The long-form write-up lives in the first article written some weeks ago. This one is the picture book. I hope it helps you memorize as much as it helps me.

Table of contents

  1. The actors
  2. Value creation
  3. Service management
  4. The 7 guiding principles
  5. The 4 dimensions
  6. The service value system
  7. The service value chain
  8. Service relationships
  9. Continual improvement
  10. The 34 practices
  11. What kind of ticket is this?
  12. The toy exam



The actors

Who is in the room? Customer, user, sponsor, provider.

Who does what β€” for whom

Click any node to see its ITIL 4 definition

βš™ Service Provider
🧱
Resource
Raw input to build with
↓ assembles into
πŸ“¦
Product
Configured for value delivery
↓ packaged as
⚑
Service
Enables consumer outcomes
↓ described in
πŸ“‹
Service Offering
Formal promise to the consumer
β†’delivers
Utility Γ— Warranty
= Value
co-created
by both sides
requires←
πŸ‘₯ Service Consumer
πŸ’°
Sponsor
Authorizes the budget
↓ funds
🎯
Customer
Defines requirements & owns outcomes
↓ specifies for
πŸ–₯
User
Uses the service day-to-day
↓ feeds back to
🌐
Stakeholder
Any party with an interest
← Click any node to see its definition

Value creation

A service is a trade: it supports outcomes and removes costs and risks, while introducing new ones. Value is what's left when the scale settles.

ITIL 4 β€” Value Creation

A service is a trade: value is what's left when the scale settles β€” click any element

+ What the service brings
Supported outcomes
Results the consumer can now achieve
Costs removed
Expenses the consumer no longer carries
Risks removed
Threats the provider now absorbs
βš–οΈ
✨
Value
the net result,
as perceived
βˆ’ What the service costs
Affected outcomes
Results negatively impacted
Costs introduced
New expenses the consumer takes on
Risks introduced
New threats the consumer accepts
← Click an element above to see how it weighs on the scale
Exam classic β€” output vs outcome: an output is what the service produces (a report); an outcome is what the consumer achieves thanks to it (a decision made). Services are judged on outcomes.

Service management

The whole discipline in one sentence: "capabilities enabling value, for customers, in the form of services."

ITIL 4 β€” What is Service Management?

The definition, drawn β€” click any component to learn more

🧠
Capabilities
Knowledge Β· people Β· technology
✨
Value
Perceived usefulness
Utility Γ— Warranty
πŸ§‘β€πŸ’Ό
Customers
Who co-create value with the provider
πŸ›Ž
Services
A means of enabling value co-creation
πŸ“¦
Products
Designed to offer value to a consumer
🧱
Resources
People Β· infrastructure Β· capital Β· information
Service management: a set of specialized organizational capabilities* for enabling value for customers in the form of services β€” each service built from products, and each product a configuration of resources*.
← Click a component above to see its definition and role
* The resources vs capabilities pair is formal ITIL v3 vocabulary (both were "service assets"). ITIL 4 kept capabilities in the definition of service management but folded the concept into practices β€” "sets of organizational resources designed for performing work". The distinction still holds: a resource is what you have and can buy; a capability is what you can do with it, and must be built.

The 7 guiding principles

7 recommendations that apply to every decision, in every circumstance.

ITIL 4 β€” The 7 Guiding Principles

Universal recommendations that apply to every decision, at every level β€” click one to learn more

1🎯
Focus on value
Every action should trace back to a benefit for a stakeholder
2πŸ“
Start where you are
Assess what already works before designing something new
3πŸ”
Progress iteratively with feedback
Small increments, real feedback, adjust
4🀝
Collaborate and promote visibility
Make work visible; involve the right people early
5🌐
Think and work holistically
Services are systems β€” consider the whole, not just your part
6πŸͺΆ
Keep it simple and practical
If a step adds no value, eliminate it
7βš™οΈ
Optimize and automate
Fix the process first, then automate what remains
← Click a principle above to see what it means in practice
Unlike practices, the guiding principles are not optional and not situational: they apply to every component of the SVS, in every circumstance, and cannot be overridden by management or policy.

The 4 dimensions

Neglect any one of them and the project fails.

ITIL 4 β€” The Four Dimensions Model

Click a dimension, the value hexagon, or a PESTLE factor to learn more

PoliticalEconomicEnvironmentalSocialLegalTechnological
πŸ‘₯
Organizations
& People
Structure Β· culture Β· roles Β· skills
πŸ–₯
Information
& Technology
Data Β· knowledge Β· tools Β· infrastructure
🀝
Partners
& Suppliers
Vendors Β· contracts Β· integrations
πŸ”€
Value Streams
& Processes
Workflows Β· activities Β· procedures
Products & Services
Value
Utility Γ— Warranty
← Click a dimension above to see what it covers β€” and how ignoring it makes projects fail
Organizations & People
Information & Technology
Partners & Suppliers
Value Streams & Processes
PESTLE external factors

The service value system

How an organization turns opportunity and demand into value.

ITIL 4 β€” Service Value System (SVS)

Opportunity and demand go in, value comes out β€” click any layer to learn more

πŸ’‘
Opportunity
/ Demand
⇄
Guiding Principles
Governance
Service Value Chain
Plan Β· Engage Β· Design & Transition Β· Obtain/Build Β· Deliver & Support Β· Improve
Practices
Continual Improvement
⇄
✨
Value
← Click a layer, or an endpoint, to see its role in the SVS
Guiding Principles
Governance & Practices
Service Value Chain
Continual Improvement

The service value chain

6 activities that every value stream is assembled from.

ITIL 4 β€” Service Value Chain (SVC)

How demand becomes value β€” click any element to learn more

πŸ“₯
Demand
⇄
🀝
Engage
Stakeholders & needs
⇄
πŸ—Ί Planβ€” direction & strategy, spanning every activity
πŸ“
Design &
Transition
πŸ”¨
Obtain /
Build
πŸš€
Deliver &
Support
πŸ“ˆ Improveβ€” continual, spanning every activity
⇄
πŸ“¦
Products &
Services
⇄
✨
Value
⇄ The chain is non-linear: each value stream combines the six activities differently
← Click an element above to see its role in the chain
Plan β€” spans the chain
Engage & core activities
Improve β€” spans the chain
Products & Services

Service relationships

An org is both provider and consumer.

ITIL 4 β€” Service Relationships

Every organization is both provider and consumer β€” click an organization, a relationship, or a component

🏭
Organization A
Provider β†’ B
🏒
Organization B
Consumer ← AProvider β†’ C
πŸ₯
Organization C
Consumer ← BProvider β†’ D
πŸ§‘β€πŸ”¬
Organization D
Consumer ← C
Inside every service relationship
Service Provision
What the provider does
Service Relationship Management
What both do, together
Service Consumption
What the consumer does
← Click an element above to see its role in the relationship model
Provider side β€” provision
Joint β€” relationship management
Consumer side β€” consumption
Not to be confused with relationship management, one of the 14 general management practices: that practice lives inside a single provider, while service relationship management is the joint activity spanning both parties of a service relationship.

Continual improvement

I remember a very old woman who used to say "Moins on en fait, mieux on se porte" lol.

ITIL 4 β€” Continual Improvement

The 7-step model: each question paired with the action that answers it β€” click a step to learn more

1What is the vision?
⇄
Business vision, mission, goals and objectives
↓
2Where are we now?
⇄
Perform a baseline assessment
↓
3Where do we want to be?
⇄
Define measurable targets
↓
4How do we get there?
⇄
Define the improvement plan
↓
5Take action
⇄
Execute the improvement actions
↓
6Did we get there?
⇄
Evaluate metrics and KPIs
↓
↻7. How do we keep the momentum going?β€” loops back to step 1
← Click a step above to see what it involves
Continual improvement appears three times in ITIL 4: as a guiding principle (a mindset), as one of the 34 practices (with the CIR as its operational tool), and as the Improve activity of the service value chain. This model is how the practice actually runs β€” and reaching step 7 doesn't mean you're done, it means you start over.

The 34 practices

The 34 practices. Adopt the ones that solve your problems and leave the rest on the shelf.

ITIL 4 β€” The 34 Management Practices

Three categories, adopt what solves your problems β€” click a category or a practice

14
General
Management
Adapted from general business management
17
Service
Management
The heart of ITSM day-to-day work
3
Technical
Management
Adapted from technology management
The 7 practices the Foundation exam drills into
Continual improvementChange enablementIncident managementProblem managementService request managementService deskService level management
← Click a category or a practice above
Adopt and adapt: nobody implements all 34. Identify your pain points, pick the practices that address them, and leave the rest on the shelf.

What kind of ticket is this?

The question every IT team answers a dozen times a day.

What kind of ticket is this?

Answer each question to classify your request

The toy exam

Here are 60 (not so hidden) questions, to help you prepare the exam.

ITIL 4 β€” The Toy Exam

60 questions, drawn at random from a bank of 200+

For reference, the real Foundation exam: 40 questions, 65% to pass (26/40), 60 minutes, closed book.

More on this topic:

Not much really.