Watch the webinar here:
When budget pressure hits, the message most operational leaders hear is some version of "we're committed to Lean, just not right now."
Warren Stokes' argument in this webinar is that this is exactly backwards. The conditions that create short-term pressure -- budget gaps, demand shifts, pricing changes, supply chain disruption -- are the same conditions where Lean thinking does its most useful work. The instinct to pause the improvement effort and pivot to command-and-control cost cutting almost always destroys more than it saves. It damages the trust that took years to build, disengages the frontline workers who hold most of the practical knowledge, and produces solutions that are often worse than the problems they were meant to fix.
The session is a practical playbook for leaders navigating that moment. Stokes draws on his background bridging manufacturing, the military, and healthcare to argue for a simpler, more visible, more frontline-engaged version of Lean than the toolkit most organizations reach for under stress.
Warren Stokes served as Director of Process Improvement at HonorHealth at the time of this recording. His background includes manufacturing roles at Pratt & Whitney and Hamilton Sundstrand, service in the United States Air Force, and healthcare improvement work at Cancer Treatment Centers of America. He holds a BS in Aeronautics, Aerospace Science, and Technology from Embry-Riddle Aeronautical University and an MA in Public Administration from Columbus State University.
The host is Mark Graban, then VP of Improvement and Innovation Services at KaiNexus and the author of Lean Hospitals and co-author of Healthcare Kaizen.
The framing problem most leaders face under pressure is the assumption that Lean is something extra -- a strategic initiative that requires time and patience, neither of which feels available when the budget gap is real and the deadline is short.
Stokes rejects the framing. Short-term cost pressure isn't a reason to pause Lean. It's a reason to practice Lean more deliberately. The disciplines that make Lean effective -- understanding the current state, engaging the frontline, focusing on the critical few, removing waste, running rapid cycles of improvement -- are exactly what produces results when the pressure is acute. Setting Lean aside and reaching for traditional cost-cutting (layoffs, across-the-board reductions, capital deferrals) tends to produce short-term financial relief while destroying the engagement and trust that drive long-term performance.
The phrase Stokes uses to capture this: "We can't afford not to be Lean, especially in the short term."
The reframe isn't just rhetorical. It changes how leaders behave in the moment. A leader who believes Lean is for normal times will pull back on improvement work when pressure hits. A leader who believes Lean is the way to operate under pressure will lean into it harder -- and find the cost reductions the organization needs faster than the alternative approach would have.
Stokes lays out a three-layer model of where cost reduction opportunities exist in most organizations. The model is simple, but the implications are significant -- particularly for leaders who are tempted to jump immediately to the third layer.
Layer one: roughly 10% of cost. This is what Stokes calls "fruit on the ground" -- ideas the frontline already knows about. These are improvements that don't require analysis or investigation. The people doing the work see them every day. They've often had workarounds in place for months or years. All that's needed is the willingness to ask, listen, and remove the barriers that have prevented these ideas from being acted on. Stokes is explicit: don't put boundaries around this. Let ideas flow from anywhere in the organization, on any topic. This isn't where you focus the priority list. This is where you open the gates and let the accumulated frontline knowledge come forward.
Layer two: roughly 20% of cost. This is operational risk and waste -- the eight wastes of Lean, plus the time leaders lose to excessive meetings, plus the gaps in daily management that let problems persist. Cost of poor quality alone typically runs around 15% of sales (the data on this comes mostly from manufacturing studies, but Stokes argues the parallel exists in healthcare even if it's been less rigorously measured). Rework, scrap, downtime, defects, and the meetings that consume management time without producing decisions are all addressable here. The work at this layer requires structure -- prioritization, visual management, simple problem-solving tools -- but it doesn't require cross-functional restructuring.
Layer three: roughly 30% of cost. This is process restructuring across departments and value streams. The work that requires understanding customer requirements, mapping handoffs between functions, redesigning workflows that cross organizational boundaries. This is the layer most organizations jump to first, because it's where the big numbers are. Stokes argues this is a mistake. The first two layers produce real impact faster, build the engagement that makes the third layer possible, and reduce the disruption that always accompanies structural change.
The implication for leaders: work the layers in order. Don't skip the easy 10% to chase the harder 30%. The 10% builds the trust and energy that makes the 20% possible, which in turn makes the 30% sustainable.
Before any of the cost reduction work begins, Stokes argues, leadership needs to align on what the actual current state is. This is the move most organizations skip.
The instinct under pressure is to act fast. The data you have feels good enough. The narrative everyone agrees on must be roughly true. Let's just start cutting.
Stokes' counterargument is structural. If the data you're working from has integrity problems -- different definitions across departments, calculations that don't match, exceptions handled differently in different places -- then the cost-cutting decisions you make from it will be wrong. You'll cut things you shouldn't have cut, leave intact things that should have been addressed, and discover the mistake months later when the financial results don't match the projections.
The discipline Stokes recommends: validate the definitions and calculations behind the critical few metrics before acting. If on-time start percentage is 90% at one hospital and 30% at another, find out whether that's a real performance difference or a difference in how each site counts late starts. If turnaround time looks fine but the people doing the work say it isn't, figure out which one is wrong. The work isn't glamorous. It's the foundation that makes everything else accurate.
The phrase Stokes uses: turn data into information. Data is the raw material. Information is data plus context -- the picture that emerges when the puzzle pieces are assembled in a way that lets leaders see what's actually going on. Most organizations have more data than they can use and less information than they need. The leadership work is to fill in the context.
Visualization is part of the discipline. A wall of numbers on a dashboard doesn't help anyone. A visual display that shows the critical few metrics, their trends, and the context around them lets the whole team align around the same picture of reality. This is the move that makes everything downstream possible.
The leadership work in this moment isn't issuing directives. It's creating the conditions where the frontline brings their intellectual capital forward.
Stokes is direct about what kills that energy. Generic phrases ("we need to do more with less," "work smarter not harder") signal that leadership hasn't thought clearly about the situation and is repeating phrases they've heard. Frontline workers translate these phrases instantly: "I've been working smart this whole time, and now you're telling me to work harder?"
What works instead is specificity. Tell the team exactly what the pressure is, exactly which metrics matter, exactly what good looks like, and exactly why the organization is acting now. The clarity doesn't reduce the difficulty of the situation, but it does reduce the anxiety that comes from ambiguity. People who understand the problem can contribute to solving it. People who only know that something is wrong tend to disengage.
Stokes also names a risk that's specific to focused improvement work. When leadership decides to focus attention on a particular department or service line, the people in that area often interpret the focus as targeting. "Why are they looking at us? Did we do something wrong?" Without explicit framing, the focus produces defensiveness rather than engagement. The leadership work is to make the focus visible without making it threatening -- to explain why this area, why now, and why the organization sees the team as part of the solution rather than the source of the problem.
The phrase Stokes uses to capture the leadership move: create the right energy to capitalize on the right energy. The first half is the leadership work -- setting context, framing the challenge specifically, removing the anxiety that disengages people. The second half is what the frontline brings -- the discretionary effort, the institutional knowledge, the practical ideas that produce most of the actual improvement. The first half doesn't produce results directly. It produces the conditions under which the second half can happen.
One of the sharpest practitioner observations in the session is about Lean vocabulary itself.
The standard Lean lexicon -- muda, kanban, heijunka, gemba, kaizen -- is useful when practitioners from different organizations need to communicate. It's a universal language that lets a Lean leader from manufacturing and a Lean leader from healthcare share frameworks and learnings without translating.
Inside an organization, the same lexicon can become a barrier. Frontline staff who haven't been trained in Lean don't hear muda and think "waste." They hear muda and conclude that the improvement team is speaking a language they're not part of. The vocabulary that creates connection between practitioners can create distance from the people whose engagement the program depends on.
The reframe Stokes offers: the language of Lean inside your organization is the language of your organization. "Find the muda" becomes "where is the waste?" "Implement kanban" becomes "let's smooth out the workflow." "Heijunka" becomes "balance the workload." The substance is identical. The accessibility is different.
This isn't a rejection of the Lean lexicon. It's a recognition that the lexicon serves connection between practitioners, not connection between practitioners and the people they're trying to engage. The Cobra Kai analogy Stokes uses lands because it captures the dynamic precisely -- the moment when specialized language becomes a way of marking insiders and outsiders rather than a way of doing the work.
For improvement teams, the implication is operational. Translate the vocabulary into the organization's own language before you use it in coaching, training, or daily conversation. Reserve the standard lexicon for moments when it actually serves communication -- typically with other practitioners or in formal training settings.
The data Stokes references on meeting load is striking: middle managers spend roughly 35% of their time in meetings, senior leaders roughly 50%. This is the baseline under normal conditions. Under short-term pressure, the meeting load typically increases as leadership demands more frequent updates, action plan reviews, and progress check-ins.
The pattern is self-defeating. The organization needs leaders out on the floor solving problems, removing barriers, and engaging with the work. Instead, the pressure produces more meetings, which pulls leaders further from the work, which slows the actual improvement, which produces more pressure for updates, which produces more meetings.
The intervention Stokes recommends: replace meetings with visual management. A team that aligns around a visual board doesn't need a status meeting to know where things stand. A leader who walks the floor and sees the current state firsthand doesn't need a written update. A problem-solving process documented on an A3 storyboard doesn't need a separate report-out.
The phrase Stokes uses: "Make markers, not meetings." The work happens where the work is, with the people who do the work, supported by visual tools that anyone can see and update. The meetings that remain are the ones that genuinely require synchronous discussion -- not the status updates and progress reviews that fill calendars by default.
The session walks through several practical tools that leaders can apply immediately without specialized training.
A prioritization matrix that maps frequency against impact. Where do failures or problems occur often and with high consequence? That's where the focus belongs. Where do they occur rarely or with low consequence? That's where to leave them alone for now. The matrix doesn't require sophisticated statistical analysis -- it requires the discipline to plot the actual data the organization has on the axes that matter.
Visual dashboards that show the critical few metrics. Stokes makes a sharp distinction between a dashboard and what he calls a "crash board" -- a wall of indicators that overwhelms the viewer rather than orienting them. A dashboard focuses on two to four metrics at any given time. A crash board shows everything. The dashboard supports decision-making. The crash board produces confusion. Most organizations operate from crash boards and call them dashboards.
A3 storyboards for visible problem-solving. The discipline of fitting the current state, target state, root causes, countermeasures, and verification onto a single page forces clarity. The A3 isn't really about the paper. It's about the thinking the format enforces. Stokes uses a "feeding the baby" example -- a domestic problem-solving exercise that captures the discipline in a context anyone can recognize. The point isn't that the example is sophisticated. The point is that the framework works on any problem at any scale.
SIPOC (Suppliers, Inputs, Process, Outputs, Customer) for clarifying cross-functional work. SIPOC is fundamental enough to be worth implementing even outside a short-term cost reduction effort. The tool produces alignment between suppliers and customers (whether internal or external) on what's needed, how it's needed, and when it's needed. Stokes argues that communication failures between suppliers and customers are the number one driver of rework, longer cycle times, and processing delays. The SIPOC walkthrough doesn't fix those failures by itself, but it makes them visible -- which is the prerequisite for fixing them.
Two-week rapid PDSA cycles. Don't try to solve everything at once. Scope a chunk of work that can be addressed in two weeks, apply PDSA (Plan-Do-Study-Adjust) to it, verify the result, and move on to the next chunk. The two-week cadence keeps the energy up, produces visible results quickly, and prevents the analysis paralysis that often accompanies bigger improvement efforts.
Several elements of the approach Stokes describes are operationally supported by the platform in ways worth naming.
The frontline idea capture that produces the 10% layer of opportunity is exactly what the platform was designed for. Without infrastructure, the ideas the frontline has been holding for years stay in their heads. With it, the ideas surface, get assigned, get implemented, and get measured. The 60-65% to 80% implementation rates that strong KaiNexus customers achieve depend on the platform's ability to make ideas visible and trackable from submission through completion.
The visual management Stokes argues should replace meetings is supported by the platform's dashboards, status displays, and reporting. The "critical few" metrics that should be visible to the whole team can live in the platform and update automatically as work moves through the system.
The A3 storyboarding for structured problem-solving has direct support in the platform's project templates. Teams running PDSA cycles, value stream improvement projects, or kaizen events can use the same standardized formats Stokes describes, with the additional benefit that the work is captured and searchable across the organization.
The cross-departmental SIPOC work and value stream improvements that constitute the 30% layer benefit from the platform's collaboration features -- assigning collaborators across functions, routing work between departments, and making the cross-functional improvement effort visible to all the affected parties.
The spread of completed improvements across multiple sites or facilities is supported by the platform's broadcast and search capabilities. An improvement implemented at one site becomes a template that other sites can adapt, with the benefit that the original team's learnings travel along with the implementation details.
None of this substitutes for the leadership work Stokes describes. The platform amplifies the practice; it doesn't replace it. But for organizations trying to apply Lean disciplines at scale under short-term pressure, the infrastructure matters. Without it, the work depends on heroic effort from a small improvement team. With it, the disciplines can scale to the entire organization.
Warren Stokes served as Director of Process Improvement at HonorHealth at the time of this recording. His background bridges manufacturing, the military, and healthcare. He worked in manufacturing roles at Pratt & Whitney and Hamilton Sundstrand, served in the United States Air Force, and entered healthcare improvement work at Cancer Treatment Centers of America before joining HonorHealth. He holds a BS in Aeronautics, Aerospace Science, and Technology from Embry-Riddle Aeronautical University and an MA in Public Administration from Columbus State University. Warren is known for translating Lean thinking into clear, accessible language that resonates with both frontline staff and senior leaders.
Why is short-term pressure the wrong time to pause Lean work?
Because the disciplines Lean teaches -- understanding the current state, engaging the frontline, focusing on the critical few, removing waste, running rapid cycles of improvement -- are exactly what produces results when pressure is acute. Pausing Lean and pivoting to traditional cost-cutting (layoffs, across-the-board reductions) typically produces short-term financial relief while damaging the engagement and trust that drive long-term performance. The reframe is simple: short-term pressure isn't a reason to set Lean aside. It's a reason to practice it more deliberately than usual.
What is the three-layer opportunity model and how should leaders use it?
A framework Warren Stokes uses to describe where cost reduction opportunities exist. Roughly 10% is "fruit on the ground" -- ideas the frontline already knows about and can act on with minimal investigation. Roughly 20% is operational risk and waste -- rework, scrap, downtime, defects, and excessive meetings. Roughly 30% is process restructuring across departments and value streams. The mistake most leaders make under pressure is jumping straight to the 30% layer, because it's where the big numbers are. Stokes argues for working the layers in order: the 10% builds the engagement and trust that makes the 20% possible, which makes the 30% sustainable.
What's the difference between data and information?
Data is the raw material -- the numbers, metrics, and measurements an organization captures. Information is data plus context -- the picture that emerges when the puzzle pieces are assembled in a way that lets leaders see what's actually happening. Most organizations have more data than they can use and less information than they need. The leadership work is to validate that the data is trustworthy (consistent definitions, matching calculations, integrity in the reporting), add the context that makes it interpretable, and visualize it in a way that aligns the team around the same picture of reality.
Why does Lean vocabulary sometimes work against engagement?
Because the standard Lean lexicon -- muda, kanban, heijunka, gemba, kaizen -- creates connection between practitioners but distance from people who haven't been trained in it. Frontline staff who hear "muda" don't think "waste." They conclude that the improvement team is speaking a language they're not part of. The reframe is to use the organization's own language for the work itself ("where is the waste?" instead of "find the muda") while reserving the standard lexicon for moments when it genuinely serves communication -- typically with other practitioners or in formal training.
How much time do leaders actually spend in meetings, and what's the implication?
Middle managers spend roughly 35% of their time in meetings under normal conditions. Senior leaders spend roughly 50%. Under short-term pressure, the meeting load typically increases as leadership demands more updates and progress reviews. The pattern is self-defeating -- the organization needs leaders out on the floor solving problems, but the meetings pull them away from the work. The intervention is to replace meetings with visual management wherever possible. The work happens where the work is, supported by visual tools anyone can see and update. The meetings that remain are the ones that genuinely require synchronous discussion.
What's the right cadence for improvement work under short-term pressure?
Two-week rapid PDSA cycles. Scope a chunk of work that can be addressed in two weeks, apply Plan-Do-Study-Adjust (or Plan-Do-Check-Act), verify the result, and move on to the next chunk. The cadence keeps energy up, produces visible results quickly, and prevents the analysis paralysis that often accompanies larger improvement efforts. Each chunk gets its own A3 storyboard for visible problem-solving. The visual tracking lives in the daily management system. The discipline is to keep the work scoped small enough to complete in the cycle, not to take on more than the team can finish.
.svg)
Copyright © 2026
Privacy Policy