If you've spent any time in continuous improvement, you've heard it.

You're in the room. You've done the preparation, you know the data, you have a solid case for change. And someone - usually someone who's been around long enough to have seen a few things - looks at you and says: "We tried this before and it didn't work."

Early in my Lean career, I treated that statement as an obstacle. Something to get past. I'd try to explain why this time was different. Better methodology. Better data. Better support from leadership. I had answers ready before I fully understood the question. I knew the value of Lean, surely I can convince them as well.

It didn't work. And looking back, it was never going to.

What that statement is actually telling you

It took me a while, but I started to realize. "We tried this before and it didn't work" is not a rejection. It's an invitation. It's someone telling you, often at some personal risk, that there is history in this organization that you don't know about. That people have been here before. Promises were made and not kept. That effort was put in and nothing changed - or worse, something changed and it made things harder.

That's not resistance for the sake of it. That's earned skepticism. And it deserves to be treated with respect, not managed away with a better slide deck or persuasive responses.

The question that changes the conversation

At some point I stopped trying to win that conversation and started getting curious about it. "Tell me about that. What happened?" That's it. Four words. And then - this is the hard part - you stop talking and you actually listen. I never afforded people the time (or decency) to do this. Results were far more important to me, getting this program up and running was my priority.

What comes next is almost always more valuable than anything you brought to the room. You start to hear the real story. The initiative that was launched with fanfare and quietly dropped six months later. The consultant who came in, made recommendations, and was never seen again. The team that put in the work and saw no change in how leadership behaved. You learn what broke trust. And once you know that, you know what you're actually working with.

Why this matters more than the methodology

I've seen well-designed projects fail because nobody asked this question. And I've seen projects that were far from perfect succeed because someone took the time to understand the history before they started pushing for change.

Organizations have long memories. The people on the shop floor, the supervisors, the middle managers who've been there through multiple restructures and initiative cycles - they remember. Even when leadership has turned over. Even when the people who made the original promises have long since moved on. That history lives in the culture. And if you walk in without acknowledging it, you're not starting from zero. You're starting from a deficit you don't even know exists.

What to do with what you hear

When someone tells you it didn't work before, you have a choice. You can defend the new initiative. Explain why this time is different. Try to shift their perspective with logic, data, and persuasion or you can acknowledge what they went through. Validate their skepticism is reasonable and ask what needs to be different this time for them to trust the process and more importantly - trust you.

The second approach is harder. It requires you to slow down when everything in you wants to move forward. It requires you to sit with someone else's frustration and not immediately try to fix it or have the stock standard answer. It's the only approach that builds the foundation you actually need.

The honest truth

Not every project with a difficult history can be recovered. Sometimes the skepticism is so deep, the trust so damaged, that no amount of honest conversation is going to move things quickly. I've been in those situations. They're hard. But I've never once regretted asking the question. Even when the answer was uncomfortable. Even when what I heard meant rethinking the approach entirely.

Because the alternative - pushing forward regardless without respecting or understanding the history - is how good methodology gets wasted in organizations that need it most.

"We tried this before and it didn't work" is the most honest thing someone can say to you. Treat it that way.

If this resonates, the free guide — The 10 Questions Every Lean Practitioner Gets Asked — covers more of the real conversations you face in the field.

Get the Free Guide →

Based in Franklin, Tennessee. Working with manufacturers and operations teams across Middle Tennessee — Nashville, Murfreesboro, Chattanooga, Memphis, and Huntsville AL.

If you're dealing with the gap between what Lean promises and what's actually happening on your floor, see how we work together or get in touch directly.

Mark Fairclough
Founder, The Lean Gap · theleangap.com
Change by Design