<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=749646578535459&amp;ev=PageView&amp;noscript=1">

The One Metric That Tells You If Your CI Culture Is Real

Posted by Mark Graban

Mar 16, 2026 4:45:00 AM

 

Across the Ask Us Anything series, Greg Jacboson and I have fielded dozens of questions about culture. How do you measure it? How do you know it is working? How do you know it is not just surface-level activity? Read more about this series and other posts

People often expect a complicated answer -- dashboards, maturity models, engagement surveys, idea counts.

But after revisiting the full series, one theme kept resurfacing. There is one indicator that tells you more than almost anything else. Not idea volume. Not cost savings. Not the number of Kaizen events.

It is this:

How long does it take for a problem raised by a frontline employee to get acknowledged and acted on?

Why Response Time Matters More Than Idea Count

You can launch training. You can roll out software. You can brand your initiative and track hundreds of submitted ideas. But if someone raises a problem and nothing happens (if it doesn't turn into action), your culture is not real yet.

What we have seen, over and over, is that employees do not judge a CI culture by what leaders say. They judge it by what happens when they speak up.

When a nurse, operator, technician, or analyst flags an issue, what happens next? Is there visible follow-up? Is someone accountable? Does leadership ask questions? Does the person get support? Or does the issue disappear into a queue?

That cycle time -- from problem identification to visible response -- reveals more about your culture than any survey.

What the Research Supports

Amy Edmondson's research on psychological safety (hear my podcast with her) shows that people are more likely to speak up when they see that speaking up leads somewhere. Not necessarily to agreement. Not necessarily to immediate change. But to engagement. When feedback disappears into silence, people stop offering it.

Behavioral science reinforces this too. Timely reinforcement strengthens behavior. Delayed or inconsistent reinforcement weakens it. If your improvement system is slow, bureaucratic, or opaque, participation will decay -- even if the formal program remains in place.

That is why response time matters more than idea count. You can have 500 ideas in a database and a disengaged workforce. Or you can have 15 ideas actively moving with visible ownership and a growing culture.

What We Kept Seeing in the Series

In one session, someone asked how to increase idea submission rates. The answer was not "market it better." It was closer to:

before you ask for more ideas, make sure you are closing the loop on the ones you already have.

In another session, we talked about why early CI efforts stall. It was not lack of tools. It was not even lack of training. It was slow follow-up.

When frontline employees see weeks go by without acknowledgment, leaders who do not circle back, and problems that resurface repeatedly, they internalize a message: this is not urgent. And if it is not urgent to leadership, it will not be urgent to anyone else.

The Difference Between Real and Performative

It is possible to perform continuous improvement. You can hold events, report activity, and celebrate wins quarterly. But a real CI culture feels different at the daily level.

In a real culture, problems are surfaced quickly. Leaders respond quickly. Barriers get escalated. Experiments start. Not perfectly, not flawlessly, but visibly.

What stands out to me is that the speed of follow-up communicates priority. If leaders respond to production issues within hours but improvement ideas within weeks, the hierarchy of importance becomes obvious to everyone.

What Good Looks Like

It is less about hitting a specific number and more about consistency. Problems acknowledged within a day or two. Clear ownership assigned. Status visible to the team. Regular check-ins until resolution or experiment.

Some organizations formalize this with leader standard work -- weekly review of open issues, daily huddles with visual boards, defined escalation pathways. Others do it less formally. But in every case where CI has been sustained, follow-up is not optional. It is routine.

A Simple Test

If you want to know whether your CI culture is real, ask a frontline employee:

"When you raise a problem, what usually happens?"

If the answer is something like "it depends" or "sometimes something happens" or "it goes into the system," there is work to do.

If the answer is "my manager reviews it with me" or "we try something within a week" or "I always know where it stands," you are on solid ground.

Culture is not measured by enthusiasm. It is measured by habits. And the habit of responding -- quickly and visibly -- is the clearest signal that continuous improvement is embedded in how work gets done, not just advertised.

The Deeper Point

Looking back across the series, we have talked about strategy, resistance, metrics, burnout, leadership, engagement, and scaling. But underneath all of it is something simpler.

Continuous improvement becomes real the moment people trust that speaking up leads to action. Shorten that cycle. Protect that habit. The rest of the culture tends to follow.

What does follow-up look like in your organization? I would be curious to hear what is working -- and where the gaps are.

Topics: Improvement Culture, Continuous Improvement, Ask Us Anything

Recent Posts