Most CI coaches have experienced this frustration: you train a team on A3 thinking, they do one or two, and then... nothing. You launch a huddle cadence, it runs strong for a month, and quietly dies. You roll out an idea system, get a burst of submissions, and watch engagement flatline.

The problem usually isn't the methodology. It's that nobody designed the behavior to stick.

That's the premise behind a three-part webinar series from KaiNexus CEO Greg Jacobson and Customer Marketing Manager Morgan Wright. Over the course of three sessions, they made a compelling case that habit science -- the body of research behind how humans form, sustain, and break habits -- is essential knowledge for anyone trying to build a culture of continuous improvement.

Here's what they covered and how you can apply it.

Part 1: The Foundations of Habit Science and CI

The Biology Is Real

Greg opened the series with a story that sets the stakes. A man who lost his hippocampus to a viral infection -- meaning he could no longer form new conscious memories -- still managed to learn his daily walking route after his wife walked it with him for two to three months. He couldn't remember learning the route. But one day his wife found him gone, then found him sitting in his chair after completing the walk on his own.

The point: habits aren't stored where we keep our conscious memories. They're wired into a different brain structure, the basal ganglia, and they operate below conscious thought. About 50% of what we do every day, we do out of habit, without any deliberate decision-making. That's not a weakness -- it's a feature we can design for.

If you're a CI coach trying to get people to submit ideas, run huddles, do structured problem-solving, or review improvement metrics, you're trying to build habits. And habit science gives you a framework for doing that deliberately rather than hoping training and good intentions carry the load.

The Habit Loop: Three Parts, No Shortcuts

Drawing primarily from Charles Duhigg's "The Power of Habit," James Clear's "Atomic Habits," and BJ Fogg's "Tiny Habits," Jacobson and Wright distilled the core framework into three components:

Cue -- something that triggers the behavior. It could be a time of day, a location, an event that just happened, or a visual reminder. Without a cue, even motivated people with the ability to do something simply won't remember to do it.

Routine -- the behavior itself. The key insight here: make it easy, especially at first. If submitting an improvement idea requires filling out a 10-field form, you've killed the habit before it starts. If running a huddle requires 30 minutes of prep, leaders will skip it when things get busy. Two minutes is the starting target. Master showing up first, then build complexity.

Reward -- something that triggers dopamine and makes the brain want to repeat the loop. This is where most CI programs fall short. We train the routine and maybe set up a cue, but we skip the reward entirely -- and then wonder why the behavior doesn't stick.

One critical distinction from the series: rewards are not the same as incentives. A reward follows the routine closely enough that the brain connects the two. A badge earned immediately after submitting an idea is a reward. A $50 gift card distributed at the end of the quarter is an incentive. Incentives can help get things started, but they don't rewire behavior the way immediate, satisfying feedback does.

Before the Loop: Fog's Behavior Model

Before any habit loop can work, the person needs two things: the ability to do the behavior and sufficient motivation. BJ Fogg's behavior model maps these on two axes, with an "action line" separating behaviors that happen from those that don't.

