Guiding principles (ITIL 5)

Seven recommendations that guide an organization's decisions and actions in all circumstances: Focus on value; Start where you are; Progress iteratively with feedback; Collaborate and promote visibility; Think and work holistically; Keep it simple and practical; Optimize and automate.

Always identify, understand, and maximize value for customers and stakeholders. Ask "Value for whom?" and "How will we know?" before acting.

Assess the current state objectively and use what is already available instead of building everything from scratch.

The application of artificial intelligence and machine learning to IT operations data to improve monitoring, event correlation, and incident response.

The use of technology to perform tasks with reduced human assistance, often to increase speed, consistency, and scalability.

The means by which an organization is directed and controlled, including policies, decision‑making structures, and oversight mechanisms.

What is Value stream?

A series of steps an organization undertakes to create and deliver products and services to consumers.

Guiding Principles and Continual Improvement in ITIL Version 5 — ITIL Foundation (Version 5) Exam Prep Bootcamp

Q: Which guiding principle is most clearly demonstrated by simplifying categories and rules **before** introducing AI automation?

Optimize and automate. **Optimize and automate** is best here: the team optimizes (simplifies and cleans up) the process first, then plans to automate it with AI. "Keep it simple and practical" is related, but the explicit optimize‑then‑automate pattern matches this principle most directly.

From ITIL 4 to ITIL 5: Why Guiding Principles Matter

Why Guiding Principles?

Guiding principles are short, memorable rules that help teams make good decisions when priorities clash or information is incomplete. They tell you how to think, not just what process to follow.

ITIL 5 Context

ITIL 5 builds on ITIL 4 and keeps the same core guiding principles, sharpening their use for fast‑changing, AI‑enabled environments like cloud, DevOps, and data‑driven operations.

A Compass, Not a Map

Treat guiding principles as a compass: even if detailed procedures are outdated, the compass still points you toward value, collaboration, and continual improvement across the service management system.

What You Will Learn

You will learn the seven ITIL guiding principles, the continual improvement model, and how to apply both to realistic caselets with trade‑offs, constraints, and stakeholder expectations.

The Seven ITIL Guiding Principles (ITIL 4 → ITIL 5)

The Seven Principles

ITIL 5 keeps seven guiding principles: 1) Focus on value, 2) Start where you are, 3) Progress iteratively with feedback, 4) Collaborate and promote visibility, 5) Think and work holistically, 6) Keep it simple and practical, 7) Optimize and automate.

Applies Everywhere

These principles apply to strategies, value streams, governance, AI tooling, and day‑to‑day decisions. On exams, they often appear in caselets asking which principle best guides an action.

Memory Grouping

Group them as: Value and context (1–2), Learning and collaboration (3–4), Systems thinking (5), Lean and automation (6–7). This helps you recall them quickly under exam pressure.

Principles 1–3 in Practice: Value, Reality, and Iteration

Focus on Value

Focus on value means asking "Value for whom and how do we measure it?" Example: Before deploying a student support chatbot, define metrics like response time, satisfaction, and fewer human‑handled tickets.

Start Where You Are

Start where you are means understand and reuse what you already have. Example: Before buying new AIOps tools, analyze existing logs and find that clearer incident ownership fixes most delays.

Progress Iteratively With Feedback

Progress iteratively with feedback means small steps plus learning. Example: Improve one self‑service request (password reset) first, gather feedback, then expand to other portal features.

Visual Metaphors

Picture a target for value, a magnifying glass on a map for current state, and a spiral staircase for iterative progress. These images help you recall which principle to apply.

Principles 4–7 in Practice: Collaboration, Systems, Simplicity, Automation

Collaborate and Promote Visibility

Collaborate and promote visibility: involve the right people and make work visible. Example: A major incident uses one shared channel and a live board so Dev, Ops, Security, and vendors see the same status.

Think and Work Holistically

