Insight
EXECUTIVE SUMMARY
Most organizations that invest in continuous improvement can point to the evidence: belts certified, kaizens run, a savings number in the board deck. Far fewer can show that improvement still happens at the same pace when the original sponsor moves on, the CI leader is promoted, or the business gets busy.
That gap is where CI programs stall. In our work across manufacturing, healthcare, financial services, and technology organizations, the stall rarely comes from the methodology. It comes from ownership that never left the CI team, management routines that never changed, and results that were never tied into how the business is run.
This paper sets out:
WHAT'S INSIDE
What separates a mature CI program from one still waiting to stall, and why training counts and savings totals don’t answer that question.
The five patterns that show up again and again when continuous improvement loses momentum, and what they look like inside a real plant or team.
An eight-dimension, five-level framework that scores evidence instead of intention, plus the eight questions that matter more than the average.
Six Adonis Partners engagements, each showing the maturity gap behind the business challenge and whether the fix held.
What a structured diagnostic tells leadership that a training log or a savings tracker can’t.
The one question that predicts whether a CI program survives the next leadership change.
Download the White Paper:
Launching a CI program is a solved problem. Pick a methodology, train a cohort, run pilots, publicize an early win. The harder question is what happens in years two, three, and four, after launch energy fades and attention shifts to the next priority.
The real test is whether continuous improvement has become the way the organization sets priorities, manages work, solves problems, develops leaders, and allocates resources. That is a different question from how many people have been trained or how many projects have closed.
Two things are easy to confuse, and most assessments only measure the first.
CI program maturity:
Organizational improvement capability:
A program can score well on the first and poorly on the second. That combination looks healthy in a quarterly review and is the most common profile we find in stalled programs.
Executive sponsorship is necessary to start. It secures budget, signals priority, and clears early obstacles. But sponsorship is episodic: a kickoff, a quarterly review, a recognition event. What sustains CI is what operating leaders do every day and every week.
Deploying CI tools looks like:
Embedding CI in the operating and management system looks like:
Sustainable CI requires three systems to change together:
Change the operating system without the management system and new methods sit on top of old accountability. Change both without addressing behaviors and the organization complies without committing. When one system is left behind, the program drifts back toward where it started.
These patterns show up repeatedly in programs that lose momentum. Any one slows a program down. Two or three together usually stop it.
Most maturity models count activity: people trained, projects completed, events held. Activity is easy to report and says little about durability. The framework below scores evidence that behaviors, systems, and results exist, not whether someone believes they do.
Each dimension is scored 1 to 5. The lens shows whether the dimension primarily reflects how well the program runs (Program) or whether improvement has become an organizational capability (Capability).
The evidence rules matter more than the questions. An organization cannot score itself on intention:
Evidence is triangulated from three sources: interviews at executive, middle-management, and frontline levels; artifacts such as tollgate records, savings validation, huddle boards, and standard work; and direct observation of the routines themselves. When the three disagree, the lowest-supported score stands.
Why Level 5 Doesn't Require a Leadership Change
An actual leadership transition that the program survives is the strongest proof of institutionalization, but waiting for one means few organizations could ever score a 5, and those that fail the test learn too late. Succession readiness, distributed ownership, and standards maintained by line leaders are observable now and predict the same outcome.
Regardless of the overall score, a program is at risk if any of these comes back no:
The illustrative profile below is a composite of patterns we commonly see, not a specific client. On an average basis, this organization looks like a solid Level 3 program approaching Level 4.
Illustrative composite scores, not client data:
What the average hides:
The strong scores are real: a disciplined pipeline, finance-validated savings, and a growing bench of trained belts. But they are scores of the program. The weak scores are the ones that determine whether improvement is an organizational capability. More training would not move this profile. Shifting project sponsorship to operating leaders, connecting huddles to operating reviews, and building a succession bench would.
The examples below are drawn from Adonis Partners engagements. Each follows the same logic: the business challenge, the maturity gap behind it, the intervention, the measured outcome, and the mechanism intended to sustain it. Where sustainability has not yet been demonstrated, we say so.
Primary dimensions: Pipeline and prioritization; Delivery governance and value realization
Business challenge: Leadership set an aggressive supply chain productivity target as growth in expenditures trended ahead of growth in revenue. Supply chain teams had improvement ideas but no time to pursue them alongside day-to-day demand.
Maturity gap: No structured pipeline or consistent project governance, and a budgeting approach that did not separate fixed from variable supply chain cost, which made real productivity hard to see.
Intervention: A data-driven review of supply chain cost identified more than $5 million in opportunities across transportation, procurement, distribution, planning, and customer service. Twenty-seven opportunities were prioritized on savings impact versus effort, and each was assigned a client project leader. Governance ran on a fixed cadence: weekly project meetings led by the project leader, monthly updates to the supply chain leadership team to review savings and clear resource barriers, and a monthly savings tracker aligned with finance.
Measured outcome: $1 million in savings within four months. By the end of the fiscal year, the supply chain function had realized $5.3 million in savings across transportation, procurement, distribution, and planning.
Sustainability mechanism: Client-owned project leadership and a leadership review cadence, with savings calculations aligned to finance. Staff confidence in delivering improvement projects was a stated outcome.
What it shows: The number was the output; the governance was the asset. Even so, asked whether the same energy would continue, the client’s supply chain leader said he hoped it would, but that it would depend on how busy the team was with day-to-day work. Strong governance does not by itself answer the sustainability question.
Primary dimensions: Capability and internal autonomy; Leadership ownership; Pipeline and prioritization
Business challenge: In 2018, there was no corporate CI program. One plant engaged Adonis Partners to begin a CI effort focused on quality, scrap, equipment effectiveness, and labor productivity.
Maturity gap: Initially, no methodology, no internal CI roles, and no project selection discipline. Later, after the program had scaled, a different gap emerged: a productivity pipeline at 86 percent of target, with 68 percent of identified opportunities carried over, and plant CI specialists who varied in their ability to influence plant leadership teams.
Intervention: Phase one trained project leaders and team members at Yellow and Green Belt levels, starting at one plant, and coached them through projects selected for bottom-line impact. Success led to a corporate-wide initiative across all plants. When the pipeline stalled, a standardized three-week sprint at each site combined data analysis with facilitated workshops in which plant leadership teams identified, prioritized, and planned their own opportunities.
Measured outcome: More than 300 people trained; a dedicated CI leader in each of the four plants; $6.0 million in EBITDA impact over three years. The site sprints surfaced 202 opportunities, about 50 per site, and $6.9 million CAD in identified opportunity across four sites in three months.
Sustainability mechanism: Internal CI leaders at every plant; certification tied to completed projects; a standard method for ongoing cost analysis; and recommended operating review routines and a standard reporting dashboard to embed pipeline discipline.
What it shows: A program can mature on capability while leadership ownership of the pipeline lags. The fix was to put plant leadership teams in charge of finding and committing to the opportunities. More training would not have closed the gap.
Primary dimensions: Daily management and system integration; Capability and internal autonomy
Business challenge: Roughly 40 percent annual growth over several years, with more than ten field teams across North America each executing major component exchanges differently.
Maturity gap: CI maturity was low. There were no detailed, optimized standards for exchange jobs, and most team members had no exposure to Lean methods.
Intervention: Eight priority projects, including standard work for exchange jobs from mobilization through disassembly. Lean Six Sigma training across all levels, hands-on coaching of project teams, and a plan to hire and build an internal CI team to sustain the work through the growth period.
Measured outcome: Reduced job duration for gearbox and main shaft exchanges, worth more than $3 million in annual savings. Trained 145 White Belts, 13 Yellow Belts, 3 Green Belts, and 1 Black Belt. Daily management, including daily huddles and stand-up boards, implemented across all field teams.
Sustainability mechanism: Standard work for the core job, daily huddles in every field team, and an internal CI team rather than continued reliance on outside support.
What it shows: Standard work reduces variation; daily management keeps it from creeping back. Extending both to every field team, not just a pilot crew, is what separates a defined program from one that’s actually integrated.
Primary dimensions: Daily management and system integration; Leadership ownership and behaviors
Business challenge: Customers were satisfied and capital spending was improving, but labor efficiency, equipment effectiveness, quality, and safety had stalled or were slipping across a large North American plant network.
Maturity gap: Plant leadership teams lacked a simple, consistent way to solve different types of problems, and no escalation path connected daily issues to leadership attention.
Intervention: An operating system covering planned maintenance, autonomous maintenance, leader standard work (reviews and walks), and focused improvement. Problems were tiered: a daily problem-solving process for simple, one-off issues; unresolved problems reviewed by the plant leadership team in a weekly management review; and recurring or multi-day issues routed to a standard seven-step focused improvement method. Leaders were coached for performance and outcomes.
Measured outcome: Problem-solving skills increased across plant employees, and solved problems reduced losses, improving equipment effectiveness by 10 percent across the plant network.
Sustainability mechanism: Leader standard work and a weekly management review that made problem escalation a routine part of running the plant.
What it shows: The management system did the work. Tiered escalation gave every problem an owner and a forum.
Primary dimensions: Leadership ownership and behaviors; Daily management and system integration
Business challenge: Rising scrap, a Green Belt project portfolio that needed support, and numerous changes to the site leadership team.
Maturity gap: The initial site visit pointed to the need for a mindset and cultural shift in leadership, operational excellence, continuous improvement, and maintenance.
Intervention: Coached selected leaders through operational challenges. Trained the leadership team on high-performing teams, change management, CI culture, Gemba walks, and waste, plus formal Yellow Belt training. Established leadership Gemba walks to drive quick actions from employee feedback, a daily production meeting that was continuously improved over time, and a focus on safety walks. Cleared roadblocks across the Green Belt portfolio.
Measured outcome: Average scrap of 13.2 percent versus 14.1 percent in the six months before the engagement, at or below target in three of six months. Audit score improved from 25.6 percent to 50.4 percent within three months. The Green Belt portfolio delivered $523,000 in expense reduction.
Sustainability mechanism: Leader Gemba walks and a daily production meeting owned by the site leadership team.
What it shows: When leaders turn over, routines are what carry the work. This case shows routines being installed during turbulence. Whether they hold through future changes is exactly what the sustainability question should test.
Primary dimension: Capability and internal autonomy
Business challenge: The technology division of a large health insurer set out to reimagine continuous improvement across roughly 2,000 technology associates spanning change and release management, service management, security, application development, program management, and intake and demand management.
Maturity gap: Manufacturing-origin CI frameworks needed adapting before they would take hold in a technology organization.
Intervention: A core team was trained at Yellow Belt and Kaizen Facilitator levels, then expanded to include leaders from selected areas. The team was coached through developing its own training and kaizen facilitation playbook. Kaizen was applied to challenges such as project intake and assessment, and testing, with project focus on cycle time, lead time, opportunity rationalization, and workload visibility.
Measured outcome: The effort grew into a department-wide initiative. Financial outcomes were not quantified in our engagement record, which is itself a common gap in technology functions at this stage.
Sustainability mechanism: An internally owned playbook and a facilitator bench, built by the team rather than imported from outside.
What it shows: Capability density matters more than certification volume. An internally owned playbook and facilitator bench are strong signals on the capability and internal autonomy dimension.
Three years after Adonis Partners delivered Design of Experiments training to the R&D team of a specialty chemicals manufacturer, the client reported that the techniques had been ingrained into the culture there. One participant put it plainly: our company now uses DOE routinely to develop plans in our R&D labs through plant operations. That is a single capability rather than a full CI program. But it is the test that matters: the method is still in use, years later, without anyone prompting it.
A maturity score is only a starting point. The real value is a sharper conversation about which dimension is actually holding the program back, and whether that is a training gap, a governance gap, or a management system that never changed.
The CI Maturity Diagnostic is designed to answer that question with evidence. It examines both lenses, how well the program runs and whether improvement has become an organizational capability, using interviews across leadership levels, review of program artifacts and financial validation, and observation of the routines where CI should be showing up: huddles, operating reviews, tollgates, and the gemba.
The diagnostic is built to answer four questions leadership teams rarely get straight answers to:
Programs at Level 2 or 3 usually don’t need more training. They need governance, a real pipeline, and leadership behavior that treats CI as part of running the business. Programs at Level 4 face a different problem: protecting what works while the organization changes around it. The diagnostic tells you which problem you have.
Training counts, project totals, and savings figures all measure what a program has done. None of them tells you whether it will keep doing it.
If your CI leader left tomorrow, would continuous improvement continue at the same pace?
If the honest answer is probably not, or we don’t know, the gap is identifiable and fixable. The place to start is an evidence-based view of where your program stands and which constraint matters most.
Adonis Partners helps operating leaders turn continuous improvement from a program into a capability that outlasts any one sponsor. A CI Maturity Diagnostic pinpoints the constraint holding your program back before you spend another budget cycle on more training.