Overview
Learning outcome 2 carries 6 marks and has two assessment criteria. Criterion 2.1, worth one mark, asks you to describe the nature, use and interaction of the guiding principles. Criterion 2.2, worth five marks, asks you to explain the use of each principle: focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; and optimize and automate.
A guiding principle is a recommendation that guides an organization in all circumstances, regardless of changes in its goals, strategies, type of work or management structure. The principles are universal and enduring, and they are one of the five components of the service value system. They are not steps in a sequence. Several usually apply to a single decision, and the organization chooses which matter most in its context.
How it's tested
Expect one question on the nature or interaction of the principles and five that test individual principles. Most give a short workplace scenario and ask which principle is being applied, which advice a principle gives, or which action best fits a named principle. Negative questions, asking which statement is not guidance from a principle, also appear.
-
Name the principle
A team's behaviour is described, such as releasing a small change and gathering user reactions, and you choose the principle it shows.
-
Principle advice
A principle is named and you choose the recommendation that belongs to it, for example assessing the current state before planning.
-
Interaction statement
You choose the correct statement about how principles relate, such as that they should be considered together and adapted to context.
A stem says a manager wants to replace a ticketing tool but first asks staff which current workflows work well and measures them directly. The options include start where you are and optimize and automate. The manager is not automating anything yet. Reviewing and measuring what already exists before deciding what to keep is the core guidance of start where you are, so that is the answer.
Assessment criteria 2
Official assessment criteria from the PeopleCert outline, in outline order.
2.1 Describe the nature, use and interaction of the guiding principlesWhat a guiding principle is, why the set is universal, and how the principles combine.
- What it means
- Guiding principles are recommendations that apply to an organization in every situation, regardless of its goals, strategy, kind of work or structure. They encourage and support continual improvement at every level and help people make good decisions without detailed rules. They are not a process and do not prescribe steps.
- What to understand
- The principles interact and depend on each other. For example, progressing iteratively needs feedback, which relies on visibility and collaboration, and optimizing a workflow needs a holistic view of how it fits. Not every principle is equally relevant to every decision, so the organization reviews them together and applies those that matter in context. The principles also echo ideas in Agile, DevOps, Lean and other frameworks, which is why ITIL presents them as a shared set rather than ITIL-only rules.
- How it shows up
- One mark, usually a statement-based question about how principles should be used together.
- Common confusion
- Thinking the principles must be applied in the order listed, or that only one may be used at a time.
2.2 Explain the use of the guiding principlesThe specific guidance attached to each of the seven principles.
- What it means
- Focus on value means knowing who is served, understanding value from the consumer's perspective, and attending to customer and user experience. Start where you are means assessing what already exists, measuring it directly, and reusing what works. Progress iteratively with feedback means splitting work into smaller pieces and using feedback loops. Collaborate and promote visibility means involving the right people and making work visible. Think and work holistically means seeing end-to-end work and its interactions. Keep it simple and practical means using the minimum steps needed. Optimize and automate means improving work before automating it and reserving human effort for where it adds value.
- What to understand
- Learn two or three pieces of guidance for each principle. Start where you are warns against building from scratch without checking existing assets and prefers direct observation over reports. Progress iteratively notes that fast does not mean incomplete and that each iteration should be reassessed. Collaborate and promote visibility warns that hidden work leads to poor decisions and stresses communicating in ways each audience hears. Keep it simple and practical advises removing anything that does not add value and designing rules for the normal case, not every exception. Optimize and automate advises standardizing and simplifying first, then automating, and using metrics to judge the result.
- How it shows up
- Five marks of scenario questions: which principle is shown, or which advice belongs to a named principle.
- Common confusion
- Choosing optimize and automate whenever a scenario mentions tools; automating a broken process breaks the advice to optimize first.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Guiding principle
A recommendation that guides an organization in all circumstances.
- Remember
- Universal and enduring, regardless of goals or structure.
- Tested as
- Criterion 2.1 nature question.
- Trap
- Describing principles as mandatory process steps.
-
Focus on value
Everything should link back to value for stakeholders.
- Remember
- Identify the consumer first, then their view of value.
- Tested as
- Scenarios about understanding who benefits.
- Trap
- Taking the provider's view of value.
-
Start where you are
Assess and reuse what exists before building new.
- Remember
- Measure directly; do not rely only on reports.
- Tested as
- Scenarios about replacing tools or processes.
- Trap
- Picking it for any scenario about the current state, even when the point is iteration.
-
Progress iteratively with feedback
Work in small, manageable pieces with feedback loops.
- Remember
- Fast does not mean incomplete.
- Tested as
- Scenarios with pilots, small releases or minimum viable products.
- Trap
- Confusing feedback loops with collaboration.
-
Collaborate and promote visibility
Involve the right people and make work and decisions visible.
- Remember
- Hidden agendas and invisible work undermine improvement.
- Tested as
- Scenarios about stakeholders, dashboards or transparency.
- Trap
- Choosing think holistically whenever other teams are mentioned.
-
Think and work holistically
No service or practice stands alone; consider the end-to-end system.
- Remember
- Look at how parts interact across the four dimensions.
- Tested as
- Scenarios where local fixes harm another area.
- Trap
- Treating it as the same as collaboration.
-
Keep it simple and practical
Use the minimum steps needed to achieve the objective.
- Remember
- If something adds no value, remove it.
- Tested as
- Scenarios about eliminating steps or over-designed processes.
- Trap
- Selecting optimize and automate when nothing is automated.
-
Optimize and automate
Make work as effective and useful as possible, then automate where sensible.
- Remember
- Optimize before you automate.
- Tested as
- Scenarios involving tools, bots or scripted workflows.
- Trap
- Automating a process before simplifying it.
-
Principle interaction
Principles depend on one another and are considered together.
- Remember
- Not all principles apply equally to every decision.
- Tested as
- Criterion 2.1 statements.
- Trap
- Assuming principles are ranked or sequential.
-
Outcome-based thinking
Part of keep it simple and practical: design for the outcome, not the activity.
- Remember
- Rules for exceptions add complexity; design for the normal case.
- Tested as
- Advice questions on simplification.
- Trap
- Writing rules for every possible exception.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Principles that are often confused
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Keep it simple and practical | Remove steps that add no value | About reducing complexity | Chosen for automation scenarios |
| Optimize and automate | Improve, then automate repetitive work | Automation follows optimization | Chosen when nothing is being automated |
| Collaborate and promote visibility | Bring in people and make work visible | About people and transparency | Swapped with holistic thinking |
| Think and work holistically | See the end-to-end system and interactions | About the whole system, not just the people | Swapped with collaboration |
Starting points and pace
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Start where you are | Use what already exists as the base | Concerns the starting position | Confused with iteration |
| Progress iteratively with feedback | Move in small steps and learn from each | Concerns how you move forward | Confused with starting over |
| Focus on value | Tie every step to stakeholder value | Concerns why work is done | Ignoring the consumer's view |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Automation keyword
- What candidates pick
- Optimize and automate for every scenario that mentions a tool.
- Why it looks right
- The word automation is in the principle's name.
- Why it's wrong
- If the scenario is about removing unnecessary steps, the principle is keep it simple and practical, with no automation involved.
Clue to watch for Check whether anything is actually being automated.
-
Start from scratch
- What candidates pick
- An option recommending a clean redesign with no reference to current processes.
- Why it looks right
- A fresh start sounds bold and modern.
- Why it's wrong
- Start where you are advises reviewing and reusing existing services and processes before discarding them.
Clue to watch for Answer options that ignore what already exists.
-
Speed equals incomplete
- What candidates pick
- An option claiming iterative work delivers partial, low-quality results.
- Why it looks right
- Small releases can feel unfinished.
- Why it's wrong
- The principle states that fast does not mean incomplete; each iteration should deliver something useful.
Clue to watch for Statements questioning the quality of iterations.
-
Collaboration means consensus
- What candidates pick
- An option saying everyone must agree before work proceeds.
- Why it looks right
- Collaboration sounds like agreement.
- Why it's wrong
- The principle is about involving the right people and visibility, not requiring full consensus.
Clue to watch for Words like unanimous or everyone must approve.
-
Principles in order
- What candidates pick
- An option saying the principles are applied one after another.
- Why it looks right
- They are always listed in the same order.
- Why it's wrong
- The principles interact and should be considered together, with relevance depending on the situation.
Clue to watch for Criterion 2.1 statements about sequence.
-
Provider view of value
- What candidates pick
- An answer defining value from the provider's internal metrics.
- Why it looks right
- Providers measure their own work easily.
- Why it's wrong
- Focus on value starts by identifying the consumer and understanding value from their perspective.
Clue to watch for Options mentioning internal efficiency only.
Answer framework
When a stem asks which guiding principle applies, test the options in this order.
- Identify what the person in the scenario is actually doing, ignoring buzzwords such as automation or collaboration.
- Ask whether the action is about understanding value for a consumer, reusing the current state, or moving in small steps with feedback.
- If other people or teams are involved, decide whether the point is involving and informing them, or seeing how the whole system fits together.
- If waste is being cut, check whether steps are simply removed, which is keep it simple, or optimized and then automated.
- Eliminate options whose specific guidance does not match, and choose the principle whose advice describes the action most directly.
Practice question
Want more like this? The ITIL 4 Foundation practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Learn the seven names first, then attach two specific pieces of guidance to each. A simple table with columns for the principle, its key advice, and a workplace example is enough. Make the examples your own, such as a pilot release for iteration or a shared progress board for visibility, because the exam describes behaviour rather than quoting the principle name.
Then practise discrimination. The most common errors come from four pairs: keep it simple versus optimize and automate, collaborate versus holistic, start where you are versus iterate, and focus on value versus everything else. Write one scenario that fits only the first principle of each pair and one that fits only the second, and explain to yourself what made the difference.
Finish with a mixed set of scenario questions and read every option. When two seem right, ask which principle's specific advice the scenario describes, not which sounds most general. Budget four to five hours, and review this outcome again with continual improvement, since the improvement model applies several principles.
FAQ
How many questions come from The ITIL Guiding Principles?
The ITIL Guiding Principles, learning outcome 2, carries 6 marks, which is 15% of the 40-question paper: one on the nature and interaction of the principles and five on applying them.
Do I need to memorise the principles in order?
Knowing the list helps recall, but the exam does not test order. It tests whether you can recognise each principle in a scenario and know the guidance attached to it.
Which principles are confused most often?
Keep it simple and practical with optimize and automate, and collaborate and promote visibility with think and work holistically. Learn the specific advice under each to separate them.
Are the guiding principles the same in ITIL (Version 5)?
Yes. Version 5 keeps the same seven principles, so this material transfers if you later move to the newer scheme.
Is there a principle about customers specifically?
Focus on value covers it: identify the service consumer, understand their view of value, and pay attention to customer and user experience.
Can more than one principle apply to a scenario?
Often, yes. The exam asks for the one that applies most directly, so pick the principle whose specific guidance matches the described action.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 2 knowledge
Try scenario questions that test whether you can pick the most direct principle, especially for the commonly confused pairs.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the ITIL 4 Foundation AI tutor Get any concept explained your way