Think and work holistically: avoid local optimization. Example: AI‑based auto‑scaling is evaluated not just for cloud cost, but also user experience, support load, billing, and compliance.

Keep It Simple and Practical

Keep it simple and practical: remove unnecessary steps. Example: Replace a 15‑field change form with a short standard‑change template for low‑risk updates.

Optimize and Automate

Optimize and automate: first streamline the process, then automate. Example: Simplify incident severity and routing before training an AI model to triage tickets.

The ITIL Continual Improvement Model

Why Continual Improvement?

Continual improvement is a structured way to keep services, practices, and value streams getting better over time, instead of treating improvement as a one‑off project.

The 7 Steps (1–3)

The model asks: 1) What is the vision? 2) Where are we now? 3) Where do we want to be? These steps align improvements with strategy and define a measurable target state.

The 7 Steps (4–7)

Then: 4) How do we get there? 5) Take action. 6) Did we get there? 7) How do we keep the momentum going? This creates a repeating improvement loop.

Typical Triggers

Triggers include recurring incidents, complaints, audit findings, new technology like AI, or strategic and regulatory changes. Each trigger can start a new pass through the model.

Mini Case: Applying the Continual Improvement Model

Work through this thought exercise step by step. You can jot down short bullet answers.

Scenario: Your university's online exam system suffered three outages during finals week. Students complained on social media; faculty escalated to the CIO.

Using the continual improvement model:

What is the vision?

Write 1–2 sentences for a vision related to reliable, stress‑free online exams.

Where are we now?

List 2–3 facts you would collect (for example, outage duration, root causes, affected courses).

Where do we want to be?

Define 2 measurable targets (for example, maximum allowed downtime during exam periods, satisfaction score).

How do we get there?

List 3 concrete actions. Try to use at least two guiding principles (for example, Focus on value, Collaborate and promote visibility).

Did we get there?

Describe 2 metrics or feedback sources you would check after implementing changes.

How to keep momentum?

Note 1 idea to ensure exam reliability is reviewed before every exam period (for example, a regular readiness check in the academic calendar).

As you do this, explicitly label where you are using guiding principles. For example: "Action: set up joint Dev‑Ops‑Network review (Collaborate and promote visibility)."

Culture of Learning, Feedback, and Experimentation

Culture Enables Principles

Guiding principles and continual improvement only work if the culture supports learning and experimentation. Without this, models stay on paper and behavior does not change.

Safety and Feedback

Psychological safety lets people report issues honestly. Feedback loops from users, systems, and teams power accurate "Where are we now?" and "Did we get there?" steps.

Experiments and Transparency

Small, safe experiments use progress‑with‑feedback and simplicity. Visual boards and dashboards make work and value streams visible, supporting collaboration and governance.

Responsible AI and Automation

Responsible AI use means checking alignment with value, monitoring bias, and seeing system‑wide effects. This connects Focus on value, Holistic thinking, and Optimize and automate.

Connecting Guiding Principles, Governance, and Value Streams

Guiding Principles and Value Streams

Value streams are end‑to‑end paths that deliver value. Guiding principles shape them: Focus on value, Keep it simple, and Optimize and automate guide how you design and improve these flows.

Guiding Principles and Governance

Governance sets direction and controls. Principles like Think and work holistically and Collaborate and promote visibility influence how decisions are made and communicated.

Continual Improvement in Governance

Continual improvement becomes part of governance when boards require improvement backlogs and review whether changes actually delivered value, not just whether they were completed.

AI, Automation, and Oversight

In AI‑enabled environments, governance ensures automation supports value streams and risk appetite, while guiding principles and continual improvement drive safe, adaptive change.

Quick Check: Matching Principles to Actions

Choose the best guiding principle for this situation.

Question:

A team wants to introduce an AI‑based assistant to categorize incoming incidents. Before automating, they simplify the existing categories, clarify routing rules, and clean up historical data. Which guiding principle is most clearly demonstrated?

Think first, then select your answer.

