The 7 Guiding Principles

What Are Guiding Principles?

Guiding principles are recommendations that can guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.

They are:

• Universal — applicable to any organization and any situation
• Enduring — valid regardless of changes in context
• Flexible — used together or individually, depending on circumstances
• A tool to adopt and adapt ITIL to specific needs

The guiding principles are a core component of the Service Value System (SVS).

---

1. Focus on Value

Everything the organization does should link, directly or indirectly, to value for itself, its customers, and other stakeholders.

What It Means

Everything should map back to value. This includes understanding:

• Who is the service consumer? (customer, user, sponsor)
• What does the consumer value? (outcomes, not just outputs)
• How does this activity contribute to that value?

Value may come in many forms: revenue, customer loyalty, lower cost, growth opportunities, or reduced risk.

Why It Matters

Without a focus on value, organizations risk optimizing processes or delivering outputs that consumers don't actually care about.

Practical Application

• Always ask: "How does this create value for the customer?"
• Map improvement initiatives back to outcomes
• Understand the customer experience at every touchpoint
• Measure what matters to consumers, not just what's easy to measure

Exam Tip

Questions about this principle often involve identifying what a service consumer cares about most, or asking which principle would help an organization understand what customers value. This principle is also primarily concerned with the consumer's revenue and growth.

---

2. Start Where You Are

Do not start from scratch and build something new without first considering what is already available to be leveraged.

What It Means

Before designing a solution, assess the current state carefully. Understand:

• What services and methods already exist
• What is working well and can be reused
• What needs to be changed or discarded
• What can be built upon

Why It Matters

Organizations often waste effort rebuilding what already exists. Existing services, tools, processes, and knowledge have already been tested and refined — ignoring them is wasteful.

Direct Observation

The principle emphasizes direct observation over relying on reports and assumptions. Measure and observe the current state as accurately as possible to make informed decisions.

Practical Application

• Conduct current-state assessments before starting improvement work
• Reuse existing workflows, tools, and knowledge where possible
• Preserve what works; only discard what doesn't add value
• Baseline metrics before making changes

Exam Tip

Questions about this principle typically involve phrases like "assess the current state," "decide what can be reused," or "avoid starting from scratch." It is the principle that recommends leveraging what already exists.

---

3. Progress Iteratively with Feedback

Resist the temptation to do everything at once. Even huge initiatives must be accomplished iteratively.

What It Means

Organize work into smaller, manageable pieces that can be executed and completed in a timely manner. After each iteration:

• Collect feedback
• Evaluate results
• Adjust the approach

Why It Matters

Attempting to do everything at once:

• Increases risk
• Delays value delivery
• Makes it hard to course-correct
• Can lead to analysis paralysis — spending so much time planning that nothing gets done

Feedback Loops

Feedback loops are essential. They allow the organization to:

• Detect and respond to changes early
• Validate assumptions before full commitment
• Incorporate stakeholder input continuously

Practical Application

• Break large improvements into small, deliverable iterations
• Define success criteria for each iteration
• Collect feedback at each stage
• Be willing to pivot based on what you learn
• Start with a minimum viable product (MVP) approach

Exam Tip

The phrase "analysis paralysis" is strongly associated with this principle. Questions often describe a scenario where an organization keeps analyzing options without acting — the answer will be this principle. It also describes doing something instead of spending a long time analyzing different options.

---

4. Collaborate and Promote Visibility

Organizations work better when they work together, and achieving this requires information, understanding, and trust.

What It Means

Include the right people in the right roles in decisions and improvement initiatives. Make work visible so that:

• Decision-making improves
• Accountability increases
• Stakeholders trust the process

Why It Matters

Insufficient visibility leads to:

• Poor decision-making
• Difficulty driving improvements
• Missed opportunities to identify bottlenecks
• Lack of stakeholder trust

Understand the Flow of Work

This principle explicitly calls for organizations to:

• Understand the flow of work in progress
• Identify bottlenecks and excess capacity
• Uncover waste

Practical Application

• Involve stakeholders early and throughout initiatives
• Use visual management (kanban boards, dashboards)
• Communicate progress openly and regularly
• Remove silos between teams
• Share data and insights across the organization

Exam Tip

This is the principle associated with flow of work, bottlenecks, and waste. If a question asks which principle focuses on visibility, collaboration, or understanding work in progress — this is the answer. Don't confuse it with "Think and work holistically" which is about integrated systems thinking.

---

5. Think and Work Holistically

No service, practice, process, department, or supplier stands alone. The outputs of every activity affect — directly or indirectly — other activities and the entire SVS.

What It Means

Think beyond individual components. Consider how:

• All parts of the organization are interconnected
• Changes in one area affect others
• Services must be designed and delivered end-to-end
• Optimization of one part shouldn't sub-optimize the whole

