The Operations Bridge

Kaizen events have a very specific emotional arc. The week itself is energizing — a focused team, visible progress, a celebration at the end with before-and-after photos. Then, a few months later, someone walks the area and finds the new process has quietly drifted back toward the old one. I’ve started calling this the kaizen hangover, and it’s more common than most improvement programs like to admit.

The event ends, but the process doesn’t defend itself

During the event, the new way of working has an entire team’s attention behind it. The week after, it has to compete with a normal operating rhythm, turnover, distraction, and the simple gravitational pull of old habits. If nobody is actively defending the new standard, it doesn’t stay defended by itself — that’s not a failure of the team, it’s just how habits work.

Build the follow-up into the plan, not as an afterthought

The events that actually stuck for us had a follow-up schedule built in from day one — a thirty, sixty, and ninety day check where someone specifically audits whether the new standard is still being followed, and if not, why. Without that structure, follow-up becomes whatever’s left over after everything more urgent, which in practice means it doesn’t happen.

Ask why it drifted, not just that it did

When we do find drift, the temptation is to just re-enforce the standard and move on. I’ve found it’s more useful to ask why the drift happened — sometimes the new process genuinely didn’t account for a real constraint, and the drift is actually useful feedback rather than a discipline problem. Treating every instance of drift as a failure to follow instructions misses the cases where the instructions themselves needed adjusting.

A kaizen event is the easy part. Making the gain permanent is the actual work, and it happens in the quiet weeks after the celebration, not during it.