The perceived benefits, usefulness, and importance of something. In ITIL 4, value is co-created by the service provider and consumers.

Considering the whole system, including all components and their interactions, rather than focusing only on individual parts.

A single cycle of work in an incremental approach, where a small part of the solution is delivered and then improved using feedback.

ITIL 4 Guiding Principles: Navigating Real-World Scenarios — ITIL 4 Foundation Exam Prep: Complete Syllabus, Exam-Focused

Q: A university IT department wants to reduce the time it takes to approve student software requests. First, they remove unnecessary approval steps and simplify the form. Only then do they add an automated workflow in the service portal. Which guiding principle is the BEST fit?

Optimize and automate. **Optimize and automate** is best because the scenario explicitly describes improving and streamlining the process (optimize) and then adding an automated workflow (automate). **Focus on value** is always relevant but is not the main idea here. **Keep it simple and practical** appears (simplifying the form), but the question highlights both optimization and automation together, which directly matches the wording of Optimize and automate.

Q: A team designing a new mobile app for students starts by interviewing students and academic staff to understand what outcomes they care about most. They drop several planned features that do not contribute to those outcomes. Which guiding principle is the BEST fit?

Focus on value. The scenario focuses on understanding what outcomes users and stakeholders care about and removing features that do not contribute to those outcomes. This is a direct application of **Focus on value**. Think and work holistically would emphasize understanding the whole system; here the emphasis is clearly on value and outcomes.

Big Picture: What Are the ITIL 4 Guiding Principles?

Your Decision-Making Compass

In ITIL 4, the seven guiding principles are a decision-making compass. They are universal recommendations that should influence every decision, change, and improvement.

The Seven Principles

The seven 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

They apply to any organization, any service, any situation. They reinforce each other, and exam questions often ask which principle best guides what to do next in a scenario.

What You Will Practice

You will learn exam-ready wording for each principle, practice matching them to scenarios, and learn to separate similar-sounding ones like Focus on value vs Optimize and automate.

Principles 1–3: Value, Reality, and Iteration

1. Focus on value

Idea: Everything you do should create value for customers, users, and the organization. Always ask: Value for whom? Value in what form? Avoid work that does not clearly support value.

Focus on value – Example

If a service desk adds many form fields that slow users down without real benefit, Focus on value says: do not add complexity that reduces user value.

2. Start where you are

Idea: Do not build from scratch. Assess the current state and use what is already available. Reuse existing processes, tools, and data that already work.

Start where you are – Example

Before buying a new ticketing tool, a team reviews and reuses working workflows from the current system instead of redesigning everything. That is Start where you are.

3. Progress iteratively with feedback

Idea: Do not try to do everything at once. Work in small, manageable steps and use feedback to guide each step. Break work into increments and adjust after each one.

Iterate – Example

IT upgrades Wi‑Fi one building at a time, collects user feedback, fixes issues, then moves on. That is Progress iteratively with feedback.

Principles 4–7: People, Whole System, Simplicity, and Automation

4. Collaborate and promote visibility

Idea: Work together across boundaries and make work and information visible. Avoid silos and use shared boards or tools so everyone can see progress and risks.

5. Think and work holistically

Idea: See the service as a whole system, not isolated parts. Understand how people, processes, technology, partners, and information interact before changing anything.

6. Keep it simple and practical

Idea: Use the minimum number of steps and controls needed to achieve the objective. Remove unnecessary activities and prefer practical, usable solutions.

7. Optimize and automate

Idea: Improve and streamline work before automating, then use technology for repetitive tasks. First optimize the process, then automate stable, well-understood steps.

Putting 4–7 Together

Remember these four as: work with people, see the whole, keep it simple, then optimize and automate. Together with the first three, they guide every ITIL decision.

Spot the Principle: Quick Thought Drills

Try these short thought exercises. Do not overthink; go with the principle that best fits the main idea.

Scenario A

An IT manager wants to redesign incident management. Before drawing any new process maps, she reviews existing incident data, current workflows, and what already works well.

Which principle is most central?
A. Start where you are
B. Progress iteratively with feedback
C. Optimize and automate

Scenario B

A team is rolling out a new online portal. They first release a basic version to a small group of students, gather feedback, improve it, then roll it out to the whole campus.

Which principle is most central?
A. Think and work holistically
B. Progress iteratively with feedback
C. Keep it simple and practical

Scenario C

The change manager invites representatives from support, security, networking, and business units to a weekly change review meeting. A shared dashboard shows all planned changes and their status.

Which principle is most central?
A. Collaborate and promote visibility
B. Focus on value
C. Optimize and automate

Check yourself (mentally):

Scenario A → Start where you are (using what exists).
Scenario B → Progress iteratively with feedback (small release, feedback, adjust).
Scenario C → Collaborate and promote visibility (joint work and shared view).

