The Living Register

Why continual improvement survives on rhythm, not enthusiasm

Most service organisations do not lack improvement ideas. They accumulate them constantly — in retrospectives, incident reviews, audit findings, and the quiet frustrations of the people who run services. The scarcity lies elsewhere. What goes missing is the discipline to hold those ideas in one place, revisit them on a predictable schedule, and act on them in an order that reflects value rather than volume.

This is the gap between an improvement register that exists and one that lives. A register created during a maturity assessment is easy to produce and easy to forget. Within a quarter it reads like a museum piece: entries logged with enthusiasm, then stranded as attention moves on. The document survives; the practice does not.

Continual improvement stalls not because the pipeline of ideas runs dry, but because the operating rhythm around them never forms. Survey evidence is consistent with this: in one 2026 study of smaller IT organisations, only 12% described their service-management approach as mature and proactive, while nearly two in five operated without consistent processes.[3] Treat the register as a standing capability — with cadence, ownership, and living prioritisation — and improvement compounds. Treat it as a one-off deliverable and it silts up like an unused channel.

What continual improvement actually is

Strip away the noise and continual improvement is a small set of commitments. ITIL 4 frames it as a practice supported by the continual improvement model[1] — a sequence that begins with a vision, reads the current state, then moves through measured steps towards a target. Behind it sits the older logic of Plan-Do-Check-Act[2]: change deliberately, observe the effect, and adjust.

The register is the connective tissue. Known variously as the CSI register or improvement register[1], it is the authoritative record of improvement opportunities, their status, and their expected value. It exists so that ideas are not lost, priorities can be compared openly, and decisions to defer or decline leave a written trace. Everything that follows rests on that point: the register is an operating instrument, not an artefact.

Why registers decay

Registers rarely fail loudly. They erode under conditions predictable enough to name. The first is absent ownership. When a register belongs to everyone, it belongs to no one, and entries age. The second is missing cadence. Without a scheduled review, it is consulted only when someone remembers it exists — which is to say, seldom.

The third condition is prioritisation that never changes. A list ranked once and frozen diverges from reality as risks shift and services evolve. The fourth is the absence of decision records. When no one can see why an item was parked, the same debates repeat and trust drains. Each condition compounds the others.

A framework for a living register

A living register turns on four mechanics. Cadence comes first: a fixed, recurring review — monthly, or aligned to service cycles — where entries are reprioritised and progressed. The date is not negotiable; the agenda is short.

Ownership comes second. A named owner curates the register, prepares each review, and holds accountability for movement, whilst each improvement carries its own owner. Prioritisation comes third, and must stay alive. A transparent scoring approach — weighing value, effort, risk, and urgency — lets items rise and fall as conditions change, so scarce capacity reaches what matters now. Decision records come fourth: every material choice, whether to progress, defer, or decline, is captured with its rationale, sparing the organisation from relitigating settled questions. Together these four keep the channel dredged.

The dimension technology cannot solve

Tooling can host a register, automate reminders, and surface a dashboard. It cannot supply the behaviours that make the discipline real, and mistaking the platform for the practice is costly. A register lives or dies on human commitments: leaders who protect the review slot when delivery pressure mounts, owners who chase movement over activity logs, and a culture that treats a declined improvement as a legitimate, recorded outcome rather than a failure to bury. None of this is discretionary. When improvement work is visibly valued alongside project delivery, people invest in it; when it is treated as optional, it is the first casualty of a crowded quarter.

Psychological safety matters here more than workflow. People surface candid ideas — including those that implicate their own work — only when doing so is safe and visibly acted upon. Where suggestions vanish without acknowledgement, the pipeline quietly closes, and no software reopens it. The register reflects the health of the conversation around it — a leadership responsibility, sustained by example, not delegated to a tool.

The risk is not a dramatic collapse but a slow return to the starting point. An organisation that lets its register fall quiet does not merely pause improvement; it teaches its people that raising ideas is futile, and that lesson is expensive to unlearn.

Rhythm is the remedy, and rhythm is unglamorous. A protected hour each month, a named owner, a prioritisation that moves, and a short record of what was decided and why: modest commitments whose power lies in repetition. Improvement that arrives in bursts fades; on a schedule, it accumulates.

Continual improvement asks less heroism and more consistency. The register is where that consistency becomes visible. Kept living, it turns a scatter of good intentions into a compounding record of change — and gives service leaders something rarer than ideas: a dependable means of acting on them.

References & Further Reading

[1] AXELOS / PeopleCert — ITIL® 4: the continual improvement practice and the continual improvement model, including the CSI (improvement) register. https://www.peoplecert.org/browse-certifications/itil

[2] W. Edwards Deming — the Plan-Do-Check-Act (PDCA) cycle, the foundation of iterative improvement.

[3] EasyVista & OTRS Group — The State of SMB IT for 2026 (ITSM maturity figures; only 12% "mature and proactive"). Reported by ITSM.tools. https://itsm.tools/itsm-maturity/

[4] ITSM.tools — Do You Need to Invest More in Your Continual Improvement Register? (on registers created and then abandoned). https://itsm.tools/do-you-need-to-invest-more-in-your-continual-improvement-register/