Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
ITIL®4 – A Pocket Guide

ITIL®4 – A Pocket Guide

Make IT service work serve customer outcomes, control risk, and improve through measurable feedback.
by Van Haren Publishing 2019 180 pages
3.57
7 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat every service as a partnership that creates value in use

Value happens in use. ITIL 4 describes a service as a way to help customers achieve outcomes without making them manage every supporting cost and risk themselves. Value is not simply transferred when a provider delivers a product. It is shaped by how providers, consumers, and other stakeholders use resources together. A product might contain technology the consumer never sees; the service makes its useful capabilities available through access, goods, or support.

Name the people involved. The consumer role can include a customer, who defines requirements and owns responsibility for outcomes; a user, who uses the service; and a sponsor, who authorizes its budget. These roles may belong to different people, so their expectations need to be understood rather than assumed.

Analysis

The shift from delivery to use is a useful corrective to organizations that count outputs while overlooking whether anyone benefits from them. It also clarifies why service design requires customer participation: providers cannot fully specify value from their own side of the contract. Yet the language of partnership should not obscure unequal power. A provider may control the technology, terms, and evidence about performance, while users bear the disruption. Genuine co-creation therefore depends on transparency and meaningful ways for consumers to shape requirements and report outcomes.

Connect strategy, practices, and governance in one value-producing system

See the whole operating system. The service value system, or SVS, is ITIL 4's model for how an organization combines its activities and resources to create value. Its inputs are opportunity and demand; its intended outcome is value for stakeholders. Five components work together: the service value chain, practices, guiding principles, governance, and continual improvement. Practices supply resources for work, while governance directs and monitors the organization and improvement helps it adapt.

Avoid isolated fixes. A service problem may involve policy, people, technology, suppliers, and workflows at once. The SVS asks an organization to coordinate these elements rather than treat service management as a collection of disconnected departments. ITIL 4 replaces the older lifecycle emphasis with a more flexible model for adapting work to changing business needs.

Analysis

The SVS resembles a systems model more than a recipe: its value lies in showing dependencies that functional org charts often hide. That is especially useful when a local improvement shifts costs or risks elsewhere, such as speeding a release while increasing support burden. The framework's breadth is also its challenge. A diagram can encourage holistic thinking, but it cannot decide priorities or settle conflicts between stakeholders. Governance must make those tradeoffs explicit, and performance evidence must test whether coordination produces better outcomes.

Check people, technology, suppliers, and workflows together before changing services

Use four connected lenses. ITIL calls these the four dimensions of service management: organizations and people; information and technology; partners and suppliers; and value streams and processes. Together they describe the conditions a service needs to work. A new tool, for example, cannot succeed on its own if staff lack the skills to operate it, supplier agreements are unclear, or the workflow creates unnecessary delays.

Look beyond the organization. The dimensions overlap and should be considered together across the service value system. The guide also uses PESTLE to group external influences: political, economic, social, technological, legal, and environmental factors. Changing privacy rules, economic pressures, or new technology can alter what a service must provide and how it can be delivered.

Analysis

This is a practical socio-technical lens: service performance emerges from interactions among people, tools, institutions, and routines, not from technology alone. Considering suppliers and external conditions also makes the model more realistic than an internal process map. The risk is turning four dimensions into a box-ticking exercise. Their value comes from tracing dependencies in a particular service, such as how a supplier change affects staff workload, data access, and recovery procedures. A short, concrete map of those links can be more useful than a comprehensive inventory.

Use ITIL's seven principles as adaptable tests, not a compliance checklist

Choose with principles. ITIL's guiding principles are recommendations for decisions across different organizational settings. They are meant to be considered together and adapted to the situation, not applied as mandatory steps. The seven principles are:

1. Focus on value.
2. Start from what already exists.
3. Make progress in small steps and use feedback.
4. Collaborate and make work visible.
5. Consider the whole system.
6. Keep solutions simple and practical.
7. Optimize work before automating it.

Use them to challenge plans. Before automating a workflow, for instance, check whether the workflow creates value and whether unnecessary steps can be removed first. Iterative delivery can expose problems sooner, while feedback helps teams adjust their next step. The principles are compatible with Agile and DevOps approaches, which emphasize collaboration and adaptable delivery.

Analysis

