ITIL 4 Foundation — Practice Q&A
Q: What's the fundamental structural difference between ITIL 4 and ITIL v3?
A: ITIL v3 organized around a service lifecycle (Strategy, Design, Transition, Operation, Continual Service Improvement) with formal processes within each stage. ITIL 4 replaced this with the Service Value System — guiding principles, governance, the service value chain, practices, and continual improvement — a more holistic, value-co-creation-focused model reflecting how modern IT service delivery has moved toward more collaborative, continuously-evolving practice, influenced by agile and DevOps.
Q: Why are ITIL 4's guiding principles described as applying "universally" while practices are described as "context-dependent"?
A: The seven guiding principles are explicitly designed to offer decision-making guidance in any circumstance, regardless of organizational structure or specific situation — they're deliberately broad. Practices, by contrast, are specific sets of resources for performing particular work (like incident management), and how a practice is actually implemented varies significantly depending on an organization's specific context, size, and the four dimensions shaping it.
Q: What's the key distinction between incident management and problem management?
A: Incident management prioritizes restoring normal service operation as quickly as possible, even through a workaround that doesn't address the underlying cause. Problem management specifically investigates and addresses the root cause of incidents to prevent recurrence, which may take longer than any individual incident's restoration. A single underlying problem can generate multiple incidents over time before its root cause is identified and resolved.
Q: Why does ITIL 4 distinguish between standard, normal, and emergency changes rather than using one uniform change-approval process?
A: Applying the same heavy-weight authorization process to every change regardless of actual risk would be inefficient and contrary to the "keep it simple and practical" guiding principle. Standard changes (pre-authorized, low-risk, routine) need minimal process, normal changes (higher risk or novelty) need full assessment and authorization, and emergency changes (needing rapid implementation to resolve or prevent a significant incident) need an expedited but still controlled process — matching the process weight to the actual risk involved.
Q: What does "value co-creation" mean in ITIL 4, and how does it differ from how IT service delivery was traditionally framed?
A: Value co-creation means value isn't simply delivered by IT to a passive business/customer — it's created through collaboration between the service provider and service consumer, with both contributing to and benefiting from the outcome. This differs from a traditional framing where IT executes requests efficiently as a purely internal service provider; ITIL 4's framing shifts the implicit goal toward IT and business stakeholders jointly ensuring services actually produce intended outcomes.
Q: Why does ITIL 4 treat continual improvement as embedded throughout the framework rather than a separate final phase?
A: The service value chain's "improve" activity operates continuously across all other activities, not as a distinct end-of-lifecycle stage, and continual improvement also appears as a guiding principle and as its own formal practice. This reflects a deliberate departure from ITIL v3's "Continual Service Improvement" lifecycle stage, which could imply improvement happens mainly at the end of a service's lifecycle rather than constantly throughout.