Learning path
IT Service Management (ITIL 4) learning path: everything to study, topic by topic
Assesses readiness for ITIL 4 Foundation and everyday IT service management work: key concepts of value co-creation, the four dimensions, the service value system, the seven guiding principles, the service value chain and the practices examined at Foundation level, with a practice-depth category that is the extension point for ITIL practitioner-level content.
Short answer
To learn IT Service Management (ITIL 4), work through 7 modules and 23 topics in the order they build on each other. It starts with Key Concepts of Service Management, then moves on to The Four Dimensions of Service Management and The ITIL Service Value System. Use the map as a checklist, or measure your level and study only what is missing.
What you will study
Topics are grouped by module. Open one to see its objectives and key concepts.
1 · Key Concepts of Service Management2 topics
Service, Value & Co-creation
The ITIL definition of service, value co-creation, utility and warranty, outputs versus outcomes, costs and risks, and the roles of service provider, service consumer, customer, user and sponsor
Objectives
- Define service and value in ITIL terms and explain why value is co-created
- Distinguish utility from warranty and an output from an outcome
- Identify the customer, user and sponsor roles in a described situation
Key concepts
- service definition
- value co-creation
- utility and warranty
- outputs and outcomes
- costs and risks
- customer, user and sponsor roles
Service Offerings & the Service Relationship Model
Service offerings (goods, access to resources, service actions), service relationships, and the service relationship model of provision, consumption and relationship management between provider and consumer
Objectives
- Describe the elements of a service offering and give examples of each
- Explain provision, consumption and relationship management in the service relationship model
- Identify which activities belong to the provider and which to the consumer
Key concepts
- service offering
- goods, access, service actions
- service relationship
- service provision
- service consumption
- relationship management
2 · The Four Dimensions of Service Management2 topics
Four Dimensions Overview & External Factors
Why every service must be considered through the four dimensions, how they interact, and the PESTLE external factors (political, economic, social, technological, legal, environmental) that constrain them
Objectives
- Name the four dimensions and explain why all must be addressed for every service
- Map a PESTLE factor to the dimension it affects most
- Explain what goes wrong when one dimension is neglected
Key concepts
- four dimensions model
- interdependence of dimensions
- PESTLE factors
- holistic view of a service
- consequences of ignoring a dimension
Dimensions in Detail: People, Information, Partners, Value Streams
Organizations and people (culture, structure, skills), information and technology (information, knowledge, technology), partners and suppliers (strategy, relationship models) and value streams and processes
Objectives
- Describe the elements of each dimension and give an example for each
- Diagnose which dimension is the root of a described service problem
- Differentiate a value stream from a process and relate both to the value chain
Key concepts
- organizational culture and structure
- roles and competencies
- information and knowledge management
- technology enablers
- supplier strategy and sourcing
- value streams versus processes
3 · The ITIL Service Value System2 topics
Service Value System Overview
The SVS and its five components (guiding principles, governance, service value chain, practices, continual improvement), the opportunity/demand input, value output and the role of governance
Objectives
- List the five SVS components and describe the role of each
- Explain how opportunity and demand are converted into value through the SVS
- Explain what governance contributes to the SVS
Key concepts
- SVS components
- opportunity and demand
- value as output
- governance
- organizational direction and control
- SVS versus value chain
Continual Improvement Practice & Model
The continual improvement practice, where improvement happens across the SVS, and the seven-step continual improvement model from vision to keeping the momentum going
Objectives
- Recite the seven steps of the continual improvement model in order
- Apply the model to a described improvement initiative
- Explain how improvement relates to every level of the organization and every value chain activity
Key concepts
- continual improvement practice
- seven-step improvement model
- vision and baseline
- target state
- measuring results
- sustaining momentum
4 · The ITIL Guiding Principles3 topics
Principles: Focus on Value, Start Where You Are, Progress Iteratively
The first three guiding principles, what each recommends, and how to apply them when planning and delivering service improvements
Objectives
- State and explain the first three guiding principles
- Choose the principle that best applies to a described decision
- Show how iterative progress reduces risk compared with a big-bang approach
Key concepts
- focus on value
- start where you are
- progress iteratively with feedback
- reusing existing services
- small steps and feedback loops
Principles: Collaborate & Promote Visibility, Think & Work Holistically
The guiding principles on collaboration and visibility, and on seeing the whole system; how silos, hidden work and local optimization damage outcomes
Objectives
- Explain what collaboration and visibility mean in practice
- Identify holistic-thinking failures in a described scenario
- Recommend actions that improve cross-team visibility
Key concepts
- collaborate and promote visibility
- think and work holistically
- silos and hidden work
- stakeholder buy-in
- end-to-end view
Principles: Keep It Simple & Practical, Optimize & Automate
The last two guiding principles, the order of simplify before automate, and how the seven principles interact and are used together
Objectives
- Explain why optimization comes before automation
- Apply several principles together to resolve a conflict in a scenario
- Reject an over-engineered proposal using the simplicity principle
Key concepts
- keep it simple and practical
- optimize and automate
- eliminating waste
- optimize before automating
- applying principles together
- principle trade-offs
5 · The Service Value Chain2 topics
Service Value Chain Activities
The six value chain activities (plan, improve, engage, design and transition, obtain/build, deliver and support), what each one does, and its typical inputs and outputs
Objectives
- Name the six activities and state the purpose of each
- Match inputs and outputs (demand, opportunity, requirements, products and services) to the right activity
- Describe how activities combine into a value stream
Key concepts
- plan
- improve
- engage
- design and transition
- obtain/build
- deliver and support
- inputs and outputs of activities
Value Streams Across the Value Chain
Building value streams from value chain activities for typical scenarios such as incident resolution, user requests and changes; flexibility of the chain and links to practices and dimensions
Objectives
- Map a described service event to a sequence of value chain activities
- Show which practices contribute to each activity in a value stream
- Spot waste and missing activities in a proposed value stream
Key concepts
- value stream design
- activity sequence
- incident value stream
- request value stream
- practices supporting activities
- flexibility of the value chain
6 · ITIL Practices11 topics
Practices Overview & Practice Categories
What a practice is, the three practice categories (general management, service management, technical management), the 34 ITIL 4 practices, which are examined at Foundation and how the four dimensions apply to a practice
Objectives
- Define a practice and its resources and place practices into the three categories
- Identify which category a named practice belongs to
- Explain that practices are composed of the four dimensions and support value chain activities
Key concepts
- practice definition
- general management practices
- service management practices
- technical management practices
- 34 practices
- practices and the four dimensions
Change Enablement
Purpose of change enablement, the three change types (standard, normal, emergency), change authority, risk assessment and the balance between throughput and control
Objectives
- Classify a described change as standard, normal or emergency
- Explain who the change authority is and how authority is decentralized in high-velocity organizations
- Balance speed and risk when approving changes
Key concepts
- change enablement purpose
- standard change
- normal change
- emergency change
- change authority
- risk assessment
- pre-authorization
Incident Management
Purpose of incident management, definition of incident, prioritization by impact and urgency, escalation, major incidents and swarming
Objectives
- Define incident and state the purpose of the practice
- Prioritize a set of incidents using impact and urgency
- Describe how a major incident differs from a normal incident in handling
Key concepts
- incident definition
- restore normal service
- impact and urgency
- incident prioritization
- major incident handling
- escalation
- swarming
Problem Management
Purpose of problem management, problem versus incident, known errors and workarounds, and the problem identification, problem control and error control phases
Objectives
- Distinguish problem, known error and incident
- Explain when to document a workaround and where the known error record is used
- Plan a response to recurring incidents using the problem management phases
Key concepts
- problem definition
- known error
- workaround
- problem identification
- problem control
- error control
- root cause analysis
Service Request Management & Service Desk
Service request management (standardized, pre-approved requests and fulfilment) and the service desk as the single point of contact, including empathy, omnichannel and the practice's link to incidents
Objectives
- Differentiate a service request from an incident and a change
- Describe the purpose and key skills of the service desk
- Design a simple fulfilment path for a standard request
Key concepts
- service request definition
- request fulfilment
- pre-approved requests
- single point of contact
- empathy and user experience
- omnichannel support
- request versus incident
Service Level Management
Purpose of service level management, service level agreements, business-based and customer-based metrics, service reviews and the watermelon effect
Objectives
- State the purpose of service level management and what an SLA contains
- Replace technical metrics with outcome-based service level metrics
- Recognize and resolve the watermelon effect
Key concepts
- service level agreement
- customer-based metrics
- business-based targets
- service review
- watermelon SLA
- negotiating targets
- reporting
IT Asset Management & Service Configuration Management
Purpose and scope of IT asset management and service configuration management, configuration items, the configuration management system, and how accurate data supports other practices
Objectives
- Distinguish IT asset management from service configuration management
- Explain why accurate configuration data matters to changes and incidents
- Define a configuration item and give examples
Key concepts
- IT asset lifecycle
- configuration item
- configuration management system
- CMDB data accuracy
- asset versus configuration data
- relationships between CIs
Monitoring & Event Management
Purpose of monitoring and event management, event types (informational, warning, exception), thresholds, and how events trigger incidents, changes or no action
Objectives
- Classify events by type and decide the appropriate response
- Explain how monitoring data and events feed other practices
- Reduce alert noise without hiding real exceptions
Key concepts
- event definition
- informational, warning, exception
- thresholds
- monitoring versus event management
- automated responses
- event-to-incident handoff
Release Management & Deployment Management
Purpose of release management (making services and features available for use) versus deployment management (moving components to live environments) and deployment approaches (phased, continuous delivery, big bang, pull)
Objectives
- Separate release from deployment in a described situation
- Choose a deployment approach for a given risk and speed profile
- Link release and deployment to change enablement
Key concepts
- release versus deployment
- release planning
- phased deployment
- big bang deployment
- continuous delivery
- pull deployment
Relationship Management & Supplier Management
Purpose of relationship management (stakeholder links and trust) and supplier management (managing suppliers and their performance), supplier strategy and the role of contracts and integration
Objectives
- State the purpose of relationship and supplier management
- Explain how supplier management protects service quality
- Handle a conflict between a supplier commitment and a customer need
Key concepts
- stakeholder relationships
- stakeholder satisfaction
- supplier strategy
- supplier performance
- contracts and agreements
- multi-supplier integration
Information Security Management
Purpose of information security management, protecting confidentiality, integrity and availability, authentication and non-repudiation, and how security is integrated across the value chain
Objectives
- State the purpose of information security management and the CIA triad
- Spot where a security control belongs in a value stream
- Balance security needs with usability and speed
Key concepts
- confidentiality integrity availability
- authentication
- non-repudiation
- security policy
- security by design
- security across the value chain
7 · Practice Depth & Practitioner Bridge1 topic
Practice Integration, Metrics & Practitioner Bridge
How practices work together across value streams, critical success factors and KPIs, maturity and scaling, and the extension point for ITIL practitioner-level topics (ITIL 4 Specialist and Strategist modules)
Objectives
- Design a coordinated set of practices for a described value stream
- Define CSFs and KPIs that measure outcomes instead of activity
- Prioritize improvement investments across practices
Key concepts
- practice interrelationships
- critical success factors
- KPIs and metrics
- value stream optimization
- maturity and scaling
- organizational change and adoption
Levels: Junior, Mid, and Senior
Explain it in your own words
Graded by AI · no account · 1 questionNo options to guess from: you write, the AI grades against the topic's rubric and tells you what level your answer reads at.
Already studying IT Service Management (ITIL 4)?
The assessment measures topic by topic, and your plan skips what you already know.
Open to read. An account is only needed to be measured.
Frequently asked questions
Where should I start studying IT Service Management (ITIL 4)?
Start with Key Concepts of Service Management: Service, Value & Co-creation and Service Offerings & the Service Relationship Model. The map orders topics by what they depend on, so each one prepares the next.
How long does a full IT Service Management (ITIL 4) assessment take?
A full assessment of this path takes about 45 minutes. Study time depends on where you start; a diagnostic shows which topics you can skip.
Do I need an account to use this page?
No. The map, objectives and key concepts are open. You only need an account to be measured, get your gap by topic and receive a plan.