The principles work best as questions that expose weak assumptions: whose value is being served, what evidence supports a redesign, and what complexity can be removed? This is more flexible than treating them as a fixed sequence. Their openness, however, can allow almost any choice to be justified after the fact. Teams can reduce that ambiguity by recording which principles informed a decision, which were in tension, and what result would count as success. Principles become useful when they change observable decisions, not when they decorate them.

Build value streams from six activities in whatever sequence the work needs

Treat the chain as adaptable. The service value chain is the SVS operating model, made up of six activities: Plan, Improve, Engage, Design and transition, Obtain/build, and Deliver and support. They cover direction, stakeholder contact, service design, acquiring or creating components, operations, and improvement. The activities are not a mandatory one-way sequence. Organizations combine them into value streams, meaning the steps used to create and deliver a product or service in a particular situation.

Follow the work. A user interaction may lead directly to support, or it may generate a request for a change, which calls for components to be built or acquired before delivery. Feedback from operation can then prompt another improvement. Practices can support multiple activities, so teams can select the capabilities a particular value stream requires.

Analysis

The flexible chain is a strong bridge between stable operating responsibilities and the variable paths real work takes. It resembles workflow design in which a common set of capabilities can be recombined for different customer needs. This avoids forcing every request through a lifecycle-shaped bureaucracy. Flexibility still requires discipline: if teams cannot see how work moves, where it waits, or who owns the next step, adaptability becomes inconsistency. Mapping a few high-volume or high-risk value streams can reveal friction without pretending that every case follows one ideal route.

Judge services by outcomes, utility, assurance, costs, and risks

Separate delivery from benefit. An output is a deliverable; an outcome is the result a stakeholder achieves with it. Outcomes are closer to value, so providers need to understand what customers are trying to accomplish. ITIL uses utility for the functionality that meets a need, or whether a service is fit for purpose. Warranty is the assurance that agreed requirements will be met, or whether it is fit for use. Availability, capacity, security, and continuity can all shape that assurance.

Count what changes hands. A service can remove costs and risks from a consumer, such as the need to maintain its own infrastructure, while imposing other costs and risks, such as fees or dependence on a provider. Value depends on the balance, not on functionality alone. Providers and consumers need to agree on requirements and assess both sides of that balance.

Analysis

Separating utility from warranty prevents a common category error: a service can have the right features and still be too unreliable to use, or be dependable while solving the wrong problem. The output-to-outcome distinction similarly shifts attention from what teams produce to what users can achieve. This is compatible with decision analysis, where alternatives are judged by both expected benefits and exposure to loss. The harder issue is whose costs count. A provider's efficiency gain may become a customer's training burden, so assessments should include effects across the relationship, not just one organization's ledger.

Make improvement everyone's routine, then track whether it actually helps

Give improvement a method. Continual improvement means repeatedly aligning services and practices with changing business needs. ITIL treats it as an organization-wide responsibility, supported by the Improve value chain activity and a dedicated practice. Improvement opportunities can be logged, assessed, prioritized, supported by a business case, implemented, and evaluated. A continual improvement register can track ideas and their progress rather than letting suggestions disappear into informal conversation.

Close the feedback loop. The continual improvement model is iterative and connected to organizational vision and customer value, rather than a rigid sequence that must be followed once. Measurement matters because implementation alone does not prove success. Teams should compare results with the intended effect and use what they learn to adjust further work. Improvement can draw on methods such as Lean, Agile, and DevOps.

Analysis

This turns improvement from a slogan into a feedback mechanism. In control theory, a system cannot reliably correct its behavior without information about the gap between intended and observed results. The same logic applies here: a register creates traceability, while evaluation tests whether a change delivered value. A register can also become a graveyard of ideas if it rewards logging more than resolving. Clear ownership, realistic capacity, and evidence of impact matter more than the volume of entries. Local improvements should also be checked for effects on connected teams and services.

Restore service quickly, then investigate causes that threaten repeat failures

Separate symptom from cause. An incident is an unplanned interruption or decline in service quality. Incident management aims to reduce its negative impact by restoring normal service as quickly as possible. Incidents should be recorded and prioritized by their effect, with serious disruptions receiving coordinated attention. Fast restoration matters to users, even when the underlying cause is not yet known.

Make recurrence less likely. A problem is an actual or potential cause of incidents. Problem management identifies and records problems, analyzes and prioritizes them, then manages known errors and possible resolutions. A known error is an analyzed problem that remains unresolved. A workaround reduces the impact while a full fix is unavailable. Incident records and problem analysis can inform one another, but restoring service and eliminating a cause are distinct jobs.

