Most organizations launching a continuous improvement program think the hard part is choosing the methodology. It isn't. The hard part is getting people to actually use the system -- executives who set the tone, frontline workers who generate the ideas, and leaders at every level who need to trust the numbers enough to act on them.

These are the questions our Customer Success team hears most often:

• How do other customers get executive leadership engaged?
• How do they drive participation among frontline staff?
• How do they measure whether the program is actually working?

What follows are patterns we see consistently across customers who build durable improvement programs -- not the ones that launch with energy and plateau six months in, but the ones that compound over time.

Getting Executive Leadership Engaged

There's a version of executive buy-in that looks like support but isn't. A VP attends the kickoff, nods approvingly at the pilot results, and then disappears back into their calendar. The CI team gets the budget line and the blessing. What they don't get is the signal that improvement is an organizational priority, not an IT project.

The customers who build real executive engagement treat it as a design problem, not a communication problem. They're not trying to write a better email to leadership. They're building routines that make executive involvement easy, visible, and self-reinforcing.

Frame progress in terms of what executives already track. A CI leader who reports, "We completed 47 improvements this quarter," is speaking in a language that doesn't translate to the executive suite. Customers who sustain leadership attention lead with the metrics executives already own: cost per unit, patient safety incident rates, employee turnover, and on-time delivery. KaiNexus tracks financial impact, quality outcomes, and satisfaction gains at the improvement level precisely because this translation matters. At Mary Greeley Medical Center, the ability to quantify results changed how leadership engaged with the program. Their CEO put it plainly: KaiNexus gave them a framework and a vehicle to capture improvement ideas -- and a spark to get those ideas implemented. When improvement becomes legible to the people running the organization, it gets treated as a strategic priority rather than a background program.

For more on building this case: How Do I Get Executive Buy-In for Improvement Initiatives?

Make the data available before anyone asks for it. Executives who have to request a status report will request one less often over time. Customers who sustain leadership attention configure dashboards that surface progress automatically -- a weekly digest, a live view accessible from any device, a summary that lands without anyone having to produce it. Electrolux is a useful example: before KaiNexus, checking audit status meant scheduling a meeting or digging through emails. Now department leaders can see the status of audits and their connected improvements in real time through a single Board. When improvement data is just there, visible and current, it becomes part of how leaders read the organization's health rather than something they have to seek out.

Build improvement into existing leadership routines. The organizations with the deepest executive engagement don't add CI reviews to the calendar. They embed improvement visibility into the meetings that already happen -- the weekly ops review, the board quality committee, the quarterly business review. This matters because it signals that improvement isn't a separate program sitting alongside the real business. It's how the real business gets better.

Tirlán, an Irish food and ingredients cooperative, took this seriously when seeking executive approval for KaiNexus. Their CI team built a formal business case that walked leadership through the strategic value -- specifically the reduction of duplicated effort, time savings, and the financial case for replacing their fragmented Excel and PowerPoint-based systems. That rigor earned them executive approval and, crucially, genuine buy-in rather than reluctant sign-off. Michael Phelan, their Head of Operations and Supply Chain Excellence, describes the result: before KaiNexus, their CI leads spent countless hours chasing updates and managing spreadsheets; now they can instantly see project and KPI status and focus on what actually matters. The time freed from administrative work created space for leaders to take on strategic improvement initiatives they'd never had capacity for.

Start with gemba walks. For executives newer to the practice, a structured gemba walk with a clear purpose is often the fastest path from passive sponsor to active participant. Going to where the work happens -- and asking questions rather than issuing directives -- changes how leaders relate to improvement in ways no dashboard can replicate. See: An 11-Step Gemba Walk Template for Executive Leaders

The UMass Memorial Health case is worth studying here. Facing a $55 million operating loss, executive leadership didn't just sponsor improvement -- they built it into the management system, attending huddles and reviewing improvement data as part of weekly operations. The result: 200,000+ frontline ideas and a bond rating the organization hadn't seen in 35 years. That outcome doesn't come from passive sponsorship. Read the full story: What 200,000+ Frontline Ideas Look Like When Leaders Actually Listen

Driving Frontline Participation

Frontline engagement is where most improvement programs live or die. Executives set direction and signal priority. Frontline workers are where the ideas actually come from -- and where most organizations leave enormous value on the table.

Traditional suggestion systems implement about 2-3% of submitted ideas. That rate isn't a people problem. It's a system problem. When submissions disappear without acknowledgment, when approvals take weeks, when the person who had the idea isn't involved in testing or implementing it -- people stop submitting. Not because they've run out of ideas. Because they've learned it isn't worth the effort.

The customers who build strong frontline participation address the structural barriers before they try to motivate anyone.

Be strategic about rollout, especially with a small CI team. Iluka Resources, a $2B Australian critical minerals company, launched KaiNexus for 1,000+ users with a deliberately lean CI team -- which made their rollout approach critical. Rather than going organization-wide at once, they rolled out site-by-site, giving each department the focused support it needed before moving on. They set clear success benchmarks, ran weekly leadership meetings to review progress and remove roadblocks, and assigned a dedicated site champion in each department -- typically a senior leader who was genuinely invested in CI work. The result: 3,000+ captured improvement opportunities and a 73% average engagement rate across the organization. That kind of participation doesn't happen by accident. It's the product of a rollout designed to make adoption achievable for every site rather than assuming enthusiasm would carry the program.

See: How Iluka Resources Harnesses KaiNexus to Grow and Scale Its Improvement Program