If you picked differently, ask: What is the main action or mindset in the scenario? That usually points to the right principle.

Quiz 1: Focus on Value vs Optimize and Automate

Test your ability to separate two commonly confused principles.

A university IT department wants to reduce the time it takes to approve student software requests. First, they remove unnecessary approval steps and simplify the form. Only then do they add an automated workflow in the service portal. Which guiding principle is the BEST fit?

Focus on value
Optimize and automate
Keep it simple and practical
Progress iteratively with feedback

Show Answer

Answer: B) Optimize and automate

**Optimize and automate** is best because the scenario explicitly describes improving and streamlining the process (optimize) and then adding an automated workflow (automate). **Focus on value** is always relevant but is not the main idea here. **Keep it simple and practical** appears (simplifying the form), but the question highlights both optimization and automation together, which directly matches the wording of Optimize and automate.

Quiz 2: Matching Principle to Scenario

Another quick check on principle recognition.

A team designing a new mobile app for students starts by interviewing students and academic staff to understand what outcomes they care about most. They drop several planned features that do not contribute to those outcomes. Which guiding principle is the BEST fit?

Focus on value
Think and work holistically
Collaborate and promote visibility
Start where you are

Show Answer

Answer: A) Focus on value

The scenario focuses on understanding what outcomes users and stakeholders care about and removing features that do not contribute to those outcomes. This is a direct application of **Focus on value**. Think and work holistically would emphasize understanding the whole system; here the emphasis is clearly on value and outcomes.

Putting Principles Together in a Realistic Case

Case: Student IT Support

A university receives many complaints about slow IT support. They launch an improvement effort. Watch how multiple guiding principles appear in the same real-world case.

Steps 1–2: Value and Reality

1) Interview students and staff to define good support → Focus on value. 2) Review current ticket data, tools, and workflows instead of starting blank → Start where you are.

Steps 3–4: Iterate and Collaborate

3) Fix the worst pain (password resets) first and pilot with one faculty → Progress iteratively with feedback. 4) Involve multiple teams and a student rep using a shared board → Collaborate and promote visibility.

Steps 5–7: Whole, Simple, Automated

5) Map the full support journey → Think and work holistically. 6) Remove duplicate approvals and questions → Keep it simple and practical. 7) Add a self-service reset portal → Optimize and automate.

Key Takeaway

All seven principles can appear in one initiative. Exam questions ask for the single best match, but real life often uses several principles together.

Flashcards: Exam-Ready Wording of Each Principle

Use these flashcards to lock in short, exam-friendly descriptions.

Focus on value: Everything the organization does should create value for customers, users, and the organization. Always ask: value for whom and in what form?
Start where you are: Do not build from scratch. Assess the current state and use what is already available before deciding what to change.
Progress iteratively with feedback: Do not try to do everything at once. Work in small, manageable steps and use feedback to guide each step.
Collaborate and promote visibility: Work together across boundaries and make work and information visible so people can make better decisions.
Think and work holistically: See the service and organization as a whole system. Understand how all parts interact, not just isolated pieces.
Keep it simple and practical: Use the minimum number of steps and controls necessary. Remove anything that does not help achieve the objective.
Optimize and automate: Improve and streamline work before automating. Then use technology to automate well-understood, repeatable tasks.

Exam-Style Drill: Distinguishing Similar Principles

For each pair, decide which principle fits better. Say your answer out loud or jot it down.

Focus on value vs Keep it simple and practical

Scenario: The team removes rarely used features from a service portal because they confuse users and do not support any key outcome.

Better fit?
Reason: The main idea is removing non-value-adding features, so Focus on value is usually the better match. Simplicity is a result, but value is the driver.

Start where you are vs Think and work holistically

Scenario: Before changing the VPN service, the team analyses how it affects remote workers, security policies, help desk calls, and network capacity.

Better fit?
Reason: This is about understanding the whole system, so Think and work holistically is the better match. Start where you are would focus more on reusing existing tools and data.

Progress iteratively with feedback vs Optimize and automate

Scenario: The team releases a basic chatbot for student FAQs, collects feedback for a month, then improves the bot’s answers and adds new topics.

Better fit?
Reason: The key behavior is small steps and feedback, so Progress iteratively with feedback is the best answer, even though automation is present.

Tip for the exam: When two principles seem to fit, ask “What is the main behavior or decision in this scenario?” Choose the principle that matches that behavior most directly.

Key Terms

Value: The perceived benefits, usefulness, and importance of something. In ITIL 4, value is co-created by the service provider and consumers.
Holistic: Considering the whole system, including all components and their interactions, rather than focusing only on individual parts.
Iteration: A single cycle of work in an incremental approach, where a small part of the solution is delivered and then improved using feedback.
Automation: The use of technology to perform tasks with little or no human intervention, typically for stable, repeatable activities.
Guiding principle: A recommendation that guides an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.