4.2 The Seven Guiding Principles (Part 1)

The Guiding Principles: Universal Advice for Every Decision

The guiding principles are one of the five components of the ITIL Value System, and they are a favorite exam topic. A guiding principle is a recommendation that guides an organization in all circumstances, regardless of changes in goals, strategies, work type, or management structure. Three qualities define them: they are universal (they apply to any situation), enduring (they do not go out of date), and advisory (they guide rather than dictate). Importantly, the seven principles are identical in ITIL 4 and Version 5, so no re-memorizing is needed if you already know them.

They are also meant to be used together and continuously, not followed once and set aside, and not picked individually while ignoring the rest.

The full list, in order, is: focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; and optimize and automate. This section covers the first three; section 4.3 covers the remaining four.

1. Focus on value

Focus on value states that every activity the organization undertakes should map, directly or indirectly, to value for itself, its customers, and other stakeholders. Value is not only functional output; it includes outcomes, experience (UX and CX), cost, risk, and sustainability. Applying the principle starts with knowing who is being served and what they consider valuable, then continually checking that work still serves them.

Application example: a product team chooses which features to build by asking which option best improves customer outcomes and sustainability, rather than which option is easiest to code. The classic anti-pattern this principle guards against is internal optimization, shipping the lowest-effort feature that delivers no consumer value. A useful exam cue: if a scenario mentions selecting work by consumer outcome, experience, or sustainability, the answer is usually focus on value.

2. Start where you are

Start where you are advises against automatically scrapping the current state and starting from scratch. Before building something new, honestly assess what already exists, current services, data, tools, processes, skills, and capabilities, and reuse or improve whatever is valuable. Two supporting ideas matter for the exam. First, the assessment should be objective, ideally using direct observation and measurement rather than assumptions or second-hand reports, because opinions about the current state are often wrong. Second, reusing working assets is usually cheaper and lower risk than a greenfield rebuild.

Application example: a service team studies its current incident data and user feedback before redesigning support, instead of assuming it already knows the problems. The principle protects against the not-invented-here bias that destroys perfectly good working assets. Note the boundary: start where you are does not mean refuse to change; it means base change on an accurate picture of the present.

3. Progress iteratively with feedback

Progress iteratively with feedback advises breaking work into small, manageable increments, delivering them, and using the resulting feedback to shape the next increment. Big-bang delivery delays learning and magnifies risk; small increments surface problems early, when they are cheap to fix. Each iteration should be a coherent piece that can be evaluated. Crucially, feedback loops run before, during, and after each iteration, so the organization keeps sensing changing needs, stakeholder reactions, and results.

Application example: a product team releases a small improvement, measures adoption, then adjusts the next increment. This is why Version 5 aligns naturally with Agile and Lean ways of working, and why it pairs well with CI/CD pipelines that make small, frequent releases practical. Watch the trap where an option suggests delivering everything in one final release with no interim feedback, that is the opposite of this principle.

How the first three work together

These principles reinforce one another. Focus on value tells you why to act; start where you are grounds you in reality before acting; and progress iteratively with feedback governs how you move forward, in small, evidence-led steps. A team modernizing a payroll service would use all three at once: confirm what payroll value means to employees and the business (focus on value), measure the existing service and reuse what works (start where you are), and roll out changes in slices while gathering feedback (progress iteratively with feedback).

Treating the principles as a menu, applying one while ignoring the others, is the mistake the exam most often rewards you for spotting.

Nature of the principles and common traps

A subtle point the syllabus makes: not every principle is equally relevant in every situation, but each should always be considered to judge how much it applies. The principles are guidance, not rigid rules, and they are deliberately enduring, they have survived multiple ITIL updates and are word-for-word the same in Version 5. Watch for these traps:

• Focus on value only after launch. Wrong, it applies throughout the lifecycle, from discovery onward.
• Start where you are means never change. Wrong, it means base change on an accurate current-state assessment.
• Iterating means no planning. Wrong, each increment is still planned; feedback simply shapes the next one.

Recognizing the signature cue of each principle, value for principle 1, current-state assessment for principle 2, small feedback-driven steps for principle 3, is the fastest route to the marks.