The question most organizations ask about continuous improvement is "what should we do?"
Jeff Roussel's argument in this session is that the question is in the wrong order. Before deciding what to do, an organization needs to know why it's pursuing improvement at all -- and before getting to what, it needs to figure out how it will practice. Skip either of the first two questions and the tactics that follow will be brittle. Programs collapse not because the techniques were wrong but because the foundation underneath wasn't built.
Jeff is unusual among presenters in this library. He's not a Black Belt. He's not a certified Lean practitioner. He says explicitly that the only belts he has hold up his pants. What he has instead is a particular vantage point: as the head of sales for KaiNexus, he's spent years talking with thousands of organizations about where their improvement work is breaking down, what they've tried, and what's keeping them stuck. That vantage point produces a diagnostic framework that travels well across industries and maturity levels.
This webinar walks through that framework. It opens with why continuous improvement matters (the substantive case, not the slogan), moves into how to practice it (the leadership behaviors, processes, and technology that make practice possible), and closes with what to focus on (the five organizational priorities that distinguish world-class CI programs from average ones).
Jeff Roussel served as VP of Sales at KaiNexus at the time of this recording and is currently Chief Revenue Officer. The session is hosted by Mark Graban, then VP of Improvement and Innovation Services at KaiNexus and the author of Lean Hospitals, Healthcare Kaizen, and The Mistakes That Make Us.
Jeff opens with a reference to Simon Sinek's Start With Why and applies it directly to continuous improvement. The argument: most organizations that say they're "doing Lean" can't actually articulate why they're doing it. If you press them, the answer often dissolves into generalities about efficiency or quality. Without a clear answer to why, the program is vulnerable to the first serious headwind.
The why that Jeff returns to repeatedly is a particular belief about how organizations work. The traditional model of management is command-and-control: managers tell employees what to do, then make sure they do it correctly. The alternative model is collaboration: managers ask employees what needs to happen next, and employees figure out how to improve the work they're doing.
The phrase Jeff uses to capture this: "Every employee in an organization should have two jobs -- they should do their work, and they should improve their work."
If an organization doesn't believe this, no amount of Lean tools will produce a Lean culture. If it does believe this, the tools become useful because they're serving an underlying commitment that's already in place.
The business case for the why is also real, and Jeff doesn't shy away from it. Toyota's earnings before interest and taxes per vehicle sold has historically run substantially above other major auto manufacturers -- a pattern that's been visible for decades and that points to something durable about how Toyota operates rather than a temporary advantage. Mark adds context from his own experience at General Motors in the early 1990s, where a Toyota-trained plant manager arrived at a struggling facility and helped create the culture that produced the turnaround.
The deeper point Mark surfaces: improving quality leads to better financial results. This is different from the traditional cost-cutting view that dominates many industries. The traditional sequence is "cut costs, then quality will follow." The Toyota-influenced sequence is the opposite: "improve quality, and costs will follow." Organizations that get the sequence backward tend to damage the engagement and process discipline that produce sustained results.
Jeff makes a sharp move on the second question. The standard framing is "how do we become Lean?" Jeff rejects the question. "Become" implies a destination -- some state of being-Lean that you eventually arrive at. The reality is that Lean is practiced, not achieved. Organizations that get good at improvement are organizations that practice it daily.
The reframed question: how do we practice Lean? And the answer Jeff provides is grounded in the Golden Triangle -- a business school concept that maps cleanly onto continuous improvement.
The three components of the Golden Triangle, applied to CI:
People -- the leadership behaviors that make improvement possible.
Process -- the improvement processes and methodologies the organization uses.
Technology -- the enabling technology that supports the practice at scale.
Jeff is explicit that all three are required. Organizations that focus only on tools and methodologies, without addressing leadership behaviors, end up with technically correct programs that nobody participates in. Organizations that focus only on leadership culture, without disciplined processes, produce enthusiasm without results. Organizations that focus only on technology produce expensive suggestion boxes that decay over time.
The diagnostic move Jeff offers: when an improvement program is struggling, the question isn't "do we have problems?" The question is "where are the problems concentrated?" The Golden Triangle gives a structured way to answer it.
The first area Jeff drills into is leadership behaviors. The pattern he sees across organizations that have built real improvement cultures is consistent enough to be diagnostic.
Commitment. Lean cultures don't happen by accident. Like any meaningful personal change -- losing weight, building a new skill, breaking a bad habit -- the choice to commit comes first, and the commitment is what carries the organization through the inevitable obstacles. Jeff notes that this commitment doesn't have to come from the CEO. It's stronger if it does, but a director, a team leader, or a department head can make the commitment for their own group and still produce real results within their scope. What can't happen is for the commitment to be absent. Without it, the first serious headwind ends the program.
Communication. If improvement is genuinely a priority, it shows up in how the organization talks about itself. Mentions in every leadership meeting. References in emails. A cadence of conversations that doesn't depend on quarterly review cycles or annual reports. Jeff's diagnostic test: is improvement showing up in the routine communication of the organization, or only in the formal occasions? If it's only the formal occasions, the organization is signaling that improvement is a special event rather than how the work gets done.
Resources. Leaders who are serious about improvement give their people the bandwidth to participate. This doesn't mean 40 hours a week for everyone -- most organizations can't sustain that and don't need to. But thousands of people doing improvement an hour or two a week requires that the hour or two actually exists. Leaders who tell their teams to do improvement but won't protect the time for it are giving instructions that can't be followed.
Accountability. If improvement is a goal, leaders and staff need to be accountable for their participation in it. Not in a punitive way -- accountability and punishment are different things -- but in the sense that participation in improvement is part of how performance is evaluated. Without accountability, the people who care about improvement do it and the people who don't, don't, and the program runs on the discretionary effort of a small number of believers.
These four areas function as a diagnostic. An organization that's weak on any one of them will struggle to build a sustainable improvement culture, regardless of how good the tools and processes are.
Jeff offers a practical list of leadership behaviors that strengthen a Lean culture. The list is structured as actionable habits rather than aspirational principles.
1. State your belief in continuous improvement. Frequently. In writing. In meetings. The team can't read the leader's mind. If improvement matters, it needs to be said out loud, regularly enough that the team understands the leader's position is durable rather than situational.
2. Tell the team why improvement is important. Tie it to organizational strategy and tie it to the individual. Improvement that's framed only at the strategic level feels abstract. Improvement that's framed only at the individual level feels disconnected from the mission. Both framings matter.
3. Participate in improvement yourself. This is the most commonly violated behavior. CI teams that train others to do improvement work but don't improve their own processes signal that improvement is for other people. Leader standard work doesn't need to be elaborate, but it needs to be visible.
4. Spend time where the work happens. Jeff uses "the workplace" rather than "gemba" because the Japanese term sometimes intimidates teams that aren't classically trained. Whatever you call it, the principle is the same: leaders need to be physically present where the work is happening more often than they think. The amount that feels like enough is usually not enough.
5. Ask for opportunities for improvement -- often. If leaders don't ask, the team often doesn't volunteer. The asking is a daily or weekly practice, not a quarterly event.
6. Respond quickly when ideas come in. Slow response is worse than no asking, because slow response teaches the team that their input doesn't matter. The asking creates the expectation. Failing to respond destroys the trust the asking built.
7. Set a goal to implement something. Not everything has to be implemented, but the team needs to see that some ideas turn into action. The smaller changes -- signage, layout adjustments, communication tweaks -- often produce more engagement than waiting for the big idea.
8. Help create time for action. This goes back to the resources question. Leaders who say improvement is important but don't protect time for it are setting their teams up for failure.
9. Teach basic problem-solving. Jeff is specific that this doesn't mean turning everyone into Black Belts. Most frontline staff need PDCA or a simple structured approach. The mistake Jeff sees most often is over-complicating the methodology and losing the masses in pursuit of training a small number of experts.
10. Teach people to identify waste in the language of their work. Lean vocabulary (overproduction, motion, transportation, waiting) is useful for trained practitioners but creates a barrier for untrained staff. The reframe: help people identify waste in the terms they use about their actual work, not in the terms a Lean textbook would use.
The list is practical enough to be applied next week. Jeff is explicit that any leader struggling with their improvement program could do worse than ringing the daily bell around these ten behaviors.
The second leg of the Golden Triangle is improvement processes and methodologies. Jeff is agnostic about which specific methodology an organization adopts. Lean works. Six Sigma works. Lean Six Sigma works. A3 thinking works. Homegrown methodologies work. What separates programs that succeed from programs that struggle isn't the methodology itself -- it's how the methodology is implemented.
The four principles that distinguish strong processes from weak ones:
Simple. If frontline staff find the process complex, they disengage. Jeff's example: an organization that asks employees to fill out a 27-field form with four required checkboxes before they can submit an idea. The form is well-intentioned -- the organization is trying to capture enough context to act -- but the form itself becomes the barrier. Submissions drop. The data the form was designed to capture stops arriving because the form prevents the submissions from happening in the first place.
Consistent. When different groups within the organization use different processes, the cost is real. Reporting becomes harder because the data structures don't align. Cross-functional improvement work becomes harder because each function operates from a different playbook. New employees joining the organization have to relearn the system every time they move between groups. Consistency doesn't mean uniformity at the lowest level of detail -- groups can customize within a standard frame. It means the foundational structure is shared.
Disciplined. Lean processes require cadence. The organization needs to be meeting to talk about improvement on a regular schedule -- not once a quarter, not when something breaks. The discipline of regular review is what keeps the work moving rather than stalling.
Organized. Disorganized processes -- documentation scattered across systems, completed improvements that nobody can find, project status that lives in different places for different teams -- produce disengagement. Staff who can't find what they need stop looking.
The diagnostic move: if your improvement program is struggling and the leadership behaviors look reasonable, the problem may be process. Look at simple, consistent, disciplined, organized, and figure out which one is weakest.
The third leg of the Golden Triangle is the one Jeff handles most directly. The Lean community sometimes treats technology as a distraction from "real" improvement work -- a position Jeff names and pushes back on. The Golden Triangle has three sides for a reason. Organizations that ignore technology can build improvement culture at small scale, but they hit ceilings that the other two legs can't break through.
The specific problems technology addresses:
Visibility. If leaders can't see what improvements are happening across the organization, and if employees can't see what their coworkers are doing, the program is operating blind. Visibility problems produce slow decision-making, duplicate work, and uncertainty about whether to voice ideas at all.
Collaboration. Same-room collaboration works fine. Cross-departmental and cross-site collaboration is structurally harder. Different shifts, different geographies, different time zones all introduce friction that physical artifacts can't bridge. Technology removes the friction without removing the collaboration itself.
Standards. Templated formats, consistent workflows, and standardized reporting are easier to enforce in software than on paper. Standardization isn't about restricting creativity -- it's about creating the shared structure that lets the program scale without breaking down into a dozen incompatible local systems.
Knowledge sharing. When completed improvements live in folders that nobody opens again, the organization loses the institutional learning. The next team that hits the same problem starts from scratch. Searchable, accessible knowledge repositories convert one-time learning into permanent assets.
Impact. Visible impact tracking -- both for individual employees and for the program as a whole -- reinforces the engagement that produces future improvements. Programs that can't articulate their impact struggle to maintain support during budget pressure. Programs that can demonstrate aggregate value across categories (cost, quality, safety, satisfaction, time) defend themselves easily.
Jeff's diagnostic question for each: "Do I have a visibility problem? A collaboration problem? A knowledge-sharing problem?" If the answer to any of these is yes, the question of whether technology can help becomes a real one rather than a religious one.
The final framework Jeff offers is about where leaders should concentrate their attention if they want to build a strong improvement culture from end to end.
Bottom-up improvement. The day-to-day capture of ideas from the people doing the work. The "three-foot radius" framing some KaiNexus customers use captures this well -- identify what frustrates you within three feet of where you actually work, and start there. Bottom-up improvement produces high volume, builds engagement, and surfaces problems that leaders can't see from their offices.
Top-down improvement. Bigger, structured projects that require cross-functional coordination, capital investment, or strategic focus. Top-down isn't a contradiction of bottom-up -- both have their place. Bottom-up handles the daily work of getting better. Top-down handles the projects that benefit from concentrated attention and resources.
Strategy deployment. The mechanism that connects daily improvement work to organizational strategy. Hoshin kanri, the X-matrix, or other strategy-deployment frameworks all serve the same function: making sure that the improvement work people do every day is aligned with what the organization is trying to accomplish.
KPIs. The measurement discipline that tells you whether the improvement work is producing the results it's supposed to produce. If improvement activity is high but the metrics aren't moving, either the wrong metrics are being measured or the improvements aren't addressing the real problems.
Continual learning. Training, development, and the ongoing investment in capability building. Jeff is explicit that even though he isn't a Black Belt, he doesn't dismiss the value of training. Building the masses up to a baseline level of competency in basic problem-solving is part of what makes the rest of the program work.
The five areas operate together. Strong bottom-up improvement without strategy deployment produces lots of activity that isn't aligned with what matters. Strong strategy deployment without bottom-up improvement produces aligned activity that doesn't have the volume to compound. Strong KPIs without continual learning produce measurement without the capability to act on what's measured. The areas need each other.
The session is more direct about platform support than most webinars in your library because Jeff is positioning the technology leg of the Golden Triangle explicitly. A few connections are worth naming.
The visibility problem -- not knowing what improvements are happening across the organization -- is what KaiNexus was designed to solve at its core. The platform makes improvement work visible across departments, sites, and levels in a way that physical boards and spreadsheets can't.
The collaboration support enables cross-departmental and cross-site work without the friction that distance introduces. Improvements that affect multiple teams can route work between collaborators automatically, with notifications and updates flowing to everyone involved.
The standards layer comes through workflow templates, status definitions, and reporting formats that the organization can customize within a consistent framework. The standardization doesn't restrict creativity at the local level -- it provides the structure that lets local creativity aggregate into organizational learning.
The knowledge repository functionality turns completed improvements into searchable, permanent assets. A team starting work on a problem can find every related improvement ever attempted, anywhere in the organization, in seconds.
The impact tracking covers the full range of categories that matter -- cost savings, revenue generation, quality improvements, safety outcomes, time saved, satisfaction gains -- and aggregates the data across departments, sites, and time periods without manual rollup work.
None of this substitutes for the leadership behaviors and process disciplines Jeff describes. The platform amplifies the practice; it doesn't replace it. But for organizations whose improvement work needs to operate at scale, the infrastructure matters in the same way that any other operational infrastructure matters. You don't run an enterprise on email and spreadsheets indefinitely. Eventually, the work outgrows what the available tools can support, and the choice is to upgrade the tools or accept the ceiling.
Jeff Roussel served as VP of Sales at KaiNexus at the time of this recording and is currently Chief Revenue Officer. His vantage point -- speaking with hundreds of organizations every year about their improvement journeys -- gives him an unusually broad view of what works and what doesn't across industries and maturity levels.
Mark Graban is Senior Advisor at KaiNexus and the author of Lean Hospitals, co-author of Healthcare Kaizen, and author of The Mistakes That Make Us. He has worked with organizations across healthcare, manufacturing, and service industries to build cultures of continuous improvement grounded in respect for people.
Why does Jeff argue that "becoming Lean" is the wrong question?
Because "become" implies a destination -- a state of being-Lean that you eventually arrive at -- and the reality is that Lean is practiced, not achieved. Organizations that get good at improvement are organizations that practice it daily and keep practicing it. The reframe matters because it changes what leaders look for. Leaders chasing "Lean" as an endpoint tend to declare victory prematurely or get discouraged when the work doesn't end. Leaders practicing Lean accept that the work is ongoing and build the disciplines that sustain practice over time.
What is the Golden Triangle and how does it apply to continuous improvement?
A business school concept that maps three components onto any business system: people, process, and technology. Jeff applies it specifically to CI. People becomes the leadership behaviors that make improvement possible. Process becomes the improvement methodologies the organization uses. Technology becomes the enabling infrastructure that supports practice at scale. All three are required. Organizations that focus on only one or two of the legs produce programs that look complete from one angle but break down from another. The diagnostic value of the framework is that it makes the source of problems easier to locate.
What are the four aspects of great Lean leadership?
Commitment, communication, resources, and accountability. Commitment is the choice to make improvement a priority, sustained through obstacles. Communication is the routine, ongoing conversation about improvement in everyday work rather than only in formal review sessions. Resources is the protected time and bandwidth that lets staff actually participate. Accountability is the recognition that participation in improvement is part of performance, not optional discretionary effort. An organization weak on any of these four will struggle to build a sustainable improvement culture regardless of how good the tools and processes are.
Why does Jeff prefer simple problem-solving methods over Black Belt training for most staff?
Because most frontline staff don't need to be Black Belts to participate effectively in continuous improvement. The mistake Jeff sees most often is over-complicating the methodology in pursuit of training a small number of experts, which leaves the masses behind. Simple methods -- PDCA cycles, basic root cause questions, the four-step capture/implement/measure/share cadence -- are enough for most situations. The advanced techniques have their place for genuinely complex problems, but treating every improvement as if it requires advanced methodology produces a program that nobody but specialists can participate in.
How should leaders identify waste in a way that engages frontline staff?
In the language of the work, not in the language of Lean. The eight wastes are useful for trained practitioners, but terms like "overproduction" or "muda" create distance for staff who haven't been trained in them. Jeff's example from sales: instead of asking the team to identify overproduction, ask them what's causing delays in their actual work -- waiting for approvals, missing referrals, conversations with people who aren't decision-makers. The substance is the same. The accessibility is different. Staff can engage with problems they recognize in language they use every day.
What's the right way to think about quotas or targets for improvement participation?
With caution. Quotas can produce low-quality submissions where employees fill the quota without genuine engagement. They can also become limits -- if the quota is two improvements per year, employees with four ideas may only submit two, holding back the rest in case next year's quota is raised to four. The healthier alternative is to focus on leadership behaviors that engage people in improvement: asking, responding quickly, implementing what comes in, recognizing contributions. The variable that produces sustained participation is leadership effort, not quota pressure.
.svg)
Copyright © 2026
Privacy Policy