Why It Matters

Siloed thinking leads to:

• Local optimizations that harm overall performance
• Poor end-to-end customer experience
• Missed integration issues
• Fragile, brittle services

Practical Application

• Design services thinking about the entire value stream
• When changing one component, assess impact on others
• Break down organizational silos
• Use end-to-end metrics alongside component metrics
• Ensure all four dimensions are considered together

Exam Tip

This principle is about systems thinking — seeing the whole, not just the parts. Questions involving "interconnected," "end-to-end," or "impact on other activities" point to this principle. The key differentiator from "collaborate" is that this is about integrated thinking, not just stakeholder involvement.

---

6. Keep It Simple and Practical

If a process, service, action, or metric fails to provide value or produce a useful outcome, eliminate it.

What It Means

Always use the minimum number of steps to accomplish an objective. Use outcome-based thinking to produce practical solutions. Avoid:

• Unnecessary complexity
• Processes that exist "just because we've always done it this way"
• Metrics that no one acts on
• Steps that produce no useful outcome

Why It Matters

Complexity:

• Slows delivery
• Increases cost
• Increases the chance of errors
• Makes improvement harder

Practical Application

• Challenge every step in a process: "What value does this add?"
• Eliminate exception processes that are rarely used
• Use the fewest possible forms, approvals, and handoffs
• Design for the most common case, handle exceptions separately
• "Do less, but do it better"

Exam Tip

Questions for this principle often describe an overly complex process or ask how to approach simplification. The answer involves eliminating steps that add no value. It's also about using the minimum number of steps. Do not confuse with "optimize and automate" — simplify before automating.

---

7. Optimize and Automate

Maximize the value of the work carried out by human and technical resources.

What It Means

Organizations should:

1. Understand and agree the context and objectives
2. Assess the current state to identify improvement opportunities
3. Agree on the future state and priorities, focusing on simplification
4. Ensure stakeholder engagement and commitment
5. Automate — but only after optimizing

The Optimization Steps (in order)

The principle defines a clear sequence:

1. Understand vision and objectives
2. Assess current state (identify biggest positive impact)
3. Agree future state and priorities (standardize and simplify)
4. Secure stakeholder engagement
5. Implement iteratively with feedback
6. Monitor and measure continuously

Why Automate After Optimizing?

Automating a bad process produces bad results faster. "Attempting to automate something that is complex or suboptimal is unlikely to achieve the desired outcome."

Practical Application

• Identify repetitive, low-value manual tasks for automation
• Use AI, RPA, and tooling for routine work
• Free up human capacity for complex, judgment-intensive work
• But always understand the process first
• Ensure humans can intervene where automation isn't appropriate

Exam Tip

The starting point for optimization is understanding the vision and objectives of the organization — not assessing current state (that's step 2), not stakeholder engagement (that's step 4). Remember the order. Also: simplify before you automate.

---

How the Principles Work Together

The guiding principles are not mutually exclusive — they're meant to be used together. Some natural groupings:

Principles	How They Combine
Focus on value + Start where you are	Assess what currently delivers value before changing anything
Progress iteratively + Collaborate	Iterate with input from stakeholders at each step
Keep it simple + Optimize and automate	Simplify first, then automate the simplified process
Think holistically + Collaborate	Working together requires seeing the full picture

Priority When Principles Conflict

In practice, Focus on value is often the tiebreaker — if there's doubt about which path to take, ask which creates more value for the consumer.

---

Exam Summary Table

Principle	Key Phrase	Common Distractor
Focus on value	Revenue, growth, customer loyalty	"stakeholder engagement" — that's step 4 of optimize
Start where you are	Assess current state, reuse	Don't confuse with "progress iteratively"
Progress iteratively	Analysis paralysis, do something	Not about doing everything at once
Collaborate and promote visibility	Flow, bottlenecks, waste, visibility	Not "think holistically"
Think and work holistically	Interconnected, end-to-end, whole system	Not "collaborate"
Keep it simple	Minimum steps, eliminate waste, outcome-based	Not "optimize and automate"
Optimize and automate	Starting point = understand vision/objectives	Starting point ≠ current state assessment

Key Takeaways

• There are 7 guiding principles in ITIL 4
• They are universal — applicable in any situation, any organization
• They help organizations adopt and adapt ITIL guidance
• Focus on value is the foundational principle
• Start where you are prevents wasted effort rebuilding what works
• Progress iteratively combats analysis paralysis and reduces risk
• Collaborate and promote visibility is about flow, bottlenecks, and stakeholder trust
• Think and work holistically is about systems thinking and end-to-end perspective
• Keep it simple eliminates unnecessary complexity
• Optimize and automate: understand vision first, simplify, then automate