Watch the webinar here:
Click the link below to view the slides:
Most organizations start their Lean journey with physical boards, stand-up huddles, and local improvement efforts. The tools work. Visible improvement boards bring the work into the open. Daily huddles build the cadence. Local managers run the day-to-day work, and a small central team supports them.
Then the organization grows. Departments multiply. Sites spread across cities or regions. Improvement work that was visible on one wall becomes invisible to anyone not standing in front of that wall. The boards in active departments fill up; the boards in stalled departments gather dust. Senior leaders trying to see how the whole organization is doing have to walk the floors, ask managers, or wait for monthly reports that arrive weeks after the work happened.
The infrastructure that worked at the scale of a single department or a single facility hits a ceiling. The question that follows is what to do about it.
This webinar is Mark and Greg's working framework for daily Lean management as a system -- not as a tool deployment or a set of meetings, but as the integrated set of practices that make continuous improvement part of how the organization operates every day. The five elements they walk through are not a checklist. They are interdependent components, and the argument is that most organizations get part of the system right and underinvest in the rest.
The session also features two guest contributors: Michael Lombard, then corporate director of operational excellence at Cornerstone Healthcare Group, who applies a Toyota Kata-influenced view to rounding and coaching; and Brian Taber, then manager of the rehab department at Middlesex Hospital, who shares how his five-location department uses KaiNexus to run their daily standup huddles across distributed sites.
Mark Graban is a Senior Advisor to KaiNexus and the author of Lean Hospitals and co-author of Healthcare Kaizen. Greg Jacobson, MD is co-founder and CEO of KaiNexus.
The framing Mark opens with is one Greg returns to throughout the session: Lean is not just tools, and it is not just projects. The diagram from Toyota names three sides of a triangle -- technical methods and tools, the philosophy that underlies their use, and the managerial system that keeps it going on an ongoing basis. The integration is the point. Pick any one side without the others and the result is fragile.
Greg's analogy: a tool is a fad diet, a system is a lifestyle. Organizations that succeed at Lean treat it the way physicians practice medicine -- they get better at it over time, with sustained discipline, supported by coaching. Organizations that treat it as a toolkit deploy tools in pockets, see initial results, and watch those results decay as the underlying management system fails to support the practice.
Two books worth knowing if you're working in this space. David Mann's Creating a Lean Culture (now in its third edition, with healthcare and other-industry examples) is the foundational text on Lean as a daily management discipline. Kim Barnas's Beyond the Wall of Resistance and her work documenting ThedaCare's management system in Beyond Heroes offer detailed views of how one health system built their management infrastructure piece by piece. Both books cover the same territory the session walks through, with deeper development.
The first of the five elements is strategy deployment, also called hoshin kanri or policy deployment. The Japanese term translates roughly as "management compass" -- the work of aligning the entire organization around a small set of true-north objectives.
The mechanic is catchball. Senior leaders identify a small number of true-north categories, typically four or five. Common ones in a health system: safety, quality, people, finance, customer experience. Within each category, specific submeasures are chosen for the year -- this year's safety measures might be falls and infection rates, while next year's might be different submeasures depending on what's been improved and what new priorities have emerged.
The objectives are not handed down. They go back and forth between levels of leadership. Senior leaders propose, the next level responds with what they think is realistic, what resources they need, what constraints they see. The conversation continues until alignment is real, not just nominal. The result is an organization where every department's improvement work connects to overall priorities rather than each team optimizing locally without reference to the whole.
Greg's frame for why this matters: most organizations have a mission statement that lives at the level of abstraction. Strategy deployment is the work of translating "we provide great healthcare to our community" into specific metrics that can actually be improved, in ways that connect to what individual departments and individual people do day to day.
A balanced view matters. Twenty or thirty years ago, finance was the only metric many organizations tracked. The result was organizations that improved their financial numbers while patient experience, safety, and staff engagement deteriorated. Strategy deployment with four or five true-north categories forces a more balanced view, which produces a more balanced organization.
The second element is what gets called rounding in healthcare, gemba walks in Lean vocabulary, or process audits in some operational excellence frameworks. The word "audit" sends chills, which is part of why the practice often gets misunderstood. Done well, it's not policing. Done badly, it's exactly that, and the bad version actively undermines the work it's supposed to support.
The reference point Mark uses is Gary Kaplan at Virginia Mason Medical Center, who tours the hospital daily looking for problems and opportunities. The behavior matters more than the title. Kaplan isn't auditing in the sense of catching people doing things wrong. He's modeling the behavior of being at the gemba, asking questions, trusting the people who do the work, and treating problems as opportunities rather than as occasions for blame.
The contrast Mark draws is between the cop and the coach. The cop goes out looking for violations and writes people up. The coach goes out looking for understanding and asks questions. The cop creates a culture where staff hide problems and sweep them under the rug. The coach creates a culture where staff surface problems because surfacing them produces help rather than punishment. Lean improvement needs the coach version. Without it, the organization's improvement system trains people to be invisible.
Michael Lombard's contribution at this point is the sharper version of the same idea: every rounding event should be treated as an experiment. The hypothesis is that you expect to find abnormalities -- some related to training gaps, some related to process barriers, some that turn out to be unsanctioned innovations that haven't been captured yet. Treating rounding as an experiment puts the leader in a frame of mind that is collaborative and proactive rather than checking-the-box or catching-people-wrong.
This is the Toyota Kata framing applied to leader behavior. The discipline is in the mindset. The rounding produces useful information not because the leader is skilled at finding flaws, but because the leader walks in expecting that abnormalities exist and the work is to understand what they mean and what they require.
The visual management piece extends this. A nurse rounding clock outside every room -- a simple analog device that resets when rounding is completed -- gives the team and leadership a real-time signal about whether the rounding standard is being met. White clocks down a hallway tell a story. The story might be that rounding isn't happening, or that it's happening but the clock isn't being reset. Either way, the visible signal prompts the conversation. Without the visual, the team and the leader both have to guess.
The third element is metrics, with a specific argument: monthly metrics arriving weeks late from a central group are too slow and too disconnected to drive improvement behavior at the frontline.
The pattern Mark describes is common. The team gets August's numbers in October. The numbers come from finance or quality or a central analytics group. They show up on a wall down the hall from where the work happens. The team can't connect them back to specific days, specific decisions, or specific problems. The result is a metric that gets reviewed in a monthly meeting and forgotten the rest of the time.
The alternative is daily or weekly metrics that the team itself tracks, visible at the workplace, tied directly to the team's daily decisions. Turnaround times in a lab. First-pass yield in a manufacturing cell. Patient satisfaction scores by shift. The metric becomes the score during the game, not the after-action report. The team adjusts in real time rather than reading about their performance after the period has ended.
The caveat is statistical literacy. Reacting to every up and down treats noise as signal and produces tampering. The discipline is to notice when there's a meaningful pattern -- a sustained shift, a clear trend, a point outside the control limits -- and ask the question then. The metrics don't replace judgment; they prompt better questions.
The leadership posture that goes with this is the same coach-vs-cop distinction. The cop uses metrics to identify who failed. The coach uses metrics to identify what process needs improving. Pressuring people to make the numbers tends to produce two outcomes: gamed numbers or burnout. Working on the process that produces the numbers produces sustained improvement.
The fourth element is Kaizen as continuous improvement, in the original Masaaki Imai sense: not just events, not just projects, but everybody improving everywhere every day. The events have a role. So do the projects. But the volume of improvement in an organization with a real Kaizen culture comes from the small daily ideas that accumulate.
The patterns the session illustrates are familiar to anyone who has run an improvement program. A nurse notices that patients keep asking for ginger ale for nausea but the unit doesn't stock it. The fix is small -- talk to dietary, get ginger ale on the unit, save staff trips to another floor, improve patient satisfaction. The idea is not going to win an industry award. But it's real, and the team that comes up with hundreds of ideas like this accumulates more impact than the team that runs four high-profile Kaizen events a year.
Michael's second contribution here is worth pulling out. He names three benefits of daily Kaizen practice. The first is the obvious one -- process improvement. The second is developing people as problem-solvers. The third, less obvious, is that every Kaizen cycle is also an opportunity for the coach to practice. The coach treats each coaching interaction as an experiment in technique: did this question land, did this just-in-time teaching moment connect, did this intervention develop the thinking I wanted to develop? The discipline of treating coaching itself as a Kaizen practice is what builds coaching capability over time. Without it, leaders coach the same way for years without ever getting better at it.
The physical board pattern works at the local team level. Mark walks through what these typically look like -- problems on the left, in-progress in the middle, completed on the right, with simple writeups documenting what was tried and what was learned. The challenges that emerge as the practice grows are predictable. Local boards are invisible to anyone not standing in front of them. Distributed teams can't share ideas across locations. Tabulating impact across many teams becomes a manual project. Senior leaders can't see at a glance which areas of the organization are healthy and which need support.
This is where the system question becomes practical. The physical board is a tool. The Kaizen practice is a methodology. The leadership behaviors are a management discipline. None of these scale without infrastructure that makes the work visible across the organization.
The fifth element is the daily huddle -- short, standup, structured meetings that synchronize the team around performance, problems, and improvement work.
The pattern Mark describes: 10 to 15 minutes, standing rather than sitting (so the meeting doesn't drift), rotating leadership (so it doesn't become the manager's monologue), standard agenda (so the format becomes habitual rather than reinvented each day). A typical agenda starts with a safety topic to set the tone, then reviews the previous day's performance against key metrics, then addresses problems and improvement ideas, then closes with priorities for the current day.
The huddle is where the rest of the system comes together. The metrics from element three get reviewed. The improvements from element four get visible. The strategic priorities from element one get reinforced. The rounding observations from element two get discussed. Without the huddle, the other elements operate in isolation. With it, they become a coherent management practice rather than a collection of activities.
Brian Taber's contribution illustrates what this looks like in practice at a distributed department. His rehab team at Middlesex Hospital operated across five locations. Each location had its own work, but the improvement work had been local and invisible to other sites. The team had used physical Kaizen boards, then moved to shared drives, and hit limits on both. When the team adopted KaiNexus, they reorganized their morning huddle around a digital dashboard where each location could see what the others were working on, where outstanding items were stuck, and where they could collaborate across sites.
Brian's specific example was a redesign of the department's front-office process. The redesign had multiple components -- tracking physician note authorizations, building alerts into a scheduling system that didn't have them, restructuring patient form distribution. The platform let the team manage all of these as connected pieces of a larger initiative rather than as separate threads of work. The huddle had a shared visual reference. Cross-site collaboration became possible because the work was visible to everyone, not just the team that originated it.
A useful framing late in the session, attributed to Kevin Tousey at the University of Michigan Health System: visual metrics without team huddles and gemba walks turn into wallpaper that nobody looks at, while huddles and gemba walks without visual metrics become social events.
The point is that the five elements are not independent. Pick any subset and the practice drifts. Strategy deployment without daily management produces alignment on paper that doesn't show up in daily decisions. Daily huddles without metrics become discussions without data. Metrics without huddles become reports that pile up unreviewed. Rounding without metrics or huddles becomes a check-the-box exercise. Kaizen without strategy deployment becomes scattered improvement that doesn't accumulate.
The argument is for the system, not for any single element. The temptation to start with one element and ignore the others usually produces the predictable result: the program works for a while, then stalls, then gets replaced by the next initiative. The system version is harder to install. It's also what actually sustains.
The structural argument throughout the session is that daily Lean management at scale needs infrastructure to support the practice without replacing it.
Strategy deployment in the platform means every piece of improvement work can be tagged to the strategic initiative it supports. Leaders can see at a glance whether activity is balanced across the true-north categories or skewed toward one. The conversation about whether resources are deployed against the right priorities becomes a data-supported conversation rather than an impressions-based one.
Rounding and gemba walks become more useful when the leader is walking with the organization's improvement work at their fingertips -- able to capture a problem on the spot, search whether anyone else has worked on something similar, and respond to staff questions with real information rather than promises to check later. The mobile and tablet access matters because the work happens at the gemba, not at the desk.
Metrics live in the platform at every level of the organization. Departments have their own run charts. Work groups have theirs. Senior leaders can see all of them without depending on someone in each department to email an Excel file. The visibility supports the daily review without creating manual reporting work.
Kaizen at scale requires the spread mechanism that physical boards can't provide. An idea implemented in one department becomes searchable and adaptable by other departments. The patient call-light caddy example, the ginger ale on the unit example, the front-office redesign example -- all of these become learning that the next team can build on rather than rediscover.
Daily huddles become a digital-friendly practice rather than a location-dependent one. Brian's rehab department running five-location huddles is a concrete example. The same mechanism scales to enterprise-wide huddles for organizations whose work doesn't happen in a single building.
None of this replaces the management discipline. The platform supports the practice; it doesn't substitute for it. The argument is that the practice and the platform together produce something neither produces alone.
Mark Graban is a Senior Advisor to KaiNexus and an internationally recognized Lean consultant, author, and speaker. He is the author of Lean Hospitals and co-author of Healthcare Kaizen, and has worked extensively in healthcare and other industries to strengthen improvement culture and leadership practices.
Greg Jacobson, MD is co-founder and CEO of KaiNexus. A practicing emergency physician before founding the company, he has focused on the science of organizational culture, habit formation, and the systems that make continuous improvement sustainable at scale.
Michael Lombard served as corporate director of operational excellence at Cornerstone Healthcare Group at the time of this recording. His work emphasizes the application of Toyota Kata-influenced coaching to daily management practices including rounding and gemba walks.
Brian Taber served as manager of the rehab department at Middlesex Hospital at the time of this recording, where he led the deployment of KaiNexus across the department's five locations for daily huddle management and improvement tracking.
What is daily Lean management?
Daily Lean management is the integrated set of practices that make continuous improvement part of how an organization operates every day, rather than something that happens during periodic events. The five elements Mark and Greg walk through are strategy deployment, leader rounding and gemba walks, performance metrics that drive behavior, Kaizen as everyone-everywhere-every-day improvement, and daily huddles that synchronize the team. The argument is that these elements work as a system. Picking and choosing among them tends to produce drift back to the previous state.
What is strategy deployment and why does it matter?
Strategy deployment is the work of translating organizational mission and strategy into specific measurable objectives at every level of the organization. The Japanese term is hoshin kanri, which translates roughly as "management compass." Done well, it produces alignment -- every department's improvement work connects to overall priorities, rather than each team optimizing locally without reference to the whole. The mechanic is catchball, a back-and-forth conversation between levels of leadership about what's realistic, what's needed, and what constraints exist. The objectives aren't handed down; they're negotiated until alignment is real.
What's the difference between a gemba walk and an audit?
The difference is in posture, not in what gets observed. An audit is policing -- the leader is looking for violations, and the consequence of finding one is punishment for the person who made the mistake. A gemba walk in the Lean tradition is coaching -- the leader is looking for understanding, and the consequence of finding a problem is collaborative work on the underlying process. The same activity (walking the floor, observing the work, asking questions) produces opposite cultural effects depending on which posture the leader brings. The audit posture trains people to hide problems. The gemba walk posture trains people to surface them.
Why do monthly metrics fail to drive improvement?
Because they arrive too late and too far from the work to prompt action. A team that gets August's numbers in October can't connect the data to specific days, specific decisions, or specific problems. The metric becomes something to review in a monthly meeting rather than something that drives daily behavior. Daily or weekly metrics, tracked by the team itself and visible at the workplace, function as the score during the game -- the team adjusts in real time rather than reading about their performance after the period ends. The caveat is that the team needs the discipline to react to meaningful patterns rather than to every up and down.
Why does Kaizen need to be daily rather than event-based?
Because most improvement happens in small ideas that accumulate, not in large breakthrough projects. Kaizen events have a role -- they're appropriate for cross-functional or complex problems. But the volume of improvement that produces a culture comes from the dozens or hundreds of small ideas that frontline staff identify and implement in their own work. Without the daily practice, the organization depends on a small number of events for all of its improvement, which is expensive, slow, and exhausting for the people who run the events. With the daily practice, the events become punctuation rather than the entire program.
Why do daily huddles fail when they fail?
Most often because they drift. The standard agenda becomes informal and then disappears. The cadence slips from daily to a few days a week to whenever the team feels like it. The standup becomes a sit-down and then a long meeting and then a meeting people skip. The metrics being reviewed stop being current. The improvement ideas being discussed stop getting tracked. The huddle becomes one more thing on the calendar rather than the cadence that holds the rest of the management system together. The discipline is in the structure -- short, standing, standard agenda, every day, with the rest of the system visible in the room.
.svg)
Copyright © 2026
Privacy Policy