The Kaizen Event Is the Easy Part

Run enough Kaizen events and a pattern shows up: the workshop always works. Put the right people in a room for three days, map the current state, argue about root causes, design a future state, and by Friday you have a plan everyone believes in. The energy is real. The wins on the whiteboard are real.

Then six months later, you go back and half of it has quietly reverted.

This isn't a Kaizen problem. It's a sustainment problem, and it's the part almost nobody budgets time or attention for.

Why improvements regress

A few patterns show up again and again:

• The new process depends on a person, not a system. Someone on the team remembers the new steps and enforces them by habit. When that person moves teams, goes on leave, or just gets busy, the old shortcuts creep back in because nothing structural is stopping them.
• Nobody's measuring the thing that mattered. The Kaizen event picked a metric to prove the win, everyone hit target for the report-out, and then no one looked at it again. Metrics that aren't reviewed stop being metrics -- they become trivia.
• The control plan exists on paper, not in the workflow. A control plan that lives in a shared drive isn't a control. A control plan built into the actual tool people touch every day -- a checklist field, a system validation, a visual cue on the floor -- is.

What actually holds

The events that stick share three things, and none of them happen during the workshop itself:

A named owner with a standing review cadence. Not "the team owns it" -- one person's name, on a recurring calendar invite, reporting the metric to someone who will ask questions if it slips.

Standard work that's easier than the old way, not just better. If the improved process requires more discipline than the broken one, it will lose to human nature eventually. The best control plans make the right behavior the path of least resistance.

A leader who asks about it after the excitement fades. The single best predictor I've seen for whether an improvement survives past 90 days is whether a leader two levels up mentions it, unprompted, in a review three months later. That's not about micromanagement -- it's a signal to the team that the work still matters after the workshop photos are taken down.

The real deliverable

I've started treating the sustainment plan as the actual deliverable of a Kaizen event, not an appendix to it. The future-state map is a hypothesis. The control plan, the review cadence, and the accountable owner are what turn that hypothesis into a result that's still true a year later.

The workshop is genuinely the easy part. Plan for the part after it.