The Hidden Reason Your Improvement Efforts Don’t Stick
We often see this pattern in an organization’s quest to become “Lean”:
You run a kaizen event, and everyone leaves energized. Or your team gets trained on standard work, and there’s a flurry of documentation and training. Or you make a push for visual management, and are excited to finally see metrics up on whiteboards.
For a while, it works. But after several months go by, you start to notice:
The boards aren’t regularly updated
Improvement ideas from weeks ago were never implemented
You’re not sure when anyone last reviewed their job instructions
And suddenly, you’re back in the role of Chief Reminder Officer. You’re chasing people down:
“Are we still doing that kanban thing?”
“Did anyone actually try that countermeasure we talked about?”
“Can someone tell me what’s happening on Line 6?”
And here’s the real tell:
Continuous improvement only happens when you’re actively hounding people.
The good news is, there’s nothing wrong with your team. But it might be time to reexamine your role in the improvement journey.
It’s Not a Buy-In Problem
It’s tempting to think:
“People just aren’t bought in”
“We need more accountability”
“We just need more training on Lean”
But if improvement only happens sporadically, then improvement isn’t built into how the business runs. It’s an add-on. A “when we have time” activity.
And in your operation…when do you ever have extra time?
So of course it gets dropped.
Not because your team doesn’t care—but because the system doesn’t support it.
How To Tell If It’s Not Sticking
Do any of these statements ring true?
Problems only surface when they blow up
You’re not hearing about small issues daily, but you’re called to the rescue once problems become too big to hide. Standards are being ignored
Processes have started to slip, one shortcut at a time. Gradually, we’ve forgotten about the new-and-improved way and are back to the-way-things-have-always-been.Improvement work stalls out
Ideas get discussed, but not followed through.
The Hard Truth About Leadership Habits
Here’s the uncomfortable part:
Your organization is perfectly designed to get the level of improvement you’re currently getting.
Because people don’t respond to what you say is important.
They respond to what you consistently do.
Here are a few examples:
If you always review production numbers, people will prioritize hitting them
If you occasionally ask about improvement work, that will occasionally happen
If you rarely follow up on learning, it won’t be shared
No one is being difficult. They’re being rational.
They’re allocating effort to what leadership reinforces.
If you’ve got the trappings of Lean but not the impact, it’s worth asking:
What are my habits actually signaling?
The “Gemba Walk” That Wandered Over a Cliff
Here’s one example of a practice that can become rote, and lose its meaning.
You might be thinking: We’re doing this. I walk the floor every day.
But what does that actually look like? If your floor tour includes:
A quick lap through the facility
A few surface-level questions
A general sense that things are “on track”
That’s not leader standard work. That’s a drive-by.
And your team can feel the difference.
The point isn’t just to show your face every day.
The point is to engage in a way that shapes how work happens.
A productive gemba walk might include conversations like:
“What did you learn from that experiment you were going to try yesterday?”
“What is getting in the way of running this process the way we’re targeting?”
“What are you going to focus on today?”
“How can I support you in that?”
This is your chance to reinforce priorities, encourage good problem-solving, and show appreciation.
And then—this is the part that matters—you follow up tomorrow. And the next day. And the next.
If your presence doesn’t change the conversation, it won’t change the outcomes.
Why This Matters
This isn’t about doing Lean “correctly.”
It’s about three things that directly impact your business.
1. Showing Respect (and meaning it)
When you go to the floor to understand—not audit—you send a clear signal: The people doing the work matter.
You also get better information. Not filtered. Not delayed. Just the current condition, as it is.
And just as important: you model that leadership happens where value is created—not behind a desk.
2. Creating the Conditions for Daily Improvement
If coaching for problem-solving is not part of your regular rhythm, you get quick fixes, not true solutions.
Because digging in to study a problem and try things that might fail is much harder than patching up the status quo.
When leaders build simple, consistent routines of asking about the problem, what was tried, and what was learned, they start developing people in the flow of work. When you celebrate and expect logical problem-solving (as compared to ceaseless production), you signal what you want people to spend time on.
Over time, operators respond in kind. They think through obstacles, propose next steps, and show up ready to share what they learned yesterday. Improvement becomes how the work gets done, not something extra.
3. Reducing Chaos (Including Your Own)
If your day feels like:
Constant interruptions
Firefighting
Jumping from issue to issue
That’s not just the job, and it doesn’t have to be this way. You can create more calm AND accomplish more in your day by incorporating consistent leadership habits like:
Checking that standards are up to date and being followed
Proactively resolving issues that cross teams
Supporting the scientific problem-solving process
Standard work—for leaders included—makes the easy things easy.
And when that’s true, you finally have capacity for the things you wish you could spend your day on, like thinking strategically or landing that next account.
So What Should You Do?
Before you launch another initiative, tool, or training—pause.
Ask yourself:
What am I doing to model the improvement expectations I have for my people?
What am I signaling is important vs. optional? What conversations could I be having more consistently?
Am I giving my team the time and space to study problems, maintain their workspace, and properly train new employees? Or are they always on the clock to produce?
Afterall, the idea of kaizen is first and foremost about self-reflection and self-improvement. This culture of relentlessly striving to improve starts with you.
The Bottom Line
People respond to what is consistent, visible, and supported. If improvement is being ignored, it’s not because your team is resistant. It’s because the system—and your role in it—isn’t yet designed to carry it.
The good news?
That’s something you can change.
Not by working harder.
But by working more intentionally.