← Back to blog

Why Most Lean Results Don't Stick — And What Actually Makes Them Last

A team raising their hands together in a high five

Introduction

Is a great final presentation the same thing as a result that actually lasts?

Every improvement initiative ends with a readout — slides, before-and-after photos, a chart trending the right direction. What that readout can't tell you is whether the change survives contact with a normal, unsupervised Tuesday six months later, and that gap is where a large share of consulting engagements quietly fail without anyone admitting it. This raises the question we try to answer honestly with every client: what actually separates work that lands from work that just looked good in the room?

In this article, we'll walk through the pattern we've found across engagements that stuck, what predicts the ones that don't, and how we build the check for durability into the work itself rather than treating it as an afterthought.


A Good Presentation Isn't the Same as a Landed Result

A presentation can be genuinely accurate and still describe a result that doesn't outlive the engagement. The before-and-after photos are real, the numbers on the day of the readout are real, and none of that guarantees the operators keep doing the new thing once nobody's tracking compliance. We've seen this happen to good work, including our own early engagements — the gap isn't dishonesty, it's that a presentation captures a moment, and a landed result has to survive every ordinary moment after it.

"A result has landed when the team keeps doing it unsupervised, not when the slide says it worked."


The Pattern Behind Engagements That Stick

Across the results that did stick, three things were consistently present, and their absence predicts the ones that didn't.

Landed vs. Presentation-Only Results

AspectLanded ResultPresentation-Only Result
Leadership presenceStays visible past kickoffPresent mainly for the readout
Daily habitRuns without a consultant presentRuns only while being tracked
ScopeNarrow enough to actually finishBroad, never reaches a clean end state

Factors That Predict a Result Won't Stick

  1. Leadership Disappears After Kickoff: Visible sponsorship fades once the initial excitement wears off.
  2. No Daily Habit Was Built: Training happened once instead of becoming a routine like a Coaching Kata.
  3. The Scope Was Too Broad to Finish: A sweeping transformation with no clear end state is hard to sustain because it never feels done.
  4. Success Was Measured Only at the Readout: Nobody checked back in three or six months later.

Strategies for Measuring Whether It Actually Landed

1. Look for Evidence of Unsupervised Behavior

Before calling a target condition closed, look for a board being updated by the team rather than by the consultant, or a habit surviving a shift change or personnel transfer.

Signals a Result Has Actually Landed

  • Self-Maintained Boards: Tracking continues without external prompting.
  • Survives Personnel Changes: The habit continues when a key person leaves or transfers.
  • Holds Steady After Visits Stop: The metric doesn't quietly revert once weekly check-ins end.

2. Schedule a Check-In Well After the Readout

A three- or six-month follow-up visit, scheduled at the start of the engagement rather than as an afterthought, is often the single most revealing data point in the entire project.

3. Keep the Initial Scope Narrow Enough to Finish

A target condition that can actually be declared complete gives the team a real sense of accomplishment to build the next one on top of.


Real-Life Case Studies

Case Study 1: A Manufacturer's Handoff Fix That Held

A mid-size manufacturer we partnered with kept its handoff tracking habit running for over a year after our engagement ended, because ownership of the end-to-end process had been assigned to a specific team lead rather than left with an outside consultant.

Case Study 2: Virginia Mason's Sustained Lean Transformation

Virginia Mason Medical Center's decades-long adoption of the Toyota Production System in a healthcare setting is frequently cited in Lean healthcare literature precisely because it outlasted its original champions — leadership built the daily management system deeply enough into clinical routines that it survived multiple leadership transitions.


Key Takeaways

  • A good final presentation doesn't guarantee a result that survives past the engagement.
  • Visible leadership presence, a durable daily habit, and a finishable scope are the three recurring ingredients behind results that stick.
  • Success measured only at the readout misses whether the change actually lasted.
  • A scheduled follow-up visit, months later, is often the most revealing check available.
  • Assigning real ownership of the new habit is what prevents it from reverting.

FAQ Section

Q: What counts as a result actually landing, versus just looking good in a report?
A: A result has landed when the people doing the work keep doing it the new way after the consultants leave and nobody's checking. Anything that reverts to the old habit within a few months was a presentation, not a change.

Q: How long does it typically take to see floor-level results?
A: Early signals usually show up within the first few weeks of an engagement. Durable, org-wide change is a longer horizon — usually measured in quarters, not weeks.

Q: Do these results generalize across industries?
A: The specifics don't, but the pattern does. Every case we've seen involves the same three ingredients: leadership visible on the floor, a habit the team keeps without supervision, and a target narrow enough to actually finish.

Q: How do you avoid inflating results in a final presentation?
A: By building a scheduled follow-up check into the engagement from the start, rather than declaring success at the readout and moving on.


Conclusion

In conclusion, the real test of improvement work isn't the readout — it's whether the change is still true, unsupervised, months later. That's the bar we hold our own engagements to.

It's the same bar we hold every Kaizen event and engagement to. Talk to us if you want to see what that actually looks like for your own operation.

About the author

Uma KA is Founder / Director of True North Solutions, working across operations, supply chain, and engineering. Uma leads True North's Lean and Lean Digital Intelligence engagements and writes most of what's published here. Connect on LinkedIn.

← Back to blog