Best Practices
The improvement paradox: how to improve operations without losses
By Phiona Del Birut16 Jul 20267 min read
BEST PRACTICES4 min read
Australia's 2026 plastic ban wave is here and isn't the last
Treating improvement as a separate program quietly erodes frontline performance and consumes margins
Hidden losses like wasted time, rework, stalled initiatives, and thinning trust build up when improvement lives outside daily work
Embedding continuous improvement into daily workflows with aligned culture, clear decision rights, and action-driving tools reduces losses and protects outcomes
Important notice
The information contained in this article is general in nature and you should consider whether the information is appropriate to your specific needs. Legal and other matters referred to in this article are based on our interpretation of laws existing at the time and should not be relied on in place of professional advice. We are not responsible for the content of any site owned by a third party that may be linked to this article. Mitti disclaims all liability (except for any liability which by law cannot be excluded) for any error, inaccuracy, or omission from the information contained in this article, any site linked to this article, and any loss or damage suffered by any person directly or indirectly through relying on this information.
Recently, organizations have been investing more time, budget, and leadership energy into improvement than ever before. But here’s the catch: the results aren’t lasting.
In fact, according to “The Improvement Paradox,” a commissioned study conducted by Forrester Consulting on behalf of Mitti (by SafetyCulture), fewer than one in five frontline supervisors say most improvement initiatives fully succeeded in the past year. There’s plenty of activity happening, but the benefits aren’t sticking.
There is a board on what should be happening, though.
73% of frontline supervisors and 82% of leaders believe improvement should be part of daily work. But when you look at what’s actually happening on the ground, only 39% of frontline supervisors say improvement is truly embedded in their day-to-day work. Meanwhile,76% of leaders believe it’s happening .
The intent is there. The reality just doesn’t match.
This is the improvement paradox: the more improvement is treated as a separate program on top of an existing role, the more it quietly erodes performance instead of strengthening it.
Teams don’t need more initiatives. They need improvement to be woven into their daily work, without having to think twice about it.
On paper, improvement can appear to be delivering results.But for the frontline, it often looks different: another template to fill out, another review to sit through, another step added to an already packed day.
When this happens, the system gets noisier, not better.
Both leaders and frontline supervisors want worker-centric continuous improvement. But frontline supervisors report a different reality. Only 39% say improvement is embedded in daily work and many still experience improvement as a compliance activity that sits outside their core tasks.
That gap between leadership intent and frontline experience is where performance begins to decline. Losses start to creep in.
When improvement is treated like it’s a separate layer, the costs don’t always show on the balance sheet. But they exist, and they add up to the following:
Wasted time, resources, and budget: Many frontline supervisors and leaders say failed improvement efforts directly translate into wasted time, resources, or spending.
Lower frontline trust and engagement: Other frontline supervisors and leaders point to declining trust and engagement when ideas go into a black box and nothing visibly changes.
Missed customer expectations: In some industries, frontline supervisors and leaders say stalled or incomplete improvement efforts lead to missed customer expectations.
Increased rework and firefighting: Frontline supervisors report more rework and reactive firefighting when improvement efforts don’t stick.
Damage to culture or reputation: A small percentage of supervisors and leaders report that poorly executed improvement efforts damage culture or reputation when initiatives start with energy but fade without follow-through.
All these points lead to one conclusion: when improvement lives outside daily operations, initiatives end up consuming margins instead of protecting them.
The Improvement Paradox shows that improvement tends to stall when certain patterns show up inside the organization:
1. The frontline sees resource strain. Leaders see behavior gaps.
Frontline supervisors say improvement stalls because of insufficient resources or budget and added workload. Leaders, meanwhile, point to low frontline engagement and ownership, and unclear goals or measurements.
Different diagnoses lead to different fixes, which means the real constraint often goes unresolved.
2. Insight starts at the frontline, but control stays central.
40% of frontline supervisors say improvement opportunities originate from frontline observation. Yet 49% of decision-makers say governance is still centrally controlled.
3. Accountability is misaligned.
30% of frontline supervisors believe that responsibility should be shared equally across levels. However, leaders often only assign responsibility to executives and department leaders.
When ownership expectations across levels don’t match, follow-through weakens.
4. Tools capture activity, but don’t always drive action.
Despite widespread adoption, only 29% of frontline supervisors say their improvement tools are very effective. Many systems track activity well, but don’t always accelerate decisions or remove friction in daily work.
5. Feedback loops don’t fully close.
More than half of the surveyed frontline supervisors say improvement reviews occur, but only 63% hear what happens to their ideas afterward. And while most of the interviewed leaders believe leadership follows through on frontline ideas, only 57% of supervisors agree.
That perception gap erodes trust over time. As trust declines, alignment weakens, collaboration becomes strained, and even small missteps carry weight.
Solving the improvement paradox is about redesigning a system, not launching another initiative.
The Improvement Paradox highlights four capability areas that form the backbone of a strong continuous improvement operating model:
Culture and enablement: Psychological safety, shared responsibility, and the skills to surface and solve issues
Leadership and governance: Clear purpose, defined decision rights, active sponsorship, and barrier removal
Systems and tools: Interoperable, intuitive platforms that support decisions and embed improvements into workflows
Measurement and feedback: Shared metrics, regular reviews, closed loops, and tracking the speed of implementation
Together, these capabilities show up differently depending on an organization’s improvement maturity. The four stages are:
Reactive: Where improvement is considered as ad hoc and individual-led, not system-driven.
Compliant: Where routines are defined and improvement is embedded for some, as reviews happen, but measurement is backward-looking and feedback is inconsistent.
Proactive: Where systems enable better flow, strengthened ownership among all levels, and 80% of frontline workers feel empowered to act.
Integrated: Where the majority of leaders say improvement is embedded and a close number of frontline supervisors report shared ownership.
Today, most organizations sit somewhere in the middle of the compliant stage and proactive stage, with only 12% fully integrated.
The path to embedding improvement into workflows looks different depending on roles, but the system principles remain the same. For operational leaders and executives:
Align goals across layers: Connect frontline priorities with strategic outcomes. A small set of shared metrics prevents improvement from pulling in opposite directions.
Push decision rights closer to the frontline: Define clear boundaries so routine fixes don’t stall in approval loops.
Make tools drive action: Systems should guide next steps, automate simple decisions, and close loops quickly. When tools reduce friction, adoption and impact increase.
Run barrier-removal reviews: Focus leadership reviews on clearing obstacles, not just reviewing metrics.
Track speed and business impact: Measure time-to-implementation and link improvements to financial or customer outcomes. Focus on value, not vanity metrics.
For frontline supervisors and site leads:
Build improvement into daily work: Small fixes, quick experiments, and visible follow-through beat large, separate initiatives.
Surface issues in real time: Capture problems as they happen using simple digital workflows. Visibility reduces rework and creates evidence that leaders can act on.
Close the loop consistently: Communicate consistently, even when something can’t be fixed. Closure builds trust and keeps ideas flowing.
Clarify decision rights: Clear boundaries reduce hesitation and speed up fixes. Know where you can act and where you need escalation.
Use data to push back on initiative overload: Show where added programs increase rework or workload. Redirect the conversation toward system improvements, not more campaigns.
Improvement without losses isn’t about doing more. It’s about tightening the systems so effort produces results.
The research is clear: this isn’t an effort problem. It’s a system problem.
If improvement still sits outside daily work in your organization, start by understanding where you stand. Assess your improvement maturity and identify your biggest loss drivers.
From there, each step you take to align culture, governance, tools, and feedback in the flow of work moves you closer to improving operations without bleeding time, budget, or trust.
