Continual improvement concepts and principles
Domain focus
The exam tests whether you can define continual improvement (CI), explain its purpose and scope, and apply the seven ITIL 4 guiding principles and PDCA thinking to real improvement work. CI is not a one-off project; it is repeated, value-led change.
Core rules and concepts
- ITIL 4 describes CI as aligning the organization's practices and services with changing business needs through ongoing identification and improvement of services, service components, practices, or any element involved in managing products and services.
- CI applies to products, services, practices, people, partners, technology, and value streams - not only IT systems.
- Everyone contributes; leaders create conditions, budgets, time, and authority.
- PDCA (Plan–Do–Check–Act) underpins iterative improvement: plan against a baseline, act small, check evidence, standardize or adjust.
- The seven guiding 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; optimize and automate.
- Improvement must connect to value: outcomes, costs, risks, and experience. A change that looks efficient but harms customer outcomes is not an improvement.
- 'Continual' implies repeated cycles; it does not require every activity to run without pause.
Worked example
A service desk wants faster incident resolution. Applying 'start where you are,' the team measures current resolution time and finds password resets dominate volume. Rather than buying a new tool, it pilots a self-service reset for one department, checks adoption and resolution time weekly, then expands. This shows baseline-first, iterative change with feedback.
Traps
Treating principles as slogans; skipping the baseline; launching big-bang improvements without feedback; measuring activity (number of meetings) rather than outcomes; assuming CI belongs only to a CI team.