You have a CI register. You have had a few improvement meetings. Someone on your team has "CI" somewhere in their title or responsibilities.
So why does nothing feel like it is actually improving?
Many IT organizations think they have a Continual Improvement (CI) program. They have the skeleton of one. They stood it up during a framework initiative, an audit prep, or a consulting engagement, and it has been running on inertia ever since. The register exists. The meetings happen occasionally. The metrics get tracked.
But the practice is not alive. And there are five specific signs that tell you whether yours is.
The Five Signs
Your register is a graveyard.
Items go in and nothing comes out. The most recent entry is weeks old. There is no one whose job it is to move things forward, and the last time anyone looked at the register together was before a holiday or a reorg. A register that only accepts input is not a CI practice. It is a parking lot with a logo on it.
"We don't have time for that right now" is a permanent condition.
Not this quarter. Not after the audit. Not once the new platform is stable. If that phrase has been accurate for twelve consecutive months, it is not a temporary constraint. It is your organization's default answer to improvement work — and it will still be the answer in twelve more months unless the structure changes.
Firefighting earns more recognition than fire prevention.
The engineer who stayed up all night to resolve the outage gets called out in the all-hands. The engineer who built the process that prevented the next three outages is invisible. When heroics earn status and prevention earns nothing, the incentive structure is working against CI — no matter how well-documented the improvement practice is.
Metrics are tracked but never acted on.
The dashboard is populated. The monthly report goes out. Leadership nods at the numbers. Nothing changes. Tracking without decision-making is not improvement — it is documentation with extra steps. Measurement only matters when someone is accountable for acting on it.
Leadership sponsors CI in principle and disappears in practice.
Executive buy-in is on paper. In practice, the monthly review gets bumped, the improvement plan sits in an inbox unapproved, and the CI Champion is making decisions in a vacuum. Leadership presence in the monthly review is not a nice-to-have. It is what makes the practice credible to the team running it.
If two or more of these describe your organization, that is your starting point — not the framework, not the tooling, not the training. The structural fix comes first.
None of These Are Fatal
Every pattern above has a structural fix. A graveyard register needs a named owner and a review cadence — not a new tool. A permanent "no time" culture needs capacity protected for improvement work — not a mandate. Heroics culture needs prevention to be made visible — not a policy. Metrics that go nowhere need someone accountable for acting on them — not a better dashboard. Absent leadership needs a monthly ritual that makes their presence expected and their input required — not a one-time statement of executive commitment.
The question is not whether your organization can build a real CI practice. It can. The question is whether you are ready to make the structural changes that give it a chance to survive.
If you want the full field guide — how to stand up the practice, run it week by week, make it stick, and use it as the foundation for AI-driven Service Evolution — it is here: Continual Improvement: The Engine Behind Service Evolution.
If two or more of these signs sound like your organization, that is where we start. At Tideline Insights, we build the CI practice alongside your team — the right cultural foundation, executive alignment, and an operating model that sustains itself after we leave. Book a discovery call.
Ryan Holzer is an ITIL Expert and Founder & Principal ITSM Consultant at Tideline Insights, serving IT leaders across the U.S. Founder, Florida ITSM Meetup Series.