Which guiding principle is most clearly demonstrated by simplifying categories and rules **before** introducing AI automation?

Optimize and automate
Start where you are
Collaborate and promote visibility
Keep it simple and practical

Show Answer

Answer: A) Optimize and automate

**Optimize and automate** is best here: the team optimizes (simplifies and cleans up) the process first, then plans to automate it with AI. "Keep it simple and practical" is related, but the explicit optimize‑then‑automate pattern matches this principle most directly.

Exam-Style Caselet: Trade-Offs and Constraints

Read this caselet and answer the questions for yourself. Then compare your reasoning to the hints.

Caselet:

A hospital IT department is under pressure. Doctors complain about slow access to patient records. The security team insists on strict multi‑factor authentication (MFA) and complex password rules. Management wants to reduce costs and is considering automating account provisioning with an AI‑assisted identity tool.

Constraints:

Patient safety and data privacy are critical.
Budget for new tools is limited.
Doctors have very little time for extra training.

Questions:

Which two guiding principles should drive the first set of decisions? Why?
Suggest one continual improvement initiative that balances usability, security, and cost. Outline how you would use the 7‑step model at a high level.
Identify one trade‑off and explain how the chosen principles help navigate it.

Hints (check after you think):

Many students pick Focus on value (patient care, safety, privacy) and Think and work holistically (IT, clinicians, security, finance, compliance).
A good improvement initiative might start with measuring login delays, defining target login times and security levels, piloting streamlined MFA for critical areas, then reviewing results.
Trade‑offs often involve usability vs. security vs. cost; guiding principles help keep decisions aligned with value and system‑wide impacts.

Review Key Terms and Principles

Use these flashcards to review the guiding principles and continual improvement concepts.

Guiding principles (ITIL 5): Seven recommendations that guide an organization's decisions and actions in all circumstances: Focus on value; Start where you are; Progress iteratively with feedback; Collaborate and promote visibility; Think and work holistically; Keep it simple and practical; Optimize and automate.
Focus on value: Always identify, understand, and maximize value for customers and stakeholders. Ask "Value for whom?" and "How will we know?" before acting.
Start where you are: Assess the current state objectively and use what is already available instead of building everything from scratch.
Progress iteratively with feedback: Organize work into smaller, manageable pieces; use feedback at each step to reduce risk and adapt.
Collaborate and promote visibility: Work together across boundaries and make information, work, and results visible to improve decisions and trust.
Think and work holistically: Consider the whole service management system and value streams, not just individual components or silos.
Keep it simple and practical: Use the minimum number of steps, roles, and controls needed to achieve outcomes; avoid over‑engineering.
Optimize and automate: First streamline and clarify the work, then automate stable and well‑understood parts using technology.
Continual improvement model: A seven‑step model: 1) What is the vision? 2) Where are we now? 3) Where do we want to be? 4) How do we get there? 5) Take action. 6) Did we get there? 7) How do we keep the momentum going?
Improvement trigger: An event or observation that starts an improvement cycle, such as recurring incidents, complaints, audit findings, or new technology opportunities.

Key Terms

AIOps: The application of artificial intelligence and machine learning to IT operations data to improve monitoring, event correlation, and incident response.
Automation: The use of technology to perform tasks with reduced human assistance, often to increase speed, consistency, and scalability.
Governance: The means by which an organization is directed and controlled, including policies, decision‑making structures, and oversight mechanisms.
Value stream: A series of steps an organization undertakes to create and deliver products and services to consumers.
Guiding principles: High-level recommendations that guide an organization's decisions and actions in all circumstances, regardless of changes in goals, strategies, type of work, or management structure.
Psychological safety: A shared belief that the team is safe for interpersonal risk‑taking, allowing people to speak up about issues and mistakes.
Continual improvement: A recurring organizational activity performed at all levels to ensure that performance continually meets stakeholders' expectations.
Continual improvement model: An ITIL model with seven steps that provides a structured approach to planning and managing improvements.