SkarpSkarp

Chapter 5 of 14

ITIL 4 Guiding Principles: Mindset for Modern IT

Discover the seven guiding principles that shape every ITIL 4 decision, helping organizations stay agile, lean, and focused on what really matters.

15 min readen

Big Picture: Guiding Principles in the ITIL 4 SVS

What Are Guiding Principles?

In ITIL 4, guiding principles are recommendations that guide an organization in all circumstances, regardless of changes in goals, strategies, or structure.

Role in the SVS

Guiding principles shape how people think and behave while they use the Service Value System to turn demand and opportunities into value.

Seven Principles (List)

The seven ITIL 4 guiding principles are: 1) Focus on value, 2) Start where you are, 3) Progress iteratively with feedback, 4) Collaborate and promote visibility, 5) Think and work holistically, 6) Keep it simple and practical, 7) Optimize and automate.

Why They Matter for Exams

You must: list all seven principles using official wording, recognize which principle applies in a scenario, and distinguish between similar-sounding principles in multiple-choice questions.

Principle 1: Focus on Value

Official Name and Definition

Focus on value means always identifying, understanding, and focusing on value for the customer and other stakeholders in everything the organization does.

Customer-Centric Thinking

Value is defined by the customer. Always ask: Who is the customer here, and what do they actually value in outcomes, experience, cost, and risk?

Link to SVS and Dimensions

This principle influences all value chain activities and all four dimensions, but only where they contribute to stakeholder value.

Exam Clue Phrases

Watch for phrases like: understanding what matters to the customer, prioritizing outcomes and benefits, or avoiding features users do not care about.

Focus on Value: Real-World Scenarios

Scenario 1: Service Desk Reports

Managers ignore a 10-page ticket report. Applying Focus on value, the team replaces it with a 1-page dashboard showing top issues, trends, and actions that support decisions.

Scenario 2: Features vs Performance

Users complain about slow portals, not missing features. With Focus on value, the team improves performance and stability before adding new features.

Recognizing the Principle

When a scenario stresses understanding customer outcomes and prioritizing what they truly care about, the principle being applied is Focus on value.

Principles 2 & 3: Start Where You Are; Progress Iteratively With Feedback

Start Where You Are: Definition

Start where you are means do not start from scratch and build something new without first considering what is already available.

Start Where You Are: Key Ideas

Reuse existing tools, data, processes, and knowledge. Assess the current state objectively and avoid the "new tool will fix everything" mindset.

Progress Iteratively With Feedback: Definition

Progress iteratively with feedback means organize work into smaller, manageable sections and use feedback before, during, and after each iteration.

Progress Iteratively: Key Ideas

Break work into small increments, get frequent feedback from users and stakeholders, and adjust after each step instead of doing big-bang changes.

Distinguishing the Two

Start where you are is about the starting point. Progress iteratively with feedback is about how you move forward in small, feedback-driven steps.

Mini Exercise: Pick the Right Principle (1–3)

For each short scenario, decide which principle fits best: 1) Focus on value, 2) Start where you are, or 3) Progress iteratively with feedback.

Write down your answers (1, 2, or 3) before checking yourself.

Scenario A

A university IT team wants to replace its legacy ticketing tool. Before buying a new platform, they review what the current tool can already do, what data it holds, and which parts users like.

  • Your answer:
  • Best fit: 2) Start where you are
  • Why: They are assessing and reusing the current state instead of starting from zero.

Scenario B

A mobile app team releases a basic version of a new student app, collects feedback for two weeks, then adds features and fixes in short sprints.

  • Your answer:
  • Best fit: 3) Progress iteratively with feedback
  • Why: They are working in small increments and using frequent feedback.

Scenario C

A service manager stops a reporting project that no one reads and replaces it with a short monthly summary answering: "What changed for the business?" and "What decisions does this support?"

  • Your answer:
  • Best fit: 1) Focus on value
  • Why: The change is driven by what stakeholders actually find valuable.

Principles 4 & 5: Collaborate, Promote Visibility; Think and Work Holistically

Collaborate and Promote Visibility: Definition

Collaborate and promote visibility means work together across boundaries to create value, and ensure information is visible and understandable to those who need it.

Collaborate and Promote Visibility: Clues

