The ITIL guiding principles. They are the seven fundamental rules that sit underneath everything else in ITIL 4. If you understand these seven ideas, you will understand the mindset that makes IT service management work well, and you will be able to answer a number of exam questions that test whether you grasp the spirit, not just the letter, of ITIL.
Jump to a section
A simple way to picture The ITIL Guiding Principles
7 recipe cards sit on your kitchen counter. Each card has a single, memorable rule that guides how you decide to cook dinner when 4 different friends show up with different dietary needs. The first card says "Focus on value" — that means you check what each friend actually wants to eat before you start chopping onions. The second card says "Start where you are" — so you look in your fridge first before buying new ingredients. The third card says "Progress iteratively with feedback" — you taste the soup halfway through and adjust the salt. The fourth says "Collaborate and promote visibility" — so you ask your friends to chop vegetables together and keep the recipe notes where everyone can see them. The fifth says "Think and work holistically" — you check that the starter, main, and dessert all fit together, not just one perfect dish. The sixth says "Keep it simple and practical" — you skip the complicated soufflé and make a reliable pasta. The seventh says "Optimise and automate" — you use a food processor to chop faster next time. These seven cards are the ITIL guiding principles: a set of universal, practical rules that help you make good decisions in any situation, whether you are cooking dinner or running an IT service.
The principles are not steps you follow in order. They are lenses you hold up to your work. You might use all seven on one project, or just a few. They work together, like a full recipe box, not a single instruction manual. Each principle reminds you to avoid common traps — like building something nobody asked for, or trying to do everything at once. They keep you focused on what actually matters: delivering real value to real people, without wasting effort.
The ITIL guiding principles are seven general, universal recommendations that guide an organisation in any situation, regardless of changes in its goals, strategies, type of work, or management structure. They were developed by reviewing ITIL practitioners from around the world and identifying the common patterns that lead to success. The principles are not optional extras — they are embedded in every part of ITIL 4.
Here is each principle explained in plain language, with a real example a beginner can understand.
Focus on value. Everything you do in IT should directly or indirectly create value for someone. That someone could be a paying customer, an internal user, or a stakeholder. Value is not defined by the IT team — it is defined by the person receiving the service. Before starting any work, ask: "What value will this create? For whom? How will we know?" A classic mistake is building a technically impressive solution that nobody actually wants or uses. For example, an IT team might spend months developing a new expense-reporting app with advanced features, but if employees find the current system good enough and refuse to switch, no value was delivered. The principle says: always start by understanding what the customer actually values.
Start where you are. Do not start from scratch. Look at what already exists — processes, tools, data, people — and build on it. This principle saves time, money, and frustration. It also reduces resistance because you are not throwing away people's existing work. The key is to measure and observe current practices honestly, without assuming they are wrong just because they are current. For example, before redesigning the IT help desk process, a team should shadow current technicians, log current call times, and understand why certain steps exist. Often, a step that looks wasteful on paper has a good reason behind it that a new process would miss.
Progress iteratively with feedback. Big, infrequent changes are risky. Instead, make small, frequent improvements and check with stakeholders at each step. This principle comes directly from agile and lean thinking. It means break large projects into smaller chunks, deliver each chunk quickly, and get feedback to guide the next chunk. For example, instead of building a complete new customer portal over six months and launching it all at once, release a minimal version that lets customers reset their passwords after two weeks, add the ability to update their address after four weeks, and so on. Each release gets feedback that shapes the next one.
Collaborate and promote visibility. Work across teams and roles. Share information, plans, and progress openly. When people understand the bigger picture and can see what others are doing, they make better decisions and avoid duplicated effort. This principle directly fights against silos — situations where different teams hoard information or work in isolation. For example, when planning a major system upgrade, the infrastructure team, the security team, the application team, and the business stakeholders should all have a shared dashboard showing milestones, risks, and decisions. No one should be surprised by a change that affects them.
Think and work holistically. No service, process, or technology exists in isolation. Every change you make in one area will affect other areas. This principle asks you to consider the whole system — people, partners, technology, information, processes — before making a decision. For example, if you decide to switch to a cloud-based email system, you cannot just think about the email software. You also need to consider network capacity, security policies, staff training, data migration, and how it integrates with the calendar system that the sales team relies on. A holistic view prevents optimising one part at the expense of the whole.
Keep it simple and practical. If a process, procedure, or tool is complicated, people will bypass it. The simplest solution that achieves the outcome is usually the best. This principle discourages over-engineering. For example, if the goal is to track which employees have completed mandatory security training, a simple spreadsheet with a weekly email reminder might work better than a custom-built training management system with workflows, notifications, and analytics. The principle says: do not add complexity unless it clearly adds more value than it costs in confusion.
Optimise and automate. Once you have a process that works and is simple, look for ways to make it faster, cheaper, or more reliable by removing waste and, where appropriate, using technology to reduce human effort. Optimisation comes before automation — automating a bad process just makes bad things happen faster. For example, before automating the IT asset inventory process, first simplify the process: reduce the number of data fields required, eliminate duplicate approvals, and standardise the naming convention. Only then automate the simplified process with a tool.
These seven principles are not independent rules. They support and reinforce each other. For instance, "Focus on value" helps you decide what to simplify under "Keep it simple and practical". "Progress iteratively with feedback" feeds naturally into "Optimise and automate" because each iteration is a chance to optimise. The principles are a toolkit, not a checklist.
ITIL 4 expects you to be able to name all seven principles, explain each one in a sentence or two, and recognise which principle is being applied (or ignored) in a given scenario. The exam will not ask you to memorise the order of the principles, but it will expect you to correctly match each principle to its definition and to a practical example.
Identify the problem or decision
Before applying any guiding principle, you need to understand the specific situation you are dealing with. For example, is it a slow IT process, a new service request, or a recurring incident? The principles are tools for thinking, and you need a clear problem to apply them to.
Apply 'Focus on value' first
Start by asking: who is receiving value from this work, and what does that value look like to them? This step prevents you from building something nobody wants. Write down the expected value in one sentence. If you cannot, you are not ready to proceed.
Assess the current state with 'Start where you are'
Look at what already exists — processes, tools, data, people's skills. Do not assume the current way is wrong. Measure it. Observe it. Understand why it exists. This step gives you a baseline and prevents you from reinventing the wheel or breaking something that works.
Plan small improvements using 'Progress iteratively with feedback'
Based on the value goal and the current state, design the smallest possible improvement you can make. Define how you will get feedback (e.g., a quick survey, a follow-up call). Do not plan a large, long project. Plan something you can do in days or weeks, not months.
Engage others with 'Collaborate and promote visibility'
Share your plan and findings with anyone who might be affected. Create a simple board or document that shows what you are doing and why. Invite input. This step reduces resistance and catches blind spots early.
Check the whole system with 'Think and work holistically'
Before implementing the improvement, ask: what else in the organisation might be affected? Does this change impact another team's work? Does it require a change in a different system? Adjust your plan to account for ripple effects.
Simplify the solution with 'Keep it simple and practical'
Review your planned improvement. Can you do it with fewer steps, fewer people, or simpler tools? Remove any feature or step that does not directly contribute to the value identified in step 2. Resist the urge to add elegance or future-proofing.
Implement and then look for automation with 'Optimise and automate'
Run the simplified improvement manually first. Gather data on how it performs. Once it is stable and working well, identify the most repetitive or error-prone steps and automate only those. Never automate a process that is still unstable or poorly understood.
Imagine you are an IT support analyst at a medium-sized company called GreenLeaf Logistics. The company has 500 employees spread across three offices. The current process for requesting a new laptop is a paper form that the employee fills out, their manager signs, the IT manager approves, and then the purchasing department orders the laptop. The whole process takes an average of 12 working days. Employees are unhappy. IT is frustrated. Management wants a faster process.
You decide to apply the ITIL guiding principles to redesign this process.
First, you apply "Focus on value". You interview ten employees who recently requested laptops. You discover that they do not care about the approval chain — they just want a laptop within three days. The value they want is speed and clarity, not a fancy approval workflow. This insight shapes everything that follows.
Next, you apply "Start where you are". You do not throw away the existing paper form immediately. Instead, you observe the current process for two weeks. You log how many forms are submitted, who touches each one, and where the delays happen. You discover that the biggest delay is not the manager's signature — it is the purchasing department sitting on approved requests because they batch orders once a week. You now know the real bottleneck.
Then you apply "Progress iteratively with feedback". Instead of designing a complete digital system, you make one small change: you create a simple shared spreadsheet where IT logs approved requests, and purchasing checks it daily instead of weekly. This one change reduces the average time from 12 days to 9 days. You ask employees if this helps. They say yes, but they still want faster. You release another small improvement: an online form (using a simple tool like Google Forms) that replaces the paper form. Time drops to 7 days. You get more feedback. Employees want to see the status of their request.
You apply "Collaborate and promote visibility". You create a simple status board visible to all employees showing each laptop request and its current stage. You also invite a representative from purchasing and a representative from the employees' side to a weekly 15-minute meeting to review the process. This visibility reduces the number of people emailing IT to ask "Where is my laptop?" because they can see the answer themselves.
You apply "Think and work holistically". You realise the laptop request process affects more than just IT. It affects HR (onboarding new hires), finance (budgeting), and facilities (storing laptops). You invite a person from HR and finance to join the weekly meeting. You discover that HR has a separate, manual process for setting up a new employee's account that happens after the laptop is ordered, causing a two-day gap where the laptop sits unused. By coordinating, you align HR's account setup to happen the same day the laptop order is placed. The holistic view eliminates this hidden waste.
You apply "Keep it simple and practical". Someone suggests building a custom web application with automated approval routing and integration with the HR system. You resist. The current online form and spreadsheet work well for 500 employees. You decide to keep the solution simple until the company grows beyond 1,000 employees. Adding a complex system now would cost time, money, and training, with little extra value.
Finally, you apply "Optimise and automate". Now that the process is simple and working well, you look for automation opportunities. You automate the email that notifies employees when their laptop is ready. You automate the hand-off from the online form to the purchasing queue. You automate the status board updates. Each automation saves a few minutes per request, which adds up across hundreds of requests per year. The process now takes an average of 3 days — the value employees said they wanted.
In this scenario, the ITIL guiding principles were not a set of rigid steps. They were a flexible mental framework that you used to ask better questions, avoid common traps, and deliver a result that actually solved a real problem for real people. That is exactly how IT professionals use the guiding principles in practice.
The ITIL 4 Foundation exam tests the guiding principles in several specific ways. You need to be ready for these question patterns.
First, you must be able to list all seven principles by name. The exam will show you a list of options and ask: "Which of the following is one of the ITIL guiding principles?" They will include distractors like "Plan, Do, Check, Act" (that is Deming's cycle, not a guiding principle) or "Design for performance" (not real). If you have memorised the seven names, you can quickly eliminate wrong answers.
Second, you will see scenario questions. These give you a short description of a situation and ask: "Which ITIL guiding principle is being applied?" or "Which principle is being ignored?" For example: "A project team builds a new reporting tool based on a manager's request without talking to the employees who will use it. Which principle are they failing to apply?" The answer is "Focus on value" because they did not check what the actual users value.
Third, the exam tests your understanding of the definitions, not just the names. They will give you a description and ask you to pick the correct principle. For example: "A principle that encourages breaking large improvements into smaller, manageable pieces with frequent feedback loops." The answer is "Progress iteratively with feedback". You need to be comfortable with the exact wording used in the ITIL 4 official material.
Key traps to watch for on the exam:
Do not confuse "Start where you are" with "Keep it simple and practical". "Start where you are" is about using what already exists as a starting point. "Keep it simple and practical" is about avoiding unnecessary complexity in the solution. They are different.
Do not confuse "Collaborate and promote visibility" with "Think and work holistically". "Collaborate" is about people working together and sharing information. "Holistically" is about seeing the whole system, including non-people elements like technology and processes.
The exam sometimes presents a principle in a negative way: "Which principle suggests you should not try to fix everything at once?" That is "Progress iteratively with feedback".
They may ask which principle is related to "minimising waste". The answer is "Optimise and automate", but note that "Keep it simple and practical" also reduces waste by avoiding over-engineering. In those tricky cases, look for the specific wording: if the question mentions technology or automation explicitly, choose "Optimise and automate". If it only mentions simplicity, choose "Keep it simple and practical".
Fourth, the exam can ask about the relationship between the principles and other ITIL concepts. For example: "Which guiding principle is most directly related to the 'Service Value Chain'?" The answer is "Think and work holistically" because the value chain shows how all the activities fit together as a system.
Finally, memorise this checklist of exam facts:
There are exactly seven guiding principles.
They are universal — applicable to any organisation, not just IT.
They are not sequential — you can apply any of them at any time.
They are intended to be used together, not in isolation.
They are derived from real-world practitioner experience, not theory.
Each principle has a specific, unique focus that does not overlap completely with any other principle.
If you can explain each principle in one sentence and give a one-sentence example for each, you are ready for the exam questions on this topic.
The seven ITIL guiding principles are universal recommendations that apply to any decision or activity in service management, not just large projects.
Focus on value means always start by understanding what the recipient of the service actually considers valuable, not what you assume is valuable.
Start where you are means measure and observe current practices before making changes, rather than designing a new solution from scratch.
Progress iteratively with feedback means break work into small increments, deliver quickly, and use feedback to guide the next step.
Collaborate and promote visibility means share information openly across teams and roles to avoid silos and duplicated effort.
Think and work holistically means consider how any change affects the entire system — people, technology, processes, partners — not just one part.
Keep it simple and practical means choose the simplest solution that achieves the desired outcome, avoiding over-engineering.
Optimise and automate means simplify a process first, then use technology to make it faster and more reliable, never automate a bad process.
The seven principles are meant to be used together and in any order — they are a flexible toolkit, not a checklist or a sequence of steps.
The ITIL 4 Foundation exam will test your ability to match each principle to its definition and to a real-world scenario, not just to recite the names in order.
These come up on the exam all the time. Here's how to tell them apart.
Focus on Value
Asks what the recipient wants and needs
Focuses on the desired future outcome
Drives decisions about what to build or change
Start Where You Are
Asks what currently exists and works
Focuses on the present state of processes and tools
Drives the starting point for improvement work
Progress Iteratively with Feedback
Focuses on how to break work into small pieces
Requires frequent feedback from stakeholders
Works well in early stages of a project
Optimise and Automate
Focuses on improving the efficiency of a stable process
Often occurs after a process is already working well
Works well in later stages when a process is mature
Collaborate and Promote Visibility
Focuses on people sharing information and working together
Emphasises communication, transparency, and teamwork
Aims to break down silos between teams
Think and Work Holistically
Focuses on the interconnected parts of the system (technology, processes, etc.)
Emphasises understanding the whole organisation as a system
Aims to avoid optimising one part at the expense of another
Keep It Simple and Practical
Focuses on reducing complexity in the solution itself
Asks what can be removed without losing value
Often involves manual, straightforward approaches
Optimise and Automate
Focuses on improving speed and reducing human effort
Asks what can be made faster or more consistent via technology
Often involves introducing tools or scripts
Service Value Chain
A model of the six activities that deliver value
Describes what you do in service management (plan, improve, engage, etc.)
Specific to the ITIL service value system
Guiding Principles
A set of seven universal recommendations for decision-making
Describes how you should think and behave in any activity
Applicable to any context, not just ITIL
Mistake
The seven guiding principles are a step-by-step process you must follow in order.
Correct
They are universal recommendations you can apply in any order, depending on the situation. You might use all seven or just a few on a given task.
Many beginners come from process-heavy backgrounds (like accounting or manufacturing) where steps have a fixed order. ITIL principles are intentionally flexible, not a linear method.
Mistake
The principle 'Focus on value' means you should always satisfy whatever the customer asks for, without questioning it.
Correct
Focus on value means you should understand what the customer truly values, which may be different from what they ask for. A customer might ask for a specific feature when what they really need is a simpler way to achieve a goal.
This misconception arises from a literal reading of 'customer is always right'. In IT, part of professional service is to help the customer identify their real needs, not just blindly fulfil requests.
Mistake
'Start where you are' means you should never change anything — just keep existing processes as they are.
Correct
It means you should use existing processes, data, and tools as a baseline for improvement, not ignore them. You absolutely should change things, but the changes should be built on a clear understanding of the current state.
The phrase 'start where you are' sounds static. Beginners sometimes interpret it as a call to avoid change, when it is actually a practical starting point for change.
Mistake
'Optimise and automate' means you should automate everything as soon as possible to save time.
Correct
Optimisation must come before automation. Automating a wasteful or poorly designed process just makes the waste happen faster. You simplify first, then automate.
The word 'automate' is exciting and sounds like a quick win. Beginners often focus on the automation part while skipping the harder optimisation step, leading to failed or counterproductive automation efforts.
Mistake
The guiding principles are only relevant for large IT projects, not for small daily tasks.
Correct
They apply to any activity, big or small. A help desk technician can apply 'Collaborate and promote visibility' by sharing a known issue on a team chat, or 'Keep it simple and practical' by choosing a straightforward fix over a complex workaround.
Beginners often assume ITIL is only about big, formal initiatives. The principles are actually designed to be lightweight and usable in everyday decision-making.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
No, the exam does not test the order. It tests whether you can name all seven and match each to its definition and a scenario. But memorising them in a mnemonic order (like FSSPKTO) can help you ensure you have all seven in your recall.
'Progress iteratively with feedback' is about how you approach change — breaking it into small pieces and using feedback. 'Optimise and automate' is about what you do to a stable process — simplify it first, then use automation. They work well together: iterative progress gives you opportunities to optimise in each cycle.
You can use any combination that fits the situation. The principles are a toolkit, not a compulsory list. In a small task, you might only use two or three. In a large project, you might use all seven at different points. The exam will test whether you can identify which principle is being applied in a given scenario, not whether all seven are used.
They are related but not identical. 'Customer focus' is a broader attitude. 'Focus on value' is a specific principle that says you should define value from the recipient's perspective and base all decisions on that definition. It includes but is not limited to customers — value can be for users, sponsors, or other stakeholders.
They do not contradict — they balance each other. 'Think holistically' reminds you not to simplify so much that you ignore important parts of the system. 'Keep it simple' reminds you not to make the solution so comprehensive that it becomes unmanageable. You need both to find the right level of simplicity that still accounts for the whole system.
They share some ideas — like 'progress iteratively' from Agile and 'optimise and automate' from Lean — but they are not identical. The ITIL principles are a distinct set of seven, created specifically for service management, and they cover areas that Lean and Agile do not explicitly address, such as 'start where you are' and 'think holistically'.
Possibly. The principles are meant to be universal, so the exam might describe a non-IT scenario (like a restaurant or a school) and ask which principle applies. Do not panic — just look for the key behaviour in the scenario and match it to the correct principle definition.
You've finished The ITIL Guiding Principles. Continue through the ITIL4F study guide to build a complete picture of the exam.
Done with this chapter?