Invest in frontline training -- and make it relevant to daily work. Electrolux found that adoption didn't happen by installing software and sending a welcome email. Their team trained frontline workers on two things specifically: why the system matters to their daily operations, and how it makes their jobs easier. They provided extra support for people who needed it and ensured training materials were accessible in the languages their teams actually speak. That intentionality in rollout contributed to a 96% engagement rate across global manufacturing sites. Their advice to other organizations: answer the basic process questions before you touch the technology -- what devices will people use, how often should they access the system, what does each user group actually need to do? Configuration decisions made without those answers tend to require rework later.

See: How Electrolux Manages 4,000 Audits and 6,000 Improvements a Year with KaiNexus

Involve the person with the idea in the solution. One pattern that holds across high-engagement customers: the person who identified the problem is part of implementing the fix. This isn't just respectful (though it is). It produces better solutions, because the person closest to the work usually knows things the manager doesn't. And it creates a stake in the outcome. Mary Greeley's PI Coordinator described what this looks like at scale: they identified over 1,600 improvements and implemented more than 75% of them, generating nearly $2 million in impact. An implementation rate that high -- more than 30 times the industry average for suggestion systems -- reflects a program where frontline workers see their ideas move.

Speed matters more than perfection. The fastest way to kill frontline participation is slow response. When someone submits an idea and hears nothing for two weeks, the signal is clear. Customers who sustain high submission rates have built workflows that route ideas quickly, with notifications that keep the submitter informed as their idea moves. People can tolerate "under review" far better than silence.

Recognition doesn't have to be elaborate. Customers consistently report that the recognition frontline workers value most is simple and immediate -- a comment from a manager, a shoutout at the team huddle, seeing their name credited when an improvement spreads to another facility. KaiNexus preserves that attribution as improvements move through the organization. The person who had the idea stays connected to the outcome.

For a deeper look at what the most engaged customers do consistently: 5 Pillars of an Effective Employee Engagement Strategy

Measuring Whether It's Actually Working

This is where most improvement programs go wrong, and they tend to go wrong in two opposite directions.

The first failure is tracking nothing. The program runs, improvements happen, and when leadership asks "what's this worth?" the CI team has anecdotes and activity counts. That's not enough to defend a budget line when cuts come.

The second failure is tracking only financial savings. This produces a distorted picture where a safety improvement that prevented a serious incident shows up as zero, and a small cost reduction in office supplies gets disproportionate attention. It also excludes the majority of improvements that don't have a clean dollar value but represent real gains in quality, time, or staff experience.

Customers who measure well tend to track across three dimensions:

Activity answers "what's happening?" -- improvements submitted, reviewed, implemented; how fast work moves through the workflow; which teams and facilities are most active. Activity metrics are your leading indicators. They tell you whether the system is being used before you have enough data to assess impact. Tirlán found this particularly valuable: their previous Excel-based system made it nearly impossible to establish accurate benchmarks or see the full picture of what was happening across departments. With KaiNexus, their leadership gained real-time visibility into cross-functional KPIs and projects -- the kind of view that enables proactive decisions rather than reactive ones.

Engagement answers "who's participating?" -- across what percentage of the workforce, in which departments, at which locations. Engagement metrics surface the places that need attention. High activity in two departments and silence everywhere else is a warning sign, not a success. Electrolux watches their 96% engagement rate as closely as their improvement counts, because it tells them the system is genuinely embedded in how work gets done rather than being used by a motivated minority. Iluka's 73% engagement rate across a 1,000-person organization tells a similar story -- broad participation, not a CI-team-only program.

Impact answers "what's changing?" -- financial savings, quality improvements, safety outcomes, satisfaction scores, time recovered. KaiNexus tracks this at the individual improvement level and rolls it up across teams, facilities, and the enterprise. Mary Greeley's $840,000 in documented financial impact from a single three-month engagement -- including $675,000 in hard cost savings and 5,200 hours of time recovered -- came from tracking at exactly this level of specificity. Without that discipline, those results exist only as impressions. With it, they become the evidence that justifies continued investment.

For a detailed breakdown of how these dimensions work together: How to Get Data You Can Actually Trust for the ROI of Improvement

What good looks like across KaiNexus customers. Based on aggregate data: 28% of improvements have a direct financial impact. Of those, 12% reduce costs with average first-year savings of around $70,000. 36% improve quality. 31% increase staff or patient/customer satisfaction. And roughly 1 in 100 improvements generates over $100,000 in impact -- the kind of result you only find if you're generating enough volume across the organization. For a broader look at the metrics CI leaders use to evaluate their programs: How Do You Measure the True Impact of Continuous Improvement in Your Organization?

The Common Thread

Executive engagement, frontline participation, and measurement aren't three separate programs. They're the same program viewed from three angles.

Executives who see credible data about improvement impact stay engaged. Frontline workers whose ideas are implemented and credited keep contributing. Leaders who can point to real outcomes can make the case for continued investment. Each piece reinforces the others.

What the highest-performing customers have built -- whether a community hospital in Iowa, a global appliance manufacturer, an Australian mining company, or an Irish food cooperative -- is a system where improvement is visible at every level, contributions are tracked and recognized, and the data is reliable enough that nobody has to take the program's value on faith.

That's what KaiNexus is designed to support. See KaiNexus in action ->

Related reading:

• How Do I Get Executive Buy-In for Improvement Initiatives?
• 5 Pillars of an Effective Employee Engagement Strategy
• How to Get Data You Can Actually Trust for the ROI of Improvement
• What 200,000+ Frontline Ideas Look Like When Leaders Actually Listen
• How Do You Measure the True Impact of Continuous Improvement?
• How Electrolux Manages 4,000 Audits and 6,000 Improvements a Year with KaiNexus
• How Iluka Resources Harnesses KaiNexus to Grow and Scale Its Improvement Program
• Tirlán Customer Story
• Mary Greeley Medical Center Customer Story
• An 11-Step Gemba Walk Template for Executive Leaders
• How to Evaluate the Success of a Continuous Improvement Department