I85PREP
⌘ K
ITIL 4 CI study materials
ITIL 4 CI study resources

ITIL 4 CI: Continual improvement practices and methods

ITIL 4 CI · Work through your exam, one topic at a time.

All guide sections

Continual improvement practices and methods

Domain focus

The exam tests the purpose and scope of the CI practice, the methods used to find, prioritize, and run improvements, and how to measure them. Expect questions on Lean, value stream mapping, root-cause analysis, benchmarking, and prioritization.

Core rules and concepts

  • The CI practice supplies the method set, the continual improvement register (CIR), and reporting; it supports improvement across practices rather than owning every change.
  • Methods are means, not ends. Lean removes waste; value stream mapping exposes handoffs and delays; Kaizen and retrospectives generate small frequent improvements; PDCA and DMAIC structure investigation; benchmarking compares against relevant practice; maturity assessments show capability gaps.
  • Root-cause tools include 5 Whys, fishbone diagrams, and Pareto analysis. Pareto helps focus on the few causes producing most effect; 5 Whys tests causal depth; fishbone organizes possible causes.
  • Prioritize with impact/effort, cost-benefit, risk, and strategic fit. Record items in the improvement backlog with owner, value, and status, not as an unstructured wish list.
  • Use critical success factors and KPIs; prefer a mix of leading and lagging indicators. Define measures before acting, and baseline them.
  • Methods should fit the problem's size and risk. A retrospective suits a team process; DMAIC suits complex defect reduction; a small experiment suits uncertainty.

Worked example

A team has 40 improvement ideas. Pareto shows 70% of delays come from approvals. 5 Whys traces this to unclear criteria. Impact/effort ranks a one-page approval checklist as high impact, low effort. The team pilots it, measures approval lead time, and keeps or adjusts it. Reasoning: diagnose first, prioritize by evidence, test small.

Traps

Choosing a fashionable method before defining the problem; measuring activity rather than outcome; no baseline; letting the CIR become a graveyard; treating problem management RCA as automatically a CI action without ownership or measurement.