The Guiding Principles
A guiding principle is a recommendation that guides an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure. ITIL 4 defines seven guiding principles that are universal and enduring. They can be applied to any initiative and to relationships with all stakeholders, and they embody the core messages of ITIL and of service management more broadly, encouraging and supporting continual improvement at every level.
Focus on Value and Start Where You Are
The first guiding principle, focus on value, states that everything the organization does should link back, directly or indirectly, to value for itself, its customers, and other stakeholders. Applying it begins with knowing who is being served and understanding what they value, since value is subjective and defined by the consumer, not assumed by the provider. This means identifying the service consumer, understanding their desired outcomes and how they use the service, and mapping the whole consumer experience, sometimes called the customer or user journey. Anything that does not contribute to value is a candidate for elimination. This principle keeps every decision anchored to a purpose rather than to activity for its own sake, and it should be applied to routine operational work as much as to major projects. The second principle, start where you are, advises against the temptation to discard everything and rebuild from scratch. Before making changes, the organization should assess what already exists, because current services, processes, people, and tools may already be delivering value and can often be reused or extended. Rebuilding wastes the value already present and can destroy things that were working. Applying this principle means observing the current state directly and objectively rather than relying only on reports or assumptions, which can be distorted. Measurement should support this observation, but ITIL cautions that the act of measuring can change what is measured, so metrics should be used carefully and combined with direct observation. Together these two principles create a grounded starting point for any improvement: understand the value you are trying to create, then look honestly at where you already are before deciding what to change. They discourage both aimless activity and destructive reinvention, and they set up the iterative, feedback-driven approach promoted by the next principle. In practice a team applying them asks two questions first: what value are we trying to create and for whom, and what do we already have that we can build on.
Progress Iteratively with Feedback
The principle of progress iteratively with feedback advises against trying to do everything at once in a single large effort. Instead, work should be organized into smaller, manageable sections that can be executed and completed in a timely manner. Each of these iterations delivers something of value and can be tackled sequentially or in parallel. Breaking work into iterations reduces risk, delivers value sooner, maintains momentum, and makes it easier to respond to changing circumstances, because a smaller piece of work is easier to understand, deliver, and adjust than a monolithic one. Crucially, iteration must be paired with feedback. Feedback loops before, during, and after each iteration provide information about many things: the perception of value by consumers, the efficiency and effectiveness of value chain activities, the state of a service, the impact of an initiative, the demand for products and services, and whether an improvement is producing the intended result. Seeking and using feedback ensures that each iteration is reassessed as circumstances change, so effort stays focused, relevant, and grounded in reality rather than in outdated assumptions. Without feedback, iterations become disconnected steps that may drift away from what stakeholders actually need. ITIL notes that iteration and feedback work best together: iterations create natural points at which to gather and act on feedback, and feedback makes each subsequent iteration better informed. Fast feedback also allows problems to be detected and corrected early, when they are cheaper to fix. This principle underpins agile and lean ways of working and connects to continual improvement, which relies on repeated small cycles of change and assessment. When applying it, a team plans manageable increments, builds in checkpoints to gather feedback, and is willing to reassess priorities and adjust course after each increment. The combination avoids the paralysis and risk of huge one-off efforts while keeping the work continuously aligned with value, and it reinforces the earlier principles by ensuring that the focus on value is validated against real evidence at every step rather than assumed once at the outset.
Collaborate and Promote Visibility
The principle collaborate and promote visibility has two connected halves. Collaboration recognizes that work done in cooperation across boundaries produces results that have greater buy-in, more relevance to objectives, and an increased likelihood of long-term success. When the right people work together and share information, they achieve outcomes that would be impossible in isolation. Applying this principle means identifying and involving the appropriate stakeholders, both inside and outside the organization, and choosing collaborators for their genuine contribution rather than for status or position. It does not mean that everyone must be involved in everything; effective collaboration involves the right people at the right time. Different groups contribute in different ways, so customers, users, suppliers, developers, and operational teams may all need to collaborate at various points. The second half, promoting visibility, addresses a common failing in organizations: important work and its true status are often hidden, leading to poor decisions and mistrust. When work is invisible, people make assumptions, priorities become distorted, and hidden work accumulates unnoticed. By making work and its consequences visible, the organization enables better decision-making because those decisions are based on accurate, shared information. Visibility also helps surface how much work is actually in progress, which can reveal overload and bottlenecks. Techniques that support visibility include making the flow of work transparent, understanding demand accurately, and communicating status openly. Insufficient visibility of work leads to poor decision-making, which in turn undermines the ability to create value. The two halves reinforce each other: collaboration generates the information and shared understanding that make visibility possible, and visibility gives collaborators the transparency they need to work together effectively. This principle also supports a culture of trust, since openness reduces suspicion and encourages people to share problems early. When applying it, an organization asks who should be involved, ensures information flows freely between them, and deliberately makes work and its results visible so that everyone can see what is happening and contribute to better outcomes.
Think and Work Holistically; Keep it Simple and Practical
Two guiding principles work as a natural pair. Think and work holistically recognizes that no service, practice, process, department, or supplier stands alone. The outputs the organization delivers to itself, its customers, and other stakeholders will suffer unless it works in an integrated way to handle its activities as a whole rather than as separate parts. Everything is connected: the four dimensions all contribute to any service, and the components and activities of the service value system all interact. Applying this principle means understanding how the parts of the organization work together and coordinating them so that a change in one area does not undermine another. Complexity, however, is real, so ITIL pairs holistic thinking with the discipline of keeping it simple and practical. This principle advises using the minimum number of steps necessary to accomplish an objective and always using outcome-based thinking to produce practical solutions that deliver value. If a process, service, action, or metric fails to provide value or produce a useful outcome, it should be eliminated. Applying this principle involves designing for the majority of cases rather than trying to account for every rare exception, since over-engineering to cover every possible situation adds cost and complexity that usually outweigh their benefit. Judgement is needed, because simple is not the same as easy, and removing too much can be as harmful as keeping too much. Conflicting objectives should be recognized and reconciled rather than papered over with additional complexity. The two principles balance each other. Holistic thinking guards against local optimizations that harm the whole, while keeping it simple guards against the paralysis and waste that come from trying to manage everything as an intricate, all-encompassing system. Together they encourage solutions that are coherent across the organization yet lean enough to be workable. In practice, a team applies them by mapping how their work connects to the wider system, then deliberately stripping their solution down to the essential steps that produce the required outcome, discarding anything that adds effort without adding value.
Optimize and Automate
The seventh guiding principle, optimize and automate, urges organizations to maximize the value of the work carried out by their human and technical resources. It combines two related ideas in a deliberate order. Optimization means making something as effective and useful as it needs to be. Before anything is optimized, the organization should understand the context in which the proposed optimization exists, including the overall vision and objectives, and agree what the desired future state and outcomes are. It should then assess the current state, standardize and simplify, and continually review and refine, applying the other guiding principles throughout. Automation typically means using technology to perform a step, or series of steps, correctly and consistently with limited or no human intervention. Automation can make optimization possible, reduce costs, remove human error from repetitive tasks, and free people to focus on more complex decision-making and higher-value work that technology cannot easily perform. The order of the two words matters and is a frequently tested point at Foundation. An organization should optimize before it automates, because automating an inefficient or ineffective process simply lets the organization produce waste faster and at scale. Automating a broken process embeds and amplifies its flaws, so the process should first be simplified and streamlined, then automated where automation adds value. ITIL also cautions that automation is not an end in itself: it should be applied where it genuinely helps, not everywhere indiscriminately, and human judgement remains essential for tasks requiring context, empathy, or complex reasoning. This principle draws on the others. Optimization relies on focusing on value to know what good looks like, on starting where you are to understand the current state, on progressing iteratively to refine gradually, and on keeping it simple to remove unnecessary steps before technology is applied. Applied together, optimize and automate help the organization get the most from both its people and its technology, ensuring that effort is spent where it creates the greatest value and that routine, well-designed work is handled consistently and efficiently by machines.
Practice stays free. The full ITIL 4 Foundation study guide is the material itself, taught start to finish — a downloadable PDF + EPUB you keep.