A consultant runs a project. The metric moves. Everyone takes the photo. Six months later the number is quietly back where it started — and nobody can point to exactly when it slipped. This is the default outcome of operations improvement, not the exception.
The uncomfortable part is that the slide is normal. It isn’t a sign the project was bad or the team was lazy. It’s what happens to any improvement that was carried by a person or a one-off push rather than built into how the place runs. Understanding why is the difference between buying a result and owning one.
Finding the win is the easy part
Walk any floor for a week and the waste is visible: the report rebuilt by hand every morning, the changeover that takes twice as long as it should, the approval that sits in an inbox. Spotting it and fixing it once is the easy twenty per cent of the work. The hard eighty per cent is making the fix outlive the person who made it.
That’s the part most engagements skip. The deck lands, the binder goes on a shelf, the expert moves to the next client, and the organisation drifts back to the path of least resistance — which is almost always the old way.
Why gains slide back
It’s rarely laziness. Decay has structural causes, and they repeat across every business I’ve worked in:
- The change lived in a person, not the system. If the improvement depends on one knowledgeable individual remembering to do it, it leaves when they do.
- Nothing watched for drift. Without monitoring, a gain doesn’t fail loudly. It erodes a percent at a time until the baseline is normal again and no alarm ever sounded.
- The “improvement” added work. A checklist that competes with the day job loses to the day job. Every time.
- No owner after handover. “Everyone” owns it, so no one does.
A gain that depends on one tired person remembering to do it isn’t a win yet. It’s a loan.
The research is blunt about this
This isn’t a hunch. Sustaining improvement is now its own field of study — precisely because decay is so common. Systematic reviews of continuous-improvement and Lean — the waste-cutting, efficiency-first methodology LEANTA is built on — programmes repeatedly find that sustaining the gains is the dominant challenge, not achieving them, and that organisations need deliberate structures — ownership, measurement and management routines — for results to hold rather than fade.1,2,5 Operations researchers even have a name for the trap where firms abandon improvement work the moment pressure rises and quietly slide back: the “capability trap.”3 When the literature has to keep publishing on “sustainability,” that tells you the natural state is the opposite.
What actually holds a gain
The fix isn’t more willpower or a better binder. It’s building the improvement into something that runs without the hero:
- Encode the standard in software, not in someone’s head — the right way becomes the default path, not a thing to remember.
- Measure continuously, so drift is visible the day it starts — not the quarter it’s already cost you.
- Close the loop — the system flags when something moves, proposes the next correction, and keeps a human in the decision where judgment matters.
Do that, and the gain stops being an event you have to defend and becomes a property of how the place runs. That’s the high, flat line in the chart above — and it’s the whole reason the “improvement kata” tradition treats improvement as a daily routine, not a project.4
Why we built LEANTA this way
The name is the argument. Leanta is the Irish past participle of lean — “continued.” A LEANTA system is built to keep going, and keep improving, after we leave. We’d rather hand you something that runs itself than a result that needs us back next quarter to prop it up. That’s not generosity; it’s the only definition of a win that survives contact with a real business.