Michael Lombard opened the webinar with a claim that does a lot of work for the rest of the session. All ideas are not created equal.
The point isn't about the size of the result. The point is about the way an organization approaches improvement. Two organizations can pursue the same improvement objective — say, reducing a process cycle time by 30 percent — and produce wildly different long-term impact depending on how the work was done. The result on the process matters. So does what the process of improvement itself produced in the people doing the work.
Michael laid out three scenarios on a chart. The horizontal axis was the intensity of investment in developing people. The vertical axis was overall organizational impact.
The red scenario: a vendor walks in, prescribes a technological solution to an issue, implements it, and walks out. Process improvement happens. The organization gets the result. But the staff didn't participate in producing it. Nothing about how the organization thinks or operates has changed. The impact is bounded by the immediate result.
The yellow scenario: the organization engages staff through a quality circle, a rapid improvement event, or a kaizen event. The participants are involved. The team-building benefits accrue. The esprit de corps from working on a real problem together is real. Engagement adds to the impact. But once the event ends, the organization mostly returns to business as usual — with a bit more bounce in its step, but without fundamentally different capability.
The green scenario: the improvement is approached in a way that intensely develops people. The participants don't just solve the problem in front of them. They develop new mindsets, new habits, new ways of thinking about future problems. The cognitive science behind habit formation and neuroplasticity is doing the heavy lifting here. The result is dramatically larger long-term impact because the people who emerge from the improvement work are now equipped to lead the next round of improvement with stronger reflexes.
Michael's contention through the rest of the session: the green scenario is what traditional kaizen, done well, produces. Toyota Kata also produces it. Both together produce more than either alone.
That framing set up the rest of the hour.
Michael Lombard is a continuous improvement leader and practitioner with deep experience applying Kaizen and Toyota Kata in complex organizations, particularly healthcare settings. His background includes coaching frontline staff, supervisors, managers, and directors through the practice of improvement and coaching kata. He has experimented with how the kata approach integrates with kaizen, A3 thinking, strategy deployment, daily management systems, and traditional project management. His perspective draws from years of practice as both a coach and a learner working through the discipline of scientific thinking applied to operational improvement.
Mark Graban hosted the session and provided the kaizen framing portion. Mark is the author of "Lean Hospitals" and co-author of "Healthcare Kaizen" with Joe Swartz.
Mark stepped in to cover the kaizen foundation before Michael moved into the kata material.
Kaizen is a Japanese word that translates literally as "good change" or "change for the better." Mark and Joe Swartz have both written extensively on the topic. A few principles stand out as foundational.
The goal is engaging everyone in improvement. Joe's organization, Franciscan Saint Francis Health in Indianapolis, has reached close to 50 percent participation rates of employees submitting, implementing, and documenting at least one kaizen per year. Cumulatively, about two-thirds of employees have participated at least once. The leadership challenge is continually to expand that participation — not to hit a target, but to make daily improvement part of how the organization works. The cultural marker that signals success is when people start pointing out problems openly because doing so is celebrated rather than punished or covered up.
The distinction between a kaizen system and a traditional suggestion box matters. Suggestion boxes ask people for ideas about things other people will implement, and leaders approve or reject ideas without further involvement from the person who submitted. A kaizen process starts with defining a problem or opportunity for improvement, and then follows the PDSA cycle — Plan, Do, Study, Adjust — through to a tested change. The person who identified the opportunity is involved in working through it. The follow-through is what separates a kaizen culture from a suggestion-box culture.
Leadership behavior is the determining factor. How leaders react when employees speak up. Whether they collaborate with people or take over their work. Whether they coach the practice of improvement or simply demand results. The drive and energy that comes from leaders at all levels is what makes any of the rest of it work.
Michael moved into the kata material with a useful framing. Toyota Kata, the book by Mike Rother from the University of Michigan, came out of years of studying how organizations like Toyota develop people on the front lines to lead improvement in a methodical, scientific manner — and how they develop coaches to teach those principles to others.
Michael's working summary of kata is short. Kata is the scientific method with two things added: direction and deliberate practice.
The direction comes from the kata practitioner constantly working backward from a long-term vision. What's the direction we're headed? What's the challenge we're trying to achieve in the next six months to a year or two? What's the target condition we want to be at in the next couple of weeks or a couple of months? What's the next obstacle we need to tackle? PDCA is the engine. The direction is what keeps the engine pointed at something that matters.
The deliberate practice piece is the part that separates kata from other improvement methodologies. Michael was explicit that the improvement kata isn't just another process improvement technique like DMAIC. It's not in the toolbox category. It's designed to create new habits, new ways of thinking, new mental muscle memory — and the process improvement results are almost a byproduct of the cognitive change. The kata is something you do, not something you deploy.
The improvement kata has four routines. None of them is fancy. The repetition is the point.
First: understand the direction or challenge. There's a real skill to this. Most organizations and most individuals start out poor at it. The more you practice the routine, the more strategic you start to think.
Second: grasp the current condition. The novel piece in the kata approach is that grasping the current condition is itself treated as a series of small experiments. Going to gemba to observe a process or collect data is approached as a PDCA cycle. The grasp is empirical and action-oriented rather than analytical and detached.
Third: establish the next target condition. The bite of the apple. Where do we want to be in the next few weeks or month or two? The act of consensus-building around that target condition is itself an experiment. Defining the target is part of the practice.
Fourth: iterate toward the target condition. Once the target is set, a series of obstacles will stand between current state and target state. The team navigates through them through rapid cycles of PDCA. Not 30-, 60-, or 90-day pilots. 30-, 60-, or 90-minute cycles. The cadence is the discipline.
Michael introduced one of the more useful concepts from the kata practice — the gray zone. The space between current condition and target condition isn't a planned path. Kata practitioners don't assume they know the right way to get from here to there. They relish the gray zone because that's the learning zone. Side trips happen. Wrong directions happen for a cycle or two. The iteration is what produces the path. The willingness to live in uncertainty is what produces the development.
Mark interjected here with a useful parallel from Ronald Heifetz's work at Harvard on technical change versus adaptive change. Technical changes have known steps that can be planned in advance — swapping out a hard drive in a computer is technical. Adaptive changes are more complex and require iterating through the change as understanding develops. Heifetz's point: organizations consistently err by treating adaptive challenges as if they were technical ones. Michael's response was that Heifetz's framing captures exactly what kata is trying to develop — the mindset for navigating through adaptive change in the gray zone, rather than forcing every challenge into a known plan.
While the learner practices the improvement kata, the coach practices the coaching kata. The coach plans coaching cycles and executes them. The more the coach does this, the more they start to realize that every step they take as a coach is itself an experiment — not just facilitating the learner's process improvement, but honing the coach's own craft. The scientific method becomes recursive. Everyone is practicing it at every level. The cultural shift that produces is substantial.
Every step is an experiment, whether you're in the role of learner or in the role of coach. Michael's phrasing for what this does to the brain is concrete: it's like your brain lifting weights, developing mental muscle memory through deliberate repetition, rewiring neural pathways through the practice itself. The cognitive science is real. The book "Toyota Kata" makes the explicit case. The brain changes through this kind of practice in ways that ordinary training does not produce.
Michael's view, after several years of practice, is that kaizen and kata aren't competing methodologies. They aren't even merely complementary. They're symbiotic.
Kata reinforces kaizen. Kaizen is based on the scientific method. PDCA cycles work better when the people running them have strong scientific thinking habits. Kata's design is explicitly to develop those scientific thinkers through deliberate practice. An organization that practices kata will also do kaizen better, because the people doing kaizen are stronger at the underlying thinking.
The coaching dimension reinforces too. When you first start coaching kaizen, you'll make mistakes. You'll ask too many questions or not enough. You'll ask leading questions. You'll be manipulative without meaning to. You'll struggle to find the Socratic stance that develops the learner. The coaching kata gives you a framework for getting better at coaching by treating every coaching cycle as an experiment. The improvement compounds.
Kata also gives kaizen efforts a sense of direction. The improvement kata's first routine — understanding the direction or challenge — embeds strategic thinking into the practice. Even if an organization doesn't have a mature strategy deployment system, kata practice creates a small amount of direction and alignment that pulls kaizen toward bigger challenges rather than letting it drift into point kaizen (isolated improvements without strategic context).
Kaizen enables kata. Michael flipped the relationship. When he tried to introduce kata into organizations that didn't have a kaizen-aligned culture, the practice struggled. Cultures that only care about results — "what did you do to improve cost, what did you do to improve efficiency" — don't make space for words like experimentation and learning. The rapid cycle of trying, failing, learning, and trying again requires permission. Kaizen cultures already grant that permission. The fertile ground for kata is a culture that has internalized kaizen principles.
Both methods are based on the scientific method. If you already have a kaizen framework working in your organization, you don't need to dismantle it to practice kata. Kata principles plug into existing kaizen routines. The morning huddle reviewing the idea board can include a brief discussion of target condition and direction. The PDCA cycles can be tightened. The coaching can improve. The integration is incremental.
Mark added two practical points to round out this section. Kaizen is also a learn-by-doing practice — at some point you have to dive in, and ideally with someone coaching you. Leaders and employees will make mistakes. The environment has to be one where mistakes during honest attempts at improvement aren't punished, because the fear of mistakes will produce paralysis and the improvement work won't happen. The role of the leader-as-coach is to prevent wildly irresponsible actions without becoming bureaucratic and slow, which is the suggestion-box failure mode.
Mark's second point: you can get better as a coach without formal kata practice. Doing kaizen every day, engaging with your team, treating every coaching cycle as an experiment, and consistently honing your craft will produce growth. Adding kata to that practice can speed up the development. But the underlying habit of treating coaching as a learning practice is what matters, with or without the formal kata framework.
Michael walked through two concrete examples from hospital settings to make the abstract principles operational.
The hospital had implemented barcode medication verification technology — scanners and armbands designed to improve patient safety by verifying the right medication was being given to the right patient. The technology had been in place for some time but wasn't being properly utilized. A nursing manager wanted to improve compliance.
The red approach: have the technology vendor come in with an audit checklist, mandate additional training, and call it done. Compliance would have improved. The development of people would not have.
The yellow approach: form a unit-based council, brainstorm the top ten ideas for improving compliance, prioritize them using dot-voting, and implement the best ones. Some improvement would have happened. Staff would have felt some ownership.
The green approach: the nursing manager practiced the improvement kata while Michael practiced the coaching kata. Michael was honest that this was early in his coaching practice and they made plenty of mistakes. The early cycles produced superficial solutions like "more training for staff" and "more auditing" — the same things the red and yellow approaches would have produced.
But by running cycle after cycle and watching what didn't work, the nursing manager started to develop a new reflex. The reflex was to take another step rather than assume an answer. When in doubt, go to gemba, do another PDCA cycle, see what you learn. After many cycles, the root cause turned out to be that the armbands were washing out — a materials management and purchasing issue rather than a training or compliance issue. The fix was straightforward once the cause was visible. Patient safety improved.
The patient safety improvement was important. The more durable result was what happened to the nursing manager. He developed a mental muscle memory for taking the next step rather than guessing. That capability transferred to every subsequent problem he tackled. The process improvement was real. The capability development was bigger.
The hospital used patient room whiteboards as a visual communication tool — letting nurses, doctors, the patient, and family stay aligned on plan of care, expected discharge date, and other relevant information. The boards weren't being used effectively. Visual communication was poor.
A frontline clinical primary nurse wanted to tackle this. He had never led improvement work before. Michael had never coached a frontline clinical staff member through the coaching kata before — his prior work had been with supervisors, managers, and directors. The pairing was new territory for both of them.
The red approach: research the Studer Group's evidence-based work on patient whiteboards, disseminate the model, and audit against the principles. Knowledge would have transferred. Some improvement would have happened. The learning cycle would not have been the developmental experience.
The yellow approach: another unit-based council, possibly a kaizen event, with engagement from physicians and patient families. The participation would have been meaningful. The development would have been moderate.
The green approach: the primary nurse practiced the improvement kata. The early obstacles were small. The markers on the boards kept going dry. The boards were hard to erase. These were unglamorous problems, but cycle after cycle of working on them sent a message to the staff that the manager wasn't going to assume the issue was about education and accountability. The system was being made easier rather than the people being blamed.
Then bigger issues emerged. The nurse and the doctor weren't rounding together, which meant they weren't using the board collaboratively, which meant the board often went unused. That's a more complex, more political problem. But the cycles continued. The nurse got stronger. He started to see how empirical root cause analysis — doing one more PDCA cycle rather than speculating — could surface causes that traditional analysis would miss. Michael started to learn how to coach frontline nurses and physicians, which he hadn't done before. Both sides developed.
The improvement was real. The development was the larger story.
Michael shifted to how the kata practice integrates with the platform itself. The integration is direct.
KaiNexus was built with kaizen principles baked in. Greg Jacobson, the founder, based much of the design on Masaaki Imai's book "Gemba Kaizen." The kaizen orientation is in the platform's bones.
The Opportunity for Improvement (OI) record in KaiNexus has, traditionally, a description box (where the problem is captured) and a proposed solution box (where the proposed solution is captured). Michael started experimenting with a small reframe. The proposed solution box becomes the target condition. The description box stays as the current condition. The OI tasks panel on the bottom right becomes the iteration space — the rapid PDCA cycles aimed at eliminating obstacles on the way to the target condition.
In that frame, the overall OI record represents the pursuit of a target condition over the course of a few weeks to a few months. The tasks panel represents the daily iteration that removes obstacles along the way. The platform supports the kata practice without modification — just a different way of thinking about what each field captures.
The integration matters because kata practice produces volume. A learner running 30- to 90-minute PDCA cycles will produce many small experiments. Tracking those experiments in a system that holds them, makes them visible, and surfaces progress is what keeps the practice from becoming overwhelming. The infrastructure carries the load that the discipline produces.
Michael's broader argument was that kata principles plug into whatever improvement architecture an organization already uses. A3 thinking. Strategy deployment. Daily management systems. Kaizen events. Value stream maps. Old-school project management.
He gave a project management example to make the point. A hospital was relocating from one side of town to the other. Classic large-scale project management. A Gantt chart with hundreds of deliverables. The project management activity was reduced to the project manager pestering people for updates on their deliverables.
The organization was new to lean and had no formal training in kaizen or kata. What they did was simple. They took all the deliverables off the Gantt chart and turned them into sticky notes on a wall. To Do, Doing, Done — classic kanban. That's already a kaizen-style move: make work visible, make it flow.
Then they added a kata layer. They split the Doing column into two: Doing This Week, and Doing Today. Each sticky in the weekly column became a target condition for that week. Each sticky in the daily column was a daily PDCA cycle being run against that week's target. Big parent stickies stayed in the weekly column. Smaller child stickies — the daily experiments — moved through the daily column. Rapid cycle iteration got embedded into the project management practice without the word "kata" ever being introduced to the organization's vocabulary.
The point Michael wanted to land was that you don't need formal kata language or formal kata training to start infusing kata principles into existing work. Experiment with how the four routines map onto your current practice. Try treating coaching cycles as experiments. Try splitting your work-in-progress visualization into weekly target conditions and daily iterations. See what produces development.
The symbiotic nature of kaizen and kata becomes visible in practice rather than through theory. Michael's closing point was that the way you approach improvement matters at least as much as the results. When you start to change mindsets, anything is possible in the future. A team that thinks like scientists can tackle whatever challenge arrives. That's what makes any idea truly priceless.
The framework Michael walked through is a working integration of two practices that often get described separately. Kaizen is the engagement and idea-flow side. Kata is the deliberate practice and scientific thinking side. Neither replaces the other. Together they produce something that neither alone fully achieves.
The infrastructure question for both practices is similar. Kaizen at the volume Michael and Mark referenced — Joe Swartz's organization reaching 50 percent annual participation — is not sustainable on spreadsheets or paper. The administrative overhead of tracking that many improvements through identification, implementation, study, and adjustment crushes most attempts before they reach scale. The infrastructure that handles the workflow without consuming the CI lead's time is what makes the volume tractable.
Kata produces a different kind of volume. A learner running PDCA cycles at 30- to 90-minute cadences generates a lot of experiments. Most of those experiments produce a small finding that informs the next experiment. The collective trajectory is what produces the development. Without infrastructure that captures each cycle — what was tested, what was predicted, what actually happened, what was learned — the practice becomes either ceremonial (we said we ran experiments but we didn't track them) or unsustainable (the learner gives up because the administrative overhead of tracking cycles eats the time they'd otherwise spend running them).
Michael's reframe of the KaiNexus OI fields — proposed solution becoming target condition, tasks panel becoming the experiment iteration space — is a small example of how an existing platform can hold the new practice. The fields didn't change. The interpretation of the fields changed. The platform held the structure.
The coaching dimension benefits from the same infrastructure. Michael's coaching kata practice involved observing learners at storyboards, asking the structured set of coaching questions, and tracking his own development as a coach. The storyboards can be physical or digital. The advantage of a digital home for the work is that the coaching cycles are visible to others — peer coaches who want to learn, second-line coaches who are developing the first-line coaches, leaders who want to see whether the practice is producing development. The visibility makes the practice teachable rather than confined to the dyad.
The leadership dimension that Mark emphasized — leaders practicing PDCA visibly, posting their own A3s, treating coaching as a learning practice — depends on the same visibility. Where leaders' improvement work is invisible, employees learn that improvement work is something other people do. Where it's visible, the practice spreads through observation. Infrastructure that keeps leadership work visible is part of the cultural mechanism.
None of this changes what Michael and Mark were teaching. The kaizen is the kaizen. The kata is the kata. The scientific thinking and the coaching and the deliberate practice are the work. What infrastructure does is keep the practice from getting buried, keep the volume tractable, and make the cumulative development visible across the organization rather than confined to the people directly involved.
What does Michael mean by "all ideas are not created equal"? The result an improvement produces is one dimension of its value. The way the improvement was pursued is another. An improvement that produces a process result without developing the people involved produces bounded impact. An improvement that engages staff in the work produces additional impact through engagement and team-building. An improvement that intensely develops the people involved — producing new mindsets, new habits, new scientific thinking reflexes — produces dramatically larger long-term impact because the people who emerge are equipped to lead the next round of improvement with stronger capability. The pursuit matters as much as the result.
What is Toyota Kata? A practice developed at Toyota and articulated in Mike Rother's book "Toyota Kata" for developing scientific thinking habits in organizations. Michael's working summary: kata is the scientific method with two additions — direction (always pursuing a long-term challenge or vision, with target conditions cascading down from it) and deliberate practice (structured repetition that produces habit change rather than just knowledge). Kata is not a process improvement methodology like DMAIC. It's a practice you do daily that produces process improvement as a byproduct of the cognitive change it creates.
What are the four routines of the improvement kata? First: understand the direction or challenge. Second: grasp the current condition through direct observation and rapid PDCA cycles. Third: establish the next target condition — where you want to be in a few weeks to a couple months. Fourth: iterate toward the target condition through rapid PDCA cycles against the obstacles that stand between current and target. None of the routines is exotic. The discipline is the repetition.
What is the gray zone? The space between the current condition and the target condition. Kata practitioners don't assume they know the direct path between the two. They expect to take side trips, head in wrong directions for a cycle or two, and iterate their way through. The willingness to live in that uncertainty — to relish the gray zone rather than try to plan it away — is what produces the learning. Michael linked this to Ronald Heifetz's distinction between technical change (known steps, plannable in advance) and adaptive change (requires iterating through as understanding develops). Most operational improvements are adaptive, even when organizations treat them as technical.
How are kaizen and kata related? They're symbiotic. Kata reinforces kaizen because kaizen's PDCA cycles work better when practitioners have stronger scientific thinking habits — which kata develops through deliberate practice. Coaching skill develops similarly through the coaching kata. Kata also gives kaizen efforts some strategic direction by embedding the question "what's our long-term direction" into the practice. Kaizen reinforces kata because the cultural permission to experiment, fail, and learn that kata requires is what kaizen cultures already provide. Both methods are based on the scientific method, which means they integrate into existing practice without requiring an organization to dismantle what's already working.
Why is coaching such a big part of the kata framework? Because deliberate practice without coaching doesn't produce habit change at the pace it could. The coaching kata gives the coach a structured set of questions to ask the learner during daily coaching cycles. The learner is doing the improvement work. The coach is helping the learner think more scientifically about it. Both sides develop. The coach also treats coaching as an experiment — what's working, what's not, where can I improve my craft. Michael was explicit that you'll make mistakes as a new coach. You'll ask leading questions, manipulative questions, too many questions, not enough questions. The framework gives you a way to get better at coaching while doing the coaching, rather than studying coaching in the abstract.
Can you practice kata without formal training? Yes. Michael's example of the relocating hospital was an organization with no formal kaizen or kata training that adopted the structural elements of both practices simply by visualizing work, splitting it into weekly target conditions and daily PDCA cycles, and running rapid iteration. The word "kata" never entered the organization's vocabulary. The practice did. Mark added that you can get better as a coach through daily kaizen practice alone, by treating every coaching cycle as an experiment and consistently honing your craft. The kata framework speeds up development, but the underlying habit of treating improvement and coaching as experimental practices is the engine.
What was the barcode medication verification example? A hospital had implemented barcode medication verification technology but compliance was poor. A nursing manager wanted to improve it. Michael coached him through the improvement kata while Michael practiced the coaching kata. Early cycles produced superficial answers — more training, more auditing — that didn't work. After many cycles, the actual root cause emerged: the armbands were washing out, which was a materials management issue rather than a compliance issue. The fix improved patient safety. The larger result was that the nursing manager developed a new mental reflex — when in doubt, take another step rather than assume an answer — that transferred to every problem he subsequently tackled.
What was the patient whiteboard example? A hospital had patient room whiteboards for visual communication that weren't being used effectively. A frontline clinical primary nurse wanted to improve it. Michael coached him through the kata. The early obstacles were unglamorous — markers going dry, boards hard to erase. Working on those obstacles cycle by cycle sent a message that the system was being made easier rather than the staff being blamed. Larger issues emerged — nurses and doctors weren't rounding together, which meant the boards weren't being used collaboratively. The cycles continued. The nurse got stronger at empirical root cause analysis. Michael got better at coaching frontline clinical staff, a population he hadn't coached before. Both sides developed alongside the process improvement.
How does kata integrate with KaiNexus? Michael's reframe of the OI record fields is direct. The proposed solution box becomes the target condition — where you want to be in a few weeks to a couple months. The description box stays as the current condition. The OI tasks panel becomes the iteration space where rapid PDCA cycles are run against obstacles on the way to the target. The platform fields don't change. The interpretation of the fields changes. The kaizen-oriented design of the platform supports the kata practice without modification.
What's the relationship between kata and DMAIC or other improvement methodologies? Different category. DMAIC is a process improvement methodology — Define, Measure, Analyze, Improve, Control. Kata is a practice for developing scientific thinking. The process improvement results that kata produces are almost a byproduct of the cognitive change. Organizations that already use DMAIC, A3 thinking, strategy deployment, daily management systems, or other improvement frameworks can integrate kata principles into those practices without replacing them. The principles plug in. The methodologies stay. The development the kata produces makes everything else work better.
What's the connection to neuroplasticity? Michael referenced the cognitive science of habit change throughout. The brain rewires itself through deliberate repetition. New neural pathways form. Mental muscle memory develops. The improvement kata's design is explicitly to provide the repetition that produces the rewiring. Michael recommended looking for videos on neuroplasticity from other sources, since the cognitive science behind why deliberate practice works is well-developed in the broader literature and worth understanding for anyone serious about the practice.
This transcript has been edited for readability.
Mark Graban: Welcome, everybody, and thank you for joining today's webinar, The Kaizen/Kata Nexus: How a Free Idea Can Be Priceless. I'm Mark Graban, VP of Customer Success for KaiNexus and author of the books Lean Hospitals and Healthcare Kaizen. I'm your host today, and I'm joined by Michael Lombard, our primary presenter.
Michael Lombard: Thank you, Mark. I'm the corporate director of operational excellence for Cornerstone Healthcare Group, a 19-hospital system based in Dallas, Texas. I'm glad to be here to share some of my lessons learned on Kaizen and Kata.
Mark Graban: So nobody thinks I'm being rude, Michael has invited me to interject and play the role of color commentator. Michael is the play-by-play announcer for this journey through Kaizen and Toyota Kata.
Michael Lombard: Here's the agenda. We'll start with the idea that all ideas are not created equal, which sets the stage for the rest of the discussion. Then a quick overview of Kaizen and the Toyota Kata approach, in case you haven't been exposed to them, and, more importantly, how they work together. Because you don't want to hear theory all day, we'll get into two examples from my experience in hospitals: barcode medication verification compliance and patient whiteboards. Then I'll talk about how KaiNexus can be a platform for Kata and Kaizen, and we'll wrap up with how to connect Kaizen and Kata to other components of Lean you may already use.
Michael Lombard: I believe all ideas are not created equal. By that I mean the way we approach improvement matters. It's not just about the result on the process -- did we improve efficiency or reduce cost? That's important, of course, but how we go about it matters too. My hypothesis is that if we approach improvement in a way that has a high intensity of developing our people, which is the horizontal axis on this graph, we increase the overall impact of pursuing that idea.
Michael Lombard: Let me walk through three scenarios. In red, we approach an improvement effort in a way that doesn't really develop our people. Say a vendor comes in and prescribes a technological solution. We'll get some good process improvement, but that's about the extent of the impact.
Michael Lombard: In yellow, we engage staff in tackling the issue, maybe through a quality circle or a rapid improvement event -- a Kaizen event. We get an extra bump from staff engagement, which is incredibly valuable. The esprit de corps and team building from that kind of event enhance the impact. But once the event is over, we're back to business as usual, maybe with a little more bounce in our step.
Michael Lombard: In green, we approach improvement in a way that intensely focuses on developing our people. We get the process improvement and the staff engagement, but we also develop new mindsets. There's a lot of cognitive science about what it takes to change habits and form new neural pathways -- there are good videos on neuroplasticity if you want to learn more. When we approach improvement that way, the overall impact is radically better. So indeed, all ideas are not created equal. My contention is that the green box is where we see the traditional Kaizen approach, and I think Kata also has a role in intensely developing our people.
Mark Graban: Michael asked me to touch briefly on the principles of Kaizen. Kaizen is a Japanese word that translates quite literally as good change, or change for the better. Joe Swartz and I have done a lot of work and writing on this. One key principle is the goal of engaging everybody in improvement. At Joe's health system in Indianapolis, they've reached close to 50 percent participation in a given year -- people submitting, implementing, and documenting at least one Kaizen. Overall, about two-thirds of their employees have participated at least once. Their leadership challenge is getting more people involved and helping them be a little better every day. Not just doing one Kaizen or hitting a target, but making it the culture.
Mark Graban: That's noticeable in some departments at Franciscan St. Francis Health. People love talking about improvement. They point out problems, and that's celebrated instead of punished or covered up.
Mark Graban: Another key difference between Kaizen and suggestion box systems: suggestion boxes ask, "What's your suggestion?" and those suggestions were generally things for other people to implement. Leaders would just approve or reject them. In a Kaizen process, we start by defining a problem or opportunity for improvement, and then we follow the Plan-Do-Study-Adjust cycle, which some people call PDCA. We identify the problem, understand it better, decide what to try, study the effects -- was it really a good change? -- and then adjust. We either document, share, and spread the idea, or go back and try something new to address the problem. Leadership is key to all of that. How do we react when people speak up? Do we collaborate with them and coach them? The energy that comes from leaders at all levels is critically important.
Michael Lombard: That was two minutes and 22 seconds, Mark. Good job.
Mark Graban: I yield my time to the gentleman from Dallas.
Michael Lombard: Now a quick overview of Kata. Mike Rother, out of the University of Michigan, wrote the book Toyota Kata. For years, he studied the secret sauce of organizations like Toyota. How do they develop frontline people who can lead improvement in a methodical, scientific way, and how do they develop coaches who can teach those principles? He came up with principles and techniques that are captured in the book.
Michael Lombard: I'd summarize Kata as the scientific method with direction added to it. A Kata practitioner is always thinking about the long-term direction, then working back from that to the challenge we're trying to achieve in the next six months to two years, then to the target condition for the next couple of weeks or months, and then to the next obstacle to tackle. It's PDCA or PDSA with direction applied to it.
Michael Lombard: Second, it's the scientific method with deliberate practice added. There's a science and technique to deliberate practice that differs from just practice. Deliberate practice speeds up the acquisition of new mindsets -- the rewiring of your brain, so to speak -- and Kata has a whole lot of that built in.
Michael Lombard: The set of routines we perform to lead improvement is called the improvement kata, and I want to point out that it's not just another process improvement technique. I was trained in DMAIC as part of Six Sigma, which is incredibly effective at leading improvement. But the improvement kata isn't designed just to create process improvement. It's designed to create new habits and new ways of thinking. It has a different calling, if you will.
Michael Lombard: Here are the four routines. Nothing fancy here; it's really about the repetition. First, understand the direction or challenge. There's a skill to that. You're not very good at it at first, and your organization may not be very good at strategic planning, but the more you practice, the more strategically you start to think.
Michael Lombard: Second, grasp the current condition. That's nothing new to anyone who has led improvement work the right way, but there's a nuance in Kata. It's a more action-oriented approach, where we do rapid cycles of PDCA just to go and see. We treat going to the gemba, observing a process, collecting data, or mapping a process as a little experiment in itself. It's a more empirical approach to grasping the current condition.
Michael Lombard: Third, establish the next target condition. You can think of that as the bite of the apple we want to take -- where we want to be in the next couple of weeks or a month or two. There's a technique to that, too, which involves treating consensus building, and deciding what performance level to target, as experiments.
Michael Lombard: Fourth, iterate toward the target condition. Once we know our target, there's a series of obstacles we navigate through rapid cycles of PDCA.
Michael Lombard: There's a concept in Kata called the gray zone. We don't assume we know the direct path from the current condition to the target condition, and we don't care. We relish the gray zone because that's the learning zone. We'll take side trips. We'll go in the wrong direction for a cycle or two. But we'll iteratively progress toward the target condition. When you see things that way, it becomes about how fast you can do the next learning cycle. You go from 30-, 60-, or 90-day PDCA pilots to 30-, 60-, or 90-minute cycles. That's a fundamental premise of Kata.
Mark Graban: The gray zone, that fog of uncertainty, reminds me of Ronald Heifetz, a professor at Harvard. He talks about the difference between technical change and adaptive change. A technical change has a definitive path and set of steps -- like swapping out the hard drive in my computer. Follow the steps and you're done. Adaptive changes are more complex, and Heifetz describes iterating your way through them. I'd argue most changes in the workplace are adaptive. We have a direction, or what Kata calls a target condition, and an idea about how to get there, but each step isn't planned out exactly. Heifetz makes the point that organizations err by treating adaptive challenges like technical ones. Any reaction to that?
Michael Lombard: I think that's very well said, and it captures the essence of the mindset we're trying to create through Kata. Again, Kata isn't a process improvement technique or a tool in your toolbox. It's something you do, and the purpose of doing it is repetition that teaches organizations how to navigate the gray zone with an adaptive-change mindset.
Michael Lombard: There's also the coaching kata. While the learner practices the improvement kata, the coach practices the coaching kata, which consists of planning and executing coaching cycles. The more coaching cycles you do, the more you realize that every step is an experiment -- not just for the learner trying to improve a process, but for the coach trying to hone their craft. You become a better coach faster and more scientific in how you coach. Now everyone is practicing the scientific method in one form or another, and that's a powerful cultural shift.
Michael Lombard: Whether you're the learner pursuing the improvement or the coach honing your craft, it's like your brain lifting weights. You're developing what cognitive scientists call mental muscle memory and rewiring your neural pathways.
Michael Lombard: Before you've developed that new mental muscle memory, the temptation is to see Kaizen and Kata as complementary at best or competing methodologies at worst. In fact, they're symbiotic. My hypothesis is that Kata reinforces Kaizen. Kaizen is based on the scientific method, and PDCA cycles go better when people have a strong scientific mindset. Kata develops strong scientific thinkers in a more methodical way, because that's exactly what the improvement kata and coaching kata are designed to do. The process improvement results are almost a byproduct. They're very important, but the design is to provide repetition and deliberate practice to create new mindsets, and that makes your pursuit of Kaizen more scientific and more effective.
Michael Lombard: On the coaching front, if you're coaching your team on Kaizen, you're going to make mistakes. When you first start coaching, it's tough. You ask too many questions or not enough. You ask leading questions that give away the answers or feel manipulative, when you want to become more of a Socratic, scientific coach. The coaching kata gives you a framework to develop that in spades.
Michael Lombard: Practicing Kata also gives your Kaizen efforts some direction and alignment, because there's a routine built into the improvement kata where we seek to understand the direction or big challenge we face. Without a strong strategy deployment system, you might be pursuing what I call point Kaizen -- isolated improvement efforts. Even without a good strategy deployment system, Kata can create some direction and alignment.
Michael Lombard: Flip the coin, and I believe Kata is enabled by Kaizen. When I've gone into organizations to practice Kata where the culture didn't allow for words like experimentation and learning -- where the only concern was results, what you've done to improve cost or efficiency -- you can't go through those rapid cycles of learning. It's very difficult. But if you have a culture built on Kaizen principles, you have fertile ground for practicing Kata and getting better as a learner and a coach.
Michael Lombard: Both methods are based on the scientific method. If you have an existing Kaizen framework that works for you, there's no reason to make wholesale changes to apply Kata principles. You can plug and play. Say you review your idea board in your morning huddle as part of your Kaizen system. You can benefit from a little discussion of the target condition or the overall direction, or from better coaching that comes from practicing Kata. The more you practice Kata and the more you do Kaizen, the more you see they aren't alternatives or merely complementary. Each one needs the other to perform at its highest level.
Mark Graban: I agree there are really helpful ideas in the Kata framework, and Mike Rother's work is great. Kaizen is also a learn-by-doing practice. We can learn a bit up front, but at some point we have to dive in and, hopefully, have someone coaching us. Leaders will make mistakes, and employees will make mistakes. We have to consistently create an environment where we don't punish mistakes. If fear of trying something that doesn't work out is the dominant mindset, people will be super cautious and never attempt to improve. We don't want people doing wildly irresponsible things, and that's where a leader as coach can help, without being horribly bureaucratic and slow like a suggestion box.
Michael Lombard: Exactly. And you can get better as a coach without Kata. If you're doing Kaizen every day and engaging your team, you'll get great repetition, improve your technique, and get good results. Deliberately practicing Kata on top of that may speed up the process. Either way, you can treat every coaching cycle as an experiment, keep honing your craft as a coach, and, as Mark says, lead your people down the right path without doing irresponsible things.
Michael Lombard: The first example is barcode medication verification, or BMV, compliance -- a patient safety practice. At a hospital where I worked, we had the scanners and armband technology, but it wasn't being properly used, and a nurse manager wanted to tackle the issue. Let me run through a couple of ways we could have led this, and then how we actually did.
Michael Lombard: In the red-box approach, we could have had the vendor, CareFusion, come in and give us an audit checklist for increasing compliance. We could have mandated audits and more staff training. That would have been okay. We'd have seen some improvement in compliance, but we wouldn't have done much to develop our people.
Michael Lombard: In the yellow-box approach, we could have formed a unit-based council, had them brainstorm the top 10 ideas, prioritized them with dot voting, and implemented. We'd have come up with some pretty good ideas, probably seen some improvement, and staff would have been encouraged by owning the solutions.
Michael Lombard: We attempted the green-box approach. Honestly, we weren't very good at it. This was very early in my practice of the coaching kata. I was trying to guide this nurse manager as he practiced the improvement kata, and we made a lot of mistakes. We came up with superficial solutions like more training and auditing, the same things we'd have come up with in the red or yellow approach. But by doing cycle after cycle and seeing what didn't work over and over, we developed a mental reflex: let's just take one more step. Eventually, through trial and error, we found something that worked. The armbands were washing out, which traced back to an issue in our materials management purchasing system. We fixed that and saw improvement.
Michael Lombard: Beyond the patient safety improvement, which is incredibly important, this nurse manager developed a new reflex -- a new mental muscle memory -- to always take another step forward. When in doubt, don't assume you know the answer. Go to the gemba, do another PDCA cycle, and see what you learn. That was incredibly powerful for his development, and for mine as a coach.
Michael Lombard: The second example is patient whiteboards. If you've been in a hospital patient room, you know there's typically a whiteboard that can get the nurse, the doctor, other caregivers, and the patient's family on the same page about the plan of care, the anticipated discharge date, and so on. It's a great tool for visual communication, but we weren't using the boards well, so our visual communication wasn't good. A frontline primary nurse who had never led improvement work wanted to tackle it. I was excited, because I had never coached a frontline clinical staff member using the coaching kata. I'd mostly coached supervisors, managers, and directors.
Michael Lombard: Again, there were other ways to approach it. In the red box, we could have taken the Studer Group's evidence-based guidance on patient whiteboards, disseminated it, and audited against it. We'd have seen some improvement, but we wouldn't have gone through the learning cycle. In the yellow box, another unit-based council or a Kaizen event might have engaged physicians and even patient families, which would have been pretty impactful.
Michael Lombard: We took the green-box approach, which promotes the development of new mindsets. This nurse went through cycle after cycle, dealing with many obstacles, and you could see each one as a small opportunity for Kaizen that added up. One thing he worked on was that the markers kept going dry and the board was hard to erase. He tackled little things like that, cycle after cycle, and sent a message to staff: we're not going to assume this is about education and accountability; we're going to make the job easier for you. Those incremental improvements added up.
Michael Lombard: Then he started uncovering bigger issues. For example, the nurse and the doctor didn't round together, so they weren't using the board collaboratively, which led to the board not being used at all. Those are bigger, more complex issues. But cycle after cycle, he got stronger. He saw how he could uncover root causes just by doing another PDCA cycle -- an empirical approach to root cause analysis -- and started to understand why the nurse and doctor weren't rounding together. He was making incremental improvements in Kaizen fashion and developing new mental models for root cause analysis. And as a coach, I was figuring out new ways to coach, because now I was coaching frontline nurses and physicians, which I wasn't very good at. So the green-box approach had additional overall impact, beyond the short-term process improvement.
Michael Lombard: Let me talk about my experience with KaiNexus and how I think it's a great way to do Kata. Greg Jacobson, the co-founder of KaiNexus, based many of its principles on Masaaki Imai's book Kaizen. So Kaizen is baked right into KaiNexus. My first work in Lean and process improvement in healthcare was based on Kaizen principles, so I loved it from the start. When I began experimenting with Kata, I wasn't sure how I'd merge the two. Over time, through experimentation, I realized the KaiNexus platform can be really useful for practicing Kata.
Michael Lombard: In KaiNexus, an opportunity for improvement is called an OI. Traditionally, staff see an issue and are empowered to submit it, maybe from the mobile app, and that creates a workflow. The OI has a description of the problem in the description box and a proposed solution in the proposed solution box. With a small adjustment, you can apply Kata to it.
Michael Lombard: The proposed solution box can be reformatted slightly to become your target condition, which might be a couple of weeks or months away. Along the way, multiple obstacles will arise, and each can be treated as an opportunity for PDCA. The description box holds the current condition. And the OI tasks panel can be used for iteration -- your rapid PDCA cycles aimed at removing obstacles on the way to the target condition. So the overall OI is your pursuit of the target condition, and the tasks panel is the rapid, daily iteration to remove obstacles. It's easy to plug and play KaiNexus with the Kata approach, and it's all based on Kaizen principles.
Michael Lombard: I was going to walk through how I've experimented with Kaizen and Kata alongside A3, strategy deployment, daily management systems, and Kaizen events. To summarize: my experiments have shown that they work very well together. I encourage everyone on this webinar to start experimenting. You're probably already using some of these tools -- A3s, Kaizen events, value stream maps, maybe KaiNexus. Whatever your version of Lean looks like, and it should be specific to your situation because no two Lean transformations look alike, see if you can apply some Kaizen and Kata principles to it.
Michael Lombard: One example is old-fashioned project management, which will always exist: rolling out new technology, building a new factory or hospital. Even that can work well with Kaizen and Kata principles. I worked with a hospital that was relocating from one side of town to the other. That's classic project management, with a big Gantt chart of hundreds of deliverables. Project management devolves into the project manager pestering everyone for updates. If you've been through big projects, you can probably relate.
Michael Lombard: This organization was just beginning its Lean journey and had no formal Kaizen or Kata training. We asked: can we turn all those deliverables into sticky notes and put them on the wall? We drew on a classic Kaizen technique -- make ideas visual and make them flow -- with a visual control board: a column for to-do, a column for doing, and a column for done. Now we were infusing some Kaizen mindset into a traditional project.
Michael Lombard: Then we experimented with applying some Kata thinking. We split the doing column into two: what we're doing this week, which becomes, for lack of a better term, the target condition for the week, and what we're doing today. The big deliverable -- the parent sticky note -- stays in the weekly column, and we pull small daily experiments out of it as child sticky notes in the daily column. That promotes rapid-cycle iteration and gives you far more opportunities to practice coaching and get the repetition you need to rewire your mindset, without ever introducing the word Kata into the organization's vocabulary.
Michael Lombard: Anyone can start experimenting with infusing Kaizen and Kata into whatever version of improvement, Lean, or Six Sigma they use. Again, not every idea is created equal. The way you approach improvement matters. If you experiment with adding some Kaizen and Kata to what you're already doing, you'll see more impact from the ideas that are submitted and implemented. That's how any idea can be truly priceless: when you start to change mindsets, anything is possible. When you have a whole team of people thinking like scientists, you can tackle whatever big challenge comes your way.
Mark Graban: Thanks, Michael. Even though this webinar was free, I hope everyone agrees that some of these ideas are priceless.
Mark Graban: Our first question comes from Justin, and it's a chicken-and-egg question: which should come first, Kata or Kaizen, or both?
Michael Lombard: Great question. I don't think there's a definitive answer. The answer is to experiment and see what works in your organization. In healthcare, I like starting with Kaizen right off the bat, because we can start right now regardless of our coaching competency or how well we understand Kata. Put up an idea board, get a team involved, and start getting repetition. Simultaneously, you might create an advanced team of half a dozen people who start practicing Kata, with coaching provided externally or by an advanced practitioner. Give that team something that connects their efforts across departments -- a value stream future state or an A3 to work on together -- and you'll see their development happen pretty quickly while you're already engaging everyone in simple, straightforward Kaizen. You can do both at the same time and benefit from how they reinforce each other.
Mark Graban: I'd say there's no single answer. You could ask the same question about Kaizen events versus small daily Kaizen, or A3s versus Kaizen. These are mutually beneficial approaches. From my experience -- I was about to call it a bias, and it still could be -- I tend to start with small improvements. That's classic and still-valid advice from Masaaki Imai's book Kaizen: start with the small things and get people engaged. Norman Bodek called this Quick and Easy Kaizen. Some people call them just-do-its. We have to be careful to still build good PDSA habits. Even with the smallest improvement, view it as a test that we study and adjust. Then we build our improvement skills through A3 thinking, more complex Kaizen events, Kata, and other approaches.
Mark Graban: I like starting small and on a small scale rather than saying, "All 5,000 employees, we're starting Kaizen tomorrow." That tends not to be sustainable, because it isn't supported by the proper coaching. People get excited and then it falls off, or bad habits develop. Michael, how does Kata help make sure we're building good habits rather than counterproductive ones?
Michael Lombard: That's a key point. The Power of Habit by Charles Duhigg has great information about how habits form. The author says it's not necessarily about creating new habits out of thin air, but replacing existing ones. You're not working from a blank slate; you're deconstructing an old habit and creating a new one. Kata supports that because it follows the principles of habit building in that book: a cue, a routine, and a reward, repeated over and over.
Michael Lombard: In Kata, the cue can simply be that a coaching cycle is scheduled for tomorrow. Countless clinicians have told me that was one of the most impactful things for them -- knowing that every day they'll do something and come back to report out. It creates accountability, but more intrinsic accountability than outside pressure. The routine is accessible because the improvement kata and coaching kata aren't highly complex and don't require tons of training. It's a learn-by-doing technique you can start right away. And the reward comes from Kata's emphasis that each cycle is aimed at learning, which I believe is a great intrinsic motivator. There's also the mastery that comes from repetition. If you practice your golf swing with deliberate emphasis on certain parts of your technique, you get a little jolt of satisfaction when you see it work. Kata is the same.
Mark Graban: Richard asks: some say Kata is really the pattern of Kaizen, not a different concept. How would you answer that?
Michael Lombard: They're both the scientific method, and both provide the repetition and PDCA cycles you need. If you want to differentiate them, Kata is weighted a bit more toward the deliberate practice side of the scientific method. As I said, you can become a better coach and problem solver without Kata. I just think it provides a framework that emphasizes deliberate practice to help form new neural pathways. So they aren't separate; you're adding more deliberate practice, at least early on. Mike Rother has talked about shu-ha-ri, a Japanese term describing levels of mastery. At the beginning, you practice Kata very deliberately and follow the script to form new neural pathways. Later, you can customize the approach and apply it practically without following the script exactly. That first scripted phase is what differentiates Kata a bit.
Mark Graban: When I read Toyota Kata, it felt familiar in a comfortable way, after about 15 years of practicing Lean, Kaizen, and PDSA. Someone who picks up Toyota Kata as one of their first Lean books may experience it differently. There were helpful ideas I try to apply to my practice of Kaizen, like having some rigor, even scripted questions, to teach people how to coach and how to iteratively close the gap between a current condition and a target condition. But I wouldn't say I practice Kata. Maybe I've already been preaching the word Kaizen. There are helpful ideas to incorporate.
Michael Lombard: Absolutely. The long-term goal isn't to stick to a script and practice something separate called Kata. After a while, it becomes mental muscle memory -- a reflex -- and it melds into your Kaizen system. To me, that's when you're performing at an extremely high level and getting the most out of your approach to Kaizen.
Mark Graban: And I didn't mean to imply that people use the scripting forever. It's a helpful way to get started.
Mark Graban: Another question: could you explain again how KaiNexus supports the green box in your framework, from your experience as a customer?
Michael Lombard: The green box is the idea that if you have a high intensity of people development in how you approach improvement, you get more overall impact. KaiNexus fits there because it's based on Kaizen principles, which means engaging everybody. Whether you work day shift, night shift, or weekends, at any level of the organization, anybody can submit an idea, and the technology facilitates that. That adds intensity to engaging and developing your people. And because it can also be used with deliberate practice and a Kata approach, it allows for more methodical development of people's skills and mindsets.
Michael Lombard: Even if KaiNexus weren't useful for Kata at all, it would still be useful because it lets us engage more and more of our people. It also has metrics that help you track how quickly ideas are acted on, which is worth keeping an eye on. If you emphasize rapid iteration and smaller, daily Kaizen-type improvements, you can measure that in KaiNexus, and that promotes the development of people's mindsets. I'm not a true expert on everything in KaiNexus, but in my experiments, it has provided some nice functionality.
Mark Graban: One thing I'd add, which Greg Jacobson and I have talked about in other webinars: our most successful customers have some formal methodology or combination of methodologies, whether that's Lean, Kaizen, Six Sigma, or Kata. They have enabling technology -- and a board with sticky notes is also an enabling technology. And it requires leadership: mindsets, energy, and time. Our software helps build new habits, but it doesn't magically create them. That's why we have leadership training videos and other ways of educating people about the mindsets, and then the software reinforces them, such as reminding people in an automated way to respond quickly when an opportunity for improvement is entered.
Mark Graban: One more question, from Tracy: isn't one key thing about the improvement kata and coaching kata that they're personal? Kaizen is usually a team activity, but the coaching kata is one-on-one -- one coach helping one learner at a time, even if a team is running improvement experiments together. What are your thoughts?
Michael Lombard: If you practice Kata in the classic one-learner, one-coach way, and you get that repetition and deliberate practice, you start to form a new way of thinking about improvement. Then you can see where that approach can be infused into just about every other improvement venue. Take the ultimate team-based effort, a three-day Kaizen event where the team is excited and making progress. You can infuse rapid-cycle iteration and some Kata principles into that. Same with a quality circle. If you're facilitating one, you'll benefit from having gone through hundreds of coaching cycles with people across the organization. You'll have seen the pitfalls in your coaching -- when you assert yourself too much as a facilitator, when your questions are too leading, or when you don't help the team break a big challenge into smaller target conditions and next experiments. You develop a kind of mental dexterity for facilitating in any setting -- a quality circle, a standup huddle, a Kaizen event -- because of the sheer amount of repetition Kata is designed to provide.
Mark Graban: That brings us to the top of the hour. On behalf of KaiNexus, thank you all for attending, and thank you, Michael Lombard, for sharing your thoughts today. Michael, any final thought for the audience?
Michael Lombard: Great questions. It was an honor to share some of my thoughts today. Everybody, keep experimenting.
Copyright © 2026
Privacy Policy