We recently hosted Karen Martin for an "Ask the Expert" webinar through KaiNexus, and she delivered. Karen is a two-time Shingo Award winner and the author of Clarity First, The Outstanding Organization, Value Stream Mapping, and Metrics-Based Process Mapping. She's also the founder of TKMG and TKMG Academy.

We had dozens of questions submitted in advance, plus more coming in live during the session. Karen answered them all with the directness and depth that anyone who's read her books would expect. I want to share some highlights here, because several of Karen's responses are worth revisiting -- and a few are worth quoting on a wall.

"A Process Has to Earn the Right to Be Automated"

One of the questions that generated the most energy came from Philippe, who asked how to prevent organizations from "automating waste" when AI enthusiasm pushes automation before processes are stable and standardized.

Karen said she'd just discussed this in a TKMG Academy community of practice session the day before. Her answer was sharp:

"Automating waste just makes the waste move faster. It doesn't do anything to improve the waste."

Then she shared a phrase she'd heard from a community member that had stuck with her:

"A process has to earn the right to be automated."

I think that's one of the most useful things anyone has said about the current AI moment. It's not anti-technology. It's pro-thinking. Karen drew a clear line between automation (telling the work what to do) and AI (thinking about the work and deciding what to do), and made the case that neither one fixes an unstable process. You need to understand the work, stabilize it, and improve it first. Then you've earned the right to automate.

This isn't a new principle -- people have been automating broken processes for decades with every new technology wave. But given the pace of AI adoption right now, it's worth saying clearly and often.

Clarity Is Almost Always at the Core

Karen opened the session with a remark that framed everything that followed: "Clarity is often at the core of it." When organizations struggle, when improvement stalls, when people resist -- it's worth asking whether the problem is really a clarity problem.

Tammy asked about the most common leadership behaviors that unintentionally create a lack of clarity around priorities, roles, and decision rights. Karen's answer came down to two disciplines. First, strategy deployment -- getting senior leaders to formally agree on key priorities so resources aren't competing and colliding. Second, a simple grid for role and decision clarification: decisions or roles across the top, people down the side. Not complicated to build, and enormously helpful once it exists.

The hard part isn't the grid. The hard part is getting people to agree they want to do it.

"I Was a Terrible Boss"

James asked a bold question about bloated management layers and why organizations lay off frontline workers instead of examining whether they have too many managers and directors. Karen's response was nuanced -- she said she sees it both ways, with middle manager ranks sometimes getting decimated too, and neither decision usually made with enough thought.

But the part of the conversation that stuck with me was what came next. When I asked about getting leaders to recognize that their job is to develop the people who report to them, Karen got personal. She talked about being promoted into leadership early in her career as a star performer and subject matter expert. One of her friends calls it being "hooked on the juice of being an expert." Karen said she was terrible in the beginning because nobody helped her see that the job had fundamentally changed -- from being the expert to developing others.

"That's 180 degrees from what you need to be doing," she said. "And it's not actually any fault of their own, because the organization didn't really help them see that this new development need is there."

That kind of honesty is rare, and it made the point more powerfully than any framework could.

Her mantra for leadership:

"A leader's job is first and foremost to develop their people so that they are in a position to meet the goals of the organization. And that's the sequence."

I've Never Seen a Beautiful Operation Be a Mess

Swathi asked what Karen looks for when she walks the floor of a manufacturing company -- the first two or three signs that they're operating with excellence or not.

Karen's answer was sensory and intuitive, which was interesting coming from someone so rigorous about process. She talked about cleanliness, orderliness, temperature, air quality -- the physical environment. Her observation:

"When they pay attention to the environment, there's almost always pretty good attention to other things as well."

And then she made a statement I'd challenge anyone to disprove:

"I've never seen a beautiful operation be a mess operationally. And I've never seen a mess performing at a very high level."

Don't Let Gemba Walks Become "Gemba Theater"

One of the liveliest moments in the session came from a phrase Kim used in a submitted question: "gemba theater." Karen loved it. She said TKMG Academy's gemba walks course actually has an animation of theater curtains opening with comedy and tragedy masks.

She told a story about a Toyota plant where a supervisor was told to prepare a car for a visiting boss by putting post-it notes on it to show quality problems. The team was so afraid to be honest that the car had almost no post-its on it. The boss saw through it immediately. Eventually, they papered the car with real problems -- and proved they were actively working on solving them.

Karen's takeaway: if you want honest gemba walks, the behavioral cues from leadership have to be unmistakable. No punishment. No eye rolls. Nothing. "If you ever want it to be real again, there better not be any negative reaction when reality is shown."

And for organizations trying to build this for the first time: many people come from companies where theater was the norm. You have to explicitly say, "This company is not a theater company" -- and then prove it through behavior.

Invite the Elephant in the Room Out

When Waltraud asked about revitalizing a Lean journey where senior leadership had lost enthusiasm, Karen kept coming back to the same principle: have the conversation. Find out why they're skeptical. Create a safe space for honest answers. "It's better to know than not know," she said -- something her mother taught her from the time she was two years old.

She also raised the possibility that the leaders may have had a "faux Lean experience" -- someone came in, called something Lean, and it wasn't actually Lean. The only way to find out is to ask.

This connects to a theme Karen returned to throughout the webinar. In her opening remarks, she said one of her biggest tips as a facilitator is to "invite the elephant in the room out." Invite resistance and skepticism to be verbalized. It's a lot easier to address what you can see.

The CI Team's Job Is Teaching, Not Doing

Ellen asked whether CI capabilities should be centralized or distributed. Karen said both can work, but the more important question is the team's purpose. If the CI team is out there "doing for people," that creates a crutch. People don't learn how to improve, and continuous improvement never becomes cultural.

The CI team's purpose should be teaching, coaching, guiding, and facilitating -- building skills into the workforce from frontlines to the C-suite. If that's the mission, centralized or decentralized is a secondary concern.

She also suggested a "grand rounds" model borrowed from teaching hospitals, where improvement teams present real case studies -- the situation, the problem, the approach, the minefields -- so that cross-pollination and learning happen across the organization.

All the Questions from the Session

Here's the full list of topics and questions Karen addressed during the webinar:

• What are the most common leadership behaviors that unintentionally create a lack of organizational clarity?
• What do you do when senior leadership has lost enthusiasm for the Lean journey?
• How do you prevent organizations from "automating waste" when AI enthusiasm pushes automation before processes are stable?
• Why do organizations lay off frontline workers instead of examining bloated management layers?
• How do you get leaders to recognize their job is to develop their people?
• How do you tell whether non-compliance with a mapped process is a design flaw or an implementation failure?
• What are the pros and cons of centralizing vs. distributing CI capabilities?
• Is there a better alternative to the X-Matrix for strategy deployment?
• What are the first signs of operational excellence when you walk a manufacturing floor?
• What can a Lean team do to influence leadership without top-down sponsorship?
• How do you adapt value stream mapping for variable, non-linear work?
• What do you do when an organization is too busy fighting fires to make improvements?
• How do you keep CI momentum through executive turnover?
• How do you keep CI momentum through frontline turnover?
• How do you avoid "gemba theater"?
• What motivates you to not give up when teams are stuck or resistant?

Watch the Full Recording

You can watch the full webinar recording here. Or in the video below. And if you'd like to learn more about Karen's work, visit TKMG and TKMG Academy.