KaiNexus CEO and co-founder Greg Jacobson joins host Mark Graban for the seventeenth episode of the Ask Us Anything series, the recurring session built around questions from webinar attendees. The questions in this batch share a useful thread. A continuous improvement culture is a system, and like any system it tends toward entropy unless leaders actively keep energy in it. The conversation works through how to sustain and grow a CI culture over time, how quality fits with Lean and continuous improvement, how to get managers to adopt leader standard work without making it feel like an audit, and how to balance standard work against the freedom to experiment.
Here is what the episode covers and the thinking behind each answer.
An attendee named Lynn asked how to sustain and grow a developing continuous improvement culture and keep everyone active. Mark's quick answer was that Lynn had already named most of the work: leaders continuing to ask people to speak up, recognizing improvements when they happen, coaching, and treating engagement as an active practice rather than a one-time launch.
Greg made the bigger point. The thing that most surprises him about organizations doing this work is how little they account for entropy. CI programs are not perpetual-motion machines. You cannot expect that the energy you put in at the start carries the system forever. If anything, the energy needed to sustain the work goes up as the program matures, because the novelty has worn off and the discipline now has to do the work the enthusiasm used to do. Cutting the energy you invest after the launch backfires. People read it as a signal that leadership is not serious, and the trust you built starts to leak.
There is no script for what sustaining looks like in any given year. Mark connected it to PDSA. Treat sustainment itself as a hypothesis. Plan something to keep engagement going, do it, study whether it actually moved the needle, and adjust. What worked in January 2017 might not work in January 2018. A practice that landed in one department might fall flat in another. The way you avoid the steamroller version of a rollout is the same way you avoid the stale version of sustainment: iterate, learn, adjust, and never assume that the thousand-and-first time will look exactly like the prior thousand.
The second half of Lynn's question asked what technology can do to support this. Greg's reframe was useful. Unless an organization is doing literal oral tradition, every CI program is already using some form of technology. Paper is technology. Email is technology. Word documents and spreadsheets are technology. The real question is whether the technology in use has been optimized for the problem you are trying to solve. A sheet of paper works fine for one person filling out an A3. It works badly when you need that A3 to be collaborative, visible across the organization, searchable later, and connected to the data that says whether the change worked. Jake Husband, the VP of Customer Experience at KaiNexus at the time, framed it as looking-up sunglasses with "collaboration" on one lens and "reporting" on the other. Where those two functions matter, a platform built for the work outperforms paper and shared drives.
An attendee named Elsa asked how continuous improvement, Lean, and quality relate to each other. Mark opened by naming his own discomfort with how the conversation usually goes. He has heard people say, almost literally, "we've been implementing Lean for five years and now we're going to start with continuous improvement." His reaction is the same every time: continuous improvement is one of the two pillars of the Toyota Way, paired with respect for people. It is not a separate program you add later. A Lean program that does not engage everyone in some form of continuous improvement is missing one of its load-bearing walls.
On quality, Mark went to the Toyota Production System framework. The two pillars there are just-in-time, which focuses on flow, and jidoka, which is built-in quality. Quality is not adjacent to Lean. It is structural. The mistake people make is treating Lean as efficiency or speed and forgetting that quality sits at the center. He flagged a common organizational pattern: a quality department in one silo, a Lean department in another, both with overlapping mandates and limited coordination. The organizations doing this well are breaking down those silos and treating quality, Lean, and continuous improvement as one unified front.
Greg's metaphor was basketball. Asking how continuous improvement, Lean, and quality differ is a little like asking how passing, dribbling, and dunking differ. They are different aspects of the same body of knowledge, with different emphases. Continuous improvement carries the spirit of improvement as a daily, never-finished practice. Lean is the broader management system. Quality, in many organizations, ends up being the data layer, hopefully measuring something that matches what the customer needs. He named the trap that follows: if your improvement work is not improving the data, you are either measuring the wrong thing or not actually improving. They should reconcile, and when they do not, that is a signal to look at both halves.
Mark closed the segment with the why underneath all of it. The purpose of Lean and continuous improvement is competitiveness for the organization over time. Quality is not just something to track. It is a goal that contributes to that competitiveness, and the cleanest definition is meeting the customer's needs. That definition has the customer's voice built into it, which is where the harder questions about what the customer actually needs come into the work.
An attendee asked how to motivate and encourage managers to adopt leader standard work, and whether the hosts had a process to follow. Mark led with a reframe. Leader standard work is itself a countermeasure, a solution to a problem. So the right opening conversation is not "how do we get leaders to adopt this." It is "what are you trying to accomplish, and how can this set of practices help you get there?" Asked that way, leader standard work taps into intrinsic motivation. Pitched as a mandate with audits attached, it does the opposite.
Greg agreed and added the Daniel Pink frame. The point of "Drive" is not that extrinsic motivation is useless. It is that extrinsic motivation is often deployed in situations where intrinsic motivation would produce better performance, a healthier culture, and better relationships. Leader standard work is one of those situations. He used the webinar itself as a small example. He had walked off a meeting that ran late and felt no stress about the next thirty minutes, because he had a prepared checklist for the conversation. That is standard work in a personal form. The more decisions you can take off the table through standards and checklists, the less stress you carry, and the more cognitive room you have for the decisions that still require thinking.
Mark connected it to how the practice actually develops in a leader. Early on, the document the leader carries is more like a guide, a reminder of the questions to ask. Some organizations call these status sheets. It is not meant to turn a leader into a robot, any more than a surgical checklist is meant to turn a surgeon into one. Over time, the leader develops the routine and clings less tightly to the sheet. The framework stays useful even when it stops being a script, the same way medical practitioners still work through the chief complaint, the history of present illness, the review of systems, and so on, not because they do not know how to be a doctor but because the framework surfaces what an unstructured conversation would miss.
Greg added the key summary from Pink's book that Mark put neatly: extrinsic motivations work, the problem is the side effects. Intrinsic motivation is less likely to produce the dysfunction that comes when people are reacting to incentives rather than to the work. He tied that to Simon Sinek's "Leaders Eat Last" and its argument about the biology of trust. Cortisol-heavy environments produce stress and short-term thinking. Serotonin- and oxytocin-rich environments produce engagement and durable performance. And it is not soft. Organizations that operate this way perform measurably better than those that do not.
An attendee named Matt asked how to balance the value of standard work with encouraging people to think outside the box and continuously improve. Mark went to the leader's role. If a leader is at the gemba checking standard work and they see a deviation, that moment is delicate. What looks like a violation might actually be a small Kaizen experiment in progress. A leader who walks in like a bull in a china shop, telling people they are out of compliance, will trample improvement attempts they did not even know were happening. The better default is to lead with curiosity. "I notice this looks different from the standard process. Can you help me understand what's going on?" In a healthy environment with some trust, the answer is often, "We are testing a new method today," and the response can be encouragement instead of correction.
Greg invoked the line often attributed to Taiichi Ohno, and quoted in Imai's writing: without standards, there can be no Kaizen. The point is structural. Improvement requires a stable baseline to improve against. Without a defined way the process is currently done, there is nothing to improve, only randomness. But the existence of standards does not mean checking your brain at the door. The standard is what you improve from, and the question to keep asking the people doing the work is what would make it easier, what would make it safer, what would frustrate them less. Start there and the rest follows.
Ask Us Anything is a recurring series of short sessions answering questions from KaiNexus webinar attendees. It is hosted by Mark Graban, VP of Improvement and Innovation Services at KaiNexus, with Greg Jacobson, the company's CEO and co-founder.
See every episode in the series on the Ask Us Anything main page. Earlier episodes are also available on the KaiNexus YouTube channel and in the KaiNexus podcast archive.
See KaiNexus in action and see how KaiNexus helps organizations capture ideas, coach improvement, and connect daily work to strategy.
.svg)
Copyright © 2026
Privacy Policy