SkarpChapter 12 of 19
Guiding Principles I: Focus on Value, Start Where You Are, Progress Iteratively with Feedback
Turn ITIL’s first three guiding principles into practical decision filters by applying them to realistic product and service scenarios and common exam traps.
Why Guiding Principles Matter in the SVS
Guiding Principles in the SVS
In ITIL 4, guiding principles are general recommendations that guide an organization in all circumstances, regardless of changes in goals, strategies, work type, or structure.
Decision Filters
In this module we turn three principles into daily decision filters: focus on value, start where you are, and progress iteratively with feedback.
Link to the SVS
These principles sit inside the service value system, shaping how the service value chain and continual improvement actually work in practice.
Exam and Real Life
You will learn to recognize actions that align or conflict with each principle, so you can answer scenario questions and make better real-world decisions.
Guiding Principles as Everyday Filters
Principles as Filters
Treat guiding principles as filters you pass decisions through before acting, shaping how you think rather than prescribing detailed steps.
Where They Sit
They live inside the service value system, influencing every part of the service value chain and continual improvement activities.
Policies vs Practices vs Principles
Policies say what we must do, practices say how we usually do it, and guiding principles say how we should think while doing it.
Exam Angle
Exam questions often give a scenario and ask which response best reflects a specific guiding principle, even if several answers look reasonable.
Focus on Value: What It Really Means
Central Idea
Focus on value means every decision and activity should be justified by how it contributes to value co-creation with stakeholders.
Service and Co-creation
A service enables value co-creation by helping customers achieve outcomes without managing specific costs and risks themselves.
Stakeholder View
To focus on value, know who your customers, users, and sponsors are, and what outcomes, experiences, risks, and costs matter to them.
Practical Consequences
In decisions, avoid work that is merely technically interesting; prioritize changes that improve real outcomes and experiences for stakeholders.
Focus on Value: Product and Exam Scenarios
Service Offering Context
Your organization offers an online learning service offering to universities. Stakeholders include customers, users, and sponsors.
Scenario A: Tech vs Value
Team wants a six‑month front-end rewrite, but students value reliability and offline access. Focusing on value means prioritizing those outcomes first.
Scenario B: Exam-style
Four options are given. The one that starts with surveying users and prioritizing their issues best reflects focus on value.
Typical Trap
Beware of answers that emphasize new tools or efficiency but never connect to stakeholder outcomes or experiences.
Start Where You Are: Avoiding Waste and Blind Spots
Core Idea
Start where you are means understand and reuse what already works instead of assuming you must start from a blank slate.
Objective Assessment
Assess the current state objectively using data and observation, avoiding assumptions that everything is either broken or perfect.
Reuse Capabilities
Look for existing tools, processes, skills, and relationships you can reuse or adapt instead of replacing them automatically.
Exam Clue
Good options mention reviewing current practices and evidence before big changes; bad ones rush to total replacement without analysis.
Start Where You Are: Service Improvement Scenarios
Scenario C: Service Desk
Complaints about slow resolution lead a manager to want a new tool. Starting where you are means first analyzing current data and usage.
Improvement Steps
You would review incident records, observe workflows, and improve configuration and training before deciding to replace the tool.
Scenario D: Exam-style
For change management, the best option maps and analyzes the current workflow before deciding which parts to keep or modify.
Key Trap
Beware of answers that rush to new tools or processes and dismiss existing ones without any objective assessment.
Progress Iteratively with Feedback: Reducing Risk, Increasing Learning
Core Idea
Progress iteratively with feedback means break work into small steps and use feedback after each step to guide what you do next.
Small Steps
Avoid big-bang projects. Deliver something useful early, then extend or adjust based on what you learn.
Feedback Loops
Gather regular feedback from customers, users, and internal stakeholders using both qualitative input and quantitative metrics.
Exam Signals
Look for words like "pilot", "phased rollout", "iteration", and "review"; avoid answers that rely on a single huge delivery with no feedback.
Progress Iteratively with Feedback: Release and Improvement Scenarios
Scenario E: App Feature
You release a minimal dashboard, gather usage and review data, then refine and extend based on what real users say and do.
Iteration Pattern
Each cycle delivers some value, collects feedback, and informs the next cycle, reducing risk and waste.
Scenario F: Exam-style
The best option pilots a simplified practice in one department, reviews results, adjusts, and then extends it.
Key Trap
Be careful: splitting work into phases is not enough. True iteration requires feedback and adaptation between steps.
Thought Exercise: Combining the Three Principles
Apply all three principles together to a mini case. Read carefully, then answer the reflection prompts.
Case: Your university's IT department is replacing a manual room-booking process with an online booking service for students and staff.
Current situation:
- Students email a central office to book rooms; response times are slow.
- There is an old internal calendar system that already tracks room availability but is used only by staff.
- Leadership wants a "modern" web and mobile app.
Questions to think through (you can jot notes):
- Focus on value
- Who are the key stakeholders? What does "value" look like for them in this context?
- Which outcomes matter more: fancy UI, fast confirmations, fair allocation, integration with timetables?
- Start where you are
- What existing assets or capabilities could you reuse (tools, data, knowledge)?
- What information would you gather about the current calendar system before deciding to replace it?
- Progress iteratively with feedback
- What could be a first small release that still delivers real value?
- How would you collect feedback after that first release, and from whom?
Take 3–4 minutes to outline:
- One decision that clearly aligns with all three principles
- One decision that would violate at least one principle (and which one)
You will see similar multi-principle scenarios in higher-difficulty questions and later mock exams.
Quiz 1: Focus on Value vs Internal Convenience
Check your understanding of "focus on value" in a realistic scenario.
A service provider is planning improvements to its customer support portal. Which action BEST demonstrates the guiding principle "focus on value"?
- Upgrade the underlying database technology to the latest version to reduce technical debt.
- Redesign the portal interface based only on the preferences of the internal development team.
- Interview customers and analyze support tickets to identify the most common problems, then prioritize portal changes that help customers resolve those problems faster.
- Standardize internal coding practices for all future portal changes.
Show Answer
Answer: C) Interview customers and analyze support tickets to identify the most common problems, then prioritize portal changes that help customers resolve those problems faster.
Option 3 is correct because it starts from customer needs and outcomes (faster problem resolution) and uses those to prioritize improvements. The other options may be useful internally, but they do not clearly connect to stakeholder-defined value.
Quiz 2: Start Where You Are and Progress Iteratively
Test your ability to distinguish between two guiding principles in a change scenario.
A hospital wants to improve its incident management practice. Which option BEST combines "start where you are" and "progress iteratively with feedback"?
- Replace the current incident tool immediately and deploy a completely new process to all departments at once.
- Analyze existing incident records and workflows in one department, design small improvements, pilot them in that department, review the results, then extend or adjust the improvements for other departments.
- Stop using the current incident process and allow each department to create its own approach independently.
- Hire a vendor to design a future-state process and implement it fully without involving current staff.
Show Answer
Answer: B) Analyze existing incident records and workflows in one department, design small improvements, pilot them in that department, review the results, then extend or adjust the improvements for other departments.
Option 2 is correct. It begins by analyzing the current state (start where you are), then pilots small improvements and reviews results before extending (progress iteratively with feedback). The other options either ignore the current state, lack iteration and feedback, or fragment practices.
Key Principle Check: Flashcards
Use these flashcards to reinforce the three guiding principles and related core ideas. Try to recall the answer before flipping each card.
- Guiding principles in ITIL 4 are best described as:
- General recommendations that guide an organization in all circumstances, regardless of changes in goals, strategies, work type, or management structure.
- What question should you always ask when applying "focus on value"?
- "Who receives value from this activity, and how does it improve their outcomes or experience?"
- Name two stakeholder roles and their ITIL definitions that are central to understanding value.
- Customer: "A person who defines the requirements for a service and takes responsibility for the outcomes of service consumption." User: "A person who uses services."
- What is the main risk of ignoring the principle "start where you are"?
- You may waste resources by discarding useful existing capabilities and make changes without understanding the current state, increasing risk and cost.
- Give one practical behavior that reflects "start where you are".
- Before replacing a tool or process, review current data and workflows to see what already works and can be reused or improved.
- Summarize "progress iteratively with feedback" in one sentence.
- Break work into small steps, deliver value early, and use feedback from each step to guide what you do next.
- How does "progress iteratively with feedback" support continual improvement?
- It creates recurring cycles of delivering, measuring, and learning, which is exactly how continual improvement keeps performance aligned with stakeholder expectations.
- Which principle are you applying when you pilot a new feature with a small group of users before a full rollout?
- "Progress iteratively with feedback" – you are using a small iteration and feedback from a limited group to guide further rollout.
- Which principle warns against assuming that all existing practices are useless?
- "Start where you are" – it emphasizes objective assessment and reuse of existing strengths.
- Which principle is violated if a team chooses a solution because it is "cool technology" without consulting users?
- "Focus on value" – they are prioritizing technology preferences over stakeholder outcomes.
Pulling It Together and Next Steps in Your Path
Three Filters
Focus on value, start where you are, and progress iteratively with feedback are mental filters for everyday decisions and exam scenarios.
SVS Connection
They shape how the service value chain operates and how continual improvement is performed at all levels of the organization.
Exam Strategy
Use keywords and clues about value, current state, or iteration to identify which principle a question is really testing.
Your Skarp Path
Upcoming diagnostics, mock exams, and spaced reviews will keep surfacing these principles until you can apply them automatically.
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.
- guiding principle
- A general recommendation that guides an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.
- 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.