Guiding Principles

Overview

These seven principles serve as a compass for organizational decisions, applying across all contexts regardless of strategic changes or structural modifications.

The principles originated in ITIL Practitioner (2016), became central to ITIL 4, and remain emphasized in ITIL v5 with enhanced practical guidance. In this version, principles gain concrete applications through connections to AI, experience management, complexity, and integration themes.

Seven Guiding Principles

1. Focus on Value

Core concept: "Everything the organization does should link, directly or indirectly, to value for itself, customers, and stakeholders."

Key elements:

• Understanding whom you serve and their specific needs
• Recognizing that value manifests in multiple forms: productivity gains, risk reduction, cost savings, market expansion, or competitive advantage
• Acknowledging that value remains subjective and evolves over time

Application strategies:

• Ensure all staff comprehend how their work contributes to consumer outcomes
• Maintain value focus during routine operations and improvement initiatives
• Incorporate value consideration in each improvement phase
• Use AI for continuous data analysis and predictive modeling of customer needs

2. Start Where You Are

Core concept: "Do not start from zero without considering what already exists. Observe directly, measure, and build on the current foundation."

Rationale: Rebuilding from scratch wastes resources and loses existing capabilities. Direct observation often reveals more accurate information than management reports.

Application strategies:

• Objectively evaluate current state using customer needs as your reference point
• Identify and leverage existing successful practices
• Apply risk management thinking to both reused and new approaches
• Employ AI-driven analytics for rapid assessment of existing practices and historical performance

3. Progress Iteratively with Feedback

Core concept: "Do not try to do everything at once. Organize work into small, manageable parts with continuous feedback."

Understanding feedback: Iterative work requires continuous input from stakeholders regarding reactions and opinions. This enables teams to adjust focus based on changing circumstances and priorities.

Key definitions:

• Feedback: stakeholder reactions and opinions used for improvement
• Feedback loop: output from one activity becoming input for new work

Feedback mechanisms reveal:

• User and customer perceptions of value creation
• Efficiency and effectiveness of management activities
• Governance and control effectiveness
• Organization-supplier interfaces
• Shifting demand patterns

Application strategies:

• Balance comprehensive understanding with action (avoiding "analysis paralysis")
• Recognize continuous ecosystem changes
• Apply Minimum Viable Product concepts -- maximum learning with minimal effort
• Leverage AI for processing continuous feedback and real-time metrics

4. Collaborate and Promote Visibility

Core concept: "Work together across boundaries, with transparent information to the right people at the right time."

Why collaboration matters: Including appropriate stakeholders enhances buy-in, relevance, and long-term success. Diverse perspectives generate creative solutions. Collaboration outperforms siloed activity.

Typical collaboration partners:

• Customers and consumers
• Suppliers defining requirements
• Relationship managers understanding needs
• Internal and external teams optimizing workflows
• Product teams integrating SRE and IT operations

Increasing visibility: Poor visibility suggests low priority and undermines decision-making and adoption. Teams should understand work-in-progress flow, identify bottlenecks and excess capacity, uncover waste, and use visual tools.

Application strategies:

• Tailor communication to each audience's needs
• Make decisions exclusively on visible data
• Use AI-powered platforms for breaking information silos and enabling knowledge sharing

5. Think and Work Holistically

Core concept: "No service, practice, process, or department works in isolation. Use systems thinking."

Rationale: Individual products and services don't function independently. Integrated approaches maximize outcomes. Modern organizations must track how changing one element impacts others.

Holistic approach includes:

• Evaluating all four dimensions of product and service management
• Understanding the complete product and service lifecycle
• Recognizing organizational position within supply chains
• Assessing products' and services' impact on consumers
• Continuously monitoring PESTLE factors

Application strategies:

• Recognize system complexity; simple-system methods prove ineffective for complex environments
• Prioritize collaboration for holistic thinking
• Identify patterns in system element interactions
• Apply AI algorithms for analyzing complex interactions across multiple data points, services, and stakeholders

6. Keep It Simple and Practical

Core concept: "Always use the minimum number of steps needed to reach the goal. Remove what does not create value."

Rationale: Attempting to address every exception leads to over-complication. Creating general rules handling exceptions works better than covering edge cases individually. Fixed constraints fail in high-complexity environments; enabling constraints with autonomy, trust, and resources work better.

Understanding value contribution: Activities may appear wasteful from one perspective but prove essential for regulatory compliance or other corporate needs.

Managing conflicts: Organizations must balance competing objectives -- such as data collection for decisions versus process simplicity -- through explicit agreement on appropriate balance.

Application strategies:

• Ensure every activity creates value
• Embrace simplicity as sophistication
• Execute fewer activities with greater excellence
• Trust people through autonomy and resources rather than complex procedures
• Recognize that simplicity encourages adoption
• Use AI for identifying inefficiencies and redundancies

7. Optimize and Automate

Core concept: "Optimize first, then automate. Automating a process that is not optimized only wastes effort faster."

Rationale: Technology enables scaling and frees people for complex decisions, but automation should follow governance, ethical, and compliance policies.

Understanding optimization: Making something as effective, efficient, and useful as circumstances allow within financial, compliance, time, and resource constraints.

Critical principle: Automating inefficient processes only accelerates failure. ITIL explicitly requires removing waste and simplifying before automating. This applies especially to AI implementation, which demands governance and ethical controls before scaling.

Application strategies:

• Identify and implement simple, high-impact optimizations first
• Use Lean and value stream mapping for waste identification
• Remove unnecessary steps before automating remainder
• Apply AI for automation with appropriate governance

Applying the Principles in ITIL v5

In ITIL v5, principles remain conceptually consistent but gain concrete application through contemporary contexts:

• AI-native approach: Optimize and automate plus focus on value -> AI governance
• Experience-driven: Focus on value plus collaborate -> experience management
• Complexity-native: Progress iteratively plus start where you are -> VUCA strategy
• Integrated: Think holistically plus collaborate -> product and service integration

How the Principles Relate

Principles interact and reinforce one another:

• Focus on value guides holistic thinking -- value requires end-to-end visibility
• Start where you are pairs with iterative progress -- assess current state, improve incrementally
• Collaboration supports simplicity -- visibility helps eliminate unnecessary complexity
• Optimize and automate delivers value focus -- optimization creates greater value

Related Pages

• Key Concepts
• Four Dimensions
• Governance
• Continual Improvement
• Decision Guides
• Self-Assessment Quiz 2