Look for breaking down silos, involving multiple stakeholders, sharing information, and making work or queues visible via boards or dashboards.

Think and Work Holistically: Definition

Think and work holistically means recognizing that outcomes come from effective management and integration of information, technology, people, partners, and processes.

Holistic Thinking: Clues

Watch for end-to-end views, considering all aspects of a service, and avoiding sub-optimization of one area at the expense of the whole system.

Distinguishing the Two

Collaboration is about people and visibility. Holistic thinking is about the entire system and value stream, from demand to value.

Principles 6 & 7: Keep It Simple and Practical; Optimize and Automate

Keep It Simple and Practical: Definition

Keep it simple and practical means always use the minimum number of steps needed to accomplish an objective and eliminate anything that does not contribute to value.

Simplicity: Clues

Look for over-complicated forms, too many approvals, or unnecessary steps. The fix is to simplify and remove non-value-adding activities.

Optimize and Automate: Definition

Optimize and automate means make something as effective and useful as it needs to be, then use technology to achieve what it is capable of.

Optimize, Then Automate

First improve and standardize the process; then apply tools or scripts to automate repetitive, predictable tasks. Do not automate a bad process.

Distinguishing the Two

Simplicity focuses on avoiding over-engineering. Optimization and automation focus on improving performance and using technology to execute work efficiently.

Quick Quiz: Match Scenario to Guiding Principle

Select the best guiding principle for this scenario.

A change manager wants to reduce failed changes. She proposes breaking large changes into smaller releases, each reviewed by users before the next one is planned. Which guiding principle is being applied?

  1. Start where you are
  2. Progress iteratively with feedback
  3. Keep it simple and practical
  4. Optimize and automate
Show Answer

Answer: B) Progress iteratively with feedback

The scenario clearly describes breaking work into smaller parts and using user review (feedback) between steps. This is **Progress iteratively with feedback**. It is not mainly about reusing the current state, simplifying, or using automation.

Quick Quiz: Distinguish Similar Principles

Choose the guiding principle that best fits the scenario, focusing on the keyword in the description.

An IT operations team has a 12-step incident logging form. Most fields are rarely used. They redesign it to include only the 4 fields needed to route and solve incidents quickly. Which principle is this MOST aligned with?

  1. Focus on value
  2. Keep it simple and practical
  3. Optimize and automate
  4. Collaborate and promote visibility
Show Answer

Answer: B) Keep it simple and practical

The key action is reducing the number of steps and fields to the minimum needed. This is **Keep it simple and practical**. While it may also support value, the main emphasis is on simplicity, not on automation or collaboration.

Flashcards: Seven ITIL 4 Guiding Principles

Use these flashcards to memorize the official names and short definitions of each guiding principle.

Focus on value
Always identify, understand, and focus on value for the customer and other stakeholders in everything the organization does.
Start where you are
Do not start from scratch and build something new without first considering what is already available.
Progress iteratively with feedback
Organize work into smaller, manageable sections that can be executed and completed in a timely manner, and use feedback before, during, and after each iteration.
Collaborate and promote visibility
Work together across boundaries to create value, and ensure that information is visible and understandable to those who need it.
Think and work holistically
Recognize that outcomes are delivered through the effective management and integration of information, technology, organization, people, practices, partners, and processes.
Keep it simple and practical
Always use the minimum number of steps needed to accomplish an objective, and eliminate anything that does not contribute to value.
Optimize and automate
Make something as effective and useful as it needs to be, then use technology to achieve what it is capable of.

Key Terms

Value
The perceived benefits, usefulness, and importance of something, usually defined by the customer and other stakeholders.
Holistic
Considering the whole system, including all parts and their interactions, rather than focusing on individual components in isolation.
Iteration
A small, repeatable cycle of work that produces a partial but usable result, allowing feedback and learning before the next cycle.
Automation
The use of technology to perform tasks with little or no human intervention, especially repetitive or predictable activities.
Optimization
Making something as effective, efficient, and useful as it needs to be by improving its design or operation.
Guiding principle
A recommendation that guides an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.
Service Value System (SVS)
The model in ITIL 4 that describes how all components and activities of an organization work together as a system to enable value creation.

Finished reading?

Test your understanding with a custom practice exam on this chapter.

Test yourself