ITIL 4 CI cheat sheet

Continual improvement (CI) is a recurring organizational activity performed at all levels to ensure performance continually meets stakeholders' expectations; ITIL 4 names it one of the four dimensions' enabling components and one of the three management practices in the general management category.

The ITIL 4 CI model has four stages: what is the vision (identify the goal and context), where are we now (baseline and current state), where do we want to be (measurable target), and how do we get there (plan and execute); a fifth stage, take action, covers executing, checking, and closing.

The CI model aligns with Deming's PDCA: Plan = vision + where are we now + where do we want to be; Do = how do we get there (execute); Check = did we get there (measure against target); Act = adjust and standardize.

Baseline is mandatory before improvement: without a measured current state, no target or success claim is valid; baseline metrics include KPI values, cost, risk, and stakeholder satisfaction.

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.

Guiding principle decision rules: 'start where you are' forbids discarding existing services/processes without assessing them; 'progress iteratively' forbids big-bang change; 'keep it simple' forbids adding steps that do not add value; 'optimize and automate' requires optimizing before automating.

Value for the organization from CI includes improved service quality, greater efficiency, reduced cost, reduced risk, and increased employee and customer satisfaction; these are outcomes, not outputs.

CI applies at three levels: strategic (organization-wide direction), tactical (product/service and practice level), and operational (day-to-day team level); improvement at one level must not undermine another.

A known error is a problem that has been analyzed but not resolved; CI treats recurring incidents as improvement triggers, and problem management supplies the root-cause input for the CI register.

ITIL 4 is built on the service value system (SVS): guiding principles, governance, service value chain, practices, and continual improvement; CI is the SVS component that connects all others.

The service value chain has six activities: plan, improve, engage, design and transition, obtain/build, and deliver and support; 'improve' is a value chain activity, not only a practice.

The four dimensions are organizations and people, information and technology, partners and suppliers, and value streams and processes; an improvement must be assessed across all four to avoid local optimization.

The ITIL maturity model in CI has five levels: initial, managed, defined, quantitatively managed, and optimizing; level 5 requires quantitative data and continuous feedback-driven change.

The CI practice's purpose is to align the organization's practices and services with changing business needs through the ongoing identification and improvement of services, service components, practices, or any element of the service value system.

ITIL 4 defines three management practices for CI: continual improvement (general), relationship management (general), and supplier management (general) - but the CI-specific practice is continual improvement; problem management supplies root-cause data.

Governance in the SVS evaluates, directs, and monitors; the governing body sets the direction for improvement and holds accountability, while improvement execution is delegated.

The CI register (or improvement register) records improvement opportunities with owner, status, priority, and value; it is an input to the 'improve' value chain activity and to plan.

Key CI practice inputs: feedback, incident and problem records, service level performance, audit findings, and stakeholder requirements; key outputs: improvement plans, updated practices, and measured outcomes.

The CI practice workflow: identify improvement opportunities (from feedback, metrics, audits), assess and prioritize, plan, implement, measure, and standardize or close.

Prioritization methods: value vs. effort matrix (quick wins, major projects, fill-ins, thankless tasks); impact/urgency matrix; and cost-benefit analysis; the chosen method must be documented in the improvement plan.

Improvement types: corrective (fix a defect), preventive (reduce future risk), and innovative (new value); each has a different business case and risk profile.

Metrics hierarchy: critical success factors (CSFs) state what must go well; key performance indicators (KPIs) measure it; metrics are the raw measures; a KPI must be linked to at least one CSF.

SMART targets: specific, measurable, achievable, relevant, time-bound; a target without a time-bound measure cannot be verified in the 'did we get there' stage.

Root cause analysis tools used in CI: 5 Whys, Ishikawa (fishbone) diagram, Pareto analysis (80/20), and fault tree analysis; select based on problem complexity and data availability.

The CI register entry fields: ID, description, source, owner, priority, target date, expected benefit, status, and closure evidence; a register without owners is not auditable.

PDCA and the CI model both require feedback loops; a 'lessons learned' review after each improvement is the mechanism that feeds the next iteration.

Automation rule: automate only after the process is optimized; automating a wasteful process preserves the waste and increases its scale.

A value stream is a combination of the organization's value chain activities and practices that creates value for a service consumer; CI in value streams targets flow efficiency, not only activity efficiency.

Value stream mapping identifies waste (waiting, handoffs, rework, over-processing); improvement opportunities are prioritized by their effect on end-to-end lead time and customer outcome.

Organizational change management (OCM) is required for CI: people adopt improvements only when the change is communicated, roles are clear, and incentives align; CI without OCM fails at the 'how do we get there' stage.

CI roles: the continual improvement manager owns the practice and the register; improvement owners own individual entries; all staff can raise opportunities; leadership sponsors and removes blockers.

A CI culture uses blameless review: incidents and failures are treated as learning inputs, not as grounds for punishment; this increases reporting and improves root-cause quality.

Value stream improvement measures: flow time, throughput, work in progress (WIP), and percent complete and accurate; reducing WIP usually reduces lead time.

Improvement governance: the improvement register is reviewed at a defined cadence, with decisions to approve, defer, or reject; decisions and rationale are recorded.

CI interfaces: with problem management (root causes), change enablement (implementing improvements), service level management (targets and measurement), and knowledge management (capturing lessons).

Maturity progression in value streams: from ad hoc fixes (initial) to measured, feedback-driven optimization (optimizing); each level requires evidence, not self-assessment alone.