6.2 ITIL with AI and Other Frameworks

Optimize and Automate, AI, and Complementary Frameworks

The "Optimize and Automate" Guiding Principle

Of the seven ITIL guiding principles, optimize and automate is the one most directly connected to AI. It has a deliberate order: optimize first, then automate. To optimize means to understand the desired outcome, assess the current state, agree a target, and simplify the work - removing waste and unnecessary steps. Only once the work is understood and streamlined should automation be applied to remove repetitive manual effort and free people for judgment-based tasks. The classic trap the exam tests is automating before optimizing: automating waste simply makes a poor process faster and harder to fix.

Automation and continual improvement reinforce each other; automation is never a substitute for understanding the work.

How AI and Automation Support ITIL Practices

In ITIL (Version 5), Artificial Intelligence (AI) is treated as both an enabler of automation and a governance concern. AI can assist across all eight lifecycle activities and the value chain: correlating events, triaging and categorizing incidents, predicting problems before they cause outages, generating and maintaining knowledge articles, powering virtual agents that fulfil service requests, and forecasting capacity. Applied well, AI augments human work - it does not mandate replacing every human role.

Version 5 introduces specific AI vocabulary you must recognize:

• AI maturity - the level of an organization's AI capability, from experimental use to AI that is embedded and optimized across ways of working.
• Generative AI (GenAI) - AI that creates new content such as text, summaries, drafts, or code (for example, drafting a knowledge article from incident data).
• Agentic AI - AI agents that can plan and take actions with limited human oversight, chaining tasks together toward a goal.
• AI governance - the rules, accountability, transparency, data quality, ethics, and human-oversight controls that keep AI use responsible.
• ITIL AI Capability Model - a model for assessing and building an organization's capability to adopt AI responsibly.

The key exam message: AI is a governance topic, not just an automation tool. A correct four-dimensions answer to "we want GenAI chat support" assesses skills and roles, data and AI technology, supplier dependencies, and the affected value stream - with governance in place - before launch, rather than measuring only how many automated replies are sent per hour.

ITIL and Other Frameworks - Complementary, Not Competing

A core Version 5 idea is that ITIL does not replace other ways of working; it integrates with and complements them. The official syllabus focuses on two partners: DevOps and PRINCE2.

DevOps is a culture and set of practices that break down the wall between development and operations to achieve fast, reliable flow - using continuous integration and continuous delivery or deployment (CI/CD), automation, shared ownership, and rapid feedback. ITIL contributes service management structure, governance, and end-to-end value focus; DevOps contributes speed and flow. Together they let organizations release frequently AND manage risk, value, and experience. ITIL's value streams and its "optimize and automate" principle align naturally with DevOps flow.

PRINCE2 is a structured project management method with defined roles, stages, and controls. ITIL manages products and services continuously across their whole lifecycle, whereas PRINCE2 governs finite projects - such as a major transformation, migration, or build. The two complement each other: a PRINCE2 project delivers a defined change, which ITIL then transitions, operates, and continually improves as part of the ongoing product and service lifecycle.

Although the exam's "ITIL and Other Frameworks" area centers on DevOps and PRINCE2, you should recognize that Agile (iterative, incremental delivery) and Lean (waste elimination and flow) also sit comfortably alongside ITIL - Lean thinking underpins value stream mapping, and Agile informs the adaptive, feedback-driven mindset. The unifying theme for every framework question is the same: these approaches are complementary, not competing, and ITIL provides the governance and service-management backbone that lets the others deliver value safely.

Common Traps

• Do NOT say governance is optional when Agile or DevOps teams exist - agile ways of working still need governance appropriate to context.
• Do NOT treat AI as pure automation - maturity and governance matter, and AI can augment rather than replace people.
• Do NOT automate before understanding and optimizing the work.
• Do NOT frame ITIL, DevOps, PRINCE2, Agile, or Lean as rivals; ITIL is designed to work with them.

This combined area is small - 2.5% for ITIL and AI plus 2.5% for ITIL and other frameworks, 5% together - but high-yield, because the questions are definitional and the traps are predictable. Learn the AI vocabulary, remember that optimize comes before automate, and answer every framework question with "complementary, not competing."