Watch the recording of the webinar:
View and download the slides:
Listen to the recording via our podcast:
Mark Twain said it before Toyota existed: "Continuous improvement is better than delayed perfection." Humans have been thinking about improvement as a practice, not just an event, for a long time. But most organizations still treat improvement as a project -- something launched, run for a while, and then quietly allowed to wind down when the next priority arrives.
Greg Jacobson has been thinking about continuous improvement for roughly 20 years. He's the co-founder and CEO of KaiNexus and an emergency medicine physician. Around 2015 or 2016, someone introduced him to The Power of Habit by Charles Duhigg. He found lean CI woven throughout the book. And he realized, for the first time, that you could design habits. Not just practice them, but engineer the conditions under which they reliably occur.
This session -- the first in a three-part series -- is Greg and Morgan Wright's attempt to translate that realization into something CI leaders can actually use. It covers the neuroscience of habit formation, the behavioral science of why habits stick or fade, and the framework -- cue, routine, reward -- that connects individual behavior to organizational culture.
The series draws on three books: Charles Duhigg's The Power of Habit, James Clear's Atomic Habits, and BJ Fogg's Tiny Habits. Greg has read the first two multiple times. All three are recommended directly in the session.
What follows is the substance of the session, organized so the page is useful whether you watched it or are landing here from search.
Seth Godin's definition of culture: people like us do things like this. Greg uses it throughout the series because it points at exactly the right thing. Culture isn't a poster or a set of principles or an annual kickoff meeting. Culture is what people in a group actually do repeatedly -- the norms, the defaults, the behaviors so embedded that nobody thinks about them consciously. And another word for behavior that happens regularly without deliberate thought is a habit.
The argument that follows from this: building a CI culture is fundamentally a habit design problem. Not a training problem, not a tool selection problem, not a communication problem -- a habit design problem. The organizational behavior you want to see is improvement work happening naturally, repeatedly, at every level, without requiring heroic effort from a CI team to sustain it. That's what habits produce. Everything else produces activity that requires constant re-energizing.
Greg uses two areas of the brain to explain why habits behave differently from other kinds of knowledge or memory.
The hippocampus is the area most associated with forming new memories. When the hippocampus is damaged -- by infection, injury, or disease -- people lose the ability to make new memories in the conventional sense. Greg describes a case from The Power of Habit: a man who contracted viral encephalitis that destroyed his hippocampus. His wife provided constant care. Daily life consisted of sitting in the same chair, watching TV, and walking the same route around the neighborhood. After two to three months, he began making the walk on his own without being prompted -- and without being able to remember doing it.
If memory formation requires the hippocampus and his was destroyed, how did the walking habit form?
The answer is the basal ganglia -- a different brain region thought to be where habits are formed, stored, and executed. The basal ganglia operates largely below conscious awareness. It's deep in the brain, closer to the core systems that regulate breathing and basic drives. Habits wired into the basal ganglia don't require deliberate decision-making to execute. They're triggered by a cue and run automatically.
The practical implication for CI: when a behavior has truly become a habit, it runs without requiring motivation or willpower in the moment. It's just what people do in that situation. The goal of CI culture-building is to move improvement behaviors from the "requires deliberate effort" category into the "this is just what we do" category -- from the hippocampus into the basal ganglia, metaphorically speaking.
BJ Fogg's behavior model frames the conditions for any behavior to occur. On one axis: motivation (how much does the person want to do this?). On the other axis: ability (how easy is it to do?). When motivation is high and ability is high, behaviors happen reliably. When motivation is low and ability is low, they don't.
Greg's personal example: his 11-year-old daughter Micah and the challenge of getting her to feed the dogs in the evening. She had the ability -- the dog food was right there, not requiring anything complicated. She had the motivation -- she genuinely loved her dogs. By the model, she should have been feeding them reliably. She wasn't.
The missing piece isn't covered by motivation and ability alone. It's a cue. A trigger that reminds Micah at the right moment that there's a routine to execute. Without the cue, even highly motivated, highly capable people forget to do things. The behavior never starts. The loop never runs.
This is the most common gap in CI programs. The routines are well-designed and the people are reasonably motivated. But there's no reliable cue architecture -- no system of triggers that remind people to do improvement work at the right moment, in the right context. The behavior dies not from resistance but from forgetting.
The three-part loop is the core operational model for habit formation.
Cue. Something in the environment that triggers the behavior. The most reliable cues are tied to time, location, or existing behaviors (habit stacking). For Micah, the cue the family designed was her own dinner: every evening, when she felt hungry and knew it was dinner time, she saw the dogs and remembered that they also needed to eat. The cue was already wired into her daily experience.
Routine. The behavior itself. For the habit loop to work, the routine needs to be something the person has the ability to do and finds worthwhile. If the routine is too complex, too unfamiliar, or too time-consuming at the outset, people will have the cue and then not execute.
Reward. The feedback signal that reinforces the loop. This is where most organizational habit design fails. The reward needs to be immediate, satisfying, and consistent -- and it works by activating the dopaminergic system, the brain's primary mechanism for learning and motivation.
Greg spends time on dopamine specifically because it has a reputation problem. Most conversations about dopamine are about addiction and social media loops -- the ways the dopamine system can be hijacked by things that feel rewarding but aren't good for us. But without dopamine, Greg notes, humans might not get out of bed, seek food, or do much of anything. It's the neurotransmitter that signals "this was worth doing -- do it again." Designing CI habits means learning to activate that system in service of improvement behaviors.
For Micah, the reward wasn't the allowance (too delayed, never consistently delivered) and it wasn't a punishment for not feeding the dogs (tried that, didn't work). What actually worked was immediate, specific, verbal recognition from her parents: "I'm so proud of you for feeding the dogs." Every time. Immediately. Consistently. That signal activated the reward pathway and reinforced the loop.
The CI translation is direct: when a team member submits an idea or flags a problem, the immediate response from their leader or CI coach -- "thank you for pointing that out," "this is exactly the kind of observation we need" -- is not just good manners. It's the reward signal that makes the behavior more likely to happen again. Organizations that skip this step and rely on the value of improvement to be self-evidently rewarding are missing the mechanism that makes habits form.
A distinction Morgan and Greg draw out carefully, worth preserving.
An incentive is a future-oriented promise: if you do X, you'll receive Y later. An incentive can get something started. It doesn't create a habit. The brain doesn't reliably connect a behavior to its consequence when the consequence is weeks or months away.
A reward in the habit science sense is immediate feedback. The badge that appears when you complete an action. The comment from a leader within moments of a submission. The sense of satisfaction from seeing an idea move from submitted to implemented. These rewards don't work because of their monetary value -- they work because they arrive close enough to the behavior in time for the brain to register the connection and reinforce it.
This is why financial recognition programs with quarterly payouts tend not to build habits even when they're generous. The loop doesn't close fast enough. Immediate, specific, social recognition -- even low-cost or zero-cost -- is neurologically more powerful for habit formation than delayed financial incentives.
Beyond the loop itself, the session identifies four concepts that matter for building durable habits.
Systems over goals. Borrowing from James Clear: forget about goals, focus on systems instead. Goals tell you where you want to go. Systems are what you do daily to get there. A goal of "increasing idea submission rates" gives you a target. A system of "every Monday morning, the team spends five minutes reviewing what problems came up last week" gives you the repeatable behavior that will actually move the metric. Goals help set direction. Systems create the conditions for goals to be achieved.
Identity over motivation. The most durable habits are rooted in identity -- in the answer to the question "what kind of person (or organization) am I?" The smoker who says "I'm trying to quit" relies on willpower every time the urge comes. The smoker who says "I'm not a smoker" has already made all the micro-decisions. For CI organizations, the shift is from "we're trying to do improvement work consistently" to "we're the kind of organization that does improvement work." Every micro-decision -- do we run the huddle today when things are hectic? do we document this near-miss? do we close the loop on that idea? -- becomes much easier when the answer is already embedded in the identity.
One percent better. Small improvements compound dramatically over time. The value of 1% improvement is imperceptible in any given day. It's massive over a year. For CI leaders, this principle cuts through the frustration of slow progress by reorienting the frame: the question isn't whether today was dramatically different but whether the system is pointing in the right direction. It also makes the habits themselves feel achievable. "Can you be 1% better today?" is a different ask than "can you transform how this department operates?"
Personas over individuals. You can't design individual habit loops for thousands of employees. But you can design four: one for executives, one for CI coaches, one for leaders, and one for frontline employees. Each persona has distinct responsibilities, distinct relationships to improvement work, and distinct cues and rewards that work for them. Designing at the persona level is tractable and, with the interconnections between personas, produces system-level effects that individual habit design never could. This concept is introduced here and developed in depth in Parts 2 and 3 of the series.
A question from the live session worth addressing directly, because it reflects what most CI leaders hear from the people they're trying to engage.
"In today's world of crisis management, CI is left to when we have time, which never comes."
Greg's response: the "no time" framing is real but it's also a frame that makes improvement impossible. There will always be fires. There will always be more urgent-feeling demands than there are hours. The question is whether improvement behaviors are designed to survive that reality or not.
Habits that have been genuinely established survive disruptions better than behaviors that still require deliberate motivation. Once the huddle is truly a habit, a busy week doesn't make the team wonder whether to hold it -- they hold it because that's what they do, and the exception requires more effort than the norm. Until the huddle is a habit, every week is a fresh negotiation about whether this is the right time.
The path from "we don't have time" to "this is just what we do" runs through deliberate habit design: small routines with reliable cues and consistent rewards, built up over time, connected to an identity the organization has chosen. It's not fast. But it's the only path that doesn't require constantly re-justifying improvement work against the pressing demands of the moment.
The platform isn't a habit on its own. It's infrastructure that makes building CI habits significantly more tractable.
Notifications function as cues -- scheduled, reliable, tied to the right moment for the right person to engage with the right work.
Recognition features -- comments, likes, acknowledgments from leaders -- function as rewards that close the habit loop and signal that improvement participation was worthwhile.
The visibility of improvement work across the organization makes it possible for leaders and executives to engage with the work of frontline teams, which is one of the most powerful cues and rewards in the interconnected persona loop.
And the reduction of friction in submitting ideas, progressing improvements, and documenting outcomes makes the routine small enough that the ability-motivation threshold is consistently met -- which is the precondition for the whole loop to run.
If your organization has tried to build CI habits through training and exhortation and hasn't seen them stick, the gap is almost certainly in the cue and reward design. That's what this series is built to help you address.
Morgan Wright was the Customer Marketing Manager at KaiNexus at the time of this recording. In that role, she partnered with customers to develop and execute communication strategies to engage their organizations in KaiNexus. She is a graduate of Baylor University with a degree in Marketing.
Greg Jacobson, MD is the co-founder and CEO of KaiNexus. He completed a residency in Emergency Medicine at Vanderbilt University Medical Center, where his observations of operational inefficiencies and unrealized continuous improvement opportunities led to the founding of KaiNexus. He is co-author of "Kaizen: A Method of Process Improvement in the Emergency Department," published in Academic Emergency Medicine.
What is habit science and why does it matter for continuous improvement?
Habit science is the study of how behaviors become automatic and self-sustaining. It matters for CI because the goal of any CI culture is improvement work that happens consistently without requiring constant re-motivation. About 50% of daily human behavior is habitual -- executed automatically without deliberate decision-making. Designing CI behaviors to become habits rather than relying on conscious effort and willpower is what separates organizations that sustain improvement from those that plateau.
What is the habit loop?
The habit loop has three components: a cue (a trigger that starts the behavior), a routine (the behavior itself), and a reward (immediate feedback that signals the behavior was worthwhile and reinforces it for next time). All three are necessary. A routine without a cue won't trigger reliably. A routine without a reward won't stick. Most CI programs focus on the routine and neglect cue and reward design.
What's the difference between an incentive and a reward in habit science?
An incentive is a future-oriented promise -- do this, get that, later. A reward in the habit science sense is immediate feedback that activates the brain's dopamine system close enough to the behavior that the connection registers. A badge that appears when you complete an action, a comment from a leader within minutes of a submission, the visible movement of an idea through the system -- these hit the reward pathway in a way that quarterly bonuses don't, regardless of dollar amounts.
Why is identity more powerful than motivation for building habits?
Motivation fluctuates. Identity doesn't. A person relying on motivation to keep running wakes up on a cold morning and negotiates. A person who identifies as "a runner" puts on the shoes. For CI organizations, the shift from "we're trying to improve engagement" to "we're the kind of organization that continuously improves" means that every micro-decision -- do we hold the huddle today, do we document this near-miss, do we follow up on that idea -- is already answered by the identity rather than requiring fresh motivation.
What is BJ Fogg's behavior model and how does it apply to CI?
Fogg's model shows that behavior happens at the intersection of motivation and ability. High motivation and high ability produce behavior reliably; low motivation and low ability make it unlikely. The model predicts that even highly motivated, capable people will fail to develop a habit if there's no reliable cue. For CI leaders, this reframes adoption challenges: when people aren't doing improvement work, the question isn't usually "why aren't they motivated?" It's "where is the cue that should trigger this behavior?"
What are the four personas and why are they important for habit design?
The four personas -- executive, CI coach, leader, and frontline employee -- represent the distinct roles people play in a CI organization. Each has different motivations, different relationships to improvement work, and different cues and rewards that work for them. Designing four persona-specific habit loops is tractable. Designing individual loops for thousands of people isn't. When all four persona loops are working and interconnecting -- each person's behavior creating cues and rewards for the adjacent personas -- the CI culture becomes self-reinforcing.
.svg)
Copyright © 2026
Privacy Policy