What Does Guiding principles Mean?
On This Page
Quick Definition
Guiding principles are like the core rules or beliefs that help an organization make good decisions, especially when implementing IT service management. They are not steps to follow but rather broad ideas that should always be kept in mind. For example, one principle is to focus on the value you provide, not just the technology you use.
Commonly Confused With
Processes are structured sets of activities designed to achieve a specific outcome, like incident management or change management. Guiding principles, on the other hand, are broad, universal recommendations that govern how you design and perform those processes. You can have a process that violates a principle (e.g., a change management process that is overly complex, violating 'Keep it simple'). In other words, processes are the 'what' and 'how', while principles are the 'why' and 'with what mindset'.
Your company has a password reset process. A guiding principle like 'Optimize and automate' would tell you to automate that process. The process itself is the set of steps to reset a password; the principle guides you on whether to improve it.
Policies are formal, mandatory rules or directives from management, such as 'All passwords must be 12 characters long and include special characters'. Guiding principles are not mandatory rules; they are flexible recommendations that help you make good decisions within the boundaries of policies. A policy might say you must use two-factor authentication; a principle like 'Focus on value' helps you choose the best two-factor method for your users without breaking the policy.
A security policy says you must log all access attempts. The principle 'Keep it simple and practical' suggests you log only what is necessary for audits, rather than logging every mouse click, to avoid data overload.
Corporate values are broad cultural statements about an organization's identity, like 'Integrity' or 'Innovation'. Guiding principles are more specific to service management and are actionable in day-to-day IT work. While values inspire, guiding principles direct. For example, a corporate value might be 'Customer first,' which is similar to 'Focus on value,' but the guiding principle provides a more detailed framework for applying that value in service management contexts.
A company's value is 'Teamwork.' The guiding principle 'Collaborate and promote visibility' tells you exactly how to apply that value: by making work visible and breaking down silos.
Must Know for Exams
For general IT certifications, especially those focused on ITIL 4, the guiding principles are a core exam topic. The ITIL 4 Foundation exam, for instance, expects candidates to not only name the seven principles but also to understand their meaning deeply and apply them to given scenarios. The exam domain covering the ITIL Service Value System (SVS) specifically includes guiding principles as a mandatory component. Questions will test your ability to distinguish between the principles and to identify which principle is best applied in a specific situation.
In the ITIL 4 Foundation exam, you can expect scenario-based multiple-choice questions. For example: "A team wants to automate their change approval process. Which guiding principle should they apply first to ensure they are automating a process that is efficient?" The correct answer would be 'Optimize and automate' because the principle explicitly states that automation should follow optimization. A common distractor would be 'Keep it simple and practical', which sounds similar but is about avoiding unnecessary complexity, not about the sequence of optimization before automation.
For more advanced ITIL certifications, such as ITIL 4 Managing Professional or ITIL 4 Strategic Leader, the guiding principles are not just testable as isolated facts but are integral to answering complex case study questions. Candidates must demonstrate how the principles interact and how they can be used to guide long-term strategy, governance, and continual improvement. In the ITIL 4 Direct, Plan and Improve exam, for instance, you might be asked to design a measurement framework and then justify how it aligns with multiple guiding principles.
Even for non-ITIL certifications, such as CompTIA Project+ or PMP, understanding these principles is useful because they align with general project management and business strategy concepts. PMP's guiding principles (like being a diligent steward) are different, but the skill of using a set of universal rules to make better decisions is tested directly or indirectly. For any exam that touches on IT service management, process improvement, or organizational change, expect to see questions that require you to pick the right principle for the right job, and to understand why it is important.
Simple Meaning
Imagine you are building a house. You have a book of blueprints (your plans) and a set of tools. But more importantly, you have a few core ideas that guide every decision you make: you want the house to be safe, energy-efficient, and a comfortable place for your family. These core ideas are like guiding principles. They don't tell you exactly which hammer to use or where to put the windows, but they ensure that every choice you make-from the foundation to the roof-moves you closer to your goal of a safe, efficient, comfortable home.
In IT, the most famous set of guiding principles comes from the ITIL 4 framework. These principles are meant to be universal and practical for any organization, not just IT departments. Think of them as the "north star" for service management decisions. The seven ITIL guiding principles are: 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.
Let's break that down with an everyday analogy. You are organizing a community picnic. Instead of just jumping in and buying hot dogs, you start by thinking about the real goal: bringing neighbors together (Focus on value). You look at what you already have-maybe a park reservation and some volunteers (Start where you are). You don't try to plan the entire event in one go; you outline it, get feedback from a few neighbors, and adjust (Progress iteratively with feedback). You talk to the volunteers and share the guest list so everyone knows what's happening (Collaborate and promote visibility). You consider the whole event-parking, food, activities, cleanup-not just the food (Think and work holistically). You avoid making a 10-page plan when a simple checklist works (Keep it simple and practical). Finally, you use a sign-up sheet online instead of collecting paper forms (Optimize and automate). By using these guiding principles, the picnic runs smoothly and everyone has fun. They work the same way in an IT organization: they help teams make better, more consistent decisions without getting lost in unnecessary complexity.
Full Technical Definition
In the context of ITIL 4, guiding principles are a set of seven codified recommendations that can be applied universally across all service management activities and decision-making processes. They are not prescriptive steps or policies; rather, they function as a foundational layer underpinning the entire ITIL 4 framework, designed to be adaptable to any organization's size, industry, or maturity level. These principles were derived from industry best practices, lean, agile, and DevOps methodologies, and are intended to replace the earlier ITIL guiding principles (from ITIL 2011) with a more modern, business-outcome-focused set.
The seven ITIL 4 guiding principles are: 1. Focus on value: Beyond simply delivering a service, this principle insists that every activity must map directly to value creation for stakeholders, typically measured in terms of utility (what the service does) and warranty (how it does it).
2. Start where you are: This discourages the common mistake of ignoring existing processes, tools, and data when attempting improvement. It mandates taking an honest baseline measurement of the current state before designing a future state, using tools like gap analysis and maturity assessments.
3. Progress iteratively with feedback: This principle advocates for breaking large initiatives into smaller, manageable increments. Each increment is a cycle that includes delivery of value, solicitation of stakeholder feedback, and subsequent adjustment. This aligns with agile and lean concepts.
4. Collaborate and promote visibility: This emphasizes breaking down silos between teams (development, operations, security, business units) and making work-in-progress visible through tools like kanban boards and service catalogs. The goal is to reduce hidden work and unplanned rework.
5. Think and work holistically: Also known as systems thinking, this principle requires that improvements or changes to one part of the service system (people, processes, technology, partners) consider the impact on the entire system. A change to a database schema, for example, must be evaluated against its impact on all dependent applications and reporting.
6. Keep it simple and practical: This principle is a standing critique of over-engineering. It advocates for minimizing unnecessary complexity, avoiding the accumulation of unused processes, and prioritizing outcomes over elaborate documentation.
7. Optimize and automate: This principle promotes continuous improvement of existing processes before automating them. It follows the sequence: first, standardize and simplify a process; then, measure its performance; then, optimize; and finally, automate where it provides a return on investment.
These principles are used during the ITIL 4 Service Value System (SVS) and the Service Value Chain, acting as a filter and guide for all strategic and operational decisions. They are not optional; they are integral to an ITIL 4-aligned management system. Professionals are expected to apply them reflexively, using them to challenge assumptions and validate decisions in everything from problem management to change enablement.
Real-Life Example
Let’s imagine you are the head of events for a large university. You need to organize an annual career fair. Instead of just booking the gymnasium and calling companies, you decide to apply guiding principles to make the event successful.
First, you Focus on value. The core value isn’t just having a fair; it’s helping students find internships and companies find talent. So every decision-which companies to invite, what booths to set up, what workshops to run-must support that goal. You don't invite a software company if the primary need is healthcare internships.
Next, you Start where you are. You review past career fairs. You have a database of previous attendees, feedback forms, and a budget spreadsheet. You don’t ignore these assets; you use them to build on what already exists. You realize the parking situation was a problem last year, so you plan to address it instead of reinventing the whole registration process.
You decide to Progress iteratively with feedback. Instead of building the entire plan in secret for three months, you release a rough schedule early, share it with a handful of students and company reps, and tweak it based on their input. This prevents a final plan that nobody likes.
You Collaborate and promote visibility. You set up a shared online workspace where the student volunteer team, the career services office, and the facilities team can all see the same plan, the task assignments, and the deadlines. No one is working in the dark, and you avoid the classic problem of two teams booking the same room.
You Think and work holistically. You realize that attracting more companies will also mean more cars, more noise, and a higher demand for food trucks. You consider the entire system-not just the booths, but also traffic flow, waste management, and security. A successful fair requires all these pieces to work together.
You Keep it simple and practical. You resist the temptation to create a 40-page event manual. Instead, you create a one-page checklist for each volunteer, a simple floor plan, and a clear schedule. Complexity doesn't improve the outcome.
Finally, you Optimize and automate. You notice that registering companies is still done via email. You set up a simple Google Form and automated confirmation emails. This frees up hours of manual work. By using these guiding principles, you create a career fair that runs smoothly, meets its goals, and avoids the chaos of uncoordinated decisions.
In IT, exactly the same logic applies: a team deploying a new CRM system would use these same principles to ensure the project delivers value, builds on existing data, gets early user feedback, coordinates across departments, thinks about training and support as a whole, avoids over-engineering the configuration, and automates repetitive data migration tasks.
Why This Term Matters
Guiding principles matter in practical IT because they prevent organizations from making common, costly mistakes in service management. Without them, teams often fall into the trap of chasing after bright, shiny new tools without a clear value proposition. They might implement a complex change management process that creates more paperwork than protection, or they might rebuild a system from scratch because they didn't bother to assess what already existed. The principles act as a decision-making filter, ensuring that every initiative-from a major digital transformation to a simple process update-remains aligned with the organization's overall goals.
For IT professionals, these principles are not just theoretical concepts found in a textbook. They are practical tools used daily. A system administrator proposing a server upgrade can use "Focus on value" to justify the cost by linking it to improved uptime for customers. A project manager can use "Progress iteratively with feedback" to avoid the classic "big bang" failure by delivering incremental improvements. A service desk manager can use "Optimize and automate" to justify deploying a chatbot for common password reset requests.
these principles are especially important in modern IT environments that blend DevOps, Agile, and ITIL practices. They provide a common language and decision-making framework that can bridge the gap between traditional operations teams and fast-moving development teams. For example, a principle like "Collaborate and promote visibility" directly addresses the historical tension between ops and dev by encouraging shared metrics and open communication. When an organization adopts these principles as part of its management system, they reduce internal friction, improve the velocity of change, and ultimately deliver better outcomes for the business. Professionals who understand and can apply these principles in real-world scenarios are far more valuable than those who only know the theory.
How It Appears in Exam Questions
Exam questions about guiding principles typically fall into three main patterns: scenario-based identification, principle-matching, and order-of-operations questions.
In scenario-based identification, you are given a short description of a situation and asked which guiding principle is being applied or should be applied. For example: "A project team is migrating a legacy application to the cloud. They first thoroughly document the current configuration and performance metrics before designing the new environment. Which guiding principle is the team following?" The correct answer is 'Start where you are', because they are assessing the existing state rather than starting from scratch. Distractors might include 'Focus on value' (if the scenario emphasized business benefits) or 'Progress iteratively' (if they were doing it in small steps).
Matching questions ask you to pair a description or phrase with the correct principle. For instance: "Match the following definitions to the correct guiding principle:" with options like 'Identifying what is truly important to the customer' (Focus on value), 'Making work visible using a kanban board' (Collaborate and promote visibility), and 'Building in feedback loops during project sprints' (Progress iteratively with feedback). These test your recall of the precise meaning of each principle.
Order-of-operations questions are more common in advanced exams. They might ask: "An organization wants to automate its incident resolution process. According to the guiding principles, what should be done first?" The trap is that a learner might rush to 'Optimize and automate' as a single step, but the correct reasoning is that before automating, you must first 'Keep it simple and practical' by simplifying the process, then 'Optimize' it, and only then automate. Some questions ask which principle is most important to apply before automation.
Finally, you may see scenario questions that test the ability to identify a violation of a principle. For example: "A team is implementing a new ITSM tool and decides to create a custom, highly complex workflow for every single request type, even though most requests are simple password resets. Which principle are they ignoring?" The answer is 'Keep it simple and practical', because they are adding unnecessary complexity. These questions require you to think critically about what could go wrong when principles are not followed.
Study ITIL 4
Test your understanding with exam-style practice questions.
Example Scenario
A mid-sized company called CloudSync has been experiencing poor user adoption of their internal IT support system. Users complain that the portal is confusing and the response times are slow. The IT team, led by a new manager, decides to revamp the entire support system from scratch, buying an expensive new ticketing tool and hiring a consultant to design new workflows. They skip any user survey because "they already know what's wrong."
Based on the ITIL guiding principles, they made several mistakes. First, they violated 'Start where you are'. They could have reviewed the existing system's usage data, looked at feedback from the last two years, and identified specific pain points-like a broken search function or a poorly designed form-rather than assuming everything needed replacing. Second, they violated 'Focus on value'. They spent a significant budget on a new tool without tying it to the actual value for users: faster resolution and easier access. Third, they ignored 'Collaborate and promote visibility'. They did not involve user representatives in the design, so the new portal may include features nobody wants.
Now, let's apply the principles correctly. The team first sets up a short survey (Start where you are) and discovers that 80% of support tickets are about password resets and email configuration. They realize the real value is reducing password reset time, not a shiny new portal (Focus on value). Instead of a full revamp, they implement a simple self-service password reset tool and a chatbot for common questions (Keep it simple and practical). They test this with a small group of users in one department, collect feedback, and improve it (Progress iteratively with feedback). They show the planned changes on the intranet and invite comments (Collaborate and promote visibility). They realize that the new chatbot will interact with the existing directory service, so they coordinate with the security team to ensure no vulnerabilities (Think and work holistically). Finally, they automate the password reset process entirely (Optimize and automate). The result: user satisfaction goes up, costs go down, and the company saves hundreds of hours per month. This scenario shows how following guiding principles can transform a failed project into a success.
Common Mistakes
Confusing 'Keep it simple and practical' with doing less work or skipping important steps.
The principle is about avoiding unnecessary complexity, not about cutting corners. A simple process that still meets all compliance and security requirements is very different from a process that is incomplete or insecure.
Always check if the complexity you are planning to remove is truly unnecessary. A process that ensures security or regulatory compliance is not 'unnecessary complexity.' Keep it simple, but keep it safe.
Thinking 'Start where you are' means you cannot make major changes or use new technology.
This principle does not forbid innovation. It says you should assess and leverage existing assets-processes, data, skills-as a foundation, rather than ignoring them. You can still adopt new technology, but you do so by understanding what you already have.
When proposing a new tool, first document the current state. Ask: what can we keep, what can we build upon, and what truly needs replacement? This often saves time and money.
Applying 'Optimize and automate' before 'Keep it simple and practical'.
Automating a messy, complex process only results in fast, consistent mess. The correct sequence is: first simplify the process, then optimize it, then automate it. Skipping simplification leads to wasted resources.
Before automating anything, write down the current process and look for steps that can be combined, simplified, or eliminated. Only then consider automation tools.
Believing 'Focus on value' only applies to the end customer and not to internal stakeholders like employees or partners.
Value is defined by all stakeholders of a service. An internal help desk must deliver value to employees (quick resolution) just as a customer-facing service delivers value to external clients. Ignoring internal stakeholders can lead to poor employee experience and low productivity.
When planning a new service or process, explicitly identify all stakeholder groups (customers, employees, partners, regulators) and define value for each group.
Misinterpreting 'Think and work holistically' as meaning you need to involve every department in every decision.
Systems thinking requires you to consider the impact on the whole system, but it does not require that every decision be made by a large committee. It means you should check dependencies and ripple effects, but you can still empower small teams to make decisions quickly once the impact is understood.
When making a change, ask: who will be affected? If the impact is narrow, a small team is fine. If the change affects multiple departments or the customer experience, then cross-functional input is needed.
Exam Trap — Don't Get Fooled
{"trap":"In an exam, you may be presented with a scenario where a team has made a change that seems successful, but the question asks which principle was violated. Learners often choose 'Focus on value' because they think any successful project automatically focuses on value. However, the trap is that the project may have delivered value despite violating another principle, such as 'Start where you are' or 'Collaborate and promote visibility'."
,"why_learners_choose_it":"Learners fall for this because 'Focus on value' sounds like the most obvious principle to check. If a project succeeded, they assume value was achieved, so they rule out that principle and pick a different one. But the trap is that the question is about which principle was violated, not about which one ensured success.
A successful outcome does not mean all principles were followed.","how_to_avoid_it":"Always read the scenario for evidence of negligence, not just for outcomes. Look for specific clues: did they ignore existing data?
Did they work in silos? Did they overcomplicate the process? Match the behavior to the principle definition exactly. For example, if the scenario describes that the team built a new solution without looking at existing processes, the violated principle is 'Start where you are', even if the new solution worked.
Value was delivered despite the violation."
Step-by-Step Breakdown
1. Recognize the need for a decision or improvement
Every journey begins with a trigger: a problem, an opportunity, or a request. For example, a team realizes that service desk tickets are piling up. This step identifies that a guiding principle can help frame the response.
2. Frame the decision using the 'Focus on value' principle
Before taking any action, ask: what value will this deliver, and to whom? Define the desired outcome in terms of stakeholder benefits. This prevents launching into technical solutions without a clear purpose.
3. Assess the current state using 'Start where you are'
Measure and document the existing process, tools, and data. For example, check the current ticket volume, common issues, and user satisfaction scores. This baseline helps avoid reinventing the wheel.
4. Plan a small, iterative improvement using 'Progress iteratively with feedback'
Break the improvement into small increments. For instance, first implement a simple FAQ page, measure response, then add a chatbot. Collect feedback at each step to adjust course.
5. Involve stakeholders using 'Collaborate and promote visibility'
Share your plan with users, developers, and support staff. Make progress visible on a shared board or document. This avoids surprises and builds buy-in.
6. Check for system-wide impacts using 'Think and work holistically'
Evaluate how the change affects other parts of the organization. A new chatbot might need to integrate with the knowledge base and directory services. Consider security, training, and support implications.
7. Simplify and then automate using 'Keep it simple and practical' and 'Optimize and automate'
First, remove any unnecessary steps in the process. Then, optimize the flow to make it efficient. Finally, automate where it makes sense. For example, automate ticket categorization only after you have simplified the category list.
Practical Mini-Lesson
In a real-world IT environment, guiding principles are not just a poster on the wall; they are actively used as a quality gate for every major decision. Many organizations integrate them into their change approval processes, project kickoffs, and problem reviews. For instance, before a change advisory board (CAB) approves a new change, they can check it against the principles: Does this change clearly deliver value? Have we assessed the current state? Have we simplified the approach? Are we collaborating with the right teams?
A common operational mistake is to treat the principles as a checklist that is mindlessly ticked off. For example, a team might say they have 'focused on value' by stating the benefit in a vague way, or they might claim to have 'started where they are' by listing tools but not understanding why those tools are failing. True application requires critical thinking. A senior IT professional uses the principles to challenge assumptions. When someone proposes a new monitoring tool, a professional applying 'Start where you are' would ask: what monitoring data do we already collect? What gaps does it have? Can we close those gaps with a cheaper, simpler solution?
In configuration context, consider an IT team managing firewalls. The principle 'Keep it simple and practical' suggests using a standard set of rule templates rather than creating custom rules for every tiny exception. This reduces complexity, improves performance, and makes audits easier. The principle 'Optimize and automate' would then lead them to use a firewall management tool that enforces those templates and automatically logs rule changes.
What can go wrong? Without principles, teams often over-engineer solutions. A classic example is a company that deployed a sophisticated IT asset management system with full integration, only to find that no one had the time to keep the asset database updated. They had violated 'Keep it simple and practical' and had not 'Started where they are' by understanding that their asset tracking maturity was low. The system was abandoned. Another common failure is automation gone wrong: a team automated a complex, error-prone process, resulting in automated errors happening faster. They skipped the optimization step.
Professionals need to know that the principles interact. A change that is simple and iterative (Progress iteratively) will naturally be easier to keep simple and practical. A holistic view (Think and work holistically) directly supports collaboration. Understanding these relationships helps you apply them more effectively. In practice, the principles create a culture of continuous, value-driven improvement rather than a culture of rushing to implement the next trending solution.
Memory Tip
Remember the seven principles using the acronym FISH CK SO: Focus on value, Iteratively (progress iteratively), Start where you are, Holistically (think and work holistically), Collaborate, Keep it simple, Optimize and automate.
Covered in These Exams
Current Exam Context
Current exam versions that test this topic — use these objectives when studying.
ITIL 4ITIL 4 →Related Glossary Terms
Two-factor authentication (2FA) is a security method that requires two different types of proof before granting access to an account or system.
AAA (Authentication, Authorization, and Accounting) is a security framework that controls who can access a network, what they are allowed to do, and tracks what they did.
802.1X is a network access control standard that authenticates devices before they are allowed to connect to a wired or wireless network.
Frequently Asked Questions
Are the ITIL guiding principles only for ITIL certifications?
No, they are universal concepts that can be applied in any industry or project management context. While they are explicitly taught in ITIL 4, their principles are drawn from lean, agile, and good management practices.
Do I need to memorize all seven principles word-for-word for the exam?
Yes, for ITIL 4 Foundation, you should be able to recall all seven principles by name and understand their definitions. For higher-level exams, you need to be able to apply them to case studies.
Is there a priority order among the principles?
No, all seven principles are equally important and should be used together. However, in a given situation, one principle may be more relevant to apply first, like 'Start where you are' before designing a new solution.
Can guiding principles be used for personal productivity?
Absolutely. For example, 'Focus on value' can help you prioritize tasks that matter, and 'Progress iteratively with feedback' can encourage you to share draft work early for input.
What is the difference between a guiding principle and a best practice?
A best practice is a proven method or technique for achieving a specific result, like ITIL's problem management process. A guiding principle is a broader, more foundational idea that helps you decide which best practice to use and how to adapt it.
How often do the guiding principles change?
In ITIL 4, they are considered stable. They were revised from earlier ITIL editions but are expected to remain consistent in future updates because they are based on long-standing management concepts.
Can an organization ignore a guiding principle?
Yes, but doing so often leads to suboptimal outcomes. For example, ignoring 'Collaborate and promote visibility' typically results in miscommunication and rework. The principles are advisory, not mandatory, but ignoring them increases risk.
Summary
Guiding principles in the context of ITIL and IT service management are a set of seven fundamental, universal recommendations that help organizations make better decisions, avoid common pitfalls, and consistently deliver value. They are not rigid rules or step-by-step processes; instead, they act as a mental framework that guides how teams think, plan, and execute service management activities. The seven principles are: 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.
These principles matter because they directly address the root causes of many failed IT projects, such as ignoring existing assets, over-engineering solutions, automating inefficient processes, and working in silos. For IT professionals, mastering these principles is essential not only for passing exams like ITIL 4 Foundation but also for being effective in real-world roles. They provide a common language that bridges development, operations, and business teams, fostering a culture of continuous improvement and value-centricity.
In exams, expect scenario-based questions that require you to identify which principle is being applied or violated, and to understand the proper order of operations. The biggest trap is to assume a successful outcome means no principle was violated, or to confuse the principles with processes and policies. By internalizing these principles, you will not only ace your certification exams but also become a more thoughtful and effective IT professional. Remember the acronym FISH CK SO to keep them at your fingertips.