ITIL Foundation V5 study materials
ITIL Foundation V5 study resources

ITIL Foundation V5: ITIL Guiding Principles

ITIL Foundation V5 · Work through your exam, one topic at a time.

All guide sections

ITIL Guiding Principles

What this domain tests

The exam asks you to recognize the seven guiding principles, explain what each recommends, and choose the principle that best fits a scenario. It also tests how principles interact. They are recommendations, not mandates, and they apply to every initiative and relationship.

The seven principles

  • Focus on value: map every action to value for a stakeholder; value is perceived by the recipient, not asserted by the provider.
  • Start where you are: assess what already exists; reuse and improve rather than discard by default.
  • Progress iteratively with feedback: split work into small, manageable increments and use feedback before the next increment.
  • Collaborate and promote visibility: involve the right people and share information so decisions are based on evidence and trust.
  • Think and work holistically: understand how parts interact; avoid optimizing one silo at the expense of the whole.
  • Keep it simple and practical: use the minimum steps that achieve the outcome; remove activity that adds no value.
  • Optimize and automate: optimize a workflow before automating it; automate only where it improves value.

Worked example

A service desk plans an AI chatbot. Focus on value asks whether users get faster outcomes, not whether the tool is innovative. Start where you are reuses the existing knowledge base. Progress iteratively pilots one request type and reviews transcripts. Collaborate includes agents, users, and security. Holistic thinking connects the bot to incident and knowledge practices. Keep it simple limits intents to high-volume requests. Optimize and automate standardizes the process before automation. The reasoning: each principle tests a different risk-value, wasted effort, big-bang failure, exclusion, silo effects, complexity, and premature automation.

Traps

Treating principles as auditable rules; automating a broken process; reading “start where you are” as “never change”; equating internal output with stakeholder value; using “simple” to remove necessary controls; collaborating without sharing findings.