SkarpChapter 12 of 20
The Seven ITIL Guiding Principles: From Focus on Value to Optimize and Automate
Walk through each guiding principle in turn, using realistic scenarios to see how they shape decisions and behaviors across the Service Value System.
Orienting Yourself: Guiding Principles in the Service Value System
Guiding Principles in Context
In ITIL Foundation (Version 5), the service value system shows how all components and activities work together to enable value creation. Guiding principles sit at the top and influence every decision.
Definition Reminder
A service value system is: "A model representing how all the components and activities of an organization work together as a system to enable value creation." Guiding principles shape how that system behaves.
The Canonical Seven
You must know the seven guiding principles in order: 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.
Where They Apply
These principles apply across all six service value chain activities and across exam domains like The ITIL Service Value System and Value stream identification, mapping, and management.
Guiding Principle 1: Focus on Value
What Does Focus on Value Mean?
Focus on value says: every activity should be justified by the value it creates or protects for stakeholders. If it does not contribute to value, question why it exists.
Value Is Co-Created
Value co-creation is "The joint activities performed by a service provider and a service consumer to create value." You must understand what outcomes customers and users care about.
Utility and Warranty
Value depends on utility (functionality to meet a need) and warranty (assurance requirements are met). Focus on value balances both: does it do the right thing, and do it reliably enough?
Exam Hint
In scenario questions, the best option often references stakeholder outcomes or value co-creation, not just internal efficiency or technology for its own sake.
Focus on Value: Scenarios and Exam Traps
Scenario: Reporting Overload
A 40-page monthly report is barely read. A manager suggests a 2-page dashboard with only metrics tied to customer satisfaction and business outcomes. This is clear focus on value.
Exam Trap: More Detail ≠ More Value
On the exam, options that keep huge reports "for completeness" often conflict with focus on value if stakeholders do not use them for decisions.
Scenario: Shiny Chatbot
A team wants an AI chatbot because it is trendy, but cannot state which user problems it will solve. A value-focused answer is to clarify stakeholder needs and target outcomes before building.
Scenario: Security vs Convenience
Multi-factor authentication may add friction but protects value by reducing risk. A value-focused approach balances risk reduction with user experience, not ignoring either side.
Guiding Principle 2: Start Where You Are
What Start Where You Are Means
Start where you are says: understand and use what already exists before you design something new. Do not throw away current capabilities without evidence.
Assess Objectively
Avoid "everything is broken" or "everything is perfect" thinking. Use data, observation, and stakeholder input to assess the current state realistically.
Reuse and Adapt
Look for ways to reuse and adapt existing services, tools, and skills. This saves time and reduces risk compared to always starting from scratch.
Exam Signal Phrases
Options like "review existing data", "assess the current process", or "leverage current tools" usually reflect start where you are in exam questions.
Start Where You Are: Scenarios and Misconceptions
Scenario: Service Desk Modernization
Managers want to throw away the current service desk and buy a new tool. An analyst proposes mapping current workflows and reusing what works. That analyst follows start where you are.
Scenario: Cloud Migration
Rather than rewriting all systems, a team first understands current architecture, then decides which apps to lift-and-shift and which to redesign. That is start where you are.
Scenario: Monitoring
Before buying a new observability platform, a team reviews existing logs and dashboards to identify gaps. This uses current capabilities as a baseline.
Misconceptions
Start where you are does not mean keep everything or delay change. It means base change on a realistic understanding of the present situation.
Guiding Principle 3: Progress Iteratively with Feedback
Iterative Progress
Progress iteratively with feedback means breaking work into small steps, delivering something usable, collecting feedback, and adjusting before the next step.
Small and Safe
Small, safe steps reduce risk. Each iteration is limited in scope, so failures are easier to detect and correct without major damage.
Link to Continual Improvement
Continual improvement is "a recurring activity" to keep performance meeting expectations. Progress iteratively with feedback is a key way to perform that recurring activity.
Exam Clues
Options mentioning pilots, early delivery, feedback loops, and avoiding big-bang releases usually reflect this principle.
Progress Iteratively with Feedback: Scenarios
Scenario: Self-Service Portal
Instead of building every feature and launching after a year, a team launches a portal with the top 5 request types, then expands based on feedback. That is progress iteratively with feedback.
Scenario: Process Improvement
Rather than redesigning the entire incident process, a team fixes major incident communication first, tests it, then refines and extends. Small steps plus learning.
Exam Pattern
Given a choice between big-bang design and a pilot on a high-impact area with feedback, the iterative pilot option almost always aligns with this principle.
Signal Words
Words like pilot, prototype, incremental rollout, and regular reviews are strong clues that an option reflects progress iteratively with feedback.
The Remaining Four Principles: Overview and Quick Scenarios
Collaborate and Promote Visibility
This principle is about working together across teams and sharing information openly so people can make informed decisions. Think cross-functional reviews and shared dashboards.
Think and Work Holistically
See the service as a whole system, not isolated parts. Consider all four dimensions and the entire service value chain when you design or change something.
Keep It Simple and Practical
Remove steps, reports, or controls that do not add value. Aim for the minimum complexity needed to achieve outcomes and manage risk.
Optimize and Automate
First optimize by streamlining and standardizing workflows. Then automate repetitive, well-understood tasks using technology, including AI where it makes sense.
Thought Exercise: Matching Principles to Actions
Use this step to actively apply what you have learned. For each mini-scenario, pause and decide which guiding principle is most clearly illustrated.
- Mini-scenario A
- A product team invites customer support, security, and finance to a workshop to design a new subscription feature. They share user research, incident data, and revenue forecasts on a shared board so everyone can see the same information.
- Which principle is primary? (Hint: cross-team work + shared information.)
- Mini-scenario B
- Before automating change approvals, a team maps the current change workflow, removes duplicate checks, and clarifies decision criteria. Only then do they configure automation in their change tool.
- Which principle is primary? (Hint: streamline first, then use technology.)
- Mini-scenario C
- A service owner wants a new monthly report. An analyst asks, "What decisions will this report support?" and designs a one-page summary focused only on those decisions.
- Which principle is primary? (Hint: value and simplicity both appear, but which is strongest?)
- Mini-scenario D
- Instead of launching a completely new incident classification scheme across the whole organization, a team tests it with one service, gathers feedback from analysts, and adjusts categories before wider rollout.
- Which principle is primary? (Hint: small steps with learning.)
Write down your answers, then check yourself:
- A: collaborate and promote visibility
- B: optimize and automate
- C: Most strongly focus on value, with support from keep it simple and practical
- D: progress iteratively with feedback
If you mis-matched any, quickly re-read the relevant principle description before moving on.
Quiz 1: Identify the Principle
Choose the best matching guiding principle for this scenario.
An organization wants to improve its incident management practice. The team decides to first analyze the existing process, identify what already works well, and then design improvements that build on those strengths instead of starting from scratch. Which guiding principle is MOST clearly demonstrated?
- focus on value
- start where you are
- keep it simple and practical
- progress iteratively with feedback
Show Answer
Answer: B) start where you are
The key phrase is "analyze the existing process" and "build on those strengths instead of starting from scratch." This directly reflects **start where you are**. Focus on value and keep it simple and practical are relevant to almost any improvement, but the scenario emphasizes reusing and understanding the current state, which is the core of this principle. Progress iteratively with feedback would mention small steps and feedback loops, which are not highlighted here.
Quiz 2: Best Next Action
Select the BEST next action according to the guiding principles.
A university IT department is introducing a new online exam system. They have limited time before the next exam period. What is the BEST approach in line with ITIL guiding principles?
- Design the full end-to-end system for all departments, launch it to every course at once, and gather feedback after the first exam session.
- Run a pilot with a small number of courses, gather feedback from students and lecturers, refine the system, and then expand to more courses.
- Wait until they can design a perfect system that meets every requirement, even if this delays the rollout by a year.
- Replace all existing exam-related tools immediately to avoid confusion, then design processes after the new system is live.
Show Answer
Answer: B) Run a pilot with a small number of courses, gather feedback from students and lecturers, refine the system, and then expand to more courses.
Option B reflects **progress iteratively with feedback**: a pilot, feedback, refinement, then expansion. Option A is a big-bang rollout with feedback only at the end, increasing risk. Option C delays value and ignores time constraints. Option D is reckless, replacing tools without clear processes or feedback.
Flashcards: The Seven Guiding Principles in Order
Use these flashcards to lock in the names and order of the seven guiding principles.
- 1st ITIL guiding principle
- focus on value
- 2nd ITIL guiding principle
- start where you are
- 3rd ITIL guiding principle
- progress iteratively with feedback
- 4th ITIL guiding principle
- collaborate and promote visibility
- 5th ITIL guiding principle
- think and work holistically
- 6th ITIL guiding principle
- keep it simple and practical
- 7th ITIL guiding principle
- optimize and automate
- Which principle emphasizes stakeholder outcomes and value co-creation?
- focus on value
- Which principle tells you to understand and reuse existing capabilities before changing them?
- start where you are
- Which principle encourages small steps, pilots, and learning loops?
- progress iteratively with feedback
Mini Exam Drill: Applying the First Three Principles
Work through this short drill to practice exam-style reasoning with focus on value, start where you are, and progress iteratively with feedback.
Question 1
A hospital IT team needs to improve response times for critical incidents affecting patient care. Which action best reflects focus on value?
- A) Reorganize the team’s seating plan to improve internal communication.
- B) Prioritize improvements that reduce time to restore critical clinical systems, even if less critical systems wait longer.
- C) Replace the incident management tool with a newer cloud-based product.
- D) Document the incident process in more detail.
Think, then check: B is correct because it explicitly targets outcomes that matter most to stakeholders (patient safety and clinical operations).
Question 2
A bank wants to modernize its online banking platform. They already have extensive usage data and customer feedback from the current system. Which action best reflects start where you are?
- A) Ignore existing data and run only new focus groups.
- B) Analyze current usage and feedback to identify which features are most valued, then design the new platform around those.
- C) Immediately decommission the old platform.
- D) Delay any analysis until the new design is finished.
Correct answer: B. It explicitly uses the existing situation as a foundation.
Question 3
A university wants to introduce a new timetable app. Which action best reflects progress iteratively with feedback?
- A) Launch the full app to all students at once.
- B) Design every feature in detail before any coding starts.
- C) Release a basic version to one faculty, collect student feedback, and add features over time.
- D) Wait until the app is perfect before showing it to users.
Correct answer: C. It uses small steps and feedback.
If any of your answers differed, revisit the three principles and note exactly which words in each question pointed to the right choice.
Key Terms
- user
- A person who uses services.
- service
- A means of enabling value co-creation by facilitating outcomes that customers want to achieve, without the customer having to manage specific costs and risks.
- sponsor
- A person who authorizes budget for service consumption.
- utility
- The functionality offered by a product or service to meet a particular need.
- customer
- A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption.
- warranty
- Assurance that a product or service will meet agreed requirements.
- service offering
- A description of one or more services, designed to address the needs of a target consumer group.
- value co-creation
- The joint activities performed by a service provider and a service consumer to create value.
- service management
- A set of specialized organizational capabilities for enabling value for customers in the form of services.
- service value chain
- A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization.
- service value system
- A model representing how all the components and activities of an organization work together as a system to enable value creation.
- continual improvement
- A recurring activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.
- seven guiding principles
- The ITIL guiding principles, in order: focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; optimize and automate.