ITIL Guiding Principles: The Seven Principles With Practical Examples
Frameworks cannot foresee every situation, so ITIL 4 gives you seven guiding principles: short recommendations that guide decisions in any circumstance, whatever the size of organisation or type of work. They are not rules; they are habits of thought. When you are unsure which way to go on a service improvement, the principles help you choose.
The Seven Principles
| Principle | Meaning | Example in practice |
|---|---|---|
| Focus on value | Everything should link back to value for the stakeholders | Before building a report, ask who uses it and what decision it supports |
| Start where you are | Do not start from scratch; use what already works | Reuse the existing ticket categories rather than redesigning the whole scheme |
| Progress iteratively with feedback | Work in small steps and learn from each one | Pilot a new request form with one department before rolling out to all |
| Collaborate and promote visibility | Work together across teams and make work visible | Share a single board of open problems with development and support |
| Think and work holistically | No service is delivered by one team or component | Consider people, process, suppliers and technology when changing a service |
| Keep it simple and practical | Use the minimum number of steps needed for the outcome | Remove an approval step that never rejects anything |
| Optimize and automate | Improve the work first, then automate what is stable | Automate password resets after confirming the process is sound |
Looking at Each Principle More Closely
1. Focus on value
Value is whatever stakeholders consider useful, important or beneficial. Ask “who benefits, and how?” at every step. A beautifully engineered process that nobody values is waste.
2. Start where you are
Assess what exists before changing it. Measure and observe the current state, and keep what works. Teams that scrap everything lose useful knowledge and goodwill.
3. Progress iteratively with feedback
Break big changes into smaller pieces that can be completed and checked. Feedback after each iteration reduces risk and lets you adjust. This is closely linked to Agile thinking (see ITIL with Agile, DevOps and SRE).
4. Collaborate and promote visibility
Silos hide problems. Involve the right people early, share information openly and make work and decisions visible. Trust grows when people can see what is happening.
5. Think and work holistically
Services are made of interconnected parts. Changing one part can have effects elsewhere, which is why the four dimensions (see The Four Dimensions of Service Management) are a useful checklist.
6. Keep it simple and practical
If a step does not contribute to an outcome, drop it. Prefer a short process people follow over a perfect one they avoid.
7. Optimize and automate
Make sure the work is sound before automating it; automating a bad process produces bad results faster. Use human effort where judgement matters.
Principles Work Together
The principles interact and sometimes pull in different directions. “Keep it simple” may conflict with “think holistically”, for example. Use them as a set: ask which ones apply to the decision in front of you and whether your choice respects the others.
A Worked Example
A service desk lead wants to cut the time to resolve access requests. Start where you are: she measures the current process and finds that most delay is waiting for manager approval. Focus on value: users value getting access quickly, auditors value control. Keep it simple: she removes approval for low-risk access. Progress iteratively: she pilots with one team for a month. Optimize and automate: only after the pilot succeeds does she automate provisioning. Collaborate: security and HR are involved from the start.
Common Mistakes
- Memorising the list for the exam but never applying it to real decisions.
- Using “keep it simple” as an excuse to skip necessary controls.
- Automating first and fixing the process later.
- The seven principles 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, and optimize and automate.
- They guide decisions; they are not rigid rules.
- Apply them as a set, since they sometimes pull in different directions.
- Fix the process before automating it.