Skip to content

The Seven Guiding Principles of ITIL 5

The ITIL Guiding Principles are among the most practical and reusable parts of ITIL.

They are recommendations that can guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.

And if you already knew the seven Guiding Principles from ITIL 4, there is good news: the seven principles remain in ITIL 5.

They are:

  • Focus on Value
  • Start Where You Are
  • Progress Iteratively with Feedback
  • Collaborate and Promote Visibility
  • Think and Work Holistically
  • Keep It Simple and Practical
  • Optimize and Automate

The important part isn’t simply memorizing seven names. It is understanding how to use them when making real decisions.

1. Focus on Value

Everything an organization does should ultimately connect, directly or indirectly, to value for stakeholders.

That sounds obvious, but organizations can become so focused on completing tasks, meeting deadlines, following processes, or producing outputs that they lose sight of why the work exists in the first place.

Ask questions such as:

  • Who receives value from this?
  • What do they actually need?
  • What outcome are we trying to achieve?
  • How does this activity contribute to that outcome?
  • Are we measuring activity, or are we measuring results?

For example, closing 500 service desk tickets is an output.

Helping employees get back to work quickly and effectively is an outcome.

The number of tickets closed may be useful information, but it doesn’t automatically tell you whether value was created.

Don’t confuse being busy with being valuable.

2. Start Where You Are

Improvement does not automatically mean starting over.

Before replacing a process, system, service, tool, or organizational structure, understand what you already have.

Some of it may work perfectly well.

Organizations sometimes assume that because something needs improvement, everything associated with it must be replaced. That can waste money, eliminate useful capabilities, and introduce unnecessary risk.

Instead:

  • Assess the current state.
  • Look at actual evidence.
  • Identify what works.
  • Identify what doesn’t.
  • Preserve what has value.
  • Improve or replace what does not.

Don’t destroy something useful simply because it isn’t perfect.

3. Progress Iteratively with Feedback

Large initiatives become easier to manage when they are broken into smaller, manageable pieces.

Instead of attempting to design and implement everything at once, make progress in iterations and use feedback to determine what should happen next.

This allows organizations to:

  • Deliver useful improvements sooner.
  • Identify problems earlier.
  • Learn from actual results.
  • Respond when requirements change.
  • Reduce the risk of a massive failed implementation.
  • Incorporate stakeholder feedback throughout the work.

Feedback is critical.

Without it, an organization can spend months successfully building exactly the wrong thing.

Make progress, check the results, learn, adjust, and continue.

4. Collaborate and Promote Visibility

Good decisions require the right people and the right information.

That doesn’t mean every person needs to participate in every decision. Too many participants can make decision-making slower rather than better.

It means involving the right stakeholders at the right time.

Collaboration helps organizations benefit from different knowledge, experience, and perspectives.

This is particularly important because you don’t know what you don’t know.

Someone working in another department may recognize a dependency or risk that a project team never considered.

Visibility is equally important.

People make better decisions when relevant information is available and understandable. Hidden work, unclear priorities, poor communication, and incomplete information make collaboration much harder.

Effective organizations make important work and information visible to the people who need it.

5. Think and Work Holistically

No service, process, department, technology, supplier, or team operates completely independently.

Organizations are interconnected systems.

A change in one area can create consequences somewhere else.

For example, implementing a new application could affect:

  • Employees
  • Customers
  • Security
  • Service desk support
  • Training
  • Suppliers
  • Existing technology
  • Business processes
  • Reporting
  • Documentation
  • Costs

If you only evaluate whether the application technically works, you may miss most of what determines whether the change actually succeeds.

Look at the whole system, not simply the piece directly in front of you.

This principle is especially valuable during organizational and digital transformation, where seemingly isolated changes can affect people, processes, partners, information, and technology throughout the organization.

6. Keep It Simple and Practical

If a process, service, activity, or measurement provides no value or useful outcome, ask why it exists.

Complexity is not automatically sophistication.

Organizations frequently accumulate unnecessary steps over time. A process that once had five steps becomes ten, then fifteen, because new activities are added but old ones are rarely removed.

Ask:

  • Does this step create value?
  • Is it necessary?
  • Does anyone use this report?
  • Does this approval actually reduce risk?
  • Could this be accomplished more simply?
  • Are we doing this because it is useful or because we’ve always done it?

Use the minimum number of steps necessary to accomplish the objective.

Simple does not mean careless.

It means removing unnecessary complexity while retaining what is genuinely needed.

7. Optimize and Automate

Automation can be extremely powerful, but automating a bad process simply allows you to perform a bad process faster.

Optimize first. Automate where it makes sense.

Before automating work:

  • Understand the objective.
  • Examine the current process.
  • Remove unnecessary activities.
  • Simplify the workflow.
  • Address obvious inefficiencies.
  • Determine where technology can genuinely improve performance.

Automation should support people and organizational objectives rather than becoming an objective by itself.

And not everything should necessarily be automated.

Human judgment, creativity, communication, empathy, and decision-making remain valuable. The goal is to determine the best combination of people, processes, information, and technology.

The Guiding Principles Work Together

One of the most important things to understand about the ITIL Guiding Principles is that they should not be applied independently.

Consider an organization implementing a new digital service.

It could:

  • Focus on Value by identifying the outcomes customers actually need.
  • Start Where You Are by determining which existing capabilities can be reused.
  • Progress Iteratively with Feedback by introducing the service in manageable increments.
  • Collaborate and Promote Visibility by involving relevant stakeholders throughout the initiative.
  • Think and Work Holistically by considering people, processes, technology, suppliers, and other dependencies.
  • Keep It Simple and Practical by avoiding unnecessary features and complexity.
  • Optimize and Automate by improving workflows before introducing automation.

The principles reinforce one another.

You don’t choose one Guiding Principle and ignore the other six.

A Simple Way to Remember the ITIL Guiding Principles

When you’re making a decision, ask yourself:

  • Value: Why are we doing this?
  • Start: What do we already have?
  • Iterate: Can we do this in smaller pieces and learn as we go?
  • Collaborate: Who else needs to be involved or informed?
  • Holistic: What else could this affect?
  • Simple: Do we really need all of this?
  • Optimize: Can we make it better, and then can technology help?

Those seven questions can turn the Guiding Principles from something you memorize for an exam into something you actually use at work.

The Guiding Principles Are More Than Exam Material

If you’re preparing for the ITIL 5 Foundation exam, you absolutely need to know the names of all seven Guiding Principles.

But memorizing the list is only the beginning.

You should understand what each principle means, recognize situations where it applies, and understand that the principles interact with one another.

More importantly, they are genuinely useful outside the exam.

When you’re facing a complicated decision, a failing process, a major change, a new technology, or an improvement initiative, running through the seven Guiding Principles can help you identify things you may otherwise have overlooked.

That is ultimately what makes them valuable.

They aren’t seven rules to memorize. They are seven ways to think.

Put the ITIL 5 Guiding Principles Into Practice

Want to see how the seven ITIL 5 guiding principles work in a real-world situation? Read our latest article, The 7 ITIL 5 Guiding Principles: From Theory to Real-World Service Management, where we use a simple cat adoption scenario to show how the principles work together in practice.

Ready to take your ITIL 5 knowledge further? Explore ITIL 5 Foundation training with Ashford Global IT and learn how the principles fit into the broader ITIL 5 framework.