ITIL Foundation The Seven Guiding Principles Syllabus

What are good sources of feedback under 'Progress iteratively with feedback'?

User and customer reaction to new/changed services, feedback from customers and users, results and response to marketing campaigns, internal process measurement, and feedback during/after change initiatives.

How do iteration and feedback combine to manage risk?

Working iteratively with feedback lets you respond to changing needs, fail fast and learn, and avoid wasted effort—each iteration is re-evaluated against goals based on the feedback received.

Define the guiding principle 'Collaborate and promote visibility'.

Work that includes the right people in the right roles, and that is made visible, gets better buy-in, more relevance, and greater long-term success than work done in silos with poor information sharing.

Under 'Collaborate and promote visibility', why is whom you collaborate with important?

Identifying and managing the right stakeholders and contributors improves the quality of outcomes and increases buy-in and relevance; the right people in the right roles drive success.

What problem does promoting visibility solve, according to ITIL 4?

Insufficient visibility of work leads to poor decision-making, which jeopardises improvements; if work and its consequences are hidden, prioritisation and resourcing suffer.

What is the risk of treating service management work as having little or no demand if it is not visible?

If work is not visible, it may be wrongly perceived as low priority and starved of resources; promoting visibility ensures work is recognised and properly prioritised.

Name some stakeholder groups to consider when applying 'Collaborate and promote visibility'.

Customers, users, sponsors, internal/external suppliers, the development team, relationship managers, service providers, and others contributing to or affected by the service.

Define the guiding principle 'Think and work holistically'.

No service, practice, process, department, or supplier stands alone. The organisation and its outputs should be understood and managed as a whole, with all activities directed toward delivering value.

What does 'Think and work holistically' say about the four dimensions of service management?

All four dimensions—organisations and people, information and technology, partners and suppliers, and value streams and processes—must be coordinated, since an integrated, holistic approach is needed to deliver value.

What happens if you fail to think and work holistically?

Working on elements in isolation produces a degraded result; complexity is best managed by understanding how all parts work together as a system to deliver value.

How does complexity relate to the principle 'Think and work holistically'?

Most services and systems are complex; recognising the relationships and interactions between components, and the impact of any change on the whole, is essential to delivering value.

Define the guiding principle 'Keep it simple and practical'.

If a process, service, action, or metric provides no value or produces no useful outcome, eliminate it. Use the minimum number of steps to accomplish an objective; outcome-based thinking produces practical solutions.

What does 'Keep it simple and practical' recommend about the number of steps in a process?

Always use the minimum number of steps necessary to accomplish the objective(s); avoid unnecessary complexity.

What trade-off does 'Keep it simple and practical' acknowledge about exceptions?

Designing for every exception adds complexity; it is often better to handle exceptions in a different way, since trying to cater for every case rarely adds proportional value (judgement and conflicting objectives must be balanced).

Why can over-engineering conflict with 'Keep it simple and practical'?

Adding controls or metrics that do not produce useful outputs creates waste and complexity; simplicity ensures effort is focused only on what produces value.

Define the guiding principle 'Optimise and automate'.

Resources of all types, particularly human resources, should be used to their best effect. Eliminate anything truly wasteful and use technology to achieve whatever it is capable of; human intervention should only happen where it really contributes value.

According to ITIL 4, what should you do BEFORE you automate?

Optimise first—simplify and improve the work to make it as effective as possible—because automating an inefficient or non-optimised process can magnify its flaws.

What is the relationship between 'optimise' and 'automate' in the principle 'Optimise and automate'?

Optimisation makes something as effective and useful as possible; automation then typically uses technology to perform a step or steps without human intervention. Optimise before automating.

What is the recommended path to optimisation in 'Optimise and automate'?

Understand and agree the context (vision and current state), assess where it can be optimised, agree future state and priorities, ensure appropriate engagement and commitment, execute improvements iteratively, and continually monitor.

What is the role of human intervention under 'Optimise and automate'?

Human intervention should only happen where it truly contributes value; otherwise, technology should be used so that people are freed for more complex decision-making and creative work.

Why should automation focus on frequent and repetitive tasks?

Automating standardised, repetitive, high-volume tasks frees human resources for more complex activities and reduces error, giving the best return on the use of technology.

Compare 'Focus on value' and 'Keep it simple and practical': how do they reinforce each other?

Both eliminate waste: 'Focus on value' ensures every activity links to stakeholder value, while 'Keep it simple and practical' removes steps and metrics that produce no useful outcome—together they cut out non-value-adding work.

Compare 'Start where you are' and 'Progress iteratively with feedback'.

'Start where you are' assesses and reuses the current state as a baseline; 'Progress iteratively with feedback' then improves from that baseline in small steps, re-evaluating each iteration with feedback rather than rebuilding everything at once.

How do 'Collaborate and promote visibility' and 'Think and work holistically' complement each other?

Collaboration brings the right people and information together and makes work visible; holistic thinking ensures those collaborations are coordinated across all four dimensions and value streams so the whole system delivers value.

What is a common pitfall when applying 'Progress iteratively' without the rest of the principles?

Iterations done in isolation (without holistic thinking and feedback) can drift from the overall goal; each iteration must be re-evaluated holistically and against value to remain aligned.

What does ITIL 4 mean by saying the guiding principles 'do not need to be adopted all at once'?

Organisations can review the principles and decide how relevant each is to their situation, applying them selectively and with appropriate balance rather than all equally in every case.

Under 'Focus on value', what does mapping value to the consumer involve at each step of the service?

Understanding exactly how the consumer uses the service and continually focusing on value at every interaction, so that both functional (utility) and experiential (warranty/CX) value are delivered.

What is the danger of skipping 'Start where you are' and discarding existing capabilities?

Valuable existing services, processes, people, and technology may be needlessly thrown away, wasting investment and effort; ITIL recommends assessing what can be reused before building new.

How does 'Optimise and automate' interact with 'Keep it simple and practical'?

Keeping things simple removes unnecessary steps so that what remains is worth optimising; then optimisation and automation maximise the effectiveness of the simplified work—simplify, optimise, then automate.

What overall purpose do the seven guiding principles serve within ITIL 4's service value system?

They provide universal guidance that helps an organisation adopt and adapt ITIL, supporting continual improvement and good decision-making at all levels, regardless of changes in goals or structure.

When balancing the principles, what determines which principle takes priority in a given decision?

The specific situation and context: an organisation reviews each principle's relevance, weighs them against the circumstances, and gives more weight to the principles most applicable to that decision.