Week 2: Your CI Programme Is Already Dead. You Just Haven't Noticed.

Your CI Programme Is Already Dead. You Just Haven’t Noticed.

I can tell you the exact moment a CI programme dies.

Not when the budget gets cut. Not when the CI manager leaves. Those are the funeral.

The death happened months earlier. The first time a senior leader cancelled the weekly improvement review and nobody pushed back.

One cancelled meeting. I have seen it kill programmes at oil majors, manufacturing conglomerates, financial services firms. Forty-plus organisations over twenty years. Same cause of death.

Not bad methodology. A cancelled meeting that never got rescheduled.

The 12-Month Death Spiral

Months 1-3: The Honeymoon. Leadership says the right words. Training is full. Quick wins land. Newsletters go out. It feels like the programme already succeeded. It has not. It has only begun.

Months 4-8: The Drift. Quick wins are done. What remains is harder. Cross-functional problems. Data gaps. Then the real enemy appears. Not resistance. The day job. A customer crisis. A reorg. The weekly reviews start moving. Then combining. Then the calendar invite quietly disappears.

Nobody makes a formal decision to stop. It drifts.

Months 9-12: The Isolation. The CI team works in a vacuum. Projects stall. Teams revert. The improvement board has not been updated in three weeks. At Johnson Controls, I watched a regional programme fragment when local leadership decided their priorities were different. A CI lead once told me: “I feel like I am pushing a rope.” Fifteen years later, that image is still precisely accurate.

Month 13: “CI did not work here.”

Except it did work. For about twelve weeks, it worked beautifully. Then the organisation stopped doing it and blamed the methodology. That is what always happens.

Five Signs Your Programme Is Dying

If three are true, you are in the death spiral now.

One: Leadership has not been to the Gemba this month. Not a scheduled tour. An actual walk where they talk to people doing the work. The shopfloor always knows when leaders have disengaged.

Two: The weekly review has been cancelled more than twice in eight weeks. Twice is a pattern. Three times is a decision you have not formalised.

Three: The improvement board has not been updated in two weeks. Stale boards signal nobody is watching.

Four: No new improvement projects are starting. An empty pipeline means people stopped looking.

Five: The CI team is doing the improving instead of enabling others. This looks like progress -- the team is busy. But nobody else is improving. When that team gets cut, capability leaves with them.

What Saves a Programme

At Shell Malaysia, the operating rhythm was non-negotiable. Daily huddles. Weekly reviews. Monthly steering. When crises hit, the cadence shortened rather than stopped. Five-minute stand-ups instead of fifteen. But they happened. Every time.

They made improvement visible. On the wall. On the screen in the break room. Where people cannot avoid it.

They held leaders accountable for one question: “What do you need from me to remove the barrier?” Not “Why is this late?” That question, delivered sincerely and followed by action, is worth more than any training programme.

I have delivered over $1 billion in documented savings. Not one dollar came from a programme allowed to drift. Every dollar came from discipline maintained when it was inconvenient. Especially when it was inconvenient.

Your CI programme might already be dead.

When was the last time your senior leadership attended a real Gemba walk? If you cannot answer immediately, you already know what is happening.