Recorded Webinar | Continuous Improvement | Lean Management
In this special KaiNexus webinar, Karen Martin -- internationally recognized consultant, speaker, founder of TKMG Academy, and author of Clarity First, The Outstanding Organization, Value Stream Mapping, and Metrics-Based Process Mapping -- answered audience questions drawn from her decades of experience helping leaders simplify complexity, improve performance, and design better systems for delivering value.
This was not a typical webinar. Attendees asked their most pressing questions about Lean, value stream thinking, leadership clarity, organizational design, and continuous improvement -- and Karen answered them directly.
Topics covered include why organizations still struggle with clarity despite adopting Lean tools, how to prevent "automating waste," what to do when leadership loses enthusiasm for the journey, how to tell whether a mapped process failed in design or implementation, and much more.
Whether you're leading improvement efforts, coaching teams, or working to make systems more effective and humane, this session offers practical insight from one of the most respected voices in the field.
Scroll down for audio recording, transcript, and more.
Strategy deployment is the starting point for organizational clarity. If leaders haven't agreed on priorities, everything downstream is chaos -- competing resources, unclear roles, and scattered effort.
A simple grid -- decisions or roles across the top, people down the side -- can resolve most clarity problems around decision rights. It's not hard to build. The hard part is getting people to agree they want to do it.
When leadership loses enthusiasm for Lean, treat it as a problem to solve, not a verdict. Have frank one-on-one conversations. Find out why they're skeptical. They may have had a bad experience with something that was called Lean but wasn't.
A process has to earn the right to be automated. Automating waste just makes the waste move faster. Wait until a process is stable, consistent, and well-understood before bringing in automation or AI.
The front lines deliver value to customers. The more leaders internalize that the customer is paying for frontline work, the better their decisions will be about where to cut and where to invest.
A leader's job is first and foremost to develop their people so they can meet organizational goals. That's the sequence -- you can't skip people development and expect results.
Star performers promoted into leadership roles often stay hooked on being the expert. Without deliberate coaching, they'll never switch to the work of developing others. That's an organizational failure, not a personal one.
When a mapped process isn't being followed, the most common causes are that the wrong people were involved in the mapping (or no one was involved), or that no one is minding the value stream after the map is done. Assign a value stream owner and watch the KPIs.
The CI team's purpose should be teaching and coaching, not doing improvements for people. Whether centralized or decentralized matters less than whether the team is building capability or creating a crutch.
The X-Matrix confuses more leaders than it helps. A linearized version in a spreadsheet contains the same information and lets people focus on the plan instead of the format. And any strategy deployment plan that isn't actively managed will produce no results.
When you walk a manufacturing floor, the physical environment tells you almost everything. Cleanliness, order, and attention to the workspace almost always correlate with process discipline and performance. Karen has never seen an exception.
To influence leadership without top-down sponsorship, find the highest-level person who does support improvement and help them sell across their peer group. Don't be afraid to ask for conversations with senior leaders, and come prepared to show why it works -- not just assert that it does.
Gemba theater dies when psychological safety is real. Leaders must demonstrate through behavior -- no punishment, no eye rolls -- that seeing reality is the expectation. If you want honest gemba walks, you have to make honesty safe.
When people resist improvement, find their pain. If there's no pain, ask whether it's the right improvement to prioritize. If the pain is at an organizational level they can't see, help them see it. Resistance usually melts when people understand what's at stake.
A Q&A session with Karen Martin -- two-time Shingo Award winner and author of Clarity First, The Outstanding Organization, and Value Stream Mapping -- hosted by Mark Graban. Most questions were submitted in advance; a few came in live. Cleaned up and organized below.
Karen's opening frame: There's enormous untapped potential in this work, and clarity is usually at the core of what holds organizations back. Her facilitation tip: invite the elephant in the room out. Get resistance and skepticism verbalized, because it's far easier to address something once you know exactly what you're dealing with.
Tammy: Many organizations adopt Lean tools but still struggle with clarity around priorities, roles, and decision rights. Which leadership behaviors unintentionally create that, and what discipline should leaders adopt first?
For priorities, the answer is strategy deployment (Hoshin Kanri). Chaos and resources competing with each other come from leaders never formally agreeing on the few priorities that matter. The formal process forces that agreement. For roles and decision rights, Karen recommends a simple grid -- the same format as a skills matrix, but with decisions or roles across the top and people down the side. Clarifying who owns what and who to go to is not hard once leaders agree they want it done.
Asked about a leadership skills matrix, Karen uses one for development: it classifies not just whether a leader has a capability but how often they use it and whether they stick to their plan. Filled circles or Xs are enough. Simplicity helps clarity.
Waltraud: Senior leadership has lost enthusiasm for the Lean journey. Some functions dropped their activities, others still believe. How do you create new momentum and get leaders back on board?
Direct communication and clarity. Full leadership teams are rarely unanimously committed -- there's usually a champion or two and some skeptics. Hold one-on-ones and ask what their prior experience was, what happened or failed to happen, why they're skeptical, in a setting safe enough for honest answers. "It's better to know than not know." Treat it as classic problem solving: what's the problem, why is it a problem, why does the gap exist. One common cause is a faux Lean experience -- something labeled Lean that wasn't. Mark's addition: don't guess or assume, collect data, and that data is often just candid feedback.
Philippe: How do you stop organizations from automating waste when AI enthusiasm pushes automation before processes are stable? Is there a readiness test?
Automating waste just makes the waste move faster. A line Karen liked from a community of practice member: "a process has to earn the right to be automated." It earns that right by being stable and consistently done, with real room to move work faster and at higher quality, and by freeing people from mind-numbing work for better uses of their thinking. Karen also separates the terms: automation tells the work what to do; AI thinks about the work and decides what to do.
James: Many organizations have bloated manager and director ranks but lay off frontline workers under economic pressure. Is that true, and how do you discuss it?
It goes both ways -- middle management gets cut too -- and neither is usually done with much logic, what Karen calls "dark boardy" decisions. The reframe she pushes: the front lines deliver value directly to customers, and customers pay for that work. The more leaders internalize that, the more frontline roles register as the real value. She uses her own company as an example -- she writes the courses, but the person doing the editing and animation is delivering the value at that point. Cutting middle managers also wrecks span of control: someone higher up ends up with too many direct reports to coach anyone well, the opposite of how Toyota structures itself. Mark added that bloated layers, if they exist, are a management system problem, not the fault of the people in those roles.
James (part two): How do you get leaders to recognize that their job is to optimize the value-added work of the people they lead?
Karen's mantra: a leader's job, first and foremost, is to develop their people so they're in a position to meet the organization's goals -- in that sequence. That means removing barriers, or more precisely creating the pathway and authority for others to remove them. A VP shouldn't do the heavy lift on every obstacle, but some barriers, like senior interdepartmental tension, can only be cleared by a senior leader. Mark referenced Jeff Liker on Toyota's "don't skip a hat" -- don't escalate around a person, and don't work around a leader either. Karen added the value of skip-level or "two-up" one-on-ones: they give senior leaders a clearer line of sight without bypassing the chain, since issues still get worked back down properly.
Danny: How do you tell whether non-compliance points to a flaw in the design versus a failure in implementation?
It usually traces back to who was involved. The right people -- typically leaders, since mapping prioritizes improvements at the work-system level -- must be engaged from before the map is drawn, so they become champions of everything that follows. A value stream owner should be watching the whole stream, including whether people work the way the future state was designed, and raising obstacles for a round of improvement when they aren't. Maps are not set in stone. The common failure: someone maps in a silo and hands operations a finished map they had no part in, or nobody is minding the value stream at all. KPIs tell you whether it's working. You have to mind the store.
Ellen: What are the pros and cons of centralizing CI capabilities versus distributing them? Should the approach depend on the maturity of the improvement culture?
Both work in different settings. The more important question is the team's purpose. A common failure is a CI team that does improvement for people, which creates a crutch and keeps the capability from embedding. The CI team should teach, coach, guide, and facilitate, building skills from the front line to the C-suite. When that's the role, centralized versus decentralized matters less, and you want a pull model where teams ask the CI group in. If decentralized, gather those people often and keep one person overseeing it so terminology and standards don't drift. Karen offered a "grand rounds" idea borrowed from teaching hospitals: have teams present their problem-solving stories -- the situation, the problem, the gap, the approach, where they hit a minefield -- so others learn how the thinking evolved. She and Mark agreed it can be a "yes and": decentralized improvement with a central keeper-of-the-way group, held together with dotted-line reporting.
Terry: I've used the X-Matrix for Hoshin Kanri, but it confuses many leaders. Do you have a template leaders have actually embraced?
Karen linearized the X-Matrix into a Google Sheet or Excel file -- almost all the same content, just laid out linearly instead of forcing people to rotate a page. It's a handout in her strategy deployment course. She often adds columns, including one showing which departments will be heavily involved so no department gets overloaded. The deeper point, which Mark raised and Karen reinforced: the X-Matrix is only a visualization. What matters is the management process behind it -- catchball, alignment, ruthless prioritization, and then managing the plan. Plenty of organizations build good consensus on a plan and then nobody watches it. Someone has to own it, or people will fight fires instead of doing the new work.
Swathi: When you walk the floor of a manufacturing company, what are the first two or three signs they're operating with excellence, or not?
Partly a sixth sense for stability, repeatability, and the absence of chaos. Mostly it's the senses: clean, tidy, odor-free, the right temperature and humidity. When an organization tends the environment, it almost always tends process design, equipment, and people selection too. Karen has never seen a beautiful operation that was an operational mess, or a messy one performing at a high level. Mark's example: hospital hallway signs reading "no beds or carts stored here" with beds and carts parked underneath -- not a reason to blame staff, but a prompt to ask what barrier forced the workaround.
Gail: What's one thing a Lean team can do to influence leadership when there's no top-down sponsorship or support?
Find the highest level that does support it, and get that person to lobby peers and recruit more champions. In a large organization, a committed division VP can drive real progress even without a fully bought-in CEO; in a small one, you need at least some CEO interest. Karen encourages improvement people to ask for conversations with senior leaders and be candid about what would help. Leaders often underestimate their own influence -- people watch their every move and model it. Be ready to sell the why with examples, because jaded leaders have sat through many flavors of the month.
Nate: In environments where work is highly variable and workflows are non-linear, what adaptations to traditional VSM yield the most actionable insights?
Remember the purpose. The map is a means, not the outcome -- current state map, future state map, a plan to get there, then results. Some branching and complexity is fine as long as the map stays readable; the simple maps in Learning to See were simple because they were teaching tools. The bigger lever is the charter and scoping. Karen deliberately scopes the current state very narrow, which makes people nervous, but the future state design that comes out of it almost always applies to a much broader set of conditions. From request to delivery, that should still be one value stream, even with variation across order types or customer groups. Mark's add: map one high-volume value stream rather than cramming every stream onto one map.
Michael (live): What can an internal improvement person do for an organization so busy fighting fires that it's slow to improve and "doesn't have time to solve the real problems"?
Karen first checked whether there's a champion and a senior leader asking for the work -- there is, which she called a good sign. Get that champion engaged in motivating people: explaining how the lack of improvement hurts the business, and what the improvement will do for the business and for the people themselves. The improvement person shouldn't carry the heavy lift of getting people to the table; that motivation should come from leaders. On the Coach Wooden quote, Karen uses a variation -- you're already spending the time, over and over. Do the math on minutes lost times frequency, then compare it to the two or three days the improvement would take. The bottom line: it can't be just you selling the need, unless you're a VP or above and you are the champion.
Shannon (live): How do you keep momentum for a continuous improvement culture when there's been a lot of executive turnover?
Have conversations with the new leaders. They often aren't told what they walked into -- the vibe of the organization, the work already in progress, the open problems. Help them see the momentum already built and why carrying it forward matters. Frank conversations again, and don't be afraid to ask for help.
Colleen: How would you answer that same question when there's also a lot of frontline worker turnover?
Easier than executive turnover. New people often bring fresh eyes and are less dug in on the old way. The one real risk is no training -- people you'd want improving the work don't yet know how to do the work. Mark described KaiNexus's own practice: the expectation that everyone participates in improvement comes up during interviews and onboarding, including how people raise and discuss things, not just a tool login. He's seen people make strong kaizen improvements on their first day.
Colleen's follow-up -- heavy workloads and lack of training: Heavy workloads are a logistics problem. Without a bench to cover people, improvement work sometimes lands on overtime, weekends, or off hours, and you have to plan for getting the work done while improving it. Lack of training is separate. People need to believe their time on improvement will benefit them; many have been handed "improvements" they had no part in, which are changes, not improvements. Start with one that genuinely relieves them. For technical or physical work, Training Within Industry -- specifically Job Instruction -- is very helpful, including for nurses.
Kim: How do we make sure we're not conducting "gemba theater" visits?
Karen loved the phrase. The foundation is psychological safety. She told a Toyota story from Michael Bremer's gemba walks course: a team was told to prep a car for a visiting boss by flagging quality problems with post-its, and out of fear they flagged almost none -- then over-papered the car to prove they were working on problems. They were used to hiding reality. Set honesty as the rule going in. For assessments, Karen asks leaders not to warn staff until minutes before, so nothing gets cleaned up. And when something isn't good, there can be no punishment, not even an eye roll, or honest gemba walks end. If theater was the norm at people's past employers, you have to say plainly that this is not a theater company -- assuming that's true.
Natasha: What motivates you to not give up when teams or individuals you're coaching are stuck or not receptive?
She loves solving problems, and resistance is just another gap to close. But she won't do it alone and advises against it -- you need leadership endorsement and an executive sponsor on every improvement, however large or narrow. Go back to people's pain: if they feel no pain, it's hard to motivate them, and that may be a sign it's not the right improvement to spend time on. If something is hurting the company, help people see how, since many have no view of what an outcome does at the organizational level, and that understanding melts resistance. Her closing line: with leadership involved and the right approach, people always turn.
.svg)
Copyright © 2026
Privacy Policy