What guiding principles are and why ITIL has them

This course is the second step in the HSM University ITIL preparation program. ITIL-110 introduced the vocabulary of service management: value, outcomes, costs, risks, utility, warranty and the roles of providers and consumers. This course turns to the ideas that guide decisions when no procedure tells you exactly what to do: the seven guiding principles, the governance that directs and oversees service management, and the continual improvement model that keeps services getting better. Together they answer a practical question every service team faces many times a day: given everything we know, what is the sensible next step?

A note on independence before we begin. ITIL® is a registered trade mark of the PeopleCert group. This course is an independent study guide written in our own words. It does not reproduce official publications and contains no real exam questions. The quiz and exam questions are original practice items designed to build understanding.

Why a framework needs principles

Frameworks such as ITIL describe practices: incident management, change enablement, service level management and dozens more. Practices are useful, but no set of practices can anticipate every situation. A service desk manager deciding whether to add a new approval step, a product owner choosing between two features, and an executive deciding whether to outsource a data center all face choices the practice guides do not settle. Principles fill that gap. They are short statements of good judgment that apply in any situation, at any level and in any organization.

ITIL describes a guiding principle as a recommendation that guides an organization in all circumstances, regardless of changes in its goals, strategies, type of work or management structure. Three properties make a statement a principle rather than a rule:

• It is universal. It applies to a ten-person start-up and to a federal department, to software development and to facilities management.
• It is self-validating. Its usefulness has been shown repeatedly in practice; you do not need to accept it on faith.
• It empowers people. It helps people make good decisions without waiting for someone to write a procedure.

The contrast with rules is important. A rule says "every change must be approved by the change advisory board". A principle says "keep it simple and practical". The rule may be right for high-risk changes and wasteful for low-risk ones. The principle helps people decide which situations need the heavy process and which do not.

The seven guiding principles

ITIL 4 introduced seven guiding principles in 2019, refining earlier versions that appeared in ITIL Practitioner guidance. ITIL (Version 5), released by PeopleCert in February 2026, keeps all seven names unchanged and adds more guidance on how they interact and how organizations can adapt them to their own values. At the time of writing (October 2026), both editions are in use for training and examinations, so always confirm which edition your exam is based on. The principles are:

Where the principles sit in ITIL

In ITIL 4, the guiding principles are one of the five components of the service value system, alongside governance, the service value chain, practices and continual improvement. The service value system as a whole is covered in ITIL-130; for this course it is enough to know that the principles shape how every other component is used. Governance uses the principles when setting direction. Teams apply them when they design a value stream or run a practice. Continual improvement relies on them at every step.

ITIL (Version 5) organizes its guidance around digital products and services and their life cycle, and it gives more attention to experience, sustainability and the responsible use of artificial intelligence. The guiding principles remain at the center of that guidance. If anything, they become more important when technology changes quickly, because detailed procedures date faster than principles do.

Principles from other bodies of knowledge

ITIL is not the only framework built on principles. Agile software development rests on the values and principles of the Agile Manifesto (2001). Lean thinking grew from the Toyota Production System and emphasizes value, flow and the removal of waste. DevOps emphasizes flow, feedback and continuous learning. The PRINCE2 project management method has seven principles of its own, and the PMBOK Guide (eighth edition, 2025) is organized around principles of project management. The ITIL principles share much with these. That is deliberate: ITIL was written to work alongside other approaches, not to replace them.

For an exam, learn the ITIL wording. For practice, recognize that a team already working in an Agile or Lean way will find the ITIL principles familiar and can connect them to habits it already has.

How to use the principles

The principles are not a checklist to recite. They are lenses for looking at a decision. A useful habit is to take a proposal and ask the question each principle raises. Consider a team proposing to replace its ticketing tool. Focus on value asks who benefits. Start where you are asks what the current tool does well. Progress iteratively asks whether the switch can happen in stages. Collaborate asks who should help choose. Think holistically asks what reports, integrations and training will change. Keep it simple asks whether all the requested features are needed. Optimize and automate asks whether the current workflow should be improved before it is copied into a new tool.

Not every principle will matter equally for every decision, and sometimes they pull in different directions. Keeping things simple may argue against an integration that holistic thinking says is needed. Lesson 9 looks at how to handle those tensions. For now, the key point is that the principles are meant to be considered together.

What this course covers

Lessons 2 to 8 take the principles one at a time, with scenarios, failure modes and worked examples. Lesson 9 shows how they work together and how to resolve conflicts between them. Lesson 10 covers governance: how a governing body evaluates, directs and monitors service management, with Canadian and US examples. Lesson 11 covers the continual improvement model, the continual improvement register and measurement. Lesson 12 covers reporting and culture and finishes with a capstone that applies everything to a struggling service desk.