3.4 Applying and Balancing the Guiding Principles

Universal, Enduring, and Used Together

The defining property of the guiding principles is in their definition: a principle "guides an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure." In other words they are universal (they apply to any kind of work) and enduring (they do not expire when the business changes). This is why ITIL recommends adopting them as part of how the organization thinks, rather than treating them as a checklist for a single project.

The second core idea is that the principles are used together, not in isolation. An organization should not select one favourite principle and ignore the rest. In any given decision, every situation may emphasize different principles — a crisis might lean on keep it simple and practical, while a long transformation leans on progress iteratively with feedback. ITIL advises reviewing all seven for relevance in each situation, then weighting them according to context. Their relevance can also change over time as circumstances evolve, so a principle that mattered little yesterday may dominate tomorrow.

The Principles Interact

The seven principles reinforce one another, and the better you see the connections, the easier the exam scenarios become. Optimize and automate explicitly reuses focus on value, progress iteratively with feedback, and keep it simple and practical in its path to optimization. Think and work holistically depends on collaborate and promote visibility to surface the interdependencies it must account for. Start where you are uses measurement, which feeds the feedback loops of progress iteratively.

How to Apply the Principles to a Decision

A practical approach when facing any decision:

1. Confirm the value at stake and who is being served (focus on value).
2. Assess what already exists before building anything new (start where you are).
3. Plan the work in manageable increments with feedback (progress iteratively with feedback).
4. Involve the right people and make the work visible (collaborate and promote visibility).
5. Account for the whole system, not just one part (think and work holistically).
6. Strip out steps that add no value (keep it simple and practical).
7. Optimize the result, then automate what is economical (optimize and automate).

Notice that all seven are reviewed — even if only two or three end up driving the final decision. ITIL frames this as a deliberate habit: scan every principle for relevance, then weight them according to the situation in front of you rather than applying a fixed formula. Over time the review becomes second nature, and the principles shape the organization's instinctive way of working rather than serving as an occasional checklist.

Matching Scenarios to Principles

Most Foundation questions on this topic give a short situation and ask which principle is being applied (or broken). The table below maps common cues to the correct principle.

Common Traps

• "Automate everything immediately" violates optimize and automate — optimize first.
• "No news is good news" violates collaborate and promote visibility — make work visible.
• "Rebuild from scratch" ignores start where you are — assess and reuse first.
• "Add features we assume customers want" misreads focus on value — value is the consumer's perception.

Keep the exact wording of each principle in mind, recognize that the principles work together, and you can reliably match any scenario to the right one.

Reading the Question Carefully

Scenario questions reward close reading. The key is to find the defining cue in the stem and ignore the noise. If a stem mentions "existing tools," "current process," or "before changing anything," it is almost always start where you are, even if it also mentions value or feedback. If it contrasts a team's local success with a worse overall outcome, it is think and work holistically. If it puts technology after an improvement step, it is optimize and automate. " — because the answer is the principle whose recommendation the team ignored.

Because the principles overlap, more than one may seem plausible; choose the one whose central idea the scenario most directly illustrates. Finally, remember that the principles are recommendations, not rigid rules or mandatory process steps — a stem implying they are compulsory, sequential, or tied to a single dimension is describing them incorrectly. With the seven definitions and their recommendation lists memorized, the scenario-matching items become some of the most predictable marks on the Foundation exam.