THE DIFFERENCE BETWEEN A FAILED LAUNCH AND A PROGRAM THAT WENT STALE
A CI program that never launched has a different problem than one that launched well and quietly died. The failed launch usually traces back to a missing foundation: no daily management system, no problem-solving culture, no data infrastructure to surface improvement opportunities. The why lean transformations fail small manufacturers post covers that terrain.
This post is about the other failure mode: the CI program that generated genuine energy in the first year, produced some real results, and then gradually became a ghost. The kaizen board still hangs in the break room, slightly faded. There is a stack of completed event folders somewhere in a filing cabinet. Someone on the team remembers when the group met every Tuesday. But the last event was eight months ago, the board has not been updated since spring, and if you ask the front-line operators what the CI program is, most of them will give a vague answer about lean projects from a while back.
This failure mode is more common than the failed launch in plants that are past their first two years of improvement work. And it is more demoralizing, because the organization has already put in the effort and has the scar tissue to prove it. The restart requires a different diagnosis than the initial launch, and a different sequence.
THE FOUR SIGNS YOUR CI PROGRAM IS DEAD
These indicators appear in plants where CI programs have gone stale. One is a warning sign. Three or four means the program is functionally over.
No new improvement ideas in 30 days. In a healthy CI culture, ideas surface continuously from daily meetings, near-miss reports, and operator observations. When the idea board has not had a new card in a month, the signal pipeline has broken down. Either people stopped submitting ideas because nothing happened to the last batch, or the submission process has become too cumbersome to use.
The same five people in every improvement event. When the participant list for every kaizen event looks identical, the program has become a club rather than a culture. Rotating people through events is how CI builds broad capability and organizational ownership. A program that relies on the same core team for everything creates dependency and eventually burns that team out.
No measurable savings tracked. A CI program that cannot answer "what did we save last year?" has a credibility problem with ownership and a motivation problem with the team. People need to see that the work they do produces results someone cares about. If savings are not tracked, they are not demonstrated. If they are not demonstrated, the program competes for resources on faith alone.
Leadership stopped attending kickoffs. When the plant manager or operations manager stopped attending CI event kickoffs and closings, the program lost its organizational signal. Leadership presence at CI events communicates that the organization's senior operators believe this work matters. Its absence communicates the opposite, and the team reads that signal clearly.
THE DIAGNOSTIC QUESTIONS TO ASK BEFORE RESTARTING
Before designing a restart, three diagnostic conversations are worth having. They take less than two hours and will determine whether the restart is designed for the real problem or for the symptom.
Ask the people who ran the last events: what happened to the actions that came out of the last kaizen? Were they implemented? Did anyone follow up? The answer reveals whether the program died from lack of follow-through (a sustainability problem), from lack of resource (a capacity problem), or from lack of ownership (a management problem).
Ask the frontline operators: what was the last CI project that changed how you do your job? If they cannot name one from the last 12 months, the CI program has not been producing results visible on the floor. That is a scope and selection problem: events are being run in areas that feel important to management but are not changing daily work.
Ask the plant manager: what was the most significant cost or quality improvement attributed to the CI program in the last 12 months? If the answer is uncertain, savings tracking has not been connected to the program in a way that creates accountability.
The diagnostic questions tell you whether the restart needs to address sustainability, scope, or management infrastructure. Each requires a different emphasis in the restart design.
THE DIFFERENCE BETWEEN A CI EVENT AND A CI CULTURE
A kaizen event is a structured improvement activity: a defined scope, a team pulled together for two to five days, a current-state analysis, a future-state design, rapid implementation, and a result that is measured. Events are useful. They produce concentrated improvement in a specific area and build participant skill in structured problem-solving.
A CI culture is what happens when improvement thinking is embedded in daily work rather than in episodic events. Operators identify waste and report it without being asked. Supervisors use the daily production meeting to surface small problems before they become large ones. The 5-Why process gets applied to quality escapes and near-misses as a matter of routine. The idea board is populated and reviewed weekly, and ideas get dispositioned within two weeks of submission.
Most plants with stale CI programs have a healthy event history and an underdeveloped CI culture. The events happened; the daily practices that sustain improvement between events did not take root. The restart needs to address both: resuming events as the visible signal of activity, and rebuilding the daily practices that keep improvement alive in between.
WHY INCENTIVE PROGRAMS USUALLY BACKFIRE
When CI programs go stale, one of the first proposals is usually a financial incentive: cash rewards for implemented ideas, recognition for participation, prizes for the most improvements submitted in a quarter.
Incentive programs for CI produce short-term activity increases and frequently degrade quality. Operators submit ideas to collect the reward rather than because the ideas are high-impact. The review team becomes overwhelmed with low-value submissions. The ideas that get implemented are the ones that are easy to measure, not the ones that produce the most operational improvement. And when the incentive is reduced or removed, activity drops below its pre-incentive level because the intrinsic motivation that should have developed was replaced by extrinsic reward.
The plants with the strongest CI cultures typically have modest or no financial incentives for CI participation. They have recognition, involvement, and visible impact on the work people do every day. People contribute to CI because their contributions matter and because the organization demonstrates that by acting on what is submitted.
HOW TO HANDLE THE LEGACY PROJECTS NOBODY FINISHED
Every stale CI program has a graveyard of partially completed projects: an action item from an event 14 months ago that was never closed, a pilot that ran for three weeks and was abandoned when the production schedule got tight, a recommendation that was documented, reviewed, and never implemented.
Before announcing a restart, audit the legacy backlog honestly. Each item gets one of three dispositions.
Closed as implemented: the action was taken, even if it was never formally documented as complete. Mark it done and archive it.
Closed as will not do: the action was decided against, or conditions have changed and it is no longer relevant. Mark it closed with a note explaining why. This is not failure. It is discipline.
Moved to the active backlog: the action is still relevant and still unimplemented. It goes back into the prioritization queue for the restart.
Announcing a restart while the legacy backlog is unaddressed communicates that the organization does not close its loops. That erodes the credibility of the new effort before it begins.
THE 90-DAY RESTART SEQUENCE
The restart does not begin with a kaizen event. It begins with management infrastructure.
Days 1 to 30: Rebuild the daily foundation. Confirm the daily production meeting is running with the correct format and coverage. Confirm the idea board has a submission process and a review cadence. Assign one person as the CI coordinator for the restart. Communicate to supervisors that CI activity will be reviewed monthly as part of the operations review.
Days 31 to 60: Launch one well-scoped event. Select a scope with a visible problem, a measurable baseline, and a team that includes at least two people who were not involved in previous events. Run the event with a kickoff attended by the plant manager. Close the event with a results presentation that includes a dollar impact estimate. Follow up on every action item within 30 days and report the closure publicly.
Days 61 to 90: Build the savings tracking system. Create a simple CI tracker: one row per project, with the improvement area, the baseline metric, the result, and the annualized dollar impact. Review it at the monthly operations meeting. Share the cumulative savings number with the full plant at the end of the 90 days.
By day 90, the program has rebuilt its daily foundation, demonstrated that events produce tracked results, and begun the savings discipline that gives ownership visibility into the return on CI investment.
WHAT TO COMMUNICATE TO THE TEAM ABOUT THE RESTART
The internal communication about a CI restart should be honest and short. Acknowledge that the program lost momentum. Do not over-explain it. Commit to three specific changes: events will be run with rotating participants, actions from every event will be tracked to closure and reported, and savings will be measured and shared.
Then demonstrate it. The gap between the previous program and the restart will close faster through visible action than through communication. A single well-run event that produces a tracked result and closes all its actions within 30 days does more to rebuild credibility than any all-hands presentation. The team is watching what happens, not what is said.
P8 Problem Solving and Continuous Improvement is one of the ten pillars in the Sharpen 10-pillar framework. P8 is not a ceiling pillar, but the plants that reach Stage 3 and beyond almost uniformly have a functioning CI culture, not just a CI event history. The difference is whether improvement is embedded in daily work or reserved for special projects.
WHAT TO DO NEXT
A CI program restart is a 90-day operational project, not a culture transformation. The transformation follows if the project is executed with discipline and the daily practices get embedded. The starting point is honest diagnosis: which of the four signs of a dead program are present, and which root cause (sustainability, scope, or management infrastructure) is primary?
The free Sharpen diagnostic at /intake takes about 10 minutes and produces a prioritized roadmap across all ten operational pillars. If Problem Solving and CI is identified as a gap, the diagnostic will surface it alongside the other constraints and help you sequence the restart alongside the rest of the improvement work.