The practical implication for CI coaches: if someone isn't doing the behavior you want, diagnose which side of the equation is failing. Is it an ability problem (the routine is too hard, the tool is clunky, they weren't trained properly)? Or is it a motivation problem (they don't see the point, they're afraid their ideas will be dismissed, they've been burned before)?

The important caveat: you can't rely on motivation alone. Everyone's motivation fluctuates day to day. The whole point of designing habits is to make the right behavior happen even on days when motivation is low. That's why making the routine easy and the cue obvious matter so much -- they reduce the motivation threshold needed to act.

Four Underlying Themes

The first webinar closed with four concepts that run through the entire series:

Systems over goals. Goals set direction. Systems -- repeatable daily actions -- are what actually get you there. "We want a culture of continuous improvement" is a goal. A designed huddle cadence with cues, routines, and rewards is a system.

Identity over action. There's a meaningful difference between "we're trying to huddle every morning" and "we're the kind of organization that huddles." The first is an action people can skip when motivation dips. The second is an identity that guides micro-decisions automatically. Greg shared his own example: after tearing his ACL, he told himself "I'm the kind of person who does all the rehab my physical therapist assigns." That identity carried him through the days when the exercises felt miserable.

One percent better. Small improvements compound. The gap between 1% better each day and 1% worse is invisible in the first week, dramatic after a year. For CI coaches who feel the weight of slow progress, this is a useful reframe: you don't need to transform culture next quarter. You need to make it slightly easier for the right behaviors to happen this week.

Personas, not individuals. You can't design a custom habit loop for every person in a 10,000-person organization. But you can group everyone into roughly four personas -- executives, CI coaches, leaders (middle managers), and frontline workers -- and design habit loops for each. That makes the work scalable.

Part 2: Designing Organizational Habits

The second session moved from concepts to application, introducing what Greg and Morgan called three laws of behavior change, adapted from Clear's framework and mapped directly to the habit loop.

Make It Obvious and Attractive (the Cue)

Three specific techniques stood out:

Habit stacking ties a new behavior to an existing one. "After I check my email, I log into KaiNexus." "After we clock in for the shift, we do a five-minute huddle." The existing habit serves as the cue for the new one, which works because the existing habit is already wired into the brain. Greg's advice to CI coaches: study the leader's existing daily routine and find the natural hook point for the new behavior.

Environment design puts cues where people will encounter them naturally. Physical signage near shared workstations. An app icon on the home screen. Workout clothes at the foot of the bed. If the right behavior requires searching for something, you've added friction. If it's right in front of someone, you've removed it. One of their more creative examples: customers who change screensavers on shared computers to display CI messages, creating a cue that's nearly impossible to avoid. The important note: these need to be refreshed. A sticker that's been on the wall for five years becomes invisible.

Culture and social influence. People imitate the habits of three groups: the close (their team), the many (the broader organization), and the powerful (leaders and influencers). If you're trying to get someone to adopt A3 thinking but nobody around them does it, you're fighting gravity. Greg's advice: find the informal influencers in a group -- not just the people with titles, but the people others follow -- and align them first. "If Betty's been here for 37 years and Betty doesn't like it, it's not going to happen. So spend time on Betty."

Make It Easy (the Routine)

Start absurdly small. The two-minute rule says a new habit should take less than two minutes at first. The goal isn't to do two minutes of improvement work forever -- it's to master the habit of showing up. Once showing up is automatic, you can build.

This has direct implications for how you design idea submission processes. Greg was blunt: every additional field you add to an idea submission form decreases the chance someone will use it. Start with a subject line and a description. That's it. After the habit of submitting ideas is established -- maybe a year or two in -- you can add categorization or other fields if the process genuinely needs them. Starting with a laborious form when participation is voluntary is a habit killer.

And wherever possible, automate. Notifications that route work to the right person. Calendar blocks that create cues automatically. Workflow reminders that eliminate the need to remember. The goal is to make the right behavior easier than the wrong one.

Make It Satisfying (the Reward)

What is rewarded is repeated. What is punished is avoided. Until a behavior becomes a genuine habit, the reward is doing critical work.

The most effective CI rewards they described aren't monetary. They're recognition -- and specifically, recognition that's immediate, satisfying, and consistent. A leader saying "great idea about the supply room -- tell me more" right after a huddle. A badge earned the moment an idea is submitted. An executive commenting on a specific improvement in the system. These hit the dopamine system in a way that a quarterly award ceremony can't, because the brain can connect the reward to the behavior.

They also introduced the concept of "never miss twice." Consistency doesn't require perfection. You'll miss a huddle, skip a day of checking notifications, or forget to review improvement metrics. That's fine. The goal is to not let one miss become a new pattern. Miss Monday, show up Tuesday. The people who sustain habits aren't the ones who never miss -- they're the ones who get back on track quickly.

Cues and Rewards That Work in Practice

Morgan shared specific examples drawn from successful KaiNexus customers, applicable whether you use KaiNexus or not:

Cues that work: signage in high-traffic areas (refreshed regularly); scheduled calendar blocks for processing notifications or reviewing improvements; recurring huddle meetings; regular CI mentions from executives in all-hands or team meetings; a CI slide on rotating digital displays or shared computer screensavers.

Rewards that work: badges and gamification for completing desired behaviors; individual recognition (improvement of the month, shout-outs in newsletters or on intranets); leaders and executives commenting on or acknowledging specific ideas in the system; executives going to gemba and attending huddles (which functions as both a reward for frontline workers and a cue for leaders); and in-the-moment praise directly following the desired routine.

Part 3: Sustaining the Habits

The third webinar tackled the hardest part: keeping it all going. Building a habit is one thing. Sustaining it across an organization with competing priorities, leadership turnover, and daily fires is another.

How Persona Habit Loops Interconnect

This was the conceptual breakthrough of the series. Individual habit loops don't operate in isolation. In an organization, each persona's routine becomes the cue and reward for other personas.

When an executive's routine includes spending 15 minutes a week engaging with improvements in the system -- commenting, liking, acknowledging -- that activity becomes a cue for leaders ("my boss is in here, I should be too") and a reward for frontline workers ("the CEO noticed my idea"). When a leader's routine includes running a weekly huddle, that huddle becomes a cue for frontline workers to keep their improvements moving and a source of recognition when their work gets highlighted.

Morgan mapped the full interconnection: the CI coach sets up the routines, cues, and rewards for all other personas. The executive's routine feeds cues and rewards to leaders. The leader's routine feeds cues and rewards to frontline workers. And frontline activity -- the volume and quality of ideas and improvements -- feeds the data that makes the executive's and leader's routines satisfying.

The analogy they used: your CI culture is like a car. The executive is the steering wheel (direction). Leaders are the engine (they do the hard work of improvement). The CI coach is the gas (energy and support). Frontline workers are the wheels (they're actually moving the organization forward). Remove any one, and the whole thing stalls.

This is why executive engagement isn't optional. Greg was direct: "We have not seen thriving CI cultures -- broad-based, impactful, lasting -- without executive participation." Not just sponsorship. Participation. He cited Dr. Eric Dickson at UMass Memorial Health, where the CEO of an 18,000-person organization goes to idea huddles once or twice a week. That level of visible commitment is both the most powerful cue and the most powerful reward in the system.

Sustaining Organizational Habits

The series closed with five principles for keeping habits alive over time:

Accountability partners. In personal habit science, having someone who knows whether you followed through changes behavior. The same applies organizationally. Greg shared an example of connecting a struggling site leader with a high-performing one as accountability partners -- not as a coaching relationship, but as mutual support. CI coaches can facilitate these connections rather than trying to be the sole source of accountability for every team.

Systems of reflection. Build regular check-ins -- quarterly, annually -- where you pull back and evaluate whether the designed habit loops are working. Are the cues still visible? Are the routines still easy enough? Are the rewards still landing? This is PDSA applied to your own management system, and it's easy to skip when you're focused on the content of improvements rather than the system that produces them.

Frequency over duration. Habits form from how often you do something, not how long you've been at it. Playing guitar for 10 minutes every day builds the habit faster than two hours once a week. Checking improvement metrics for five minutes daily builds the habit faster than a monthly deep-dive. This applies directly to huddle cadences, notification reviews, gemba walks, and every other CI routine. A short daily practice beats a long sporadic one.

Language matters. A small shift from "I have to run the huddle" to "I get to run the huddle" changes the emotional framing. More substantively, explaining the why behind a new behavior -- what's in it for the person being asked to change -- goes further than just issuing instructions. Morgan emphasized this from her communication work: when introducing any new CI behavior, lead with value to the individual, not just value to the organization.

Keystone habits. Drawing from the Alcoa safety story in Duhigg's book -- where Paul O'Neill's relentless focus on safety created communication infrastructure that ultimately transformed the company's financial performance -- Greg challenged the audience to identify their organization's keystone habit. What's the one behavior that, if established well, creates the scaffolding for everything else? It might be daily huddles. It might be idea submission. It might be incident reporting, as one KaiNexus healthcare customer discovered when their safety reporting habit organically expanded into a full improvement culture. The keystone habit is the one that, once ingrained, makes the next habits easier to build.

Putting It Into Practice

If you're a CI coach, a leader trying to sustain improvement, or an executive wondering why engagement with your CI program has plateaued, here's where to start:

Pick one persona and one habit loop. Don't try to design all four at once. Start with the group where you have the most influence and the highest likelihood of success. Design a specific cue, an easy routine, and an immediate reward.

Audit your current cues and rewards. Most organizations have designed the routine (the methodology, the process, the tool) without giving equal thought to what triggers the behavior and what makes it satisfying. If people aren't doing the thing, it's probably a cue or reward problem, not a training problem.

Get executives into a designed habit loop. Even 15 minutes a week of structured engagement -- reviewing improvements, commenting on ideas, attending a huddle -- creates outsized impact because it fuels the cue and reward systems for every other persona.

Start small, stay consistent, and don't miss twice.

Watch the Full Series

The three webinars go deeper into each of these topics with additional examples, audience Q&A, and practical discussion. You can watch them in order or jump to the session most relevant to your current challenge.

Recommended Reading

• Charles Duhigg, "The Power of Habit"
• James Clear, "Atomic Habits"
• BJ Fogg, "Tiny Habits"
• Daniel Pink, "Drive" (on intrinsic vs. extrinsic motivation)
• Simon Sinek, "Leaders Eat Last" (on the neuroscience of organizational trust)

Ready to build the infrastructure that makes improvement habits stick? See KaiNexus in action -->