Watch the recording of the webinar:
View and download the slides:
Listen to the recording via our podcast:
Most CI programs launch with good intentions and reasonable tools. They generate early momentum. Then six months later the dashboards are underused, the huddles are slipping, and the CI coach is the only one still actively pushing. What happened?
The tools didn't change. The routines were never habitualized.
This is the second session in KaiNexus's series on applying habit science to continuous improvement. Greg Jacobson, KaiNexus co-founder and CEO, and Morgan Wright, who at the time of this recording served as KaiNexus's Customer Marketing Manager, have spent a year studying the behavioral science literature and translating it into practical guidance for CI leaders. The first session introduced the foundational concepts. This session goes deeper: three laws of behavior change, the difference between cues and rewards that work versus those that don't, and a set of concrete examples from organizations that have used these principles to build genuine CI cultures.
The session assumes you've encountered the habit loop framework -- cue, routine, reward -- and the concept of four CI personas (executive, CI coach, leader, frontline user). If those are new, the recap at the start of the session covers the essentials. What follows here is the substance of what's new in this session.
Greg's framing at the start sets the context. CI coaches are experts at the routines: A3 thinking, process walks, idea boards, strategy deployment, huddles. The routines are documented, taught, and generally well-understood by CI professionals. What's less well-understood -- and what has been missing from most CI methodology for roughly the first 15 years Greg was working in this space -- is the role of cues and rewards.
A routine without a cue won't trigger reliably. A routine without a reward won't stick. Most CI programs focus intensively on the routine and design the cue and reward almost by accident, if at all. That's why programs plateau. The knowledge of what to do is present. The behavioral infrastructure that makes doing it automatic isn't.
This session is specifically about building that infrastructure.
Morgan and Greg use a modified version of James Clear's four laws from Atomic Habits, condensed into three that map directly to the habit loop.
Make it obvious and attractive (cue design). The cue needs to be visible, tied to something that already happens reliably, and associated with a context the person finds positive. An invisible cue doesn't trigger. A cue the person resents becomes a reason to avoid the routine rather than begin it.
Make it easy (routine design). The routine has to be small enough that there's no meaningful barrier to starting it. Greg's rule of thumb: when introducing a CI behavior, strip the submission process down to its minimum. Adding even one optional extra field to an idea submission form decreases participation. The brain calculates friction before it evaluates value. If the friction is higher than the motivation in that moment, the routine doesn't happen. Start with the smallest possible version of the behavior. Build on it once the habit is established.
Make it satisfying (reward design). What is rewarded is repeated. What is punished is avoided. This is not about financial incentives. It's about immediate feedback that signals the routine was worthwhile -- feedback that activates the brain's dopamine system close enough in time to the routine that the connection is made. Delayed incentives (a bonus at the end of the year) don't create habits the way immediate recognition does.
The most reliable way to design a new cue is to attach the new behavior to an existing behavior the person already does consistently. James Clear calls this habit stacking: "After I do [current habit], I will do [new habit]."
The formula matters because existing habits are already wired into the brain. Linking the new behavior to the existing one essentially borrows the neural infrastructure that's already in place. Instead of creating a new trigger from scratch, you're piggybacking on one that's already reliable.
The CI application: when you're trying to help a leader build a huddle habit, don't introduce it as a standalone new behavior. Find what they already do every morning and attach the huddle to that. The five minutes before the shift starts, the doors open, the line comes up. Before the daily email check. After the first coffee. The stacking point matters less than the consistency of whatever comes before.
For frontline employees learning to submit ideas: attach the behavior to a moment that already punctuates their day. The end of a shift. The beginning of a break. A specific time that already carries meaning.
One of the most underused behavior design strategies in organizational settings is environmental design -- arranging the physical or digital environment so the right behavior is the most obvious, most convenient, most visible option.
Greg frames this as "decision architecture": designing the environment so that the right decision is the easy decision. His personal example: workout clothes laid out at the foot of the bed. Not because it takes much effort to find them elsewhere, but because having them there removes the tiny friction that lets the brain decide to skip it. The shoes are already there. The decision is already halfway made.
The organizational translation: where do frontline employees encounter their work system? If the icon to submit an idea isn't visible at their workstation, that's a design choice that's working against the habit. If the huddle board is somewhere inconvenient to reach during the natural flow of the day, that's a design choice that's working against the habit.
For digital environments: screensavers on shared computer stations, prominent notification settings, strategically placed icons -- these are low-cost environmental cues that several KaiNexus customers have credited as significant contributors to adoption. One customer's improvement communication lead described the screensaver real estate as something team members "fought for" because it had become an effective channel for keeping CI visible.
People adopt habits that are praised and approved by the groups they belong to. This is not a weakness -- it's a feature of how humans learn what behavior is appropriate in a given context. Three social groups shape habit adoption: the close (immediate team members), the many (the broader organization), and the powerful (leaders, executives, informal influencers).
The practical implication for CI leaders is that these social cues often matter more than formal training. If everyone on a team is actively submitting ideas, a new team member is likely to submit ideas. If nobody is, they won't -- regardless of the training they received during onboarding.
The "Betty" example from the session is memorable and useful. Betty has been at the organization for 37 years. If Betty doesn't think something is worth doing, it probably won't spread in her part of the organization. Betty isn't formally powerful by title, but she's an influential member of the social group. Rather than targeting 100% of the population with the same behavior change strategy, CI coaches who spend disproportionate time understanding and engaging the Bettys in their organizations often see much larger returns.
One other point about social dynamics: new hires are especially susceptible to cultural norms. If they arrive in an organization where improvement work is visibly part of daily practice -- where people are submitting ideas, where leaders are asking about improvement projects, where improvement is woven into normal conversations -- the onboarding and training investment required to get them participating drops substantially.
The two-minute rule. When starting a new habit, make the entry point take less than two minutes. Not because you'll always do only two minutes -- but because mastering the habit of showing up is the actual goal. Once showing up is habitual, building intensity or depth on top of it is straightforward. The goal is not to run a marathon. It's to become the kind of person who runs. Two minutes of running is more than zero, and it's the foundation.
The CI version: don't design idea submission for completeness. Design it for frictionlessness. The two-minute version of submitting an idea is a title and a brief description. That's it. Once the habit of submitting is established, prompting for more context becomes possible. But starting with a lengthy form is starting with the hard version, which is the version most people won't do.
Automate what can be automated. The more a behavior can be made automatic -- through scheduled notifications, calendar reminders, workflow routing that doesn't require human memory -- the less it depends on willpower and motivation, both of which fluctuate. One of the primary reasons KaiNexus exists, Greg points out, is to remove the need to remember: remember to follow up on this idea, remember to close out this project, remember to check in on this improvement's results. The platform doesn't replace the thinking work of improvement. But it can handle a significant portion of the coordination and reminding work that, without automation, relies on individual discipline.
Greg makes a point worth lifting: dopamine has a bad reputation because of its association with addiction and social media loops. But dopamine is also the primary neurotransmitter for learning and motivation. Without it, the habit loop doesn't close. The question isn't whether to use it -- the question is how to activate it in the service of the behaviors you want to build.
What doesn't create habits: delayed financial incentives. By the time the reward arrives, the brain has already moved on to other things. The connection between the routine and the reward is too attenuated to reinforce the behavior.
What does create habits: immediate, specific, social recognition. Specific examples from the session and from KaiNexus customers.
Badges. Platform-native badges for desired behaviors -- submitting a first idea, maintaining a streak of logins, completing an improvement project -- provide immediate, visible feedback that the behavior happened and was noticed. Gamification gets dismissed as superficial, but the mechanism works because it activates the same neurological system that drives learning. Duolingo streaks are a frequently cited example from the session. The streak doesn't mean anything financially. The brain doesn't care. It treats the streak as a reward.
Idea of the month / shout-outs. Individual recognition for a specific improvement idea, shared at scale through newsletters, intranet posts, all-hands calls, or posters, serves two functions simultaneously. It rewards the person who submitted the idea (their contribution is visible and valued). And it functions as a cue for everyone who sees it -- their peer was recognized, which suggests that submitting ideas leads to recognition, which increases the probability that they'll submit.
Leader acknowledgment in the system. When a leader or executive comments on, likes, or acknowledges a specific improvement item in the platform, two things happen. The frontline employee whose item was touched gets an immediate reward (a leader cared enough to engage with their work). And other employees see the executive engaging, which signals that improvement work is genuinely important -- not just officially endorsed but actually attended to by the people with power.
Gemba visits from executives. When a CEO attends a small team's improvement huddle, the reward for that team is not the CEO's physical presence per se. It's the evidence that the organization's most senior person has prioritized learning from the people doing the work. Greg cites Dr. Eric Dickson, CEO of UMass Memorial with 18,000 employees, who attends several improvement huddles every week. The signal that sends is unmistakable and non-delegatable.
In-the-moment leader praise. Timing matters. A "great idea" in the huddle right after someone shares their improvement observation hits differently than the same words in an email two weeks later. The reward needs to directly follow the routine for the brain to connect them. CI coaches who want to build participation habits should design for immediate positive response as part of the structure of every meeting, every review, every gemba walk.
One of the most useful habit concepts for organizational CI practice is also the simplest: what you're optimizing for is consistency, not performance. Missing a habit once is fine. Making a pattern of missing it is the problem.
Morgan's framing: consistency does not require perfection. Missing a walk one day doesn't undo a week of walks. What it does require is getting back on the next day rather than letting the miss become the new normal. "Never miss twice" is the practical rule.
The organizational translation: when a huddle doesn't happen because of a genuine disruption, the goal is not to pretend it didn't happen or to feel that the CI culture took a blow. The goal is to run the next huddle as scheduled. The identity of "we're the kind of team that huddles every day" can absorb an occasional miss. It can't survive a pattern.
The identity shift Greg mentions is the deeper mechanism: from "we're trying to get better at huddles" (a goal) to "we're the kind of team that huddles" (an identity). Goals have endpoints and failures. Identity persists through misses. An organization that has internalized "this is just how we work" doesn't need to re-motivate itself every time a disruption occurs. It just resumes.
The routines don't operate in isolation. One persona's routine becomes another's cue or reward. This is the organizational dynamic that separates a collection of individual habits from a genuine CI culture.
When an executive routinely acknowledges improvement work (their routine), it cues leaders to engage (they see engagement from above and understand the priority) and rewards frontline employees (their work reached the executive level). When leaders run consistent huddles (their routine), it cues frontline employees to update their improvement items before the meeting and rewards them through the recognition that comes from sharing progress. When frontline employees actively submit ideas, CI coaches can report results to executives, which rewards the executive's engagement and reinforces the cycle.
Designing these interconnections deliberately -- thinking not just about what each persona should be doing but about how each persona's behavior creates the cues and rewards for the other personas -- is what makes CI culture self-sustaining rather than dependent on perpetual heroic effort from the CI team.
The platform is, in Greg's words, an attempt to automate the parts of CI that can be automated -- not the thinking, not the creativity, not the problem-solving, but the coordination, the notification, the visibility, and the reward cycle.
Cues are built into the platform: scheduled notifications, workflow reminders, prompts when items are overdue or need attention.
Rewards are built into the platform: badges, acknowledgments, comments visible to the whole organization, metrics that show ideas moving from submission to implementation.
Visibility across the organization -- the ability for executives, leaders, and CI coaches to see improvement activity across all teams -- creates the conditions for the executive engagement and the leader recognition that the habit loops depend on.
If your CI program has all the right routines and isn't getting traction, the question to ask is whether the cues and rewards have been designed as deliberately as the routines. That's where most programs have a gap. That's what this session is built to help close.
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 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 are the three laws of behavior change and how do they apply to CI?
Make it obvious and attractive (cue design), make it easy (routine design), and make it satisfying (reward design). For CI, this means: design cues that are visible and attached to existing behaviors, strip routines down to their minimum viable version when introducing them, and build immediate recognition and feedback into every improvement behavior you want to sustain. Most CI programs focus heavily on the routine (the improvement methodology) and pay little attention to cue and reward design, which is part of why they plateau.
What is habit stacking and how is it used in CI?
Habit stacking links a new behavior to an existing behavior the person already does consistently: "After I do [current habit], I will do [new habit]." The new habit borrows the neural infrastructure of the existing one. For CI leaders trying to build a huddle habit, the practical move is to find what team members already do at a consistent time and attach the huddle to that moment, rather than introducing it as a standalone new commitment.
Why do delayed financial incentives not create habits?
Because the brain can't reliably connect the routine to the reward if they're separated by weeks or months. The dopamine system that reinforces habits is activated by immediate feedback. A quarterly bonus for submitting improvement ideas won't create the same neurological reinforcement as a specific comment from a leader in the moment after the idea is shared. Design for immediate, specific, social recognition rather than delayed financial rewards.
What is "decision architecture" in the context of habit design?
Decision architecture is arranging the physical or digital environment so that the right behavior is the most obvious, most convenient, most visible option. Greg's personal example: workout clothes at the foot of the bed remove the small friction that allows the brain to skip exercising. The CI version: visible platform icons, well-placed huddle boards, screensavers on shared workstations showing improvement activity, notification settings configured to prompt engagement. The goal is to make the right choice the easy choice without requiring willpower.
What does "never miss twice" mean for CI culture?
It means optimizing for consistency rather than perfection. Missing a habit once -- a huddle that gets skipped, a week with no idea submissions -- is not a failure. Missing twice becomes a pattern. The practical rule is to return to the habit as soon as possible after any disruption, rather than waiting for conditions to be ideal or letting the miss compound. Organizations that have internalized "this is how we work" can absorb occasional disruptions. Those still treating improvement as something external to daily work cannot.
How do persona habit loops interconnect?
One persona's routine creates another's cue or reward. An executive who acknowledges an improvement item (their routine) signals to leaders that the work matters (a cue for leader engagement) and rewards the frontline employee whose work was noticed. A leader who runs consistent huddles (their routine) cues frontline employees to prepare and rewards them through recognition. Designing these interconnections deliberately -- not just individual habits but the relationships between them -- is what makes a CI culture self-sustaining.
.svg)
Copyright © 2026
Privacy Policy