Analysis

This distinction reflects a basic principle of reliability engineering: service recovery and fault elimination serve different time horizons. Users need the system back; engineers need to understand why it failed and whether the same conditions remain. Combining the two into one queue can make urgent recovery compete with slower analysis. Yet root-cause language should be used carefully. Complex failures often arise from interacting conditions rather than one culprit, and a workaround may be the safest option when a permanent correction carries greater risk. The model supports investigation without assuming every problem has a simple fix.

Route routine requests, incidents, and changes through distinct paths

Match the route to the work. A service request is a user-initiated action already agreed as a normal part of service delivery. It is not a failure; examples include requesting information or access. Standardized procedures and automation can make these requests easier to fulfill. An incident, by contrast, is an unexpected interruption or service-quality reduction and needs restoration work.

Assess changes by risk. Change enablement assesses risks, authorizes work, and manages its schedule to increase successful changes. Standard changes are low-risk and pre-authorized; normal changes follow assessment and approval; emergency changes need rapid handling while retaining as much testing and control as possible. These are technology or service changes, distinct from organizational change management, which addresses how people adopt organizational changes.

Analysis

Distinct routes prevent routine demand from being mistaken for failure and prevent risky modifications from slipping through as ordinary support work. Risk-based authorization also avoids the false choice between approving everything and blocking all change. Standardization is most useful where the work is genuinely repeatable and understood; applying a pre-approved pattern to a novel or high-impact case defeats its purpose. The emergency category deserves particular scrutiny because urgency can become habitual. Reviewing emergency work afterward can reveal whether the cause was truly exceptional or whether planning and capacity need attention.

Measure service quality where customers feel it, not only in dashboards

Make contact count. The service desk is the communication point between provider and users, capturing demand for incident resolution and service requests. Its work is not merely technical routing: staff need to understand business priorities, communicate clearly, and ensure each issue is acknowledged and owned. Portals, chat, phone, and other channels can support access, while self-service can handle suitable routine work.

Make targets meaningful. Service level management sets business-based performance targets and reviews whether services meet them. A service level agreement documents the service and expected performance. A metric can look healthy while users suffer: meeting a high availability target may still fail customers if an outage lands during a critical business period. ITIL calls this mismatch the watermelon effect, green-looking measures concealing poor experience.

Analysis

The emphasis on experience corrects a measurement problem familiar across organizations: what is easy to count can displace what matters. A service desk interaction shapes trust as well as resolution, while an SLA can make expectations explicit. This connects to Goodhart's law, the idea that a measure can become a poor proxy when it becomes the target. Metrics remain necessary, but they need context: business timing, user impact, and qualitative feedback can explain why the same outage has different consequences. A dashboard is evidence about service, not a substitute for the customer's account of it.

Analysis

ITIL 4 is best understood as an operating vocabulary and design framework, not a universal procedure manual. Its central move is to connect the work of service management to value experienced by stakeholders, then provide reusable structures for organizing that work. The service value system sets the organizational context; the four dimensions discourage narrow technical diagnoses; the value chain offers a repertoire of activities; and practices supply capabilities that can be recombined. This architecture reflects a shift from a fixed lifecycle toward adaptive coordination, which suits environments where digital services change continuously and depend on many internal and external contributors.

The framework's strength is also its main implementation risk. Terms such as value, outcome, and continual improvement encourage useful questions, but they do not answer them automatically. Organizations can adopt the vocabulary while preserving siloed incentives, overloaded approval processes, or metrics detached from user experience. The seven principles can challenge those habits, yet their flexibility makes them vulnerable to selective interpretation. Effective use therefore depends on local evidence, clear decision rights, and an honest account of tradeoffs.

The book's practical detail is strongest where it distinguishes operational purposes that are often blurred: incident response restores service, problem management reduces recurrence, change enablement controls risk, and service requests handle agreed routine demand. These distinctions help teams avoid treating every interruption as a root-cause investigation or every request as a failure. They also show why service management is socio-technical: outcomes rely on people, information, tools, suppliers, and process design together.

The pocket guide has an exam-preparation purpose, so it emphasizes definitions, categories, and recallable structures more than implementation stories or comparative evidence. Readers should treat its models as prompts for examining actual services, not proof that a process is effective merely because it bears an ITIL label. The best test is whether the organization can explain who benefits, how work flows, what risks are controlled, and what evidence demonstrates improvement.

Summary in 30 Seconds
Services create value through the results customers achieve, not through products or outputs alone. Reliable delivery depends on people, technology, suppliers, and workflows working together. Teams should tailor their activities to the work, assess costs and risks alongside benefits, and measure improvement against its intended effect. Restore service quickly after an incident, investigate causes separately, and route routine requests and risky changes through appropriate processes. Performance measures must reflect customer experience, not just technical targets.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.57 out of 5
Average of 7 ratings from Goodreads and Amazon.

ITIL®4 – A Pocket Guide receives positive feedback from readers, with an overall rating of 3.60 out of 5 based on 5 reviews. One reader praises the book for its concise yet comprehensive approach, highlighting its effectiveness in preparing for the ITIL-4 Foundation exam. The guide is commended for clearly distinguishing between exam-relevant content and additional information necessary for practical application and deeper understanding. The reviewer recommends the book for those studying for the ITIL-4 Foundation certification.

Your rating:
4.24
72 ratings
Want to read the full book?

Glossary

Service value system (SVS)

Organization-wide value model

A model of how an organization's activities and components work together to create value through products and services. Its inputs are opportunity and demand, and its components are the service value chain, practices, guiding principles, governance, and continual improvement. It encourages coordination across the organization rather than isolated service-management functions.

Four dimensions of service management

Four service design perspectives

The four perspectives ITIL uses to support holistic service management: organizations and people; information and technology; partners and suppliers; and value streams and processes. Each affects service delivery and improvement, and the dimensions can overlap. Considering them together helps expose dependencies that a technology-only or process-only analysis might miss.

ITIL guiding principles

Adaptable decision recommendations

Seven recommendations for guiding organizational decisions in different circumstances: focus on value, start from what exists, progress iteratively with feedback, collaborate and promote visibility, think and work holistically, keep it simple and practical, and optimize and automate. They are not mandates or a fixed sequence, and organizations should consider how they apply together.

ITIL service value chain

Six-activity operating model

The central operating model within the service value system. Its six activities are Plan, Improve, Engage, Design and transition, Obtain/build, and Deliver and support. They can be combined in different sequences to respond to demand and create products and services. Practices support the activities as needed rather than belonging to only one activity.

Value stream

Steps that create and deliver value

A particular series of steps an organization undertakes to create and deliver products or services to consumers. A value stream combines activities from the service value chain in a sequence suited to its situation and goals. It should emphasize activities that contribute value and identify waste or delay that can be reduced.

Utility

Functionality meeting a need

The functionality a product or service offers to meet a particular need. Utility describes what the service does and whether it is fit for purpose. It concerns whether the service supports the consumer's business activities or removes constraints that prevent desired outcomes.

Warranty

Assurance of agreed performance

The assurance that a product or service will meet agreed requirements. Warranty describes how the service performs and whether it is fit for use. Requirements may cover availability, capacity, security, and continuity, and the assurance depends on meeting conditions agreed with the service consumer.

Known error

Analyzed, unresolved problem

A problem that has been analyzed but has not yet been resolved. Identifying a known error means the cause has been investigated sufficiently to begin considering a resolution. Workarounds may reduce its impact while a permanent correction is unavailable, and the information can support incident handling.

Watermelon effect

Healthy metrics, poor experience

A mismatch in which service measures appear satisfactory while customers experience poor service. For example, an availability target may be met overall even though an outage occurs at a particularly critical business moment. The term highlights why performance metrics should reflect outcomes and customer experience, not only numerical compliance.

About the Author

Van Haren Publishing is the editor of "ITIL®4 – A Pocket Guide." As a publishing company specializing in IT and business management content, Van Haren is known for producing concise, practical guides on various industry frameworks and methodologies. Their focus on creating accessible, exam-oriented materials has made them a popular choice among professionals seeking certification in fields like ITIL, PRINCE2, and other IT service management areas. While specific information about individual authors is not provided, Van Haren's editorial approach typically involves collaborating with industry experts to ensure their publications offer accurate, up-to-date information tailored to the needs of IT professionals and students.

Download PDF

To save this ITIL®4 – A Pocket Guide summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.31 MB     Pages: 16

Download EPUB

To read this ITIL®4 – A Pocket Guide summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.35 MB     Pages: 21
Want to read the full book?
Follow
Listen1 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...