Applying the principles together

The previous seven lessons examined each guiding principle on its own. In practice, nobody applies a single principle in isolation. A real decision, such as how to improve a slow onboarding process or whether to replace a monitoring tool, draws on several principles at once, and sometimes they seem to point in different directions. This lesson looks at how the principles interact, how to resolve apparent tensions between them, how to adapt them to an organization's values and context, and how to use them as a practical decision aid. It also explains how ITIL (Version 5) extends the guidance on applying the principles, while keeping the principles themselves unchanged.

The principles interact

ITIL states that the guiding principles should not be used in isolation. Each principle supports and depends on the others. Some of the strongest connections are:

• Focus on value guides all the others: it decides what is worth simplifying, optimizing or automating.
• Start where you are and progress iteratively with feedback form a natural pair: understand the current state, then improve it step by step.
• Collaborate and promote visibility supports think and work holistically, because seeing the whole system depends on information flowing between its parts.
• Keep it simple and practical comes before optimize and automate: simplify first, then automate what remains.
• Progress iteratively with feedback supports focus on value, because feedback reveals whether value is being delivered.

The figure is a simplification: every principle connects to every other in some way. But the three pairs shown are useful to remember, both for practical work and for exam questions that ask which principles naturally go together.

Which principles apply to a decision?

Not every principle is equally relevant to every decision. ITIL advises that organizations should consider which principles are relevant and how they apply, rather than mechanically applying all seven. A useful habit is to review each principle briefly against the decision at hand and note which raise important questions.

Resolving tensions between principles

Sometimes principles appear to conflict. ITIL acknowledges this and asks practitioners to use judgment, guided above all by value. Common tensions include:

• Start where you are versus optimize and automate: reusing an old tool may be cheaper now, but a new tool may allow automation that saves more later.
• Progress iteratively versus think holistically: small iterations may seem to ignore the bigger picture, while holistic planning may seem to delay action.
• Collaborate versus keep it simple: involving many stakeholders can make decisions slower and more complex.
• Keep it simple versus think holistically: considering every dependency can make solutions more complicated.

In each case, the tension is resolved by applying the principles together rather than choosing one. For iterative versus holistic, ITIL's own wording helps: "comprehend the whole, but do something". Understand the whole system, then take a small step within it. For collaborate versus simple, involve the right people in the right way, which is not the same as involving everyone in everything.

Adapting the principles to the organization

The principles are universal, but how they are applied depends on context. A small start-up, a large bank and a government department will apply them differently. ITIL (Version 5) places more emphasis on this, encouraging organizations to adapt the principles to their own values, culture and circumstances rather than treat them as a fixed checklist.

Factors that influence how the principles are applied include:

• Regulatory environment: a heavily regulated organization may need more formal controls, which affects how far it can simplify.
• Risk appetite: an organization tolerant of risk may iterate faster and automate more boldly.
• Size and structure: collaboration in a ten-person team looks very different from collaboration across a multinational.
• Culture: an organization with a blame culture must work on trust before visibility will work (lesson 12).
• Maturity: an organization just starting service management may focus on start where you are and keep it simple before tackling advanced automation.

The principles as a decision aid

The principles are most useful when they become a shared language for decisions. When a team proposes a change, reviewers can ask which principles it applies and which it neglects. When a project stalls, the principles help diagnose why: perhaps the team did not start where it was, or feedback was missing. When two people disagree, the principles provide neutral ground for discussing the trade-offs.

Scores like these are judgments, not precise measurements. Their value lies in prompting discussion about where a proposal is weak, not in the number itself.

Principles in exam scenarios

Foundation exam questions often describe a situation and ask which principle is being applied or ignored. A reliable approach is to look for key words. References to existing tools, data or observation point to start where you are. Small steps and reviews point to progress iteratively. Removing steps points to keep it simple. Involving stakeholders or sharing information points to collaborate and promote visibility. Effects across teams or dimensions point to think and work holistically. Consumers and outcomes point to focus on value. Technology replacing manual work, after improvement, points to optimize and automate. Questions may also ask which principles work well together; the pairs in the figure above are the most common answers.

Diagnosing a stalled initiative with the principles

The principles are also useful after the fact, to understand why an initiative struggled. Imagine a two-year program to introduce a new service management platform that ended late, over budget and with low adoption. A review using the principles might find that the team did not start where it was, because it rebuilt workflows from scratch and discarded knowledge articles that worked; that it did not progress iteratively, because everything went live on one weekend; that collaboration was weak, because agents saw the new tool for the first time in training; and that focus on value was lost, because success was measured by go-live date rather than by user outcomes.

Each finding suggests a lesson for the next initiative. The review also shows that weaknesses in one principle often cause weaknesses in others: without collaboration, the team could not understand the current state, and without iteration, it had no feedback to reveal the problem early. This is the practical meaning of the statement that the principles interact.

Key point to remember

Use the principles as a set of questions, not a set of rules. For any decision, ask which principles are relevant, look for tensions between them, resolve those tensions by returning to value, and adapt the answers to your organization's context. The principles stay the same; the way they are applied changes from one situation to the next.