ITIL training should now be built around ITIL Foundation (Version 5), not treated as a small refresh of ITIL 4. The current Foundation keeps familiar ideas such as value, continual improvement, the four dimensions, guiding principles, practices, and the value system, but it places them inside a more product-centric, AI-aware model for modern digital products and services.<\/p>\n
PeopleCert also provides a Foundation Bridge for existing ITIL 4 Foundation holders, while ITIL 4 remains available during the phased transition. That means instructors need a curriculum that can serve both new learners and people upgrading existing knowledge without mixing the two syllabi together.<\/p>\n
The broader ITIL certification<\/a> path should be the starting point for deciding which learner group you are teaching.<\/p>\n Do not use one lesson plan for everyone.<\/p>\n New learners<\/strong> need the full Version 5 Foundation structure from the beginning.<\/p>\n Existing ITIL 4 Foundation holders<\/strong> may need only the changed concepts and terminology before using the Foundation Bridge route.<\/p>\n This distinction prevents two common problems: reteaching old material unnecessarily and assuming that experienced ITIL 4 learners already understand every change in Version 5.<\/p>\n Version 5 is more explicit about managing digital products and services across their lifecycle.<\/p>\n Do not teach \u201cservice management\u201d as if it sits separately from product work, technology, customer experience, suppliers, governance, and continual improvement.<\/p>\n Use scenarios where a team must manage both the product and the service around it:<\/p>\n A customer portal with a product roadmap and support obligations.<\/p>\n A data platform with internal consumers and service levels.<\/p>\n An AI-enabled application that requires governance, monitoring, and improvement after launch.<\/p>\n A SaaS platform with suppliers, users, security, and lifecycle decisions.<\/p>\n Learners should be able to explain value in terms of outcomes, costs, risks, experience, and sustainability rather than memorizing a definition.<\/p>\n For every case study, ask:<\/p>\n Who is receiving value?<\/p>\n What outcome matters?<\/p>\n Which cost or risk could reduce that value?<\/p>\n What experience does the user or customer actually have?<\/p>\n How will the organization know whether value improved?<\/p>\n The ITIL value-creation concepts<\/a> are easier to retain when they are tied to decisions rather than flashcards.<\/p>\n The four dimensions are:<\/p>\n Organizations and people.<\/p>\n Information and technology.<\/p>\n Partners and suppliers.<\/p>\n Value streams and processes.<\/p>\n Instead of teaching them as four independent chapters, use one scenario and ask learners to analyze all four dimensions.<\/p>\n For example, an organization introducing an AI support assistant may need new staff responsibilities, data and model controls, an external AI provider, redesigned support workflows, and new measures of customer experience. That single case makes the dimensions operational.<\/p>\n The new ITIL is designed for an environment where AI and automation affect products, services, decisions, and operations.<\/p>\n Do not teach AI as one isolated final slide.<\/p>\n Integrate it into:<\/p>\n Governance.<\/p>\n Risk.<\/p>\n Data handling.<\/p>\n Service operations.<\/p>\n Customer experience.<\/p>\n Continual improvement.<\/p>\n Human oversight.<\/p>\n Supplier management.<\/p>\n The connection to AI governance and risk management<\/a> is especially useful when explaining why automation still requires accountability and control.<\/p>\n Learners often memorize individual components but struggle to explain how they interact.<\/p>\n Use the ITIL Value System to show how guiding principles, governance, value-chain activities, practices, and continual improvement support one another.<\/p>\n A change to a customer-facing service, for example, can involve governance, design, supplier input, deployment, support, feedback, and improvement. The value system should explain that flow rather than become a diagram learners reproduce from memory.<\/p>\n Each guiding principle should answer a practical question.<\/p>\n Focus on value:<\/strong> what outcome are we trying to improve?<\/p>\n Start where you are:<\/strong> what existing capability or evidence can be reused?<\/p>\n Progress iteratively with feedback:<\/strong> what is the smallest meaningful change we can test?<\/p>\n Collaborate and promote visibility:<\/strong> who needs information or involvement?<\/p>\n Think and work holistically:<\/strong> what other part of the system will this change affect?<\/p>\n Keep it simple and practical:<\/strong> which control or step is adding no useful value?<\/p>\n Optimize and automate:<\/strong> what should be improved before it is automated?<\/p>\n Scenario questions become much easier when the principles are learned this way.<\/p>\n Build exercises around recognizable work.<\/p>\n Examples:<\/p>\n An outage where service must be restored before root cause is known.<\/p>\n A recurring incident that requires problem management.<\/p>\n A standard access request that belongs in a service-request workflow.<\/p>\n A risky production change requiring approval and validation.<\/p>\n A service with poor experience despite meeting a technical SLA.<\/p>\n The difference between incident and problem management<\/a> becomes much clearer when learners see why restoring service and eliminating recurrence are different objectives.<\/p>\n Change should not be taught as a paperwork exercise.<\/p>\n A good change process balances:<\/p>\n Risk.<\/p>\n Speed.<\/p>\n Approval.<\/p>\n Scheduling.<\/p>\n Communication.<\/p>\n Validation.<\/p>\n Rollback or recovery.<\/p>\n The broader change-management fundamentals<\/a> help learners understand why the right control depends on impact and risk rather than on applying maximum bureaucracy to every change.<\/p>\n A service can meet an SLA and still create a poor customer experience.<\/p>\n Include:<\/p>\n SLAs.<\/p>\n SLOs.<\/p>\n OLAs.<\/p>\n KPIs.<\/p>\n Experience measures.<\/p>\n Business outcomes.<\/p>\n The article on service levels and experience measures<\/a> helps connect operational indicators with actual service value.<\/p>\n A useful lesson cycle is:<\/p>\n Explain one concept.<\/p>\n Show a short scenario.<\/p>\n Ask learners to choose an action.<\/p>\n Have them justify the decision using ITIL language.<\/p>\n Compare alternatives.<\/p>\n Return to the concept.<\/p>\n This is more effective than teaching ten definitions and waiting until the end of the day to apply them.<\/p>\n PeopleCert\u2019s current Foundation exam contains 40 multiple-choice questions, allows 60 minutes, is closed book, and requires 65% to pass.<\/p>\n Your internal quizzes should therefore test understanding and application without creating the false impression that learners need to write essays or memorize every paragraph of the official book.<\/p>\n The Version 5 objectives<\/a> should define coverage, while internal practice should reveal whether learners can apply the concepts.<\/p>\n PeopleCert provides current official learning materials and has also provided updated assets for ITIL 4 during the transition period.<\/p>\n If you teach Version 5, rebuild the sequence around Version 5 rather than adding a \u201cwhat changed\u201d appendix to an ITIL 4 course.<\/p>\nStart by separating new learners from ITIL 4 holders<\/h3>\n
Teach digital products and services as one operating system<\/h3>\n
Keep value creation at the center<\/h3>\n
Teach the four dimensions through one case<\/h3>\n
Update the AI content deliberately<\/h3>\n
Teach the ITIL Value System as a connected model<\/h3>\n
Use guiding principles as decision rules<\/h3>\n
Use real ITSM scenarios instead of generic definitions<\/h3>\n
Connect change management with service value<\/h3>\n
Teach service levels beyond SLA compliance<\/h3>\n
Replace slide-heavy teaching with short application loops<\/h3>\n
Use the current Foundation exam structure in assessment design<\/h3>\n
Use the current Foundation materials, not an old slide deck with patches